intern link stored with contextpath in kupu
(MAGNOLIA-407)
|
|
| 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
Solution A
Solution B
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 |