rules

The original teaser for this is kind of misleading. The general question: is it possible to prevent the creation of a node with Rules? Based on a condition, can you cancel the creation of that content? I guess an option would be a special purpose role, that has permission to create the content, which is added or removed by the rule.

Hello, I'm in the process of building a site that sells tickets to events using ubercart. I'd like to be able to have a rule that automatically unpublishes the event node when the event date passes.

For the most part, I've been able to do this but there's still a question in my mind as to whether or not I've done it the best way. Here's a quick synopsis of what I did:

1. Created an "event" content type (actually an ubercart product class).
2. Added a date field to the "event" content type (field_dates).
3. Created a rule that is run on cron.
4. I did not include any conditions.

Hi,
I set up a couple triggered rules. The actions are not being performed and I don't see any evidence at /admin/reports/dblog that anything is working. Will there be log entries if actions are triggered?

Joomla has announced availability of new ACL: http://is.gd/iA5B and they seem pretty excited about it. Is that something for Drupal community to be jealous of?

If you come from a Java/J2EE background the clear answer is: NO (yes, in capital letters). You have to actually suffer from a structured, strict ACL to really appreciate the simplicity of a security system like that of Drupal.

Now, you may argue that Drupal security is slightly over-simplistic and too code-oriented (makes us, the developers happy) for "business" use.

With the the new e-Commerce I am currently intergration the store with the rules module so that the workflow can be easily altered and customize for meet the needs of the store owner.

Basically e-Commerce should not dictate how the store owner runs their business, but facilitate the running of their business.

But to start off with we will need to provide a default workflow which will allow someone who is not 100% sure to run without too many issues.

Hi,
I'm currently playing around with the beta3 version of the module.
I have set up a trigger on adding a new node, with a few basic conditions and they work fine.
So I started trying to get some custom php conditions working and have hit a wall.

I have a taxonomy term on my node and want to do stuff based on its value.. What seems to be happening is the node save (rule) is kicking in before the save of the taxonomy terms because its blank when i view the node afterwards. I could be doing this completly the wrong have a look :

Hi,

The new FriendList module is coming along nicely. I have finished the Views integration, which -- I am happy to say -- is really quite something. It took longer to integrate with "views" than it took to write the whole module!

Anyhow, I am now battling a new monster: "Rules". Rules' main developer is on holiday. So, no hard-core help there either!

If you know Rules, and would like to help me test what I did (and tell me how to test it...!), please hop here:

http://drupal.org/project/friendlist

Check out http://more.zites.net/rules/rules-beta-1-drupalcon!

I've created a session proposal for the drupalcon :)

-> see http://szeged2008.drupalcon.org/program/sessions/rules-new-opportunities...

I'd also talk about the differences to the core actions and trigger module. Look at the session description for more infos.
Hopefully the session will be selected and I'll see you there.. :)

I've just released ALPHA1.

As you can see in the development status, there are still some important features missing. But the main UI (and the API) is already working - so check it out and give me feedback!