Popular Content

Showing most liked content since 07/22/2017 in all areas

  1. 2 points
    As I just went through similar rule creation (automatically lock topics after certain amount of time), maybe I can provide some help. You will need two rules - one to hide in bulk all already old topics and one that will handle future hiding of all new topics. For the bulk rule: 1. Create custom action that has a topic as argument. 2. Create a rule that is triggered by the custom action and hides all topics that have not been updated after 20.08.2017 (for example). Select whatever conditions you prefer. 3. Run the custom action right now - it should go through all topics and hide those not updated in the last year. 4. You remove this rule or disable it, it is useful only for one time. For the ongoing rule, it seems that you got it covered, but for someone that might be looking for help with it: 1. You create one rule that has event "Topic is updated" and its action is the custom action you created earlier. The key here is to mark the rule to be executed at a future date, 1 year from the last update. 2. You create a second rule, triggered by the custom action that hides the topics based on the trigger of the first rule. Actually, there is an example rule of this type here: https://invisioncommunity.com/files/file/7373-rules-starter-example-rules-pack/
  2. 1 point
    You can create custom actions and then schedule them manually to run as a bulk processor for any given argument in your custom action. So, if you have a custom action with a topic argument, you can schedule it to run in bulk for every topic on your site. Its just then a matter of putting the correct rules on it to accomplish your task.
  3. 1 point
    Yeah, happens when I try too. Thing is, it happens for all apps in the suite. So it basically just a limitation of the friendly url modification system built into core.
  4. 1 point
    You go in to Rules->Custom Logs and create a new log, I will just give you a screenshot of the settings I use. Nothing fancy with the log settings, just make sure the log is associated with IPS\Member and just include some clear name and description. Then you need to add the fields that will be included in the log. For me thats member sending, member receiving and amount of points. To do that you need to click the + sign to the right on the created log and click "Add loggable argument". That's it, your log is ready. Now you need to go and create the rule that is going to write to this log. Go to Rules -> Create new rule. Choose event to be "A balance or transfer exchange has been completed" and in action set it to Custom logs -> Create new log entry: The dialog that is on the Next screen will allow you to fill all necessary log fields. I have it like this: That's it! Happy logging. By the way, I use the same rule to also send notifications to the members that are receiving the points, just adding another action. Otherwise they will never know. Points economy is a very flexible app, but you need to pair it with Rules Automation to unleash its full power.
  5. 1 point
    Yeah. I agree. But its like that because a collab is a content item under the hood and everything "in" the collab is just linked to it. The searching is simply an IPS core feature which is just searching the content in "this collab", which technically is only the collab description. Searching in all collabs, produces results for all collab descriptions. Searching in all apps produces results across the board.
  6. 1 point
    With Rules you can setup it to write each transaction in to a custom log.
  7. 1 point
    If you purchase rules full and the commerce rules expansion then you can do those things.
  8. 1 point
    Thats not a collab category that youre looking at. Thats a database category. You need to look in the pages app config of your collab category (in the ACP) and enable the specific database that you are trying to create database categories/records for in your collabs.