Home › Forums › Weaver Show Posts & Show Sliders › Trailing white space PHP files causes WP 5.3 PHP Warnings, Headers already sent
- This topic has 1 reply, 2 voices, and was last updated 3 years, 6 months ago by Weaver.
November 20, 2019 at 15:05 UTC - Views: 11 #62067timreevesParticipant
This is a real problem for me on many sites, already noted by myself on WP Support.
After updating to 5.3 I’m suddenly seeing lots of PHP warnings like this:
[20-Nov-2019 12:07:45] WARNING: [pool meischner.world] child 26697 said into stderr: "NOTICE: PHP message: PHP Warning: Cannot modify header information - headers already sent in /var/www/vhosts/meischner.world/httpdocs/wp-content/plugins/ comet-cache/src/includes/traits/Shared/HttpUtils.php on line 175"
After deactivating all plugins except Comet Cache the problem is gone – sequentially reactivating identified 9 (!) Plugins which cause this, on just one WP site. Show Posts (a great plugin, I use it on quite a few sites) was also a “culprit”. I checked it – ALL the PHP files have trailing white space after the
?>. I removed them and uploaded manually – the problem is solved (at least, for “Show Posts”).
@weaver: I know this is an “older” plugin and for sure it’s not making you rich – but it is a great plugin, and I and many others are relying on it. It’s still working fine in WP 5.3 (except for the problem noted here) – so could you please delete all the
?>, bump up compat to 5.3 and publish the new version? Would be very much obliged!
Thanks, TimNovember 20, 2019 at 19:11 UTC - Views: 12 #62068WeaverKeymaster
Hmm – that must be something related to WP 5.3, but I don’t remember seeing what that was a widely used version.
I can’t imagine what they might have done to “break” long standing code that follows appropriate PHP standards.
Since that seems to be an issue now, I will try to update all the plugins to not use closing ?>s. Not sure of the time frame, however.
- You must be logged in to reply to this topic.