![]() We have already experimented with different ways of "completion", e.g. Future of Content Complete: a Complete APIĬhecking completion for content is just one approach to having your Drupal websites as "complete" as possible. ![]() You can also enable the debugging mode of the Rules module: at the settings page click on "Debug rule evaluation". Test your new workflow by writing an additional message to watchdog and setting the scheduled evaluation date to for example "+1 min". Add the action "CC Check (Set)" with Content set to "created content" and User set to "content's author".Add the condition "Content has type" and select the "Album" content type.As a trigger event, we choose "After updating existing content". Go to "admin/rules/trigger/add" and fill out the label with "CC Check".Now we need to trigger that rule set on a Drupal event, for example, every time a node of type 'Album' is updated. We now have a rule set that checks the completion of the node and, if needed, sends an email reminder to the author of that node. Make sure you have cron configured to have email reminders sent out daily. Add another action "Schedule 'CC Check (Set)'", give it an identifier "CC Check ''" and as scheduled evaluation date put "+1 day". We need to reschedule our rule continuously.Fill out the subject with for example "Complete your node " and the message with something like "Click on /node//edit to complete your node." Check out the Token Replacement Patterns for more options. As recipient, select the content's author. Add the action "Send a mail to a user".Click on "Negate" such that our condition translates to "if Content Complete % < 100". I'll show you how to set up email reminders sent automatically to authors of incomplete Album nodes (= than x" and fill out 100 under "% to compare". Thanks to the integration with the powerful Rules module, you can set up complex workflows with data completion in a couple of minutes. If you have missed the introduction of the Content Complete module, please read the first part in this series. " would improve your question (it is possible to use that module, but for this question you don't " want to" use it).This is the third part of the series on Content Complete. " in your question to something like " Without using the Rules Scheduler module. ![]() Note: I think rephrasing " the Rules Scheduler module cannot be used. use user login as the event, fetch the set flags of the logged in user, check their creation time, if they are older than x day unset the flags.". Using this Rules Event also complies with your comment to my answer to your related question, ie ". This is what differs from what is shown in the video, starting from 11:30 (in the video the Rules component is triggered daily, via the Rules Scheduler). It appears to me that Rules Event "User has logged in" could be a good fit for your case (if not replace it by whatever other Rules Event that fits best). This Rules Component should then become the Rules Action to be performed by an additional rule that is triggered by an appropriate Rules Event. ![]() It should be possible to use the same Rules component as in Step 1 of my answer to " How to use the Rules module to unset all flags (set x days ago) when cron runs?". You'll have to pass the userid as a parameter also, similar to what is shown around 7:30 in that video also. And for each node in the list you want the rules action to be "unflag node" (instead of "remove sticky"). In your case you want to start from your VBO list of the nodes flagged by a user at least x days ago. Combine with loops, actions and Rules Scheduler to make awesomeness happen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |