[MAGNOLIA-9185] Resource Files App no longer listing Theme Files Created: 13/Nov/23  Updated: 13/Nov/23  Resolved: 13/Nov/23

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 6.2.38
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Daniel Einars Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tomcat 9.0.65
Magnolia: 6.2.38


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:

 Description   

As mentioned in https://jira.magnolia-cms.com/browse/MAGNOLIA-9175, I'm opening a support ticket here because the issue is still persisting for us.

Steps to reproduce

  1. Module Folder Structure:
    Module-Name/src/main/resources
      /Module-Name: contains templates, dialog configs etc
      /Module-Name-Theme: contains JS/CSS/Fonts etc.
  2. Navigate to Resource Files App

Expected results

  1. Filter by "css" or "js" and be able to patch any files

Actual results

  1. Filter by "css" or "js" and see that the JS/CSS files from the theme are no longer listed here

Workaround

  1. Navigate to JCR App
  2. Select Resources workspace
  3. Add root node of type mgnl:folder with same name as Module Theme Folder (module-name-theme)
  4. Navigate to Resource Files App
  5. See that the folder containing the theme files (css, js, fonts etc.) is now visible in the Folder Tree
  6. Filtering by "CSS" or "JS" now lists these files again and I am able to patch them.

Development notes

The last working version for us was 6.2.26. Upgrading to 6.2.40 from 6.2.38 does not fix the issue.



 Comments   
Comment by Daniel Einars [ 13/Nov/23 ]

Whoops. I actually wanted to open this issue in the SUPPORT project, but accidentally opened it here. Can someone move it to the support project or close this ticket and I'll open a new one there?

Comment by Jonathan Ayala [ 13/Nov/23 ]

Hi Daniel,

No problem, the ticket has been closed. You can now open a support ticket instead.

Regards,

Jonathan.

Generated at Mon Feb 12 04:39:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.