You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2018. It is now read-only.
Reservoir provides a default article content type for demo purposes. Many (most?) production sites won't use this particular content type, so it should be able to be deleted.
The problem is that Reservoir creates a "hello world" article at install time. So using any sort of standard configuration management workflow, when you install the site (or immediately after you install the site) and you try to import site configuration (which would delete the article content type), the import fails because content already exists:
Entities exist of type Content and Content type Article. These entities need to be deleted before importing.
I think the best solution would be to make the creation of demo / dummy content optional (perhaps by creating a separate reservoir_demo module).
The text was updated successfully, but these errors were encountered:
wimleers
changed the title
Cannot install site after deleting article content type
Demo content types + content should be optional during the installation process
Aug 25, 2017
Reservoir provides a default article content type for demo purposes. Many (most?) production sites won't use this particular content type, so it should be able to be deleted.
The problem is that Reservoir creates a "hello world" article at install time. So using any sort of standard configuration management workflow, when you install the site (or immediately after you install the site) and you try to import site configuration (which would delete the article content type), the import fails because content already exists:
I think the best solution would be to make the creation of demo / dummy content optional (perhaps by creating a separate reservoir_demo module).
The text was updated successfully, but these errors were encountered: