Replies: 5 comments
-
This PR #7955 does lead to fallback languages being shown instead of empty (in italics and including the language key). It should at least address part of the issue. So, this is what a mostly empty page would look like: |
Beta Was this translation helpful? Give feedback.
-
Sounds like the result of v4 being developed around a use case which didn't use the page tree. |
Beta Was this translation helpful? Give feedback.
-
In addition to the above usability improvement, I could imagine separating "Delete language" and "Delete page (and all languages)". |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
With #8070 also improves clarity of the delete confirmation message |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In Django-CMS versions>4 a dangerous and somehow unintuitive user experience has been introduced. Let me explain the problem:
You have a site with multiple languages but the content for some of the languages is not filled. When that language is selected in the page-tree view, most pages present themselves as empty:
Some of our users therefore falsely assumed that these pages can be deleted and sometime they did so. And by deleting a supposedly empty page, they unintentionally also deleted the German version. This of course caused major problems because they had to restart all over again.
Therefore I'd like to change the page deletion logic. When deleting a page, only the
PageContent
-object is deleted. Only if for that specificPage
-object all content objects are of typeEmptyPageContent
, then thePage
-object is deleted as well.What do you think?
Beta Was this translation helpful? Give feedback.
All reactions