[MAGNOLIA-407] intern link stored with contextpath in kupu Created: 25/May/05  Updated: 17/Mar/09  Resolved: 08/Jun/05

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

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: 0.25d Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: 0.25d Original Estimate: Not Specified
Environment:

it is not longer critical, but still important


Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-518 Use mgnl:uuid for internal links ente... Sub-task Closed Philipp Bärfuss  
MAGNOLIA-519 Use jcr:uuid instead of mgnl:uuid for... Sub-task Closed Philipp Bärfuss  
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:

 Description   

I guess this is the right place for this mail:

I'm using 2.1 revision 701 on two tomcat servers
author is named magnoliaA, and public mangoliaP
now, when using internal links within Kupu editor:
it adds context path and after publish links are not useful
ex. http://IP:PORT/magnoliaA/features.html in author
should be http://IP:PORT/magnoliaP/features.html in public

it's more of a installation concept problem
but i think you should consider it..



 Comments   
Comment by Philipp Bracher [ 01/Jun/05 ]

I moved this to a blocker: in fact this means that you can not run a author and a public instance in the same tomcat.

I will fix it first for fck (the new default editor)

Comment by Philipp Bracher [ 03/Jun/05 ]

I checked in the first steps

The link problem
================
The Html code is stored with uuids instead of links

  • in the interface (dialogs) are repository and user friendly absolute pathes used: /home/page
  • during storing all <a herf=""> tags are translated in a magnolia format containing the uuid and the original path.
  • the cms:out tag translates the magnolia format into relative links (uses LinkUtils).

LinkUtil
========
All the operations are done with the new LinkUtil which provides several transform methods.

Why can links still brake
=========================
The UUID stays not yet stable during activation (Sameer solves this problem). This means that the cms:out tag translates the links based on the stored original path. This can be changed easily after Sameer finished. After this we will never have a broken link again!!!!!!!

The browse dialog callback
==========================
I changed the repository browse dialog. Now it is possible to pass a callback object to the call. The objects callback(value) method is then called after klicking ok. This gives the caller mor flexibility. It mutch better than to add more parameters like addcontext, extension, ... Look at mgnlOpenTreeBrowser in general.js

The UUID problem
================
We can not use the UUID yet, because during activation there is no chance to get the same UUID as in the sender. This a also a big issue for jcr references. Sameer will add a property to nodes containing the UUID, which then survives the activation.

TODO
====

  • handling links in the fck editor
  • moving cms:out to the UUID mode
Comment by Philipp Bracher [ 06/Jun/05 ]

The LinkUitl uses now the UUID. Moving a page does not longer brake a link! Before closing a task i have to add this to the FCK editor

Comment by Philipp Bracher [ 08/Jun/05 ]
  • code for fck editor added
  • fck default is custom/magnoliaStandard.js
  • moved to fck version 2.0 fc
  • extracted some methods in the control.Save class
Comment by Michael Aemisegger [ 08/Aug/05 ]

The design of mgnl:uuid contains attributes that do not fit well into the design of jackrabbit. IMHO the 'namespace' of mgnl:uuid is designed too ambitiously.
If you really want to support the attributes 'repository' and 'workspace', then you'd have to ensure referential integrity outside of jackrabbit code. Jackrabbit only supports referential integrity inside a workspace of a repository but not outside the boundaries of a workspace nor a repository.

I suggest to remove the attributes 'repository' and 'workspace'.

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