Headers already sent in WP5.1

Hello.

Thank you for your request.

Could you please let us know, do you use the latest version (5.115.1) of CleanTalk plugin?

Write back anytime.

Best regards.

Thank you for your feedback.

I don’t see these errors on the same WordPress and CleanTalk versions. But I will ask our developers about it. We will contact you within 1-2 working days.

Could you try to re-install the plugin? Write to us about the results.

Best regards

Yes latest version of Cleantalk plugin, 5.115.1

Does not seem to happen with WP 5.0.3, only with latest WP 5.1 version

Thank you. We working on it.

Please wait for the answer.

Best regards

@dbm44 , @xarkitu,

We have fixed issue, please update plugin to 5.112.2,
https://cleantalk.org/help/update-wordpress

Thank you.

@shagimuratov
Sorry but this is not fixed, still produces errors in WordPress 5.1

It does work OK in WP 5.0.3 but not in WP 5.1

Going from Page or Post editor (new Gutenberg editor) back to the wp-admin/edit.php screen triggers the errors

[27-Feb-2019 16:08:13 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/****/wp-content/plugins/cleantalk-spam-protect/cleantalk.php on line 788
[27-Feb-2019 16:08:13 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/****/wp-content/plugins/cleantalk-spam-protect/cleantalk.php on line 795
[27-Feb-2019 16:08:13 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/****/wp-content/plugins/cleantalk-spam-protect/cleantalk.php on line 805
[27-Feb-2019 16:08:13 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/****/wp-content/plugins/cleantalk-spam-protect/cleantalk.php on line 812
[27-Feb-2019 16:08:13 UTC] PHP Warning: Cannot modify header information – headers already sent in /home/****/wp-content/wp-content/plugins/cleantalk-spam-protect/cleantalk.php on line 818

Thank you for your feedback. I will transfer it to our developers. We will contact you within 1-2 working days.

Best regards

Hello,

Please, send us full error text. It should looks similar to this: Cannot modify header information – headers already sent by (output started at ***\wp2.loc\wp-content\plugins\cleantalk-spam-protect\cleantalk.php:2) in ***\wp2.loc\wp-content\plugins\cleantalk-spam-protect\cleantalk.php on line 792

You could try to reinstall the plugin (Deactive, Delete, Install and Activate).

Anyway, we need this error text to fix it. It’s high priority task, so we’ll fix it in a few hours.

Please, contact us.

Thank you for feedback.

We will contact your within 48 hours.

Please, wait.

Hello @dbm44,

We need to know exactly your actions when you get this error.
We need this information to investigate the issue.

Thank you.

• This reply was modified 5 years, 8 months ago by Safronik.
• This reply was modified 5 years, 8 months ago by Safronik.

@shagimuratov

As I said in my original posts going from Page or Post editor (new Gutenberg editor) back to the wp-admin/edit.php screen triggers the errors. So edit any post or page in the new editor and then go back to list of all posts or pages and you will see the errors generated in the debug logs

I tested this on a staging site so have not installed on a live site so have no public URL. This error is stopping the upgrade to WP 5.1 so I need a fix for this ASAP

Hi guys,

Thank you for feedback. We can’t reproduce issue in Post editor page, so we are going to revise code changes since 5.114. I hope we will finish today.

We will write you back here.

Hello, everyone!

Hope we have fixed it.

Please, update to 5.116.1. version in WordPress dashboard.

Let us know the results.

Agreed, not fixed (by 5.116.2)

Multiple people have had this issue and it is still not fixed. I suspect many more people are also having this problem, they just don’t know it, because they have not tested this plugin with WP DEBUG on.

Asking people to create private tickets is not solving the problem, just hiding it.

Cleantalk as a (paid) service works well, but resolution of this issue has been very poor. A great deal of time has been spent testing supposed fixes that simply do not work

And just noticed this topic has been marked as resolved.

IT IS NOT RESOLVED