[MAGNOLIA-3429] DialogFile should be repository aware: Using LinkUtil (makes DataFileControl obsolete) Created: 01/Dec/10  Updated: 04/Dec/13  Resolved: 04/Dec/13

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

Type: Improvement Priority: Neutral
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File magnolia-module-data.patch    
Issue Links:
relation
is related to MGNLSTK-721 DialogDAM: Should be extendable for u... Closed
Template:
Patch included:
Yes
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   

The control file can be used in a context of data module itself or the DAM control again in the data module.

Because the control does not resolve the link by the repository it is stored in, the preview is not working when using within the data repo and not within website. There fore the DataFileControl was created.

using the LinkUtil for creating the link makes that obsolete, the repo is taken into account (see patch)
Code has to be checked for production quality, exceptions are not handled yet (TODO's in the code).



 Comments   
Comment by Christian Ringele [ 01/Dec/10 ]

The patch is created by eclipse with the data module name and not gui, but its the right patch. Just containing too the deprecated class of data module.

Comment by Jan Haderka [ 04/Dec/13 ]

DataFile and all other controls have been obsoleted by new UI framework introduced in Magnolia 5. Should you be affected by the problem described in this ticket in still supported 4.x branch, please request the fix under the terms of your support agreement (create a support ticket).

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