I've been exporting Panelizer configuration to features and pushing up to production. My strategy so far has been:
- Config is created on local and pushed up via features
- Content, such as Fieldable Panels Panes instances are created directly on production.
However, this is now causing issues. When I revert a Panel/Panelizer feature, it reverts back to my local settings and removes any content panes I've added on production.
A couple of ideas I have for managing content panes:
Use UUID features to push up any content panes. Trouble with this is that the content panes are now in the dev/stage/live workflow and any changes on production will be reverted with the next
Pull down a fresh copy of the database before doing any further edits to a feature, that way when a feature is recreated on local, it will contain the new content panes.
How do you manage content panes when using features?