[MGNLRES-230] Improve handling of masking JCR folders Created: 30/Sep/15 Updated: 29/Mar/22 Resolved: 15/Oct/15 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.2 |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ux | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 2d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| 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)
|
||||||||
| Epic Link: | Phase out in-place templating app | ||||||||
| Sprint: | Basel 14 | ||||||||
| Story Points: | 5 | ||||||||
| Team: | |||||||||
| Description |
|
The concept for the Resource files differentiates between folders, which can be edited (those created only in JCR) and those, which can't. However, we've discovered there's a third type of folder we have to handle separately. When I add a resource file under a non-editable folder (i.e. a folder from the filesystem or classpath), our current implementation also implicitly creates folders to map the existing folders also in the JCR origin. Such "masking JCR folders" can also be created explicitely - their characteristic is that they exist in JCR and that equally named folders with the same path exist in a read-only origin. As a result, such masking JCR folders are currently marked as editable, which is probably wrong: a user shouldn't delete them and (in the future) not move or rename them (would result in very confusing behavior). However, having a "publish with sub items" actions on such folders could proof to be very handy. Solutions I see are:
I've set the severity of this issue to "critical" as we* should resolve this before the next release* of the Resource files app, as the current behavior will cause confusion and lead to questions. |
| Comments |
| Comment by Andreas Weder [ 01/Oct/15 ] |
|
Comment from mgeljic on Hipchat:
|
| Comment by Andreas Weder [ 01/Oct/15 ] |
|
I've designed mockups for solution 1: https://wiki.magnolia-cms.com/display/UX/The+Resource+files+app#TheResourcefilesapp-Availableactionswhenselectingafolder |
| Comment by Andreas Weder [ 01/Oct/15 ] |
|
I've changed the term of these folders to "masking JCR folders", because - as Jan pointed out correctly - it's possible that such folders would also be created explicitely. |