genesteinberg

This is tricky. After a log out or two once the manual upgrade is done, it did take on all but one site, where it required two stages of going through all these silly instructions.

But the problem is all due to sloppy programming on the part of the developer of the WP beta plugin. I’ve used it in the past without trouble. With 4.2 I had to go through all these hoops.

I’m even more concerned that the developer isn’t responsive to customer problems, which makes the situation even worse.

Unless things change, and the developer takes responsibility, I cannot recommend it to anyone.

Peace,
Gene

Just copying over the installation files doesn’t alter the database. The admin panel will just grab the developer version if it’s on that branch.

But I’ll try and let you know.

At least you’ve tried to respond. Too bad the developer of the beta plugin has been missing in action so far.

Peace,
Gene

I do not run caching plugins, because our server is set up for Zend Opcache.

But I did do the other stuff and will wait to see what happens.

What about just doing a manual install after all this is said and done, since there probably won’t be another stable release for a while?

Peace,
Gene

A week later, and I hear crickets.

I’ve already done that (see second graph). No change.

Peace,
Gene

What is the conflict?

Same problem, and I see nobody is responding.

In my case, after the update to WP 4.2 and 4.2.1, I’m on a 4.3 alpha even though the plugin has been disabled, and WP has been reinstalled from the downloaded files.

So is there a solution?

This is a portly designed plugin. It should revert you to stable releases upon deactivation or that option should be added. FWIW: I didn’t have this problem with previous releases of this plugin.

Peace,
Gene

WP is up to date. The theme is custom, but one I’ve used for a long while without the recent troubles. I do not have access to the original developer, however, or to the person who did an update that allowed us to use widgets. phpMyAdmin repairs don’t seem to make any difference compared to using Lester Chan’s database plugin. I presume he’s using the same commands.

Are you suggesting something in the theme is making this happen?

Anyone care to look at it?

Peace,
Gene

After upgrading to Apache 2.4.4, I’m getting this:

Warning: preg_match(): Compilation failed: unknown option bit(s) set at offset -1 in /home/technigh/public_html/wp-content/plugins/wp-thread-comment/wp-thread-comment.php on line 544

If someone can’t find a fix, I’ll be forced to remove this plugin, for better or worse.

Hopefully not.

Anyone?

Peace,
Gene

OK, we’re good now.

Thanks.

Peace,
Gene

Maybe, but now it says:

Fatal error: Call to private PayPalDonations::__construct() from invalid context in /home/technigh/public_html/wp-content/themes/technightowl/single.php on line 47

Peace,
Gene

Never mind, I saw the Update notice. It appears to be properly functional at first brush, and I’ll continue to work with it this weekend.

Thanks for resuming work on this plug-in, which is one of my indispensables.

Peace,
Gene

Is it up or do you have a link for it?

Peace,
Gene

Well, they appear to be tone deaf. There is never a response to the ongoing problems.

Peace,
Gene

How did you try. Email? Phone? Why not just do it privately?

Peace,
Gene