intern link stored with contextpath in kupu (MAGNOLIA-407)

[MAGNOLIA-518] Use mgnl:uuid for internal links entered through the link control Created: 08/Aug/05  Updated: 23/Jan/13  Resolved: 26/Jan/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.1 Final
Fix Version/s: 3.0 Beta 1

Type: Sub-task Priority: Major
Reporter: Michael Aemisegger Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.25d
Time Spent: Not Specified
Original Estimate: 0.25d
Environment:

all


Template:
Date of First Response:

 Description   

Links entered through the link control (i.e. not entered through any rich edit control) should be treated the same way as for rich edit controls

Unfortunately, the hidden SaveInfo form parameters do not tell what kind of control type was used to enter the data. What about adding this info to the SaveInfo parameters?

Then, it would be easy to test on the control type and replace the hardcoded path with the internal magnolia link format.



 Comments   
Comment by Philipp Bracher [ 08/Aug/05 ]

I would like to avoid this SaveInfo stuff. But since we did not yet refactor the save mechanism we do not have a choice. Adding the control type in general would help a lot.

Comment by Philipp Bracher [ 09/Aug/05 ]

i tryied to add this in a short work and i found out that it is not so easy to do:

Reason
======

  • ControlSuper (basis control) creates the save info
  • the dialog controls (subclasses of DialogSuper) creates there own basis control (like a container)
  • the type name is defined in the config and belongs to the dialog control
  • the basis controls are also used independent of the dialog controls

Solution A
======

  • the base control can have an aditional save info (a list)
  • the factory set the registration name of the dialog control
  • the dialog control must add the registration name to all created base controls as an additional save info

Solution B
========

  • we wate for the real refactoring

I vote for B

Comment by Philipp Bracher [ 02/Nov/05 ]

Soon we will have the synchronized jcr:uuid on both side (the author and public). I will change this for the content/links.

Comment by Philipp Bracher [ 26/Jan/06 ]

jcr:uuid is now kept during the activation process. in the 2.2 code the jcr:uuid is stored in the HTML (with the fallback path)

Sameer is writing a converter for moveing old 2.1 content to 2.2

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