• Resolved WFSupport

    (@wfsupport)


    Welcome to Wordfence 6.0.5!
    We have some exciting fixes and changes in this release so please update ASAP.

    • * Improvement: Added option to disable SSL verification for hosts that have outdated versions cURL.
    • * Improvement: Added default of 127.0.0.1 when $_SERVER[‘REMOTE_ADDR’] is not set. Helps if you’re running WordPress cron from Linux cron.
    • * Improvement: Added compatability with Godaddy’s MU (must use) limit login plugin and our two factor. Change makes sure you can see the message from Wordfence to enter your cellphone code.
    • * Improvement: Added direction: ltr; to admin pages.
    • * Improvement: Added focus/blur events to scan activity log ajax to improve server performance.
    • * Improvement: Merged wp_option charset and database vulnerability scans to improve performance and make UI more intuitive.
    • * Improvement: Opened ‘See recent traffic’ in a new window from the Live Traffic page.
    • * Improvement: Updated browser pcap cache file for compatibility with detecting newer Firefox browsers.
    • * Fix: Fixed bug in directories excluded from scans (escaped directory separator).
    • * Fix: Updated known files and outdated plugins/themes to use wp_get_themes.
    • * Fix: Fixed bug with wfScanEngine where scans forked between scan_database_main and scan_database_finish would not display results of database scan.
    • * Fix: Added return false; to wfScan::error_handler to allow default error handler to process error.
    • * Fix: Fixed notice with wfUserIPRange::isValidIPv4Range.
    • * Fix: Fixed bug with ‘Allow HTTPS pages to be cached’ setting being unset after saving options.
    • * Fix: Fixed a couple of typos and spelling.
    • * Fix: Fixed errors upon plugin activation where wfConfig was queried before it was created.
    • * Fix: Fixed issue with notices from serializing wordfenceDBScanner and private properties belonging to parent class.

    Thanks all for the suggestions and feedback. Please remember not to post issues in this post, but open your own post at https://www.ads-software.com/support/plugin/wordfence per forum rules.

    tim

    https://www.ads-software.com/plugins/wordfence/

Viewing 9 replies - 1 through 9 (of 9 total)
  • WARNING WARNING WARNING – DON”T APPLY THIS UPDATER

    I applied the lastest WordFence update mentioned above and it completely stopped the site from presenting any pages….. The site no longer presents any public pages and I can’t get access to the login page. I have posted a ticket with WordFence but for now – I would not apply this plugin update…..

    DON”T APPLY THIS UPDATE — SOMETHING ISN”T WORKING CORRECTLY.

    I will post a follow up once I hear from WordFence

    WordFence support came through – apparently my site was applying the update just as WordFence support was patching the upgrade causing an incomplete update of my plugin.

    They recommended removing WF and then reinstalling; what I ended up doing was renaming the WordFence directory (which them allowed me to get into the site); WordPress Plugins still displayed WordFence as an installed plugin but indicated that it was deactivated and that there was an update available. I applied the update and then activated the plugin and everything worked. When I checked options/settings/etc. everything was back to normal and working.

    Other than this being somewhat frustrating that an update can be partially applied because the original source is in the middle of being updated/patched (chance timing) – the WordFence support was great and responded quickly. Love the product and am pleased with their support. Would suggest some time of lockup feature for plugin updates to prevent this type of thing from happening.

    Latest update has broken half of my sites all I get is:
    Parse error: syntax error, unexpected T_FUNCTION in /home/geofones/webapps/geof/wp-content/plugins/wordfence/lib/wordfenceClass.php on line 509
    When trying to access the sites ??

    Thank you ekgc – weird that only 15 of my 30 WP sites were affected when I upgraded Wordfence when using Infinite Word Press to upgrade them all.

    All seems to be OK now

    Got a report that files associated with this plugin were modified this morning which seemed odd as I didn’t get a notification there was an upgrade. I deleted and re-installed the plugin. Now getting this warning: Warning: call_user_func() expects parameter 1 to be a valid callback, class ‘wfScanEngine’ does not have a method ‘scan_options’ in /xxx/xxx/public_html/wp-content/plugins/ (line 126 – i think). Any suggestions?

    Same error message as dogstalker:
    [Jun 02 17:20:54] Warning: call_user_func() expects parameter 1 to be a valid callback, class ‘wfScanEngine’ does not have a method ‘scan_options’ in /home/aimetruyen/domains/aimetruyens.be/public_html/kroniek/wp-content/plugins/wordfence/lib/wfScanEngine.php on line 126 0

    Thread Starter WFSupport

    (@wfsupport)

    Please confirm you are using version 6.0.5 and not 6.0.4. Also I will need the php version on your website. Post in forums at https://www.ads-software.com/support/plugin/wordfence and not here. Any support issues posted in this post will not be answered.

    tim

    Getting this error with every request in New Relic since updating to 6.0.5 two days ago. I’m running WP 4.2.2.

    Error message
    MysqlError: Duplicate column name 'id'
    
    Sample stack trace
    …ery called at /data/home/mysite.com/httpdocs/wp-content/
    db.php (777)
    …/mysite.com/httpdocs/wp-content/plugins/wordfence/lib/
    wfDB.php (30)
    in wfDB::queryWrite called at ? (?)
    …/mysite.com/httpdocs/wp-content/plugins/wordfence/lib/
    wfDB.php (50)
    …mysite.com/httpdocs/wp-content/plugins/wordfence/lib/
    wordfenceClass.php (332)
    …mysite.com/httpdocs/wp-content/plugins/wordfence/lib/
    wordfenceClass.php (432)
    …mysite.com/httpdocs/wp-content/plugins/wordfence/
    wordfence.php (25)
    …_once called at /data/home/mysite.com/httpdocs/
    wp-settings.php (215)
    …re_once called at /data/home/mysite.com/httpdocs/
    wp-config.php (123)
    …uire_once called at /data/home/mysite.com/httpdocs/
    wp-load.php (37)
    …ce called at /data/home/mysite.com/httpdocs/
    wp-blog-header.php (12)
    in require called at /data/home/mysite.com/httpdocs/index.php (17)
    Thread Starter WFSupport

    (@wfsupport)

    Please post in forums at https://www.ads-software.com/support/plugin/wordfence and not here. Any support issues posted in this post will not be answered.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Wordfence 6.0.5 is live!’ is closed to new replies.