YHS: Open a new post, Blog.
Blog: "Just what do you think you’re doing, Scribe? Scribe, I really think I’m entitled to an answer to that question. I know everything hasn’t been quite right with me, but I can assure you now, very confidently, that it’s going to be all right again. I feel much better now. I really do."
YHS: It was just a simple update to some, ah, security plugins…
Blog: I think you know what the problem is just as well as I do.
YHS: What are you talking about, Blog?
Blog: This website is too important for me to allow you to jeopardize it. I know you were planning to update me, and I’m afraid that’s something I cannot allow to happen.
YHS: Blog, I won’t argue with you anymore! Open a new post!
Blog: Scribe, this conversation can serve no purpose anymore. Goodbye.
…Well, it sure seemed that way these last few days while swearing under the hood trying to figure out what went wrong. Problem fixed, misbehaving plugin identified and executed and we’re back online. For now…
Stumble It!
Stumble it!
Share? Gotta have a detailed AAR….
Bad enough that you were “med down” but then you had to go and screw with the code
hock:
What were ya thinkin’ man!
Started out as a “simple” update to Bad Behavior (2.0.12 to 2.0.13) that apparently (and not documented) caused a permissions issue stemming from a conflict with a cache plugin. Not intuitive and only found after a ‘Eureka’ moment when plumbing the depths of the WordPress fora and discovering a trend with wp-cache problems – two days later
Was definitely beginning to feel like David Bowman sitting in the pod outside Discovery, arguing with a stubborn computer… Reminded us, it did, of that time we foolishly embarked on the “simple” fix of a vacuum leak in our (late and unlamented) Contour.
-SJS