safari error with wordpress
- October 30th, 2015
- Posted in Uncategorized
- Write comment
I haven’t been able to solve this problem yet, so I’m throwing it out to the world. I’d throw it out to Apple Support forums, but they’re apparently doing something to them (and have been for the last few days) and they won’t let me post – I get a backend-under-renovation notice whenever I try to log in.
100% of the time, I can reproduce this error when I try to edit the timestamp of a comment in WordPress. It happens literally every second time I try to make such an edit:
It also happens when saving or editing posts. Not every time, but enough that I’ve started saving posts in the paste buffer so I don’t lose them. It will also reproduce on other WordPress administrative pages involving post or comment edits – commits, really – enough that it will happen during most sessions. If you search, you’ll find other people are experiencing this as well; it’s been going on since at least Mavericks.
It does not reproduce in Firefox on the same machine, at the same time, under any circumstances. There have been multiple posts to Apple support communities about it, but none of the solutions offered – solutions which did fix it for those posters – fix it here. That includes deleting all saved website data, disabling all (non-Apple) extensions, disabling all plug-ins, deleting add-on input methods and scripting additions (of which I had one of each), everything here.
But the one thing I have found is that it does not reproduce in safe mode. At all. Something specific is causing this.
Ideas, anybody?
Looking for the Grammy Awards Long List nominee post? Thank you for listening, and for your consideration.
I may have found it. Editing this comment is another test.
So far I can’t reproduce the problem anymore. That’s not proof in the sense I like it, but it’s looking pretty good.
Yeah, I think I might’ve got it. The fix survives across Safari restarts. Still no repro anymore.
ETA: IT IS NOT FIXED. Goddammit.
What did your fix end up being? I’ve seen similar behavior before, but mine was always solved by fully clearing all cookies and cache.
So basically, it’s been a combination of individual fixes that worked for other people, but none of which worked for me individually.
I think what happened is that I had browser extensions which had corrupted some of their internal data, and which were also corrupting cache data. This would be why clearing cache data – the most common successful fix for this – never worked; the new cache data would be re-corrupted immediately.
So, how I got here and what I did:
I didn’t mention in the post above that I had also been having two other problems with Safari recently. That’s because I got both fixed yesterday. They were:
Both of those problems vanished when I disabled three browser extensions: SocialFixer, ClickToFlash, and AdBlock. And they stayed gone when I re-enabled those extensions. (I then also did an upgrade of two, which had upgrades pending.)
Sadly, that didn’t fix the WordPress problem. Neither did other things I did:
But.
After doing all that, I decided to delete website data again, because I know it’s something specific, because booting to safe mode stopped the problem from reproducing. And I did it just for the wordpress blog, and not for anything else.
And so far, that’s done it.
If it holds up, I’ll consider my hypothesis supported.
Josh: Your comment question came in while I was editing up that description of what I did. But it looks like I answered you specifically. HA!
But yeah, that’s what I did. So, hopefully it’ll stay fixed.
Aaaaand it didn’t. It’s not fixed.