• Resolved lstreng

    (@lstreng)


    Greetings!

    Recently I’ve upgraded to PHP v8 from v7.4. On v7.4 I had no PHP warnings/errors flagged, but on PHP v8 I find myself with a flood of the following:
    unlink(/code/web/wp-content/uploads/wflogs/template.0232964001657801493.tmp): No such file or directory

    WordPress: v6.0.1
    Plugins:

    
    +------------------+----------+-----------+---------+
    | name             | status   | update    | version |
    +------------------+----------+-----------+---------+
    | accordion-blocks | active   | none      | 1.5.0   |
    | acf-content-anal | active   | none      | 3.0.1   |
    | ysis-for-yoast-s |          |           |         |
    | eo               |          |           |         |
    | advanced-custom- | active   | available | 5.12.2  |
    | fields-pro       |          |           |         |
    | disable-comments | active   | none      | 2.3.6   |
    | display-environm | active   | none      | 1.3.1   |
    | ent-type         |          |           |         |
    | facetwp          | active   | none      | 4.0.4   |
    | flexible-table-b | active   | none      | 2.7.2   |
    | lock             |          |           |         |
    | cookie-law-info  | active   | none      | 2.1.2   |
    | gravityforms     | active   | none      | 2.6.4   |
    | kirki            | active   | none      | 4.0.24  |
    | wp-native-php-se | active   | none      | 1.2.4   |
    | ssions           |          |           |         |
    | pantheon-advance | active   | none      | 1.0.0   |
    | d-page-cache     |          |           |         |
    | pantheon-hud     | active   | none      | 0.3.1   |
    | safe-redirect-ma | active   | none      | 1.11.0  |
    | nager            |          |           |         |
    | searchwp         | active   | none      | 4.2.3   |
    | google-site-kit  | active   | none      | 1.78.0  |
    | google-site-kit- | active   | none      | 0.4.0   |
    | dev-settings     |          |           |         |
    | timber-library   | active   | none      | 1.20.0  |
    | wordfence-assist | active   | none      | 1.0.9   |
    | ant              |          |           |         |
    | wordfence        | active   | none      | 7.5.11  |
    | wp-cfm           | active   | none      | 1.7.4   |
    | wp-mail-smtp     | active   | available | 3.4.0   |
    | wp-redis         | active   | none      | 1.2.0   |
    | wordpress-seo    | active   | none      | 19.3    |
    

    Hosting: Pantheon – Noting that the site has followed Pantheon’s instructions for configuring WordPress when using Wordfence on their environment
    PHP: v8

    Any information/help would be much appreciated. The logs are flooded and it would be great to figure out how to resolve these warnings.

    • This topic was modified 3 years, 9 months ago by lstreng.
    • This topic was modified 3 years, 9 months ago by lstreng.
Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @lstreng, thanks for getting in touch with us!

    The issue you’re seeing is most likely to be solved by changing how Wordfence stores its logs, although doesn’t address whether there are any file permissions issues on your server when visiting Wordfence > Tools > Diagnostics. A specific area to check in your case would be “Filesystem” near the top.

    You can delete the wp-content/wflogs folder altogether and change Wordfence to log using MySQLi instead of files by following the instructions here: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    Currently, some plugins may not work well with WordPress, or indeed Wordfence on PHP 8. As PHP 7.4 will still be fully security supported until November 2022, not all bugs or deprecations will have been addressed by all plugin developers yet so it’d be safe to roll back to 7.4 if this is the case. Also, ensure all of your plugin versions are always fully up-to-date just in case any PHP 8 specific updates are released over time.

    Thanks,

    Peter.

Viewing 1 replies (of 1 total)

The topic ‘PHP 8 Wordfence Warnings’ is closed to new replies.