[MAGNOLIA-6302] Less items in Magnolia menu after changing to 5.4 Created: 15/Jul/15  Updated: 19/May/22  Resolved: 19/May/22

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

Type: Improvement Priority: Neutral
Reporter: Dominika Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.4


Attachments: PNG File magAfter.png     PNG File magBefore.png    
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:

 Description   

After updating Magnolia version in Maven to

<magnoliaVersion>5.4</magnoliaVersion>

Magnolia menu has less items.
Before:
After:

Is this as intended? Do we need to manually configure that menu? Should the new Resources app be visible at least?

Additionally we have moved resources in our custom app jars to the new path "src/main/resources/<module-name>/resources/something.xyz" but they are not being picked up, so we think we must do something more to migrate to 5.4 but we could not find anything in the documentation. Please could you help or refer us to correct project for help?



 Comments   
Comment by Jan Haderka [ 16/Jul/15 ]

Hi,
if you look on the demo instance at http://demoauthor.magnolia-cms.com all the icons are still there so it is most likely caused by the declared dependencies in your build. If I was to guess, previously you had admin-legacy module pulled in via STK and it is no longer the case so you will need to declare it explicitly. If that doesn't help, you might want to run mvn dependency:tree before and after the change to 5.4 and see the differences in modules pulled and those that are missing add explicitly.

HTH,
Jan

Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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