V ersioning and Dependencies

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a version with a dependency on a certain template
2. In the new version, change the template
3. Try to delete the template used by the old version 

What is the expected output? What do you see instead?

* System indicated that the template was in use by the page, meaning the old 
version. 

Tracking dependent resources, like templates, is a "Good Thing" but it can make 
it can complicate refactoring a site to use fewer resources. 

It seems like we have three options 

(1) Do nothing. Either the resource must be retained as long as the version 
exists, or the prior version must be updated to remove the reference. (Removing 
the reference from prior version does work.)

(2) Revamp versioning so that it works more like Subversion (ugh). 

(3) Allow dependent resources to be hidden in the user interface (like columns 
on an Excel spreadsheet) and from the approved version. (If a hidden resource 
were used on the site, an error would be raised.)

My preference is (3).

Thoughts?

-Ted

Original issue reported on code.google.com by ted.husted on 1 Jan 2011 at 5:44

• Blocking: #403

[GoogleCodeExporter]

If someone doing refactoring then he need to clean pages first and finish by 
old template.

We can help author to track references to template from pages by providing 
cascading page delete or showing all referenced pages.

Original comment by kinyelo@gmail.com on 1 Jan 2011 at 8:22