foxglove16

Yes V9.0.0 took my site down completely. I had to delete the plugin from the back end and I just reinstalled V8.9.3

Not great as I updated to V9.0.0 because I got a message in my WordPress Dashboard strongly advising me to upgrade to V9.0.0 as a security issue.

Really surprised that testing of V9.0.0 has been so poor. Looking around the chat rooms it seems to have taken hundreds of WordPress sites off-line. Would be great to hear a few words from the author on what went wrong? And can we see something on the plug-in home page to advise folks who have been caught out.

Hi Emily

I don’t know why but https://aboutdereham.org/xmlrpc.php has started working again.

I found that I had to disconnect and then reconnect my site to my account and then access to the social sharing settings appeared again.

So all is working again. Thanks for your help.

Regards

Robert

Hi Gaurav

The site url is https://aboutdereham.org/

A example of a post which triggered the Jetpack social media sharing to Facebook is https://aboutdereham.org/event/mnfhs-meeting-the-history-of-the-rspca/

Regards

Robert

Hi there

Sorry I missed your first reply.

The easy part of your questions to answer is that the PHP Memory Limit is 1024M.

Your other question is more complicated but I will do my best:

The only part of Jetpack which we actively interact with is the sharing to social media facility, specifically when anyone posts on our site (it is a membership type site) then it is shared on Facebook, so that is most likely what triggered the error message from WordPress.

However I’m confused because although the post sharing to Facebook still appears to be working, I can no longer get access to the sharing settings. When I go to ‘My Jetpack’ then the ‘Social’ (Auto-publish to social media) is shown as being Inactive.

Then I see in www.remarpro.com that there is a separate Jetpack Social plugin which I don’t have downloaded, yet my post sharing to Facebook is still working!

I’d appreciate you help to get to the bottom of this mystery.

Regards

Robert

Thanks. If its easier to add some code in the functions.php then I’m happy to do that if you can provide the code. Whatever is easiest for you.

Hi Arnaud

I tried changing the nickname to ‘noname’ then selected ‘noname’ in the user ‘Display name publicly as’ dropdown.

However when I inspect the same post https://aboutdereham.org/keepderehamclean-2/ I still get the Username ‘selbyc’ displayed.

Have I misunderstood what you meant?

Yes it’s working now, many thanks for taking care of this so quickly.

Regards

Robert

I have loaded your plugin and made it live. It’s working on some of my forms (where I can see the WP Armour banner) but not on my key contact form which is the important one. (I tried taking out the ReCaptcha but still not seeing the WP Armour banner). I’ve created a test page for you to look at which uses the same contact form. Please view https://aboutdereham.org/test-wp-armour/

Can you see any reason why its not working on that page/form?

Thanks

Robert

Yes I found the problem which was server based. Sorted now thanks.

Turns out to be a new ‘feature’ on Litespeed servers. See https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/

I got my hosting provider to bypass it as it interferes with my custom log-in and I have WordFence to protect my site.

Hi @subiewrx

Turns out to be a new ‘feature’ on Litespeed servers. See https://docs.litespeedtech.com/lsws/cp/cpanel/recaptcha/

I got my hosting provider to bypass it as it interferes with my custom log-in and I have WordFence to protect my site.

Thanks

Robert

Hi @wfpeter

You were right! Despite my hosting company saying it wasn’t a server issue, litespeed was the culprit. Sorted now.

Thanks so much.

Robert

Thanks for the latest version which seems to have cured the problem. Can I ask why this plug-in is being updated automatically even when audio-updates is switched off? I want to be able to control my plug-in updates on my site.

Well I tried a temporary change to my config.php file as follows:

define( 'WP_AUTO_UPDATE_CORE', false );

And the beta version is STILL being overridden by the faulty V3.32.0 version.

Hopefully the plug-in developers are on with getting this sorted as its a real pain to have to load the beta version pretty well every day!

I think the reason for the re-emergence of the problem is that the beta version has been automatically updated back to the 3.32.0 (non beta) version, even though auto updates is not enabled. This is exactly what happened to my site over the last 24 hours. I have updated to the beta version again but I suspect that it will get overwritten again. Can you help to find a way to stop this happening please.