search

liedekef / events-made-easy

The wordpress/classicpress plugin events-made-easy to manage events, memberships and more.
https://www.e-dynamics.be/wordpress
GNU General Public License v2.0
26 stars 5 forks source link

Bug with PHP 8.2 #383

Closed RoundAboutWEB closed 11 months ago

RoundAboutWEB commented 11 months ago

PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /html/wordpress/wp-content/plugins/events-made-easy-main/eme-events.php on line 3943

PHP Deprecated: substr_replace(): Passing null to parameter #2 ($replace) of type array|string is deprecated in /html/wordpress/wp-content/plugins/events-made-easy-main/eme-events.php on line 3942

liedekef commented 11 months ago

which version of EME are you using?

liedekef commented 11 months ago

Next to that: please specify which placeholder is triggering this

liedekef commented 11 months ago

While waiting for an answer, I already updated the code to better take into account possible null-values for replacement of a placeholder (also possible for images that no longer exist).

RoundAboutWEB commented 11 months ago

Hello, since EME is no longer supported by WordPress since the security breach, I have decided in the meantime to use a verified plugin and no longer use EME. Thanks for the answer anyway. Greetings Stefan

liedekef commented 11 months ago

EME is still supported (and the security breach is long closed, about a year ago ...). But no problem, you're free to use any plugin of choice.

RoundAboutWEB commented 11 months ago

That is not correct. EME is no longer offered at https://wordpress.org/plugins/ because it is no longer verified and therefore does not fulfil the WordPress security requirements for the plugin. I have therefore opted for a different solution.

liedekef commented 11 months ago

No, EME is no longer offered not because of the security issue but because they have imposed new coding standards that I believe to be too strict (and not logical). The security issue is long fixed but since they refuse the plugin (because of the coding standards), they refuse to release the fixed version. This is something unseen in the security world (and as somewhat of a security expert I know what I'm talking about): they leave their users open to a known security issue. I've had several discussions with them but to no avail. So I've abandoned wordpress.org and stopped trying to get it right. Other plugins suffered the same issue (even a security scan plugin like WP Cerber, read about that here: https://wpcerber.com/cerber-sw-repository/ )