Tagged: ,

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • August 25, 2018 at 12:56 am #1001444
    loudcow

    Hey there – I have a new self-hosted install running on PHP 7.2 – Latest version of WP core + Enfold theme.

    Any time I “update” a page or post I get the following warnings on a blank screen…

    Warning: count(): Parameter must be an array or an object that implements Countable in /public/wp-includes/post-template.php on line 284

    Warning: Cannot modify header information – headers already sent by (output started at //public/wp-includes/post-template.php:284) in /public/wp-admin/post.php on line 198

    Warning: Cannot modify header information – headers already sent by (output started at //public/wp-includes/post-template.php:284) in /public/wp-includes/pluggable.php on line 1219

    I can navigate out and back to the site and backend no worries after the warnings appear. It does not seem to affect the front end. And the updates are applied without issue.

    I have deactivated all plugins and have isolated it to Yoast SEO + Enfold. When yoast seo plugin deactivated no warnings are triggered. When I reactivate Yoast the warning persists.

    However – when I change themes to Twenty Seventeen (as advised by Yoast devs) the issue disappears.

    I have added link to site in question in private content.

    Thank you!

    August 25, 2018 at 10:51 am #1001564
    Victoria

    Hey loudcow,

    You need to configure debug to write to a log file, here is how to do it:

    Debugging WordPress: How to Use WP_DEBUG

    Best regards,
    Victoria

    August 28, 2018 at 10:08 am #1002616
    loudcow
    This reply has been marked as private.
    August 28, 2018 at 9:46 pm #1002851
    Basilis

    Hi,

    If you downgrade to php 7.1 does things work?

    Best regards,
    Basilis

    August 28, 2018 at 10:46 pm #1002894
    loudcow
    This reply has been marked as private.
    August 29, 2018 at 11:41 am #1003088
    Dude

    Hi,

    I’d recommend to add following code to the child theme functions.php:

    
error_reporting(0);

    to deactivate the error/warning output. Use this code even if you’re not experiencing any issues because php warning/error messages might help hackers/attackers to find weak points or backdoors.

    Best regards,
    Dude

    November 6, 2018 at 5:46 pm #1030477
    Cliffy

    I’ve come across this issue also. I was creating a blog post through the Advanced Builder rather than the default. I only encountered the error when adding the Social Sharing Element to the post and then trying to save. Removing the social share element means I can save the content without the error.
    I hope that helps the dev team.

    H

    November 7, 2018 at 10:00 am #1030769
    Rikard

    Hi Heathcliffe,

    Thanks for the feedback, if you want us to have a closer look at your site then please open a new thread and include admin login details in private.

    Best regards,
    Rikard

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.