-
Improvement
-
Resolution: Done
-
Neutral
-
6.2.8
-
None
-
Empty show more show less
-
Yes
-
UI FW 32
-
3
Steps to reproduce
- Define 50 languages in a site
- Open a dialog in that site (e.g. a page properties dialog)
Expected results
- The dialog opening is as fast as I'd have one language per site as I want to edit just one or few languages, not all of them.
Actual results
- It takes a visibly long time to open the dialog.
Workaround
There doesn't seems to be a viable workaround except reducing number of languages.
Patch for M6.2.9
<dependency> <groupId>info.magnolia.ui</groupId> <artifactId>magnolia-ui-framework</artifactId> <version>6.2.9-MGNLUI-6724</version> </dependency>
Development notes
The form fields are created in 50 variations in memory.
- we can create it just for the current language
- add next variation on language switch
- what about validation, do we need to/should we validate untouched languages?
Acceptance criteria
- is causing
-
MGNLPN-564 Preview As Visitor unusable if JVM default language is not plain english
- Closed
-
MGNLUI-6857 Cannot update only non-i18n fields
- Closed
-
MGNLUI-6880 Cannot save dialogs in another language when required fields in default language are empty
- Closed
- is related to
-
MAGNOLIA-7993 Improve throughput and performance under stress
- Selected
- mentioned in
-
Page Loading...