jair

Constituant
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    23

jair last won the day on July 28 2018

jair had the most liked content!

Community Reputation

22 Excellent

About jair

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It seems that Date/Time fields are not supported in the pages expansion. I do have a form with a few fields, on which I try to send an email with content on each submit. Date/Time fields are not caught by rules and I cannot use tokens for them.
  2. jair

    Collab header cover not display

    It is done automatically when you click the "Something is not working correctly". Check your first screenshot, it says in pale gray letters "We have cleared all cached data". You are good to go, but I will check the other warnings - about the server time, and especially the one for the database.
  3. jair

    Detect reactions?

    That looks like a vert faint glimpse of hope Please keep us posted, I might play with it too. One note though, from my experience adding more conditions actually slows things down. I think it makes sense - more conditions need to be checked on each event, which consumes resources, regardless if it ends in firing an action or not.
  4. jair

    4.2 plans for Rules app

    Hi Kevin, do you have any plans in the foreseeable future for 4.2/4.3 upgrade?
  5. jair

    add points to everyone in a group

    You can do that with Rules with Bulk actions. I very much doubt points economy will get any features that can be created with Rules, the two apps complement each other.
  6. Create custom data field to track the number of reviews. Rule 1: Event: article is published Action: increase the value of the custom data field by one Rule 2: Event: custom data field is updated Condition: is the value >1, 5, 10, etc Action: award a medal. Need some working, but this should be the basic idea.
  7. Should be fairly straightforward, probably the most difficult part will be inserting it in the template where you want it to be visible. But just create a member related custom data field (do not use profile field for that) from a datetime type that should be editable by users. Then on the frontend, just show how many days since this date have passed - should be very simple php code.
  8. Is there an action for flagging as spammer? I do not remember on top of my head, so my suggestion is kinda rough, but something like this. Create a custom data field of integer type, connected to a member that contains number of reports. Rule 1: Event: Content is reported Action: Add +1 to the created custom data field. Rule 2: Event: Custom field is updated Condition: is the value of the created custom field > 5 Action: flag member as spammer Something like that. Sorry, I am a bit tired, so it probably needs a lot of work to get it going, just a direction you can think about.
  9. Would it be difficult to implement custom data field, from let say "Button" type and then we can catch the event and do stuff related to the content item when the button is clicked? The missing reactions are killing pretty much all my ideas (I know, IPS did it), but actually I don't need the reactions, I need an easy way to catch members interaction with the content and some extra buttons can do the trick. Here is a graphical example of what I mean: Events would be "Button is clicked" and we could take parameters from the item on which was the button (post on which button is clicked), the member that clicked the button, etc. Is something like that possible?
  10. Yeah, best way to learn is by trial and error. Otherwise, you might be spoonfed some partially working solution, but at the first moment you need to customize it, you will be in trouble. So, keep digging, eventually you will get it right and it will be much easier to create additional rules from that point on
  11. This will simply check if the member joined the site in the last 6 hours. Not really what you are looking for from what I can get from your description earlier.
  12. Then you need a rule to also delete the award if the user did not logged in during the night in the last two days... Roughly something like that. It will take some experimenting, for example in your screenshot you compare the timestamp, which is not the best way to do it, timestamp is a static unique value, you can't have it repeating each day, so this means you will have to change your rule each day, not much of an automation Play around with the compare dates or use different time then timestamp. Or if you use the timestamp, try to find which seconds of the timestamp belong to the night time. Something like this.
  13. It would be nice if we can choose on which exact topic to add the Topi/Comment data field. Right now you can select entire forums, but usually with such fields you want more granular control.
  14. Something like this: Event: user logged in Condition: check number value. if current time is after 12:00am and before 6am for example Action: award the trophy As I have mentioned in other threads, I don't know if those users that have remembered their logins will be triggered by the event. You will also have to think what to do with the trophies afterwards - remove them on the next day, or in the morning, etc, you haven't provided information about that.
  15. Rules is extremely powerful app, but not the most user friendly, that's a known fact. This prevents it from getting popularity it deserves both with the members and other developers. My suggestion here is to fix the issue with user friendliness, of course if it is possible. So, we can export our rules as XML and give them to others. shortening the path for them, but unfortunately this does not improve the user friendliness by much. You can serve a perfect rule on a plate, if the other side does not understand it, they won't be able to make the small tweaks required to customize a rule for their use case and we are back at the start. My suggestion is to build another layer in the app, allowing us to export rules as a plugin with settings. So the other users won't have to modify the events/conditions/actions, they will just change a few settings that we expose to them. For a simple example lets take the "send member a welcome pm" use case. Right now you need to create event (member is validated) and action (send the pm from this author). The last sentence is in foreign language for almost all people. It will be much better if I can create the "rules" logic and export it as a plugin that has two setting fields - one for sender, one for the message and thats it. The end user just needs to have the core of the Rules installed and they don't have to care about events, conditions and actions, this is all taken care of under the hood. This will allow many of us to share our creative rules in a way that is simple for the others and won't require excessive support. Right now I do have some creative stuff (I think) and I do have even bigger ideas. But I definitely don't want to provide my ideas on the marketplace and be forced to deal with all the questions that will come with the more complicated rules. So it will look like this: Kevin - develops and supports the core, everyone will have to have this. People like me - provide creative rules as plugins. The heavy lifting of the development will be taken care of in the core, we can use our creativity to develop final solutions for the ordinary users. We will also support our plugins with answering questions, improvements, etc. Ordinary users - they will buy the plugins and the core. So no contribution from their part, except increasing the popularity of the app and the plugins and providing monetary compensation to the other two layers. I hope this is doable and I am sure it can bring some life in to the application, because I frankly think right now it is almost abandoned. There haven't been any new features related to 4.2 and 4.3 and even though @Kevin Carwile supports it with the rare bug fix here and there the development to me is far from where it needs to be.