[MAGNOLIA-8155] Resource mapping conflict is not detected Created: 27/Sep/17  Updated: 05/Apr/22

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: 6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: blocked, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File resources-not-detected.png    
Issue Links:
Relates
duplicate
is duplicated by PAGES-303 Subpages Created Under Pages With "Re... Closed
relation
is related to PAGES-145 Conflicting URI mapping icons are mis... Closed
is related to PAGES-149 Visual warning clue for context path Closed
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:
Story Points: 5
Team: DeveloperX

 Description   

We having a URI mapping for the resources workspace that is not being picked up. Most likely because of the custom mapping class used.

Consider to remove most of the mappings. It should be sufficient to just leave the website mapping there, remove others.

See: https://demo.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/server/URI2RepositoryMapping/mappings:treeview:



 Comments   
Comment by Jan Haderka [ 19/Dec/17 ]

please provide said custom mapping to reproduce issue.

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