pcvip

OK, so … as you’re running on a “dedicated cloud server” (hmmm … there’s really no such thing …), I’ll just translate that as “you are using more server power than most people do”. Appreciate the specificity!

But the rest of your answer kind of contradicts itself. I REALIZE you’ve created your own set of tables and pointed that out in my original question. I applaud this, as well; if ever your plug-in is uninstalled getting rid of it would be simple. BUT: what I was trying to understand is just what kind of a server hit having that structure imposes, and also what kind of hit YOUR very large metatable will result in … and when?

Hey Jan.

There was no 500 error per se, although I supposes WSOD IS one, right?

The fix turned out to be … get ready for this one … that a required plug-in which accompanies the theme (and which had been installed, internal to WP by following the instructions that popped up) wasn’t the correct version of the plugin.

So the good news is that once the developer ‘fessed up and provided the correct version of the plug-in, this was automagically resolved. The bad news, of course, is that it leaves me speculating about how such an error could have snuck by in the first place. That said, Ultra is a new theme and it’s entirely possible I was the very first person to flip it OFF.

Frustrating, though.

My apologies for not remembering to come back in here and updating the case. PRESUMABLY whatever was wrong (other than the postmeta thing above, which I maintain is a very bad idea) is now OK.

Thanks!

Hugh, I get that “it’s working as long as … ” qualifies as “issue resolved”. AND: new posts are picking up none of that silliness; I need to fill them in to make them work (which isn’t as god as magic, but I can’t argue with right?).

My concern is that something in your software scanned the posts, SAW .mp3 files, and attempted to fill data in but got it wrong. And while that’s an intellectual puzzle that you might not be interested in solving the issue is “it goofed this up once, what’s to stop it from goofing something else up?”

Also (to my original question, actually), since there is something in there that filled in the boxes but the concatenation was comprised of at least one string that simply doesn’t exist (I’ve pored over the database and especially the postmeta table), Shouldn’t we both care ?

Just sayin’ …

Rich, I want my site to be as inclusive … AS I WANT IT TO BE, not as inclusive as WP decides it should be, and doesn’t disclose the change.

Not OK. Not OK, Not OK.

Alessandro, I can’t understand why you don’t see what I’ve described, but … we can stop.

@wpyogi; thanks for your input

Jeremy, I appreciate your wording and thank you for leaving “seems to” in the conversation. ALLOW ME TO POINT OUT that wordpress.domainname.com is NOT a violation.

I’ll take this offline, as you requested …

Hmmm.

I use Wordfence for security, and also run a couple of user filtering plugins, but there genuinely doesn’t seem to be anything in any of them that should be blocking xml/rpc.

(and yes, of course trackbacks are “enabled” … I did check for you, though) 😉

Your security question is well taken, though: now once again … all worked until this version of Jetpack, so … I don’t think that’s it UNLESS there’s something in Wordfence that is naturally at odds with the latest JP update. Any broad thoughts on that or the need for “extra” security, to begin with?

BTW: the caching add-on in Wordfence is spectacular, AND compatible with everything else I have running, so if possible I’d like to keep using it!

And again, I can replicate/fix/break by disabling/re-enabling Jetpack …every time. I’m just … stuck!