I just noticed that we are enabling 'defaultcontent' in panopoly.info. We should stop doing that! It's still in our make files because we can't really remove it without breaking existing upgraded users - but we certainly shouldn't be enabling it by default.

Comments

caschbre’s picture

caschbre commented

Isn't there a step in the install process to allow the admin to add demo content? Maybe it would make sense to take it out of the .info file as required and have the install profile enable it if they choose to add demo content.

mrfelton’s picture

mrfelton commented

defaultcontent is actually no longer used by panopoly as it now uses migrate to add the demo content for each app. I think we should remove defaultcontent entirely as it is not the approach that we are recommending to handle demo content any more.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented

I'm with @mrfelton! We worked pretty hard to stop using 'defaultcontent' for demo content, the fact that it's in panopoly.info just slipped our minds. :-) I'll commit this change once I get through some of the heavier stuff I'm working on right now.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Status: Active » Fixed

Commited: http://drupalcode.org/project/panopoly.git/commit/f42c2ac096a241e6d861b3...

Good riddance! :-)

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Related issues: +#2105503: Implement demo content via Migrate instead of defaultcontent

Added a relation to the issue where we replaced our use of 'defaultconfig' with 'migrate' for future reference: #2105503: Implement demo content via Migrate instead of defaultcontent

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.