iaeon

OK thanks I will look out for the forthcoming release.

Thanks

Having found the setting, deactivated, reactivated and re-entered the activation key it looks to be working fine and no debug error.

Glad to hear I don’t have to uninstall and reinstall on all the other sites that had become deactivated now that they are upgraded and reactivated!

I can deactivate and reactivate and the reported error remains.

I cannot find a ‘complete deactivation’ option on the /wp-admin/plugins.php page??

Re the other sites that are now upgraded and active – Is it OK that I did not uninstall and reinstall as suggested by safronik above?

Hi

I just noticed that Cleantalk was deactivated on about 20 sites. All individual installs on VPS.

I think most were on 5.144. I have updated all individually to 5.145.2 using the WordPress plugin update method and reactivated.

After I finished I found the thread above and your advice to uninstall and re-install. Is this really necessary or should I see if they are active in the control panel and if data seems to be logged again in about a days time?

One site did come up with an error although it seems to be active?:

Debug:
Constants:
CLEANTALK_AJAX_USE_BUFFER NOT_DEFINED
CLEANTALK_AJAX_USE_FOOTER_HEADER NOT_DEFINED
CLEANTALK_ACCESS_KEY NOT_DEFINED
CLEANTALK_CHECK_COMMENTS_NUMBER NOT_DEFINED
CLEANTALK_CHECK_MESSAGES_NUMBER NOT_DEFINED
CLEANTALK_PLUGIN_DIR /var/www/vhosts/nigelgoldie.org/httpdocs/wp-content/plugins/cleantalk-spam-protect/
WP_ALLOW_MULTISITE NOT_DEFINED
Debug log:?Drop debug data
ArrayObject Object
(
????[storage:ArrayObject:private] => Array
????????(
????????????[06:26:21_ACTION__FUNCTION_] => Array
(
????[0] => Failed.
Query: ALTER TABLE wp_cleantalk_sfw_logs
CHANGE status status ENUM(‘PASS_SFW’,’DENY_SFW’,’PASS_SFW__BY_WHITELIST’,’PASS_SFW__BY_COOKIE’,’DENY_ANTICRAWLER’,’PASS_ANTICRAWLER’,’DENY_ANTIFLOOD’,’PASS_ANTIFLOOD’) NOT NULL AFTER ip;
Error: Unknown column ‘status’ in ‘wp_cleantalk_sfw_logs’
)

????????)

)

Thanks – will keep a look out for SCA compliant updates.

I am also getting this message on all my Plesk hosted sites this morning following the upgrade to 1.2.4 of the health check plugin.

I am able to edit posts and pages with Gutenberg. Everything with REST seems to be working OK as as I can tell. What does the message mean?

Got there eventually (Kudos to Andy at Line3!)

The issue again was that running Plesk Onyx / NGINX WordPress REST API was failing so posts and pages could not be saved or updated.

The fix is as follows:

1) Under Plesk make Hosting settings ‘FastCGI / Apache’

2) In WordPress, change settings / permalink to ‘day and name’

3) REST should now work (check by loading domain.tld/wp-json/wp/v2/posts or running ‘Health Check & Troubleshooting’ WordPress plugin.

4) In Plesk swap hosting settings back to ‘FPM served by nginx’

5) In WordPress, change settings / permalink to ‘Post name’

REST should still work fine so Gutenberg should not return errors when saving.

WHY it is necessary to first change permalinks under Apache for REST to work I have no idea!

The REST API call gave the following unexpected result: (404)
Not Found
The requested URL /wp-json/wp/v2/posts was not found on this server.

ALL plugins disabled. Using a default WordPress theme.

Something else must be going on, but frustratingly I cannot find it!

Is there anything written in the migrated database which might stop REST API?

I have tried manually replacing all of WordPress apart from /wp-content and wp-config.php but not solved the problem.

/wp-json/wp/v2/posts cannot be found so the REST is not working. Pretty permalinks are set.

Another freshly installed domain on the same VPS IS working. I cannot see any difference in the configuration underpinning the two installs however.

PHP 7.0.17 MySQL 5.5.54 WP 5.0.2

What has to be in place for REST to work?

• This reply was modified 5 years, 11 months ago by iaeon.

I have disabled ALL plugins. Swapped to WP Twenty Sixteen theme (tried another default too just in case).

I did install Health Check, but as I have already disabled everything and am working on a test site it makes no difference.

This ‘publishing failed’ / ‘update failed’ situation is the same on other sites on my VPS when I have tried them and on a second (similar but older VPS) so very replicable!

3.7.1 works for me, thanks!

>>
I strongly recommend adjusting your rules to support the querystring
<<

Any advice on what to do for Nginx to support querystrings if you think this is the issue?

Odd if it is as I have other sites with the same Nginx configuration that do support querystrings.

I inadvertently upgraded to 3.7.0 which broke previous and next month navigation again.

I get a 404 with a URL such as this: /calendar?pagename=calendar&month=jun&yr=2018

I am running Nginx

Can you provide a download link to 3.5.11 please as this was OK?

Thanks

Would still like to know if it is possible to delete all settings from UpdraftPlus for a single domain when using MainWP to control multiple child sites.