• Bonjour
    When I delete an article on this site, the deletion works but I get this error message : `Warning: Undefined property: WP_Post::$filter in /datas/yulpa171734/sites/teplitz-theatre.net/htdocs/wp-includes/class-wp-post.php on line 342

    Warning: Cannot modify header information – headers already sent by (output started at /datas/yulpa171734/sites/teplitz-theatre.net/htdocs/wp-includes/class-wp-post.php:342) in /datas/yulpa171734/sites/teplitz-theatre.net/htdocs/wp-includes/pluggable.php on line 1355

    Warning: Cannot modify header information – headers already sent by (output started at /datas/yulpa171734/sites/teplitz-theatre.net/htdocs/wp-includes/class-wp-post.php:342) in /datas/yulpa171734/sites/teplitz-theatre.net/htdocs/wp-includes/pluggable.php on line 1358`

    This appears only with PHP 8.0 when reverting to PHP 7.4, no more messges. Deactivating all plugins no messages. The culprit plugin is WP Super Cache. So there is an uncompatibility Super Cache and PHP 8
    Is there a solution or have I to change my cache plugin ?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thanks for reporting this. I haven’t had a chance to test in PHP8.0 yet so I don’t know what the fix might be.

    Thread Starter fnctamp

    (@fnctamp)

    So will you test that and fix it ? Quickly ? If you do, I’m waiting because I like super cache. But I cannot wait long. Thank you

    I think this is a WordPress core issue. I found this ticket describing the problem.
    WP Super Cache uses get_sample_permalink() which unsets $post->filter.

    I would not display errors on a production site. You should send them to an error log. While the warning will still be created it won’t interfere with how your site works.

    Thread Starter fnctamp

    (@fnctamp)

    Sorry, but you cannot say that is a WordPress issu. It happens only with super cache activated and with no other plugin. So it is indeed a super cache issue, even if doesn’t display on the frontend and even if it doesn’t interfer with how the site works, what is true. It is your job to change that, with the wordpress team if you want. I hope you will be able to do so. When not, there will be more and more users with this issue when upgrading to PHP 8

    I’m quite sure other plugins use get_sample_permalink(). They’ll have the same problem. I would love to fix this bug but I can’t, sorry.

    I’m sure it will be fixed in the next release of WordPress.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘compatibility issue with PHP 8’ is closed to new replies.