![]() Returns TRUE if there are conflicts for the node. CONDITION: Contains a Resource Conflict: Evaluate a node object for conflicts.This is the event trigger for the default Rule. It provides both a node object of the node being created/edited and a form object for use with rules_forms. You should use this event if you want to set form errors, or if you want to interact with Rules_forms module. EVENT: A Resource Conflict Node Form is Validated: This rule fires during node form validation on Resource Conflict enabled content types.Here's a run down of the Rules components included with Resource Conflict 7: Best of all, it's all exposed and easy for you to maintain. Other people have asked about using the module to integrate with Organic Groups, or to control bookings of finite resources - you could easily use Rules to build those functionalities. Soft conflicts can be booked, but they create a node to record the conflict. Or maybe I try to book John Doe, who is tagged as a "Plumber", but Maintenance is already booked at that time. For example, maybe I try to book the taxonomy term "Maintenance", but the sub-term "Plumbers" is already booked at the same time. "Soft" conflicts are when you try to book a taxonomy term that is a parent or child of a term in an existing booking, or a user who is tagged with a term or child of a term that is already booked. Hard conflicts throw a form error and prevent saving the node. This is just like the above case, and it's a really simple modification on the default Rule. "Hard" conflicts are when two bookings at the same time reference the same user or taxonomy term. To give an example of how complex this can go - on a site I recently launched, I have two kinds of resource conflict events. More likely you will want to edit the rule to add some more conditions - for example, maybe a resource conflict on your site means overlapping taxonomy terms. ![]() ![]() But this is not a very realistic use case. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |