PHP Warning

So basically what the Auther is saying is he/she would rather support people who does not update their sites, and not the clients who do??

Cant you add some functionality in the plug in, for all of us people who actually keep updated sites, so we dont have to change our files via FTP?

I dont care if its pretty, I can live with a temporary solution, until youre bigger release is ready.

Pretty please.

I copied what is above.

Tried with 0. Still not resolved.

@deciosdecarvalho in the worse case scenario, it should do nothing. Can you copy the part of your config file here (without any sensitive information of course)?

I am going to have to take my site down until this is resolved. This is a very bad situation for us as we have a growing group of people who visit and use our site. This is very disappointing. We have used the plugin for about 6 years.

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

// Enable WP_DEBUG mode
define(‘WP_DEBUG’, false);
@ini_set(‘error_reporting’, 0 );
@ini_set(‘display_errors’, 0 );

// Enable Debug logging to the /wp-content/debug.log file
define(‘WP_DEBUG_LOG’, true);

// Disable display of errors and warnings
define(‘WP_DEBUG_DISPLAY’, false);

// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define(‘SCRIPT_DEBUG’, false);
?>

I am going to have to take my site down until this is resolved. This is a very bad situation for us as we have a growing group of people who visit and use our site. This is very disappointing. We have used the plugin for about 6 years.

@deciosdecarvalho Who cares? First of all it is your responsibility to take care of your website. A serios website owner never would update directly and not on the live website. If you do not test updates in a sandbox it is your fault if you get in trouble.

A PHP warning should never be appear on live but only on staging websites. If you can not handle this configuration you should hire somebody who can do this.
Stop whining and blaming other people if you do not take responsibility for your website.

Read the thread from the beginning and follow the instructions!

Polylang is a free software. If you don’t like it, don’t use it!
If you are a Pro user contact Polylang Pro support and they will help you!

What I was writing is that nobody should display warnings on a live site. The warnings are just warnings, not errors, and are intended to the developers, not the end users.

However I see that too many people have errors display on their site. It was a surprise to me. I am quite sure that it’s a surprise to WordPress developers too as WP 5.3 was pushed knowing that it would cause this warning in Polylang and a few other plugins. And it wasn’t considered as a severe issue.

So I was forced to push a new version in urgence. Polylang now requires PHP 5.6. This issue is fixed Polylang 2.6.7. This version and newer won’t worked for older versions of PHP.

Thank you @coder!

Thank you very much @chouby. Version 2.6.7 solved it. I appreciate your quick action on this. All the best.

• This reply was modified 5 years ago by deciosdecarvalho.

Thank you very much! Great plugin! Excellent support!

Magic made! Thanks for the fix.

@chouby Great! Thank you! I just added the

ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, false);
define(‘WP_DEBUG_DISPLAY’, false);

To wp-config and now I already can remove it again.

Hi guys I just updated Polylang version, should I just take off this code below from my php put back to normal

ini_set(‘display_errors’,’Off’);
ini_set(‘error_reporting’, E_ALL );
define(‘WP_DEBUG’, false);
define(‘WP_DEBUG_DISPLAY’, false);

Thank you @mstuyts , that did the trick.
The following two lines added to the wpconfig file solved the problem:
define(‘WP_DEBUG’, false);
@ini_set( ‘display_errors’, 0 );

Hope this helps others too.