Default content broken with latest version of core
Follow-up in: #293
The RC1 release hit a major snafu with default content broken (paragraphs are not rendered) likely as a result of changes in the latest version of core.
As anyone on the team who has worked on generated and manually fixing up default content for our particular use case will know, this is a headache beyond belief at this moment.
Potential solutions are:
- Use a different solution such as YAML Content and redo all default/sample content.
- Troubleshoot the problem (which seems challenging as it appears the whole work around we had been using is no longer available).
- Determine what default content is actually required (for example the home page and the home page blocks) and what is more properly "sample content" and focus the solution on that. That would require:
- Re-exporting the default content so it is is in the new format (where it relies on local ids and uuids are no longer used) the default content.
- Make the home page feature required.
- Perhaps make one content type required (such as article) so that users can see one type and one set of promoted blocks.
- Remove all other sample content.