[MAGNOLIA-4699] Complete our mixins with mgnl:title & mgnl:mimeType Created: 30/Nov/12  Updated: 19/May/22  Resolved: 19/May/22

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

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

Issue Links:
duplicate
is duplicated by MAGNOLIA-5136 MetaData as mixin: discuss and decide... Closed
relation
is related to MAGNOLIA-4640 MetaData as mixin 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)
Date of First Response:

 Description   

for dialog and template definitions we should add something like: http://www.day.com/maven/jsr170/javadocs/jcr-2.0/javax/jcr/nodetype/package-summary.html#mix:title
for DAM/assets: http://www.day.com/maven/jsr170/javadocs/jcr-2.0/javax/jcr/nodetype/package-summary.html#mix:mimeType

Caution: fixing this issue will cause some migration effort.



 Comments   
Comment by Jan Haderka [ 30/Nov/12 ]

regarding mimeType I think we need to see how this is used by webDAV before deciding whether to use our own or jcr mixin ... actually I would prefer to stick to jcr ones unless we have good reason not to.
In both cases those props are not enforced and not mandatory. The only issue i see is with jcr: prefix in names that we normally filter out, which at least in case of mime type would be imho still ok.

Comment by Tobias Mattsson [ 03/Dec/13 ]

Should the mgnl:type in the title actually be mgnl:title?

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 03:58:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.