Long time bug

  • Resolved ezequielf057

    (@ezequielf057)


    4 years, 9 months ago

    Guys you have some bugs on your plugin:

    Bug 1

    ^ array:4 [▼
  "type" => 8
  "message" => "unserialize(): Error at offset 0 of 513 bytes"
  "file" => "...\plugins\wordfence\vendor\wordfence\wf-waf\src\lib\storage\file.php"
  "line" => 623
]

    It has been for long time there and its annoying because wordpress detect a php error and push the admin menu down to display the error on the top, but not error is displaying in there. Finally I got where is it causing the problem

    ————
    Bug 2

    Also this could be another bug:

    — I have this message on several sites.

    The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was November 25, 2019 9:38 pm, so this site may be missing new rules added since then. You may wait for the next automatic attempt or try to Manually Update by clicking the “Manually Refresh Rules” button below the Rules list.

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

    (@wfpeter)

    4 years, 9 months ago

    Hi @ezequielf057,

    I have seen some historical cases regarding the first message, but would like to grab a site diagnostic if possible from the one showing the unserialize error. You can send a diagnostic report to wftest @ wordfence . com. The link to do so appears at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Note: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

    The second message can often be rectified by navigating to your wp-content/wflogs folder and finding your rules.php file using your FTP or hosting file manager. You can actually delete the wflogs folder or just this file and Wordfence should try to repopulate it within 30 minutes. Are you seeing the exact same date on all sites, or is that just one example?

    Persistent problems with this file/folder after trying the above, can be avoided entirely by setting Wordfence to write to the MySQLi storage engine instead of a file if you prefer: https://www.wordfence.com/help/firewall/mysqli-storage-engine/

    Thanks and let me know how you get on,

    Peter.

Viewing 1 replies (of 1 total)

The topic ‘Long time bug’ is closed to new replies.