What is the best practice for moving a panel from a dev environment to a live site? I don't see any way to export a panel in a manner similar to views or CCK.

If you can provide some basic explanations, I can help with further documentation.

Comments

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Postponed

This will be available in Panels 2 - alpha versions are out for helping with testing, although I've not tried that bit yet.

catch’s picture

catch
he/him
Primary language English
commented
Status: Postponed » Closed (fixed)

done!

liquidcms’s picture

liquidcms commented
Version: 5.x-1.2 » 7.x-3.x-dev
Component: Documentation » User interface
Status: Closed (fixed) » Active

I am sure i am missing it somewhere; but is there a Panel's page export? i see import but can't see export anywhere.

Letharion’s picture

Letharion commented
Status: Active » Closed (fixed)

The export link is at the top right of each Page.

liquidcms’s picture

liquidcms commented
Status: Closed (fixed) » Active

yes, you would think that's where it would be wouldn't you? http://screencast.com/t/TG72UrYcr7Hb

do you possibly mean variant, not page?

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

For 'system' pages that exist only in code, only the variants are exported. There is no database to export for things like the user profile template. It simply exists. You export the variant.

liquidcms’s picture

liquidcms commented
Status: Fixed » Active

ok. thanks. glad to know i wasn't just missing something.

i guess if we can export a variant, would be easy enough to export ALL variants. i know we have some projects where node override (also System) has over 30 variants.

merlinofchaos’s picture

merlinofchaos commented

Use the bulk export module for that.

Letharion’s picture

Letharion commented
Component: User interface » Documentation
Assigned: Unassigned » Letharion

Document the export behaviour of system-pages.

liquidcms’s picture

liquidcms commented

hmm.. when i saw the bulk exporter created a module it seemed like a long path to go down; but gave it a shot.

created a module which as far as i can tell includes all the variants for node overrides.

enabled module on remote site; but it seems to do nothing. sort of expected it would replace the overrides already on that site; but nope.

gave up... will simply have to export/import each variant one at a time.. ughh. likely not a bad idea for a contrib module to simply create a batch variant export/import module. hopefully some time next week to look at that.

merlinofchaos’s picture

merlinofchaos commented

If there is something already in the database then the module won't override it. However, all you have to do is do a revert. There is a drush command to help you do a batch revert to make it quick.

liquidcms’s picture

liquidcms commented

ok, thanks. i'll check it out.

still seems like a simple (and would be a far more popular) solution to have a page export function. :)

bdornbush’s picture

bdornbush commented

Can someone tell me what is the drush command to help you do a batch revert to make it quick?

bisonbleu’s picture

bisonbleu commented
Issue summary: View changes

For a detailed answer to #13 and more, watch Exporting, reverting, disabling and enabling any exportable with ctools and drush on YouTube.

Thanks @swentel !