Decommissioning sites - identifying shared files and other tips?

(Douglas (@finnatic at @waikato)) #1

We have a collection of sites with similar purpose, and the content from one (site A) has been partially copied across to another (site B ) which has led to a request to decommission site A.

 

The site editors have communicated that they don't believe they reused any images / files from site A on site B - but I'm wondering if there is a way to check that?  These are files which are under __data etc so I can't just grep the access log for requests for /siteA/

 

Also wondering what other tips people might like to share on decommissioning Matrix sites? 

(Bart Banda) #2

So does Site A and Site B have the same domain? So its like www.site.com/a and www.site.com/b ?

 

Anyways, if you move Site A to the trash you can then run a broken links report on Site B to see if there are any assets linking to assets in the trash. You could also try and turn safe trash on and delete big sections of site A (making it under construction first), and then seeing if safe trash will report errors that it can't move some assets to the trash because they've got live assets linking to them. 

(Douglas (@finnatic at @waikato)) #3

Yes, the two sites are on the same domain and hosted on the same server.  We have some obligations to preserve a copy of the site content, so what we can do involving trash might be limited.

 

What I've briefly done is make site A unavailable (under construction / archive status) and then run an external link checking tool (Xenu) against site B.  That turned up a number of images in site A that hadn't been migrated.