After I've upgraded core to D6.14 and afterwards panels I see my old panels in the pages list, but if I click edit they do not have any variants and therefore the configuration seems lost at all.

Any idea how this could happen and if this is expected? I really hope I do not need to re-configure all panels by hand from "scratch" :-(. The variants are really the most work...

Comments

hass’s picture

hass commented

Also the same with latest DEV.

merlinofchaos’s picture

merlinofchaos commented

Crud. I have seen this happen but when they gave me a copy of their database, and I upgraded it, it worked perfectly for me. There's something weird that may be PHP version related or something. I couldn't figure out what might be going on. You should start by looking in the database in the page_manager_handlers table and seeing if stuff got created but incorrectly or if the variants didn't even get created. THat will at least provide an avenue of exploration.

hass’s picture

hass commented

I'm always able to reproduce this with my backup database. Can I extract the tables for you to take a look? I tried to understand the field logic, but I was not able to fully understand this in the short time.

PHP 5.2.6 (cli) (built: May  2 2008 18:02:07)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
  1. page_manager_handlers.handler column is NULL. A manual created variant have a value of "panel_context".
  2. page_manager_handlers.conf after an upgrade is a:7:{s:3:"css";N;s:6:"css_id";s:0:"";s:9:"no_blocks";N;s:3:"did";s:1:"1";s:5:"title";s:1:"a";s:8:"contexts";b:0;s:13:"relationships";b:0;}. Manually created it looks like a:7:{s:5:"title";s:5:"Panel";s:9:"no_blocks";b:0;s:6:"css_id";s:0:"";s:3:"css";s:0:"";s:8:"contexts";a:0:{}s:13:"relationships";a:0:{}s:3:"did";s:2:"10";}
  3. page_manager_handlers.name have a value of "page_panel_page_1_" and a manually created variant a value of "page_panel_page_1_panel_context"

All other fields are 100% the same. Does this help? What else?

merlinofchaos’s picture

merlinofchaos commented

Yes, that NULL handler is definitely at least a problem, and it is contributing to the incorrect name. Looking at the .install file that suggests the problem is in this code:

  $plugin = page_manager_get_task_handler('panel_context');
  $handler = page_manager_new_task_handler($plugin);

That $handler should show up with the right data.

Hmm. One possibility that comes to mind is that maybe CTools and Panels are out of sync, version wise, and Panels is trying to politely decline to be involved, and that could cause the $plugin to fail. What versions of Panels and CTools are you running?

hass’s picture

hass commented

Both panels and ctools are 3.0

In my earl test i've also thougt it maybe something with ctools or the order of install/upgrade. Maybe ctools installs if panel is not updated, but expects something not yet available as the panels update hooks have not run yet… but i'm only guessing…

hass’s picture

hass commented

One thing I wondered about, not sure if the reason - if I upgrade from D5 - all modules are disabled in D5. After the update.php ran the ctools module and page_manager are enabled (?), but panels not. All other modules that have been updated via update.php are still disabled as before the update. It could be related and I wonder why ctools and page_manager have been auto-enabled... only to note here.

merlinofchaos’s picture

merlinofchaos commented

Interesting. The panels update is supposed to auto enable page manager and ctools. Yet if panels is not enabled, that should not be running. Unless, of some reason, it is, even though Panels isnt' enabled? That's very confusing.

hass’s picture

hass commented

If you upgrade from D5 to D6 it's recommended to disable all modules and remove the whole modules folder...

1. D5, disable all modules and contrib themes, switch to Garland
2. Remove all core files and the module and theme folder from disk, keep only files folder and settings.php as settings.old.php
3. Extract D6 and migrate D5 database setting to D6
4. Run update.php and thereby update core to D6
5. Copy all new D6 modules to sites/all/modules, all modules are still disabled in system table
6. run update.php
7. All modules are upgraded to D6, but still disabled.
8. Now go to modules page. All contrib modules are disabled, except ctools, page_manager
9. enable panels manually
10. check out page manager - panels base settings exists, but have no variants.

hass’s picture

hass commented

Keep in mind that D6 is the first core version that run update hooks of all modules - doesn't matter if the modules are disabled or not...

merlinofchaos’s picture

merlinofchaos commented

Oh. Well. Crap. That's the problem right there.

I did not think that the _update_X() hooks got run for disabled modules.

All right. For now the workaround is to keep the Panels module enabled when running update.php. I'll have to figure out how to deal with this.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (duplicate)

Ok, marking this as a dup of http://drupal.org/node/533724 which is the same problem.

hass’s picture

hass commented

I'm able to confirm that enabling panels, page_manager and ctools and running update.php afterwards works.