I have deploy updates for core and ctools module. While updating core to 6.12, I get the message "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 'type for db_type_placeholder' at line 1 query: SELECT * FROM cobarsoft_delegator_pages WHERE task = unsupported type for db_type_placeholder in /sites/all/modules/ctools/includes/export.inc on line 101.". I forget to disable module before updating core. Is it normal to get this warning ?
After updating remaining modules, I get the message : "warning: Invalid argument supplied for foreach() in /sites/all/modules/ctools/includes/export.inc on line 255.", on panels nodes. How to fix ?
Thanks

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Postponed (maintainer needs more info)

This is a tough one to comment on. It suggests that your schema file is not up to date. Did you run update.php? Are you sure that ctools and delegator were both fully updated, file wise? It may be best to rm ctools and unpack the directory for your tarball (or checkout from CVS if you're using that method) again, then hit update.php and make sure everything is in order.

kbahey’s picture

kbahey commented

When running update.php from D5 to D6 and using ctools 6.x-10, I got similar errors but on a different table:

# warning: Invalid argument supplied for foreach() in sites/all/modules/ctools/includes/export.inc on line 571.
# 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 'type for db_type_placeholder)' at line 1 query: SELECT * FROM page_manager_pages WHERE name IN (unsupported type for db_type_placeholder) in sites/all/modules/ctools/includes/export.inc on line 139.
# warning: Invalid argument supplied for foreach() in sites/all/modules/ctools/includes/export.inc on line 571.

merlinofchaos’s picture

merlinofchaos commented

As near as I can tell from looking at this, this is happening because the schema info is somehow incomplete. I haven't reproduced it on my own update tests, though, so I don't know why this might be.

merlinofchaos’s picture

merlinofchaos commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

No new data or ability to reproduce this in several months.