I have a pre-existing panel page from a given layout. It has about 5 contexts and a node id argument. I created a new panel page using the same layout. When I added a new context to the new panel page, the pre-existing panel page lost all of its contexts and gained the new one meant for the new panel page.

A temporary way around this is to duplicate the layout and create the new panel page from there. I've tried this and contexts will not be clobbered. So, it seems, the connection that causes clobbering is the re-use of the layout.

Comments

merlinofchaos’s picture

This suggests that somehow the 'sequences' values got out of sync somewhere. I've heard of this happening before but I have absolutely no idea why it would happen.

Compare MAX(pid) FROM panels_pane to the panles_pane_pid value in the sequences table. If the sequences value is lower, there is a problem and it must be corrected or you will continue to corrupt and/or overwrite panel content.

This is also something to check for display ids.

jyg’s picture

My coworker says that he can no longer reproduce this problem, though I saw it at least 3 times. I can no longer reproduce it either. The pid values you refer to are synchronized. Is it possible that they could have resynchronized on their own?

thanks for taking the time.

merlinofchaos’s picture

It shouldn't be possible, but it is hard to say for sure. :/

sdboyer’s picture

Status: Active » Closed (duplicate)

What PROBABLY happened (this whole discussion being thoroughly in the realm of voodoo)...

Panels_page currently doesn't handle adding context-specific displays (i.e., when you have a different panel_page for a particular context and you FIRST click on the secondary menu tab for that context to start editing it and differentiating it from the default) with all the grace it should. I haven't the foggiest on how it could have gotten resynced, but something may have gotten out of whack there. The issue I've had open on this - eek, for way too long now - is #256482: Misnumbering of newly-added panes when editing a not-yet-delinked alternate display on a panel page. Given that the behavior is no longer reproduceable on your end, and it seems like it might be the same problem, I'm gonna mark this a dupe and cross my fingers.