Hendrik57

Jeff,
Your comment is correct on me.
In fact we did enable Contactform on all sites for non-logged-in users in the plugin.

It should be fine when the plugin checks these kind of dependencies and warns or advise about settings, or even do those minimal auto settings for active plugins.

And this is not negative about WP REST API, but it is a warning that some plugins like ContactForm7 depend on open calls to the database.

Dave,
It still is not compatible with the latest 3 WordPress releases and over 1 year old now. I see version 1.7.
We use php8.1 and latest WordPress a.s.o.

Yes, quite a lot of jQuery errors. Site has become very slow.
This is just the Home page, same with PHP8.0 and PHP8.1.
(PHP7.4 is deprecated so we don’t use that anymore.)

helpers.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at helpers.min.js?v=1670907953:1:19741
(anonymous) @ helpers.min.js?v=1670907953:1
global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at global.min.js?v=1670907953:1:1
(anonymous) @ global.min.js?v=1670907953:1
front_global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at front_global.min.js?v=1670907953:1:14
(anonymous) @ front_global.min.js?v=1670907953:1
view.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at view.min.js?v=1670907953:1:1
(anonymous) @ view.min.js?v=1670907953:1
helpers.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at helpers.min.js?v=1670907953:1:19741
(anonymous) @ helpers.min.js?v=1670907953:1
global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at global.min.js?v=1670907953:1:1
(anonymous) @ global.min.js?v=1670907953:1
front_global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at front_global.min.js?v=1670907953:1:14
(anonymous) @ front_global.min.js?v=1670907953:1
view.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at view.min.js?v=1670907953:1:1
(anonymous) @ view.min.js?v=1670907953:1
helpers.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at helpers.min.js?v=1670907953:1:19741
(anonymous) @ helpers.min.js?v=1670907953:1
global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at global.min.js?v=1670907953:1:1
(anonymous) @ global.min.js?v=1670907953:1
front_global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at front_global.min.js?v=1670907953:1:14
(anonymous) @ front_global.min.js?v=1670907953:1
view.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at view.min.js?v=1670907953:1:1
(anonymous) @ view.min.js?v=1670907953:1
helpers.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at helpers.min.js?v=1670907953:1:19741
(anonymous) @ helpers.min.js?v=1670907953:1
global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at global.min.js?v=1670907953:1:1
(anonymous) @ global.min.js?v=1670907953:1
front_global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at front_global.min.js?v=1670907953:1:14
(anonymous) @ front_global.min.js?v=1670907953:1
view.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at view.min.js?v=1670907953:1:1
(anonymous) @ view.min.js?v=1670907953:1
helpers.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at helpers.min.js?v=1670907953:1:19741
(anonymous) @ helpers.min.js?v=1670907953:1
global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at global.min.js?v=1670907953:1:1
(anonymous) @ global.min.js?v=1670907953:1
front_global.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at front_global.min.js?v=1670907953:1:14
(anonymous) @ front_global.min.js?v=1670907953:1
view.min.js?v=1670907953:1 Uncaught ReferenceError: jQuery is not defined
    at view.min.js?v=1670907953:1:1

There was an update, but after updating (that went very slow) version number is the same. errors however seem to be gone …. ??

Version 6.0.6.1 seems to work with php8.0 (free version).
But lots of erros with 8.1. Date-time in Date_based lines 284, 334, Custom_tables..provider line 28, utils line 1130 and Query_monitor line 215
Site hangs sometimes.

With PHP 8.0 only this error:
Notice: Functie register_block_script_handle werd verkeerd aangeroepen. Het asset bestand voor de “editorScript” gedefinieerd in de “contact-form-7/contact-form-selector” blok definitie bestaat niet. Lees Foutopsporing in WordPress voor meer informatie.

• This reply was modified 1 year, 11 months ago by Hendrik57. Reason: completing error

Ghostery also blocks koko by default. Trust website to disable this. But that should the client do and can not be done on server level.

On three occurences is depreciated PHP used. That results in heavy processor load en error logs every 30 seconds. That causes this problem with latest WordPress and PHP 8.1.

The error holds this info and that function is used on three places:
Got error ‘PHP message: All-in-One Event Calendar: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated @ /home/sta…. wp-content/plugins/all-in-one-event-calendar/lib/query/helper.php:160 #8192PHP message: All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @

We do not use ublock plugin. Only WpRest disable.
And we don not see any statistics anymore. Last update 17-8 did not resolve that.
This happens on all sites we manage.

I’ve had same trouble. Try this:
. Clear the files cache in your browser, then Ctrl-F5 (serverside refresh)
. Clear cache in WordPress
. Watch the available memory for WordPress. That solved many problems last month for us. (php engine got in a loop because to little memory) Set it to a value higher then the 40 default in config file (I have 96 or 128 and 256 for admin)
. Check the php memory setting for the version you use on the server.

I’ve the same 404 problem with WordPress 6.0.1 and PHP 8.0 since yesterday after WordPress minor update. I need to delete the plugin through FTP and use the default login now. So far it only concerns my MainWP management site with only Twenty-one theme 1.6.
It seems solved when re?nstall the latest WordPress release through the update screen.

• This reply was modified 2 years, 4 months ago by Hendrik57.

Strange, because updates are as far as I know always initiated by a new and higher version number. I’ve not seen that individual plugin files are updated.
I think that ‘official instruction’ is wrong. It doesn’t work that way as I’ve proven for > 60 sites.
I your case, I’d create a 2.1.1 version, or a 2.1.0.1 release to force the updates.

As far as I understand the ‘official instruction’ is only used for the notice displayed on the www.ads-software.com plugin page noting that the plugin may no longer be maintained or supported. The readme is not used in the update signalisation process.

Please, do not install ‘bloatware’ by default. We have to remove all unwanted ‘extra’ plugins like Jetpack again. We use other methods!

Same problem with all our sites. We even got 500 and 404 errors on some sites.
With PHP8.0 error. Back to PHP7.4 OK, but no update is installed.
Manual delete and upload 6.5.1 works.

I see what happens. The plugin on all sites is dated 20-11-2020, Version: 2.1.0 it says in the dashboard. It is the same as current.

The readme.txt says:

Tags: memory, memory-limit, ip, ips, admin, adress, php, server, info
Requires at least: 3.0.1
Tested up to: 4.9
Requires PHP: 5.3
Stable tag: 2.1.0

And that 4.9 is used to verify compatability with the WordPress release.

The header of the installed 2.1.0 version says:

Plugin Name: Server IP & Memory Usage Display
Plugin URI: https://apasionados.es/#utm_source=wpadmin&utm_medium=plugin&utm_campaign=server-ip-memory-usage-plugin
Description: Show the memory limit, current memory usage and IP address in the admin footer.
Version: 2.1.0
Author: Apasionados, Apasionados del Marketing
Author URI: https://apasionados.es
Text Domain: server-ip-memory-usage

But indeed. The download version 2.1.0 has a language folder and a correct readme.txt file. That is not the same 2.1.0 release!

I wil replace all instances. How this could have hapenend?

• This reply was modified 2 years, 6 months ago by Hendrik57. Reason: correct now
• This reply was modified 2 years, 6 months ago by Hendrik57.