My Wordfence settings are set to the following for XML-RPC. Do these need to be adjusted?
https://pasteboard.co/8JqKmUAh5iZR.png
-
This reply was modified 2 months, 2 weeks ago by jchambo.
OK nevermind I’m blind, I see the following text now in Wordfence:
“You must choose the “Skipped” option if you use the WordPress app, the Jetpack plugin, or other services that require XML-RPC.”
What’s funny is once I switched the toggle from “REQUIRED
” to “SKIPPED
” my site broke instantly with the classic “There has been a critical error on this website.
” error. Even turning on DEBUG mode in my wp-config.php file didn’t do anything or show me any errors.
I re-downloaded the WordPress core files and uploaded them however it did not fix my issue. What…. the……. hell.
-
This reply was modified 2 months, 2 weeks ago by jchambo.
When checking /var/www/html/wp-content/debug.log
I see the following:
[19-Jul-2024 00:47:55 UTC] WordPress database error Table 'wordpress.wp_jetpack_sync_queue' doesn't exist for query SELECT COUNT(*) FROM wp_jetpack_sync_queue WHERE queue_id = 'sync' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\Jetpack\Sync\Sender->do_sync, Automattic\Jetpack\Sync\Dedicated_Sender::spawn_sync, Automattic\Jetpack\Sync\Queue->size, Automattic\Jetpack\Sync\Queue\Queue_Storage_Table->get_item_count
Well what a roller coaster ride that was…. turns out coincidentally I updated “Easy Social Share Buttons for WordPress” just prior to toggling the above option in Wordfence and that was actually the culprit.
I’ve reached out to the plugin author to release a hotfix.
I would like an answer though as to why these errors occur in Chrome and not Firefox or Firefox Developer Edition without the need to toggle the above in Wordfence.
OK definitely not fixed by changing the Wordfence setting. This appears to be a Chrome issue with Jetpack.
Please advise / resolve.
Hi there, @jchambo,
Thanks for bearing with us on this issue. It seems like we had a tiny glitch. We have alerted our developers, who are investigating further.
In the meantime, could you try the following to see if that fixes the problem?
- Log out of your site and log back in.
- Disconnect Jetpack and reconnect it.
- Open the Jetpack Social connection page in a new tab and try adding a connection.
Let me know how you get on 🤞
@erania-pinnera curious if there is any update on this? I’m experiencing the same problem on my site with comments. I did disconnect/reconnect and flush caches to no avail.
Hi there, @davidshq,
I am afraid what you’re experiencing with the comments is a known issue our developers haven’t figured out yet. I have added your report too in the comment thread on GitHub; you’re welcome to comment or add any other useful details as it’s an open issue.