Jump to content

Kevin Carwile

Clients
  • Posts

    1,237
  • Joined

  • Last visited

  • Days Won

    9

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Kevin Carwile

  1. 3 minutes ago, Paul E. said:

    In fact, this should be a precondition of selling on the IPS marketplace, I think. If a person can no longer support an extension, then IPS should mark the extension as no longer supported. Keep it available for download, yet note that the developer is no longer supporting maintenance of the project and open it up for the sites that have come to rely upon it. It's dangerous for a new community to come along and install (or worse yet, purchase) things that are essentially abandonware.

    It was the other way around. IPS removed it from their marketplace therefore there is not really any point of continuing development on it. 

    16 minutes ago, ahc said:

    We can't use the "NOT" reverse condition on any type of rule set even though it would help us automate a handful of things.  We've been dealing with this issue since 4.3. 

    The minute we turn it on, regardless of condition, it triggers all rules to activate for both members and guests the minute they visit our site, even if the rules are not set to trigger or are applicable to the member/guest.

    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.

  2. 41 minutes ago, SammyS said:

    Well, this negative review was written after the last update, almost 1 year ago.

    I think a bug fixing release 2 o 3 times per year would be fair for the people who trusted in you

     

    "Having some serious trouble here since last invision V4.4.2 and rules update V1.4.6 :

    Private Messages are randomly spread to arround 100 users from the community without their consent.

    It happened at least two times.

    Invision support says it is rules problem, rules says it is usage or invision problem ...

    Nothing has changend in the rules between the updates, in 2 years nothing like that did happen.

    There is a bug somewhere, it needs to be solved"

     

    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.

  3. 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.

  4. On 2/9/2019 at 9:12 AM, LukasGr. said:

    Hi,

    like written in your own support forum:

    with IPS 4.4 Beta coming - is it just me or did it break the category view for collabs? I assume there has been a change in the controller? I am not an expert nor am I sure if that is really the reason why collabs are broken in 4.4 for me.

    Have you already been notified about this? Is there an easy fix?

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

  5. 9 hours ago, Mousie said:

    Sounds simple in theory, except there's no Topic\Comment object available to bulk process. Content\Comment doesn't seem to allow bulk processing in manual scheduling. I can bulk process Topic\Item, but how do I drill down into each Topic\Comment contained within to count them?

    Tearing my hair out with this one haha.

    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.

  6. 10 hours ago, Mousie said:

    - Ability to choose member groups that can fill out particular fields, and what member groups those fields will display for.

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

  7. On 12/4/2018 at 3:02 PM, Fighting 13th said:

    I can't do that because the expansion pack actions (well the source portion, i.e.: "Member who RSVP'd 'yes' to the event") only work with the expansion pack events (I probably should have known that, oh well). Is there any other way you can think of to make this work? Or is there any chance those actions would be able to be updated into the rules/calendar rules expansion pack?

    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.

  8. On 11/18/2018 at 2:51 PM, Fighting 13th said:

    Why aren't the Rules App and its extensions available for purchase at the moment?

    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.

  9. We are looking into this.

    On 11/12/2018 at 3:33 PM, iacas said:

    My question is: I can have BOTH going, right? Since they have the same unique ID, whether they log in OR post, it'll push the notification back two months, right?

    Correct.

  10. 22 hours ago, Fighting 13th said:

    I'm guessing it's true, but if I upgrade from the Lite to Full, I won't lose my rules I've built right?

    No, you wont lose any rules.

    21 hours ago, Fighting 13th said:

    And also, would you be able to add an Action for "When award is given/received" or something along those lines. The intent of my request is to award points/send notifications/etc for when a user receives an award.

     

    To anyone: Is there a workaround any of you have in mind? There is a condition that can check to see if a member has an award...but what rule would I use? What other condition(s) would I have to use to make this workaround work?

    I've been trying to engineer a way for this to happen for about 30 minutes...I'm getting nothing lol. Any help is appreciated. Thanks!

    That would be an event that needs to be included by the awards app.

  11. On 8/18/2018 at 12:20 PM, Fighting 13th said:

    I have another rule I'm working on....would it be possible with this app to notify members the day of/day before a Calendar Event about the event itself? I was looking at conditions for an "Event was created" trigger and the best thing I saw was that you could do a "compare dates" condition and compare the current time to some aspect about the event--whether it's creation date/update date/last post date.

    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' )

     

  12. 1 hour ago, Joel R said:

     

    
    BadMethodCallException:  (0)
    #2 /home/nginx/domains/mycommunity.com/public/init.php(460) : eval()'d code(33): IPS\Content\seo_hook_Content_Item->noFollow()
    #3 /home/nginx/domains/mycommunity.com/public/applications/core/modules/front/system/announcement.php(37): IPS\Content\seo_hook_Content_Controller->manage()

     

    Looks like maybe the problem starts in the code above?

    As for the template issue, I'll have to look into that.

  13. On 8/8/2018 at 8:57 AM, christopher-w said:

    @Kevin Carwile

    I'm running in the IPS cloud. Can I patch there?

    Nope. Sorry. It will require a new version build to be released (unknown timeframe).

    22 hours ago, Fighting 13th said:

    I don't see any option like "application author." This is all I see:

    rulesapp.png.db1ab97b593fa803e57d8fe8edef0cda.png

    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.

  14. @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'?

  15. 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.

  16. 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.

  17. 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.

×
×
  • Create New...