Warning: count(): Parameter must be an array or an object that implements Countable in …/plugins/custom-field-template/custom-field-template.php on line 2019

This is because of changes in PHP 7.2+

It would be great, if you could handle this with next update.
Thanks a lot!

FILE: /nfsvol-e/52/52452/powerd911.guru/dac_wordpress/wp-content/plugins/image-slider-widget/inc/ewic-metaboxes.php
——————————————————————————————————————-
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
——————————————————————————————————————-
108 | WARNING | Function create_function() is deprecated since PHP 7.2; Use an anonymous function instead
——————————————————————————————————————-

Name: WPFront User Role Editor

FILE: /nfsvol-e/52/52452/powerd911.guru/dac_wordpress/wp-content/plugins/wpfront-user-role-editor/classes/base/class-wpfront-options-base.php
———————————————————————————————————————————————
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
———————————————————————————————————————————————
72 | WARNING | Function create_function() is deprecated since PHP 7.2; Use an anonymous function instead
81 | WARNING | Function create_function() is deprecated since PHP 7.2; Use an anonymous function instead
88 | WARNING | Function create_function() is deprecated since PHP 7.2; Use an anonymous function instead
———————————————————————————————————————————————

I am using php 7.2 as it is supported by ubuntu 18.04 LTS. What functionality am i supposedly missing out on?

We have memory set to 512mb

Debug says

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 32768 bytes) in /home/domainstore/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBStore.php on line 331

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 32768 bytes) in /home/domainstore/public_html/wp-content/plugins/woocommerce/vendor/automattic/jetpack-constants/src/class-constants.php on line 1

Any ideas?

Most sites on our server immediately broke, they were running updated plugins and 5.51 core

A few sites ran fine, until we upgraded them to core 5.51

So 5.51 core will not run on our server without breaking sites IF we add more than woocommerce, it’s the only plugin that works on our server with core 5.51

I found some info on cpanel about enabling nd_mysqli and another old php V 5.0 file

I found something on this site about centos needing a php_mysgl extension

Server is Centos 7.80
We have 5.6 php, 7.0 php that works fine, we installed 7.2, 7.3 and 7.4 and those break all sites as soon as we upgrade to core 5.51

Then if disable all plugins and run 5.51 core on 7.4 core works, if we run woocommerce only it works, as soon as any other plugin in activate, it crashes

Error messages range from
Critical Error
White screen of death
http 500 error

We have over 100 WP sites
All use OnePress Theme
Then many use Woo

We use about 20 plugins on the sites, never had any issues

We did have issue while ago with ultiate seo breaking stuff while we were under 7.0 php with older cores

So we just disabled that plugin and had no real issues until we started running php higher than 7.0

HELP

After updating worpdress to 5.4.2 yoast seo not working with it.

I’m using php 7.2 and when if I change it, yoast will not work well, the screen become blank.

Can you help me, please?
Now, it is deactivated!

Thank a lot

WordFence 7.4.8 is giving me 503 errors when I have the plugin enabled. This same problem came up in the forums a couple of years ago, but I didn’t see any solid resolution to it. Also, it doesn’t matter what browser I use to access the dashboard or the website when it’s broken. Nor can I run a scan, since the plugin is disabled.

I’ve temporarily disabled WF by renaming the plugin directory, and I can then access the dashboard and view the website. But as soon as I rename it back to the original, I cannot access either.

The plugin readme.txt file says I’m running WF plugin 7.4.8 and that it requires PHP 5.3 and is tested up to PHP 5.4. For some reason, my GoDaddy hosting indicates that I’m using PHP 7.2. Could that cause a problem?

How else can I troubleshoot this problem?