When Cloning some types of Node Limit restriction rules, an SQL error is displayed. Despite the error, a new record is created but it is not a true clone - the fields other than Description are default. See attached example.
Error messages similar to the following (some of the values may vary):
PDOException: SQLSTATE[21S01]: Insert value list does not match column list: 1136 Column count doesn't match value count at row 1: INSERT INTO {node_limit_role} (lid, rid) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1_rid, :db_insert_placeholder_1_name); Array ( [:db_insert_placeholder_0] => 2 [:db_insert_placeholder_1_rid] => 1 [:db_insert_placeholder_1_name] => anonymous user ) in node_limit_role_node_limit_save() (line 114 of /home/xdrcft91/public_html/foo/sites/all/modules/node_limit/node_limit_role/node_limit_role.module).
The website encountered an unexpected error. Please try again later
Comment | File | Size | Author |
---|---|---|---|
SQL Error on Cloning Node Limit.jpg | 353.45 KB | dougsap |
Comments
Comment #1
DuaelFrComment #2
Refineo CreditAttribution: Refineo commentedI also got this error in the latest 7.x-1.x-alpha5 for node_limit_userofrole.
Comment #3
HFlame7 CreditAttribution: HFlame7 commentedI am also getting this error when trying to make a clone of a limit rule. Using 7.x-1.0-alpha5.
The settings are nearly the same as those in the screenshot, only the content type is different on my end.
Comment #4
DuaelFrI just had a few minutes to fix this.
It will be deployed with the next dev release.
Comment #5
Jorrit CreditAttribution: Jorrit commentedThanks for fixing it, the fix works fine (marking it as fixed because of that).
Is there any chance a new release can be made? After all, it is still alpha and there hasn't been an alpha release since Februari.
Comment #7
HFlame7 CreditAttribution: HFlame7 commentedComment #8
DuaelFrHFlame7 you will have to explain this...
Comment #9
HFlame7 CreditAttribution: HFlame7 commentedSorry about that, I overlooked response #4 (fixed in the dev version) and only saw that the system automatically marked it as fixed.
Changing back to fixed.
Thanks for your work on this module DuaelFr!