Closed bozdoz closed 1 year ago
resolved, though there are a lot of deprecations in wordpress itself, that seem outstanding
@bozdoz Would be nice to get a release with these fixes ;)
@scrobbleme any ideas about these other warnings? https://github.com/bozdoz/wp-plugin-leaflet-map/pull/199#issuecomment-1368269822
@bozdoz Which other ones do you mean?
I just stumbled upon this: FILTER_SANITIZE_STRING The "Cannot modify header information" is probably related to this...
(Probably not possible to solve WordPress core deprecations ;)
@bozdoz The WordPress version and the Github version differ. I'm running a test installation with WordPress 6.2 beta 1, wp-plugin-leaflet-map and no warnings appear, not even from WordPress. If I switch to leaflet-map, these warnings about FILTER_SANITIZE_STRING appear. There are no warnings with php 8.0
@scrobbleme To not display these warnings, write in wp-config.php:
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
@scrobbleme Pushed to v3.2.0
@hupe13 FILTER_SANITIZE_STRING is deprecated since PHP 8.1 → therefor the warning only appear on PHP 8.1 first… and they are flooding the log, which really makes it hard to debug the system.
Disabling frontend output surely should be done for production, but this doesn't solve the problem that log files get large, really fast, and it is quite hard to find the real errors…
(Warnings should as much as possible be considered as errors, in this case, it eventually will become errors in a future PHP version.)
Yes I know.
RE: https://wordpress.org/support/topic/php-8-1-support-10/