[MGNLSD-88] 'Browse Server' provides wrong internal link for moved pages Created: 30/Nov/06  Updated: 17/Mar/09  Resolved: 08/Dec/06

Status: Closed
Project: Sitedesigner (closed)
Component/s: None
Affects Version/s: 1.0 Final
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Chris Allan Assignee: Philipp Bärfuss
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSD-83 Navigation: Using Start Path, rather ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When inserting a link to another page in your site, and using the 'Browse Server' option which shows you a tree of your site, and allows you to select the page, it quite often gives incorrect links (this is the same whether you do it from a Text & Image paragraph, or a Link paragraph). This seems to only happen with pages which have previously been in a different location, and have been moved. The link which the 'browse server' option gives you appears to be the correct link (the path it shows you after you select your page is correct) but when you save and close the paragraph, the link actually points to the old location of the page and is hence broken.

I believe this is related to another issue I have reported with the vertical navigation paragraphs, in which specifying the root node numerically works fine, but when selecting it via the 'browse server' option, results in the behaviour described above.

The ability to link between pages is fundamental to any website - FIX IT!!!



 Comments   
Comment by Chris Allan [ 30/Nov/06 ]

Is there a way to update an issue?

Anyway, with regards to the above problem, it seems that not using the 'browse server' tree view, and manually typing out the path still results in the same problem - not pointing to the location it's supposed to, and instead pointing to an old location.

Comment by Chris Allan [ 30/Nov/06 ]

Additionally, when creating links on the root node of the site, titled 'Home', links annoying become /Home/Home/ASectoin/somepage.html i.e. 'Home' is inserted twice, again making any links broken

Comment by Tom Wespi [ 01/Dec/06 ]

Hello, i tried to reproduce this issue with

  • Enterprise Edition 3.0
  • Sitedesigner 1.0
  • running on mac os x 10.4 with tomcat 5.0.28
  • Berkley DB

but everything seem to be ok.

Can you please send information about the system you use (java version, operation system, magnolia version, database), so we can set up a test server.

Thank you

Comment by Boris Kraft [ 04/Dec/06 ]

Since we cannot reproduce this issue on a new installation, its not considered a blocker.

Comment by Chris Allan [ 07/Dec/06 ]

Hi,

Firstly, appologies for the slight abruptness of the original post, it is just a rather annoying problem.

Secondly, (I've mentioned this to Boris previously) I still receive no emails to inform me of any comments on my issues (hence the lengthy delay in my response to the comments)

Thirdly, I will get Bill to post back here with the precise details of our setup. I know he has one or two thoughts on what may be going wrong, so will ask him to detail these too.
There are no further details that I can give really as to how to recreate the problem - it is 100% guaranteed to give you a broken link on a recently moved page, with our setup and version.

Chris

Comment by Bill Pulford [ 07/Dec/06 ]

Hello Tom,

the information as requested

  • Enterprise Edition 3.0
  • Sitedesigner 1.0
  • running on Windows server 2003 + tomcat 5.5.20
  • DB as delivered with the release.

Bill Pulford

as a note this is a bit of a hassle currently!

Comment by Chris Allan [ 07/Dec/06 ]

Ah, I have just received emails informing me of the last two comments - that problem solved at least (presuming the same will happen when one of you guys comments ...)

Comment by Chris Allan [ 07/Dec/06 ]

There is a get-around for this problem that we've discovered - maybe it will help you understand the nature of the problem more.

If instead of moving the page, you copy the page to a different location, and create the link to this page, the link does work - it does point to the correct, new location. You can then go to the file in the orinigal location, delete this, and the link that you just created still successfully points at the new location.

Obviously this is quite a hassle though ....

Comment by Philipp Bracher [ 08/Dec/06 ]

Copy creates a new uuid for the page, where the moving keeps it. Perhaps we have a jcr session updating problem during the moving. This would explane it.

Can you restart our instance and check if you get this behavior again. I think you will get rid of this afterward if not, it takes a bit more investigation.

Only to be sure: we are talking only about the author instance (no activation included into this process)

Comment by Chris Allan [ 08/Dec/06 ]

Yes, after moving a page and suffering from the described problem, restarting Magnolia (well, restarting Tomcat) does indeed correct the link, and make it point at the new correct location.

Sounds hopeful then ....

Oh, and yeah we are only talking about the auhtor instance

Comment by Philipp Bracher [ 08/Dec/06 ]

Thanks for testing.

The thing is that a fix maight be hard to find, but I created a bug report MAGNOLIA-1263. Let me know if this happens again.

Comment by Tom Wespi [ 08/Dec/06 ]

see MAGNOLIA-1263

Generated at Mon Feb 12 10:55:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.