Temlakos

FlexiThemes’ support team got back to me an hour ago. They have reached out to your Core team. They also have promised a quick rewrite of their theme that should be out any time. Bottom line: they’re working on it. “A backward-compatibility problem,” they said.

They also confirmed that the Downgrade plugin is a good fallback in case any further backward-compatibility issues arise.

Which version of PHP do you recommend? Their Changelog tells me they’re already up on “PHP 7 compatibility issues.” I’m using PHP 5.6, which my host tells me is the latest stable version. True? Or false?

Well, I have four sites back under WangGuard’s protection–and one other thing I did was to establish separate API keys for each, instead of using one key across sites.

In one case I had to run the Wizard, since I had so many not-checked registrations.

One thing I notice, though: a lot of sploggers slip through before the get reported somewhere else. I always check, recheck, and double check a new registrant (except one I know personally) over several days.

I don’t even get that much. The servers are out of reach and my keys have now been erased.

Apache. That makes sense. It’s the most serious technical problem a Web server can have.

A follow-up: any time a site says, “If you are the owner, contact your hosting provider,” that makes me suspect the webmaster’s host just served him with a virtual eviction notice for nonpayment of rent.

Mr. Conti:

Your domain shows what looks to me like a suspension page. Your site is advertising to all the world that you didn’t pay your hosting bill. This link:

https://wangguard.com/cgi-sys/defaultwebpage.cgi

is the resolution of “wangguard.com” and starts with the word SORRY in 72-point sans-serif gray boldface.

Also: it would appear that I’ve lost my API key on at least one of my servers. The message I get back says the key is now cleared.

Will I be able to get that API key back? Or must I re-establish one?

Let me get this straight:

Subscribe2 broke Jetpack stats. Someone wanted to kill Jetpack comments, and they killed Jetpack stats instead. Of all the stupid, careless errors a coder could make, this is the worst in a long time.

I suppose we have to keep this link handy in case, the next time someone pushes an update to subscribe2, he fails to catch these errors.

Now what? One of my sites just got its stats back. It was the site that had the least number of visitors, and I have no reason for one site to come back while the others didn’t.

The whole module’s gone. It does not show on the list of modules for Jetpack. It has vanished from Screen Options for the Dashboard.

Well? What’s WordPress going to do about it? It’s not like them to discontinue a feature so many of us have come to love, and give all the “business” to outside plug-in developers. Are we supposed to rely on Google Analytics from now on?

If I set “number of recipients = 1”, wouldn’t that mean that only one notice would go out, no matter how many subscribers I had?

Tim: I’m happy to say by now that the problem is now resolved.

I was using an obsolete version of Firefox. Way obsolete. Like–Version 3.6 instead of the Version 16-plus that’s out now.

When I upgraded to a new operating system (had to do a “clean install” to do it properly), I got a far more current “build” of Firefox. And it put the Stats graph into the right place.

I’d been having several browser issues, including the visual editor not wanting to load. I had a friend who had the same problem. But she also was using a long-out-of-date OS, and probably the browser, too.

I not only installed current versions of OS and browser, but also changed architectures, from i686 to x86_64. I played a hunch, and it paid off.

A few plugin upgrades have exposed a serious issue in the file wp-includes/capabilities.php. The file never includes the file pluggable.php, that defines the function wp_get_current_user(). The WordPress Amazon Associate plugin just crashed a few sites (including mine) by calling this function, only to find that it was undefined!

To make WordPress aware of the definition of that function, add this line:

require_once(‘pluggable.php’);

to wp-includes/capabilities.php. Add it directly after the first comments and before any class or function definitions. That will repair all issues about calls to an undefined function for getting the current user.

Someone needs to get this out right away, and push another update.

The resolution:

require_once(‘pluggable.php’)

Add this line to the file wp-includes/capabilities.php. Add it directly after the initial comments and before the first class definition.

WordPress needs to get on this right away. How many other plugins are going to crash WordPress in just that way? This was an accident waiting to happen.

All right. That works, and I reinstalled WPAA (after having to delete it to allow WordPress to function).

Memo to www.remarpro.com: this is a fatal omission in capabilities.php. Somebody needs to fix this and push another upgrade right away.

This topic is resolved, but the resolution will require a more basic fix.