New Release verifies compatibility with WordPress 5.7 and contains fixes

When I updated to the new version I started getting this error and the plugin will not work: Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 7.2.5”.

The PHP on my server is actually older but my provider patches it automatically. What should I do?

I would ask your provider to upgrade your WordPress/SQL/PHP software stack. Since your PHP is older than 7.3, it is end of life and can’t be patched anymore. I apologize for the inconvenience this causes. We will update our plugin page to update the new minimum PHP requirement.

Until you get your PHP updated, you could roll back to an older version of GDPR by downloading an older version from the plugin page under the “Advanced View.” Here is an url for the download: https://downloads.www.ads-software.com/plugin/gdpr-framework.1.0.40.zip

WordPress provides this helpful template that you can use to ask your hosting provider for an upgrade:

I’m interested in running the open-source WordPress <https://www.ads-software.com/&gt; web software and I was wondering if my account supported the following:

PHP 7.4 or greater
MySQL 5.6 or greater OR MariaDB 10.1 or greater
Nginx or Apache with mod_rewrite module
HTTPS support

Thanks!

The provider allows upgrading the PHP to any desired version with a dropdown but that will break everything in the site at the moment so we have a planned migration later in the year. The provider also uses HardenedPhP so the site is “safe”. https://www.cloudlinux.com/hardenedphp-wp. Not sure if that could be something that makes a difference on your plugin, but I will try going back a version. Thanks!

Hey, so I also noticed an issue with the plugin. I have a website currently under development. It is the latest version of wordpress (version 5.7.1), running on php version 7.3. I am also using the Custom Post Type User Interface and Advanced Custom Fields plugins. The problem is when I use them together, and use the following PHP code in the custom archive page I created from scratch, that page runs into an error. Sample code is:

$str = 'my dog sat on a hat';//imagine this value is actually stored in the database 
 from a custom field, and pulled using the get_field() function.

if(str_contains($str, 'dog')){
//do something here
}

Now, it seems as though the issue / conflict is with the php function ‘str_contains’, however, the previous version of this plugin did not have that specific issue. I have tested everything else to the best of my ability, and narrowed it down to this.

• This reply was modified 3 years, 6 months ago by kathrynmpu.
• This reply was modified 3 years, 6 months ago by kathrynmpu.

Can you provide us with an image or text of the error that you see.

You can also email it to us at [email protected] or open a ticket on our support portal so we can directly assist. data443.com/support

I didn’t notice this earlier. The function, ‘str_contains()’ is introduced in PHP8. It’s not available when you run PHP 7.3.