I dont think deleting a parent page really does delete the children
Permalink
hi there so I had a panicked phone from someone today who had very cleverly managed to delete a parent page with a lot of children and therefore lost all the pages (there are various forum posts about this issue) anyhoo after I said 'oh dear' I did some playing around and found the the child pages were still browsable (although not showing in sitemap/navigation).
I tested this in browsers on machines that had never visited the site before (so couldn't have cached them)
(using fake urls to spare their blushes) but basically:
say they had
abc.com/section1/subsection1/
abc.com/section1/subsection2/xzy/
and they deleted /section1/
I could still browse to
abc.com/section1/subsection1/
abc.com/section1/subsection2/xzy/
but could no longer browse to abc.com/section1/
so I'm thinking is it that children are deleted or is it actually the case that without the parent page the sitemap/navigation just simply doesn't know how to represent them and show them to you (after all the db has not explicitly been told to delete the child pages)?
And if this is the case might be it possible to expose them again with some code tweaking so you can access them again?
I don't know nearly enough about the backend workings of c5 to know the answers myself but it might be worth someone looking into(?)
I tested this in browsers on machines that had never visited the site before (so couldn't have cached them)
(using fake urls to spare their blushes) but basically:
say they had
abc.com/section1/subsection1/
abc.com/section1/subsection2/xzy/
and they deleted /section1/
I could still browse to
abc.com/section1/subsection1/
abc.com/section1/subsection2/xzy/
but could no longer browse to abc.com/section1/
so I'm thinking is it that children are deleted or is it actually the case that without the parent page the sitemap/navigation just simply doesn't know how to represent them and show them to you (after all the db has not explicitly been told to delete the child pages)?
And if this is the case might be it possible to expose them again with some code tweaking so you can access them again?
I don't know nearly enough about the backend workings of c5 to know the answers myself but it might be worth someone looking into(?)
Hmm interesting. Could be the Concrete5 cache keeping those pages in the /files/cache directory as well...
Deleting a parent page definitely deletes child pages. I deletedhttp://mytestsite.c5host.com/index.php/search/... and it removedhttp://mytestsite.c5host.com/index.php/search/... and the child pageshttp://mytestsite.c5host.com/index/php/search/search-results...
I do wonder if an add-on is perhaps canceling the delete process midway, in some way.
I do wonder if an add-on is perhaps canceling the delete process midway, in some way.
hmm will do some more testing of this :)
also I wonder if there is a way of forcing c5 to not be able to delete a page with children? That would be very useful....
also I wonder if there is a way of forcing c5 to not be able to delete a page with children? That would be very useful....