EZP-26682: Add Content on the Fly Bundle in clean install #144
Conversation
To be able to more strongly advice people to use clean for install and upgrade* make sure it has same lavel of features, and the bundle is somewhat more stable now. *_Doc says people can use demo for upgrade but that causes issue whenever demo add new demo specific features and people merge that in on upgrade._
andrerom
changed the title
|
review ping @bdunogier @nicolas-bastien /cc @lserwatka |
This needs to go. Demo can't be used for anything except demo :) |
|
@dpobel any objection ? :) |
|
Sent the story to QA for testing. |
|
Please @andrerom could you provide me the source of this info. I would like to correct the doc.
|
|
@mere-teresa https://doc.ez.no/display/DEVELOPER/Updating+eZ+Enterprise (so it's the doc for enterprise, aka the platform flavor our customers use, and it states that you can choose yourself between clean or demo, but demo is not really suitable for upgrades unless we then explain all the possible issues you can get by doing that :) ) |
|
Seems QA approved, I reported only issue I know about (ballon showing "undefined" when content type description is empty): https://jira.ez.no/browse/EZS-1160 /cc @lserwatka |
|
@andrerom we will look into it later this week. Should be easy to fix. |
|
@lserwatka you can now merge up to studio, I'll take care about ezplatform-demo as the demos will likely give some merge conflicts now until resolved. |
To be able to more strongly advice people to use clean for install and upgrade* make sure it has same level of features, given the rewrite to integrate the feature is currently on hold.
This applies to ezstudio as well, and once this is merged it can be naturally merged down there.
*Doc on Studio says people can use demo for upgrade but that causes issue whenever demo add new demo specific features and people merge that in on upgrade. Note: On studio templates and config for landing pages is missing, so this is most likely the root cause for people using demo on upgrade.