Kevin Carwile

It was the other way around. IPS removed it from their marketplace therefore there is not really any point of continuing development on it. I was not aware this was an issue. I remember we fixed a bug that sounds a lot like this. I'll see if I can reproduce this locally.

That's the reason why IPS removed rules from their marketplace. People get themselves into trouble and neither IPS nor myself can really do anything about it. That particular issue may be a bug "somewhere", but it is not in the IPS core, and I verified that it is not in the Rules application itself, so it is within the rules configuration on the client site. That is a configuration that nobody maintains except for the client themselves. Not sure exactly how to troubleshoot that for them without being able to reproduce it on my end. But packaging a new version of rules and calling it a maintenance release is not going to solve that issue for them.

No new features are planned for this app. Only critical bugfixes will be made to it at this point.

@Gabriel Torres Try uploading the following two patch files to your community. ./applications/advancedtagsprefixes/hooks/forumLastPostPrefix.php ./applications/advancedtagsprefixes/hooks/addPrefixToForm.php addPrefixToForm.php forumLastPostPrefix.php

Sorry, I didn't realize that I was not subscribed to this topic. I have just updated Group Collaboration for 4.4 compatibility. I'll look into Tags & Prefixes next.

Well, bulk processing topics is as close as rules core will get you. Anything further will require you to write custom php code in your processing rules.

For that, you will need to bulk process all topics on the site. Your custom action will accept an individual topic as an argument. Your rules for that custom action will have the conditions you just described. If topic is in Forum A, add two points. If topic is in Forum B, add 1 point.

I have not been able to test this as of yet.

You will need to bulk process the topic items, and in your custom action rule, you will likely need to use some custom php code in order to do whatever calculations you need based on the topic being processed.

This should already be possible using the permissions on the custom data field.

It sounds like you want to use an event for when the event is locked as you said instead of the member RSVP'ing for the event. But even so, in order to operate on all of the members that attended the event, you'll need a custom php code action to do whatever it is that you want to do.

Is this still the case? I can't verify with my account since I own the resource, and I don't have another account with a valid IPS license to be able to log into. So I cannot tell.

We are looking into this. Correct.

That sounds like it will work more reliably for you than the "logged in" event. It just requires that a member make a post.

No, you wont lose any rules. That would be an event that needs to be included by the awards app.

There are invoice actions available in the commerce rules expansion. You can check the invoice for your subscription product when it is paid and run your appropriate action then.

You could dig into the IPS\calendar\Event object class to see what kind of methods you could use to retrieve a usable date within your rules. I found this one with a quick look over: /** * Find the next occurrence of an event starting from a specified start point * * @param \IPS\calendar\Date $date Date to start from * @param string $type Type of date to check against (startDate or endDate) * @return \IPS\calendar\Date|NULL */ public function nextOccurrence( $date, $type='startDate' )

Looks like maybe the problem starts in the code above? As for the template issue, I'll have to look into that.

Nope. Sorry. It will require a new version build to be released (unknown timeframe). Well then I would question the event which you are creating the rule under. The event is going to determine what data is available. If it is the content approved event provided by rules, then the content item should be an event argument and the content author can be derived from that. If it is another event provided by the application plugin, then without the actual application as one of the event arguments, there is no way to know who the author of the application is if the rule doesn't even have access the application which has been approved.

@christopher-w Try the following patch file and see if you get the expected results. ./applications/rules/extensions/rules/Definitions/Content.php Content.php

@Fighting 13th You may have a wrong setting selecting in your rule configuration. It's hard to say. But maybe you selected the wrong option for the user to grant the award to. It should be the application author and not the currently logged in user. @christopher-w Are you using the 'set tags explicitly' option on the rule action or are you using 'add tags'?

What is an application submission and how does it get approved?

If there is a rule in particular that you are wanting to troubleshoot, edit the rule and turn the debug option on for it. Then you can perform the action again which you expect the rule to apply to and check the debug log to see if it contains an error or if it did not meet its conditions or if it even ran at all. That would be what I would start with.

If your session timeout is 30 days, and you want to ensure at least 30 days since the member has last logged in, then you set the scheduled follow up action for 60 days in the future. This ensures that the minimum amount of time since a user has last logged in is at least 30 days and at most 60. If you want to use posting as a trigger, then you can do that also. That's the beauty of rules. Pick the best solution for you.

Ok, then when you say they "logged in" as recently as yesterday... do you mean they visited the site, or they actually logged in using username and password? Because the "User has logged in" event which triggers the email to be rescheduled only occurs when they actually log in via the login form. That could be part of the problem if you have a very long session timeout on your server. You can also turn the debugging option on for the rule and make sure that it is operating without error and actually rescheduling the follow up action for users when they do log in.