Board Thread:Support Requests - Getting Technical/@comment-3218221-20170615123203/@comment-3218221-20170615131549

..........And there we go. Just purged the home page in the browser where I'm logged in, and voila, wiki menu.

Sigh. Seems like the cached incident has another takeaway, temporary as it may be: always ''suspect a cache problem. I didn't think it was cache related at first because it was so'' specific - affecting only three pages (at least, as far as I knew) - but then again that was also my thought process yesterday. Let me revise my earlier statement: ''even if it seems to be a very specific problem, suspect cache and try ?action=purge. ''

...At least for the time being. I've never witnessed such a delay in pages updating as I have thanks to the modernization rollout. Well, I assume the rollout is somehow correlated with the delay, because I most certainly did not experience this problem to such a degree before. And the incident yesterday affected a lot of pages - more than I'd initially suspected, in fact. And as TOR (Staff) pointed out, users having to resort to ?action=purge is precisely what Staff wants to avoid.

And yet...

Thanks for the responses - it's both a combination of embarrassment and frustration on my part that the cause was something I'd already experienced yesterday and should have recognized, but in the end I'm glad it wasn't something much worse. Not that the idea of users interacting with cached versions of wiki pages is particularly acceptable, but perhaps I should take solace in that it wasn't a "silly mistake" on my part that caused the hiccup.