[CONTEDIT-425] Investigate: I18n stories incompatibilities strategy (need to discuss with team) Created: 29/Sep/21 Updated: 28/Oct/21 Resolved: 28/Oct/21 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Antonín Juran |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | i18n Stories App | ||||||||
| Sprint: | Content Mngmt 14, Content Mngmt 15 | ||||||||
| Story Points: | 8 | ||||||||
| Description |
|
Copy from slack from mika. https://magnolia-cms.slack.com/archives/C0260UJMGPQ/p1632293443002100 Here is Mika' msg: The ideal case for us is to ensure that all stories in a workspace are consistent (no new & old model in the same workspace at the same time). Let's see if we can get there.
In other words my proposal is: only the pre-existing structure in JCR should drive which structure we save to => not the i18n property. This means: * If i18n is false and the workspace has the new structure, we save the indexed blocks under the blocks node (not the old way), transparently for editors.
|