Table ... doesn't exist query: SELECT * FROM panels_page in ../panels_page.read.inc
asb - June 24, 2009 - 22:25
| Project: | Panels |
| Version: | 6.x-3.0-beta2 |
| Component: | Panel pages |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
Hi,
after upgrading from D5 to D5 and from Panels 2.x to 3.x on D6, I'm getting the following warning:
user warning: Table '..._drupal.panels_page' doesn't exist query: SELECT * FROM panels_page in /var/www/.../sites/all/modules/panels/panels_page/panels_page.read.inc on line 29.Also, when clicking on "Bulk export", I'm getting:
warning: Invalid argument supplied for foreach() in /var/www/.../sites/all/modules/panels/panels_export/panels_export.module on line 126.Sorry, but I have no idea what those error message are supposed to tell me.
Thanks & greetings, -asb
#1
THe panels page module (and table) doesn't exist in Panels 3. Please remove your panels directory and re-install the files from the tarball you downloaded. It is important to remove old files.
#2
Hi,
thanks for the reply. However, I don't know what I have to do - besides not using panels anymore. If the mentioned table does not exist, I'll have to uninstall the module to remove it cleanly (and loose all panel pages); or I'll have to delete files from ./sites/all/modules, but leave remains of an older and unsupported release in the databae (which usually is unfavourable).
As it seems, once again there appears to be no clean migration path. That's pretty sad, again.
Saddened greetings, -asb
#3
Have you tried the update path? If you remove Panels and install the newest code, and CTools, it will update cleanly. If you install the older module you had and uninstall that, it will uninstall cleanly. I'm not sure how it follows that improperly upgrading a module fails to get you a clean upgrade path.
#4
Sorry, then we had a misunderstanding. I'll shut up, wait for a stable release and hope for some documentation to appear.
Greetings, -asb
#5
It is not documentation that you lack.
When you update a module in Drupal, you should always remove the module directory, then install the new code. That's what you missed. If you don't remove the module directory and instead just expand a new tarball over it, old files may not get removed. This is the situation you are in: Old files have not been removed and Drupal is still trying to use them.
#6
> When you update a module in Drupal, you should always remove the module directory, then install the new code.
Interesting point. But from a users point of view I don't want to have take care of such things, and that's why I - and currently 2,827 other counted users at the time of this writing - rely on a tool like Drush. As far as I know Drush doesn't offer a functionality to erase a modules directory prior to installing a new version, but I'll file an issue for this.
Is there any official recommendation regarding the handling of module updates I could reference to?
Greetings, -asb