[MGNLRES-3] Css in separate workspace Created: 24/Sep/08  Updated: 29/Mar/22  Resolved: 15/Oct/08

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: mme_sprint2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLRES-2 Provide default role with access to l... 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:
Team: Nucleus

 Comments   
Comment by Magnolia International [ 24/Sep/08 ]

Couple of remarks (which you probably know already)

  • icons in the tree are missing ?
  • "do not show this page in the navigation" is irrelevant in this context
  • 1st column's name "Title" isn't really appropriate - Name would work better I think ?
  • there are a whole lot of translation keys that are not needed
Comment by Magnolia International [ 24/Sep/08 ]

Couple hints:

  • the tree currently creates nodes of type contentNode - but the RenderingFilter will only render these nodes if they are of type content.
  • we probably still want to go through the renderer mechanisms, so these nodes will need a template property
  • if the above is valid, then there's an invalid bypass for /layout/ in the cms filter subchain
Comment by Teresa Miyar [ 02/Oct/08 ]

There is a new workspace - layout that stores the css. Basic functionality is in place, might need to make more user friendly

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