Closed (fixed)
Project:
Rules
Version:
7.x-2.x-dev
Component:
Rules Engine
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Aug 2010 at 14:12 UTC
Updated:
5 Sep 2010 at 13:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
klausiI'm not able to reproduce that. Did you use the latest code? What database, MySQL?
Comment #2
yaoweizhen commentedI used Drupal7-alpha6 with sqlite and latest dev version.
Comment #3
yaoweizhen commentedI also tested with Mysql. On the modules page, it went to blank page when submit module installation.
Comment #4
fagoThe blank page might be a memory issue. Sounds like sqlite compatibility issue, try to look for relevant issues in the drupal core queue.
Comment #5
yaoweizhen commentedTried Mysql again. PHP is set 128M memory limit, still WSOD.
Comment #6
x-lette commentedI can confirm installation error with sqlite.
In ./rules/rules.install I changed line #97 from
'primary key' => array('id', 'event'),to
'primary key' => array('id'), /* , 'event'), */and installation worked fine. Looks like sqlite can't handle PKs with multiple columns or the sqlite code from drupal core generates wrong statement. But as 'id' is a foreign key to another table where 'id' already is primary key it should be sufficient for consistency having 'id' solely as primary key.
Comment #7
fagoThe wrong thing is that id is specified as serial, what is auto-incrementing. No good idea for a foreign key ;)
Patch attached, please try whether it fixes the problem for you.
Comment #8
fagocommitted that, please test.