Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is a sort of meta issue to cover the things needed to switch to using Migrate for demo content. Most of this is implemented in the following three patches.
#2105433: Add Migrate modules to Panopoly Core to help facilitate better demo content patterns
#2105427: Implement Migrate module for Panopoly News demo content
#1869972: Implement Migrate Module for Panopoly Demo Content
#2105513: Implement Migrate module for Panopoly FAQ demo content
Much of the original discussion around this took place in #1869972: Implement Migrate Module for Panopoly Demo Content where several options were discussed, the main 2 contenders being UUID Features and Migrate. There was a general consensus that Migrate was the best way forwards.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2105503-panopoly-migrate.patch | 2.06 KB | mrfelton |
Comments
Comment #0.0
mrfelton commentedFixing issue links
Comment #0.1
mrfelton commentedAdd reference to panopoly_faq issue
Comment #0.2
mrfelton commentedAdd some reasoning
Comment #1
mrfelton commentedTo support this, a change is needed to the install profile to make it aware that demo content may be coming from multiple apps. Since each app provides its demo content within a submodule, the Apps install task needs to be made aware of this.
This patch also re-enables the 'Install demo content' checkbox in the install profile as this is needed in order to let the user decide wether they want all of the demo content installed or not. The previous logic assumed that the panopoly_demo module was the only module providing default content. Actually, we have Panopoly Demo, Panopoly News and Panopoly FAQ that all provide their own demo content.
Comment #1.0
mrfelton commented.
Comment #2
mrfelton commentedComment #3
lsolesen commentedWhat about extending the demo behat test to test what needs to be tested to be able to commit this? @mrfelton Do you have a list of what should be tested?
Comment #4
mrfelton commentedWell, the test would be to check that the various pieces of demo content are created properly when the demo module is enabled, and removed again when its disabled. I can provide a more comprehensive list.
But also I feel that an important part of these patches that need to be tested before they can be committed, which I have not yet tested at all is what happens when a site on RC5 or earlier with demo content enabled is upgraded to the latest code. Does the demo content just disappear? is it properly recreated? etc. I haven't tested that at all yet. Not sure if the behat setup can help there though since its only set up to test new installs at this pointI think.
Comment #5
lsolesen commentedMight fix this issue also #2008186: Panopoly users, default config permissions, and panealizer static cache issue
Comment #6
mrfelton commentedThis was actually fixed before the 1.1 release. Seems this ticket wasn't closed out properly.