I encountered an error while saving changes to a page in our installation of 4.5.2 this afternoon.
Since then, the Content tree loads normally, except that the page I was editing does not appear. I have tried:
reloading nodes - no effect
re-publishing the site from the Content node - no effect
re-publishing the parent page and all child pages - this gave an error part way through
The parent page shows the missing page when trying to do a Sort - so the page is still there, and it's just hidden from the content tree. And the public side of the page is still live, albeit without the changes I tried to make earlier.
As I can't access the page via the content tree, I can't perform a rollback, or try to edit the page again.
Any ideas on how I can get this page to re-appear?
Thanks for your reply. No, the document type is the most common one used across our site.
I've managed to get it back - looks like whatever error occurred on saving the page resulted in some orphan records in the database. I don't like making changes manually in the database, but I've done so here and removed all traces (I think) of the version which was partly created during the save. That has brought the page back, and I now seem to be able to edit it normally.
I have run into this issue a handful of times, and usually to fix I end up manually deleting the problem node from the database and having to recreate it. I am curious to know how you managed to keep it - do you happen to have the SQL statements handy still or know which tables you updated?
I'm glad I'm not the only one to have experienced this! My next step would have been to delete the node via the database, but instead I thought I'd try first just deleting the version of the node which was created when the initial error arose. That required deleting records in 2 tables - from memory (and please don't rely on this!) I think the tables were ContentVersion and Document.
After deleting the corrupt version, I was returned to the previous version of the node, which was displayed again in the Content Tree. I have since made the changes I needed to make to that page, and have saved & published them successfully.
Thanks Allan, will take a look at that next time (hopefully there won't be a next time!). I tried this once but was confused about how the versions worked in the DB. Did you have to do any updates or just deletes?
Yes, like you, I hope there won't be a next time. I didn't update any records, just deleted the ones which related to the corrupt version. From what I could see, the published version was still the previous version anyway (which explains why the old version of the page was still live on the website), but I did look to check whether that would need updating - and concluded in my case yesterday that it didn't.
Missing node in Content Tree
I encountered an error while saving changes to a page in our installation of 4.5.2 this afternoon.
Since then, the Content tree loads normally, except that the page I was editing does not appear. I have tried:
The parent page shows the missing page when trying to do a Sort - so the page is still there, and it's just hidden from the content tree. And the public side of the page is still live, albeit without the changes I tried to make earlier.
As I can't access the page via the content tree, I can't perform a rollback, or try to edit the page again.
Any ideas on how I can get this page to re-appear?
Thanks
Allan
Hi Allan
That's an odd one...
Is it based on an other document type than the other nodes? If so is the document type alias then containing some weird characters perhaps?
/Jan
Hi Jan
Thanks for your reply. No, the document type is the most common one used across our site.
I've managed to get it back - looks like whatever error occurred on saving the page resulted in some orphan records in the database. I don't like making changes manually in the database, but I've done so here and removed all traces (I think) of the version which was partly created during the save. That has brought the page back, and I now seem to be able to edit it normally.
Allan
Hi Allan,
I have run into this issue a handful of times, and usually to fix I end up manually deleting the problem node from the database and having to recreate it. I am curious to know how you managed to keep it - do you happen to have the SQL statements handy still or know which tables you updated?
Thanks,
Tom
Hi Tom
I'm glad I'm not the only one to have experienced this! My next step would have been to delete the node via the database, but instead I thought I'd try first just deleting the version of the node which was created when the initial error arose. That required deleting records in 2 tables - from memory (and please don't rely on this!) I think the tables were ContentVersion and Document.
After deleting the corrupt version, I was returned to the previous version of the node, which was displayed again in the Content Tree. I have since made the changes I needed to make to that page, and have saved & published them successfully.
Hope that helps!
Thanks
Allan
Thanks Allan, will take a look at that next time (hopefully there won't be a next time!). I tried this once but was confused about how the versions worked in the DB. Did you have to do any updates or just deletes?
Thanks,
Tom
Hi Tom
Yes, like you, I hope there won't be a next time. I didn't update any records, just deleted the ones which related to the corrupt version. From what I could see, the published version was still the previous version anyway (which explains why the old version of the page was still live on the website), but I did look to check whether that would need updating - and concluded in my case yesterday that it didn't.
Thanks
Allan
is working on a reply...