When I tried to "export" a Panels page from my DEV site and "import" it to my QA site I get this message, "Unable to get a panel page out of that."
When I tried to "export" a Panels page from my DEV site and "import" it to my QA site I get this message, "Unable to get a panel page out of that."
Comments
Comment #1
sdboyer commentedEither you did something wrong (missed a piece in your copy/pasting, something like that), or you may be butting into one of the known issues with the exporter that we've fixed since rc1a. (Wow, we REALLY need another release...). Either way, give it another try or two, copy/pasting very carefully (and ensuring that the one on your dev site is working properly, first). If you still get the same message, please post the output of the exporter into this issue - make sure you use code tags to save my eyes, please!
Comment #2
asugene commentedI was able to repeat it everytime. I built a panel page step-by-step to see if I can find the problem. It appears when I "Add a Node" under Content for a panel page and save, I get this message when I try to import it.
Comment #3
kevinwalsh commentedI replicated this error, and the fix, on 5.x-2.0-rc1a. It appears it was the node context that was causing the problem (deleting the node pane without deleting the context did not fix).
Comment #4
sdboyer commentedThanks for the confirmations, but you missed the key part of the request: I need you to paste in the contents of the faulty export.
You're using -dev when you do this? As I said, the it's an outstanding issue in rc1a; my only concern here is if it's still occuring in -dev.
Comment #5
liquidcms commentedjust confirming.. i get this same issue and yes, i am on 5.x-2.0-rc1a, will try dev version now.
Comment #6
liquidcms commentednope, doesn't work with latest 5.x-dev release either
Comment #7
liquidcms commentedhmm.. works now :).. i guess the separate export function doesn't do the same export as the export tab from within a single pane
Comment #8
joachim commentedGetting it too with this:
Comment #9
sun.core commentedSorry, but Panels for D5 will not see any further fixes, since Panels for D6 simply advanced too much and no one cares for D5.