On installing the module, I get the following warnings:

    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE name = 'rules_example_1'' at line 1 query: DELETE FROM WHERE name = 'rules_example_1' in /home/tom/workspace/wrightmedia.6/modules/rules/rules/rules.module on line 774.
    
  * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(name, data) VALUES ('rules_example_1', 'a:8:{s:5:\"#type\";s:4:\"rule\";s:4:\"#' at line 1 query: INSERT INTO (name, data) VALUES ('rules_example_1', 'a:8:{s:5:\"#type\";s:4:\"rule\";s:4:\"#set\";s:15:\"event_node_view\";s:6:\"#label\";s:59:\"Example rule: When viewing an unpublished page, publish it.\";s:7:\"#status\";s:6:\"custom\";s:11:\"#categories\";a:1:{i:0;s:7:\"example\";}s:7:\"#active\";i:0;s:11:\"#conditions\";a:2:{i:0;a:4:{s:5:\"#type\";s:9:\"condition\";s:5:\"#name\";s:36:\"rules_condition_content_is_published\";s:9:\"#settings\";a:1:{s:13:\"#argument map\";a:1:{s:4:\"node\";s:4:\"node\";}}s:7:\"#negate\";i:1;}i:1;a:3:{s:5:\"#type\";s:9:\"condition\";s:5:\"#name\";s:31:\"rules_condition_content_is_type\";s:9:\"#settings\";a:2:{s:13:\"#argument map\";a:1:{s:4:\"node\";s:4:\"node\";}s:4:\"type\";a:1:{i:0;s:4:\"page\";}}}}s:8:\"#actions\";a:1:{i:0;a:3:{s:5:\"#type\";s:6:\"action\";s:5:\"#name\";s:30:\"rules_core_node_publish_action\";s:9:\"#settings\";a:2:{s:13:\"#argument map\";a:1:{s:4:\"node\";s:4:\"node\";}s:9:\"auto_save\";b:1;}}}}') in /home/tom/workspace/wrightmedia.6/modules/rules/rules/rules.module on line 775.
    
  * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE name = 'rules_set_1'' at line 1 query: DELETE FROM WHERE name = 'rules_set_1' in /home/tom/workspace/wrightmedia.6/modules/rules/rules/rules.module on line 774.
    
  * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(name, data) VALUES ('rules_set_1', 'a:4:{s:5:\"label\";s:44:\"Example: Empty ru' at line 1 query: INSERT INTO (name, data) VALUES ('rules_set_1', 'a:4:{s:5:\"label\";s:44:\"Example: Empty rule set working with content\";s:9:\"arguments\";a:1:{s:4:\"node\";a:2:{s:4:\"type\";s:4:\"node\";s:5:\"label\";s:7:\"Content\";}}s:10:\"categories\";a:1:{i:0;s:7:\"example\";}s:6:\"status\";s:6:\"custom\";}') in /home/tom/workspace/wrightmedia.6/modules/rules/rules/rules.module on line 775.

Comments

fago’s picture

Component: Rules Core » Rules Engine

grml, this is a result of the change of #300729: Investigate default/example rules & rule set installation type - however I've tested it properly and for me it was working fine. Could you help me by answering some questions?

Have you enabled "rules" and "rules admin" both at the same time? Was it the first time you enabled the module? Does it also happen for you if you first enable the rules module and then the rules admin module afterwards?

mrfelton’s picture

It was the first time I enabled the module. I did enable Rules and Rules Administration UI at the same time. I have several rules set up now so don't want to uninstall and reinstall... I'll set up a test bed in the morning and confirm it works if I do them one at a time.

fago’s picture

Issue tags: +rules 1.0

thanks! This is important to be fixed for 1.0.

mrfelton’s picture

Well, I just downloaded the latest -dev release and installed in a D6 sandbox - no errors this time. I did exactly the same as I did last time (enabled both Rules and Rules UI at the same time).

rbl’s picture

Hi!
Just downloaded and installed Drupal, Rules and a bunch of other modules on a brand new site.
Activated Rules, Rules Scheduler and Rules Administration UI at the same time and got this error.

Ricardo

fago’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)
Issue tags: -rules 1.0

Automatically closed -- issue fixed for 2 weeks with no activity.