Bug #88823
closed
Re-introduce option to disable "Localization view" in list module and/or auto-disable it if only one language is configured
0%
Description
Since #82991 "Localization view" is always used in list module.
When working with localizations in a system, the option "Localization view" in the list module is a pre-requisite for all editors, for all installations without languages, the checkbox is not necessary.
To streamline this behaviour, the option is removed and the functionality is enabled BY DEFAULT.
If there's only one language defined, the fields "[Localization]" and "Localize to" waste precious space and should be removed.
Updated by Georg Tiefenbrunn over 5 years ago
- Related to Task #82991: Remove List module checkbox "Localization view" added
Updated by Daniel Windloff over 5 years ago
- Related to Story #82206: list module enhancements/bugfixes added
Updated by Georg Ringer over 5 years ago
- Status changed from New to Accepted
- Assignee set to Georg Ringer
Updated by Gerrit Code Review over 5 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 5 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 5 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Gerrit Code Review over 4 years ago
Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61372
Updated by Ian Solo about 4 years ago
- Priority changed from Should have to Must have
This is indeed a must have. As a constructive criticism, I suggest core developers to test with some editors on a complex multi-language website before removing useful features like this one.
Actually I'm on the List module, trying to sort 48 categories with 4 languages, it's nearly impossible.
Updated by Sybille Peters about 4 years ago
- Related to Bug #87901: Regression in TYPO3 v9: Mass-edit of localized records in List view added
Updated by Sybille Peters about 4 years ago
- Tracker changed from Feature to Bug
- TYPO3 Version set to 9
- Is Regression set to Yes
Updated by Ian Solo over 3 years ago
- Target version set to Candidate for Major Version
- TYPO3 Version changed from 9 to 10
I changed this to TYPO3 10 and candidate for major version hoping to give it more attention.
Removing the option "Localization view" did lowered a lot the usability of the backend when there are many records and many languages.
In my use case they aren't even so many (just ~50 records with 4 languages) and it's already nearly impossible to manage the list.
As a side note: when I use TYPO3 as an editor I find many annoyances which I'm sure the developers don't realize because they don't use the backend enough as editors with complex websites (many images, many pages, many records and languages and so on) and I think that this issue should be handled seriously in some way because the experience of the editors is very important for the success of a CMS.
Updated by Sybille Peters over 3 years ago
@Christian
because the experience of the editors is very important for the success of a CMS.
see also Theme-based roadmap with 3 major goals, one subgoal of which is "Improved Editor Experience"
Make TYPO3 Easier to get started with and use
-> Improved Editor Experience
- https://typo3.com/blog/introducing-a-theme-based-roadmap-for-typo3
- https://typo3.com/blog/introducing-a-theme-based-roadmap-for-typo3#&gid=lightbox-group-8834&pid=0
This is a little off-topic - but I also find editor UX very important. And I think this should be looked as a whole and not just as individual issues.
I don't know if the issues are priorititzed in any and what might contribute to an issue or topic getting bumped up in priority or importance.
Also what might be helpful if there were an iniative or a component merger for backend / editor UI or backend / editor UX - which there is currently not - not any component merger for backend UI / UX or editor experience at all, see Component Mergers or Initiatives
Maybe someone has a better idea of how to move forward with this general topic or get it on someone's radar.
P.S. If you find something lacking, see if there is anything you can do to help. There are some positive examples of initiatives where the topic was important to an individual or a group and they just started and worked on it and it evolved into an initiative.
Updated by Sybille Peters over 3 years ago
@christian
Another thought. Because you wrote:
when I use TYPO3 as an editor I find many annoyances which I'm sure the developers don't realize because they don't use the backend enough as editors with complex websites
same thing here. I work at a university with a large university website. I don't work as editor normally, but I sometimes have to reproduce problems or find solutions when editors report problems.
I have thought about conducting survey or doing something like usability tests with our editors for the TYPO3 backend (and of course also our custom adjustments). However, I have very little experience with this. But if someone would like to exchange knowhow and brainstorm a little with me, please contact me on Slack.
Updated by Benni Mack about 3 years ago
- Related to Task #94794: Hide "Localize to" column if all records are already localized added
Updated by Benni Mack about 3 years ago
- Status changed from Under Review to Closed
Version 11 now does not show the "Localize to" feature anymore if there is only one language. We also want to improve this in v12 ("Show me records only in DE, DK and FR" in list module and page module), but I will open up another ticket for this.