There seems to be a caching bug in Wikidot.
Firstly, the page revisions being displayed at the bottom of the screen was the second newest (not the newest).
Secondly, any pages that included this particular page, included the source code of the second newest revision (not the newest).
Thirdly, when I went to delete the page permanently, I am stumped with this “Please Try Again” BSOD message with “ ERROR CODE: EX200”
Fourthly, when I go to create a new page elsewhere, and rename it to my old page's name, I get the message “page already exists”
After a few minutes, the page became accessible and was deleted, and everything worked fine again.
This is just an error report. Here's the problem in action:
Click to play |
Yup, there is definitely a caching bug. It's doing the same thing again, and I've repeated the process above.
I ran into similar problems yesterday, but thought it was database corruption. I renamed a page I was using for my theme's css. I then went to recreate the old page name, but with a different theme. Things got wacky when the content of the renamed page was showing up on the newly created page (that had totally different content when I saved it). When I tried to rename page 2 to something else, it displayed the page name for page 1. At that point I thought a database table was screwed up. Before contacting support, I decided to completely delete all pages and recreate them. That seemed to work, but after hearing James' reports, I think I was lucky that I let some time pass between deleting and recreating the pages.
Community Admin
Posted up a video of the problem as it occurs right now.
Thanks, we nailed the problem. Now working on a fix.
Michał Frąckowiak @ Wikidot Inc.
Visit my blog at michalf.me
Yay!
Please verify it's back working now.
Piotr Gabryjeluk
visit my blog
Sort of…
I mean, you may need to flush the cache or something, because some pages like this one can't be edited/created.
Am I using the correct terminology? “Flushing the cache”?
But apart from the already affected pages, everything seems to be fine again.
Could you try now?
Piotr Gabryjeluk
visit my blog
Fantastic! Thankyou very much!