Orphan Assets after Delete or Move/Rename

Erin's Avatar

Erin

30 Aug, 2011 09:14 PM

We seem to be struggling with a lot of orphan assets with our site. Anytime one of our site managers renames, moves, or deletes an asset without first/simultaneously unpublishing it, we end up with orphan pages. Is there a setting in the CMS we should be aware of to combat this issue, or some type of check we can run to ensure that the folder/file structure in the CMS is identical to the one that is actually being published? Many of these orphan pages are creating issues when it comes to our SEO efforts, as they are still live and being indexed but are full of old, broken links. We wouldn't even know that many of these assets existed if it weren't for some filtered reports we have running in Google Analytics and Google Webmaster.

We are still running version 6.4.6 if that makes a difference - we're hoping to move to the newest version soon.

  1. 1 Posted by Erin on 30 Aug, 2011 09:17 PM

    Erin's Avatar

    Note - we know how to delete the pages once they're found, it's more a question of how to combat this issue before we end up with orphan pages

  2. Support Staff 2 Posted by Tim on 31 Aug, 2011 02:46 PM

    Tim's Avatar

    Hi Erin,

    Currently there is no functionality in the application that will allow for it to synchronize with the web server. This is a very common feature request which you can vote/comment on here.

    Please be sure to read over all of the existing comments on that idea as well so that you are aware of the different approaches that are possible as well as certain advantages and disadvantages of doing this one way or another.

    The feature request linked above is currently ranked 1st in our idea exchange so it is definitely on our radar.

    Let me know if you have any further questions.

    Thanks!

  3. 3 Posted by cpayan on 08 Sep, 2011 08:06 PM

    cpayan's Avatar

    As far as feature requests go, one I've been thinking about is creating a subscription between formats. At the moment, if one imports another XSLT format, that external XSLT can be deleted and cause errors without any kind of error thrown. Whether or not it's done manually (a field where I can specify dependencies/subscribers) or automatically (detecting xsl:import and similar tags), this functionality would be nice.

  4. Tim closed this discussion on 01 Nov, 2011 04:29 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac