Thanks for helping set up this partial fix and for providing a ballpark ETA around all of this - it’s all helpful.
Ok here’s what I’m seeing as I go through these steps:
I logged out and then logged back in and saw that the unknown slug modal is still there.
I did a restore back from 8/20 and unknown slug modal was not there. I was able to successfully make edits to the site without the crashing issue.
Now I am ready to publish and hope that everything works…
Everything works!
Thanks for helping get us safe and sound on this issue! Hopefully we don’t see this come back in any way. Is there any advice/information that you can give to help us avoid another one of these in the future? Much appreciated…
Thanks for letting us know the issue’s been resolved. Happy to hear everything is working as expected.
How can we avoid this happening again?
Is there any advice/information that you can give to help us avoid another one of these in the future?
In this case I’d recommend saving manual backups when you reach good stopping points as you design. Having custom restore points is definitely useful in situations like this. It goes without saying that we definitely don’t want or expect this to happen again. Just in case though, our team has put fixes in place that should prevent CMS data from being affected if a similar issue were to happen again.
The very best thing you can do in situations like this, is what you’ve all done already — provide quick and detailed updates about any issues you are experiencing. This way our team can quickly resolve these for you.
Thanks again for your help and patience throughout these CMS issues
