[MAGNOLIA-73] Module for link checking Created: 27/Aug/04  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: New Feature Priority: Major
Reporter: Boris Kraft Assignee: Unassigned
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

A way to make sure that you have no broken links in your web page. This could be a module with its own interface that – similar to the global find/replace module – shows a list of all pages containing broken links, and allow to fix them right there.

This module could also register as a listener to the save event of a page and make sure that upon save, links are correct.

This module could also register as a listener to the move or copy event and update links if needed.



 Comments   
Comment by Boris Kraft [ 24/Nov/04 ]

More comments from Steve Loyd:

1) Links that re-link when structure is moved (this is a major headache for
hard-coded links or internally chosen links from the browse button)

2) Universal link objects that update everywhere throughout the site.
Basically, instead of having to go in and change all of the instances that
link to a particular site or location you can change the object and they
will all change. This is similar to the first point above.

Comment by Sean McMains [ 02/Sep/11 ]

I think our UUID links do a pretty good job of addressing this for internal links, but external links are still treated as one-offs. This has been a feature I've seen on a number of RFPs, so is probably something we should think about at some point, if only to be able to check it off on customer feature lists.

Comment by Boris Kraft [ 03/Sep/11 ]

I assume that once M5 is out the door we can start implementing reports - this here could be one of them.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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