[MGNLRES-181] STK theme resources appear twice after migration to 5.4 Created: 16/Jul/15 Updated: 29/Mar/22 Resolved: 14/Jan/16 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Roland Polzer | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 10d 7h | ||
| Original Estimate: | 3d | ||
| 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)
|
||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | Saigon 26 | ||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||
| Team: | |||||||||||||||||||||
| Description |
|
After migration to 5.4 my theme resources appear twice under STK - Resources. Once with file extension and once without. The same happens for CSS, fonts, Images, Javascript (some, not all). Please see snapshot |
| Comments |
| Comment by Mikaël Geljić [ 11/Aug/15 ] |
|
Hi Roland,
On a side note, if re-installing the theme is an option, you may adjust your task in version-handler. Those install tasks typically take a stripExtension parameter (on by default), which you may now turn off. At least to me, it's unclear whether we can do something meaningful there. Rather take this as a helper/indication that there is inconsistency against the new resource loading cascade, and try to address those. Cheers, |
| Comment by Jan Haderka [ 09/Sep/15 ] |
|
OTOH in original resources you have extension stored as a property of the resource in repo so when migrating/upgrading to new version we should be able to bring it back into the name. Or am I wrong? |
| Comment by Sang Ngo Huu [ 26/Oct/15 ] |
|
I tried with approach using groovy script to rename name node with extension, Seem it works well. |
| Comment by Sang Ngo Huu [ 23/Dec/15 ] |
|
Update 23.12.2015
We also compare content in the case of resource already present in JCR with extension.
|
| Comment by Sang Ngo Huu [ 05/Jan/16 ] |
|
Update 05.01.2016
|
| Comment by Mikaël Geljić [ 14/Jan/16 ] |
|