Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter auctmore

    (@auctmore)

    That’s very good news. Thank you!

    Thread Starter auctmore

    (@auctmore)

    @amagsumov

    I’ve updated my four websites to Cleantalk security 2.59.1
    They all behave as they should including the admin login.

    I don’t know what has changed, but I am glad it did!

    Thank you for the amazing support!

    Thread Starter auctmore

    (@auctmore)

    @amagsumov

    No, I no longer see errors because the WP debug mode is ‘off’ now. I manage three other websites where I installed Cleantalk. I’ll upgrade those to 2.59.1 one by one.

    I’ll communicate my findings.

    Kind regards.

    Thread Starter auctmore

    (@auctmore)

    @amagsumov

    FYI:

    Meanwhile, I changed WP_DEBUG and WP_DEBUG_LOG to ‘false’ again. I tried the admin panel with 2.59.1 still installed. Success! I can log in! I can’t explain this! Can you?

    Kind regards.

    Thread Starter auctmore

    (@auctmore)

    Hello @amagsumov

    I reinstalled 2.59.1 on https://depatchmadammekes.be
    WP_DEBUG and WP_DEBUG_LOG in wp-config.php are both ‘true’.

    The public side of the website can be used but it shows:
    Notice: Undefined index: real in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php on line 145

    I can’t log into the admin panel because of a cooky error: “Cookies are blocked because of unexpected export” and the login form reappears. Above it the following output shows:

    Notice: Undefined index: real in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php on line 145 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-login.php on line 530 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-login.php on line 546 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-includes/functions.php on line 6360 Deprecated: strpos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/security-malware-firewall.php on line 1910 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-includes/pluggable.php on line 958 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-includes/pluggable.php on line 959 Warning: Cannot modify header information – headers already sent by (output started at /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-content/plugins/security-malware-firewall/lib/CleantalkSP/SpbctWP/Firewall/FW.php:145) in /customers/f/a/7/depatchmadammekes.be/httpd.www/wp-includes/pluggable.php on line 960

    I still can’t attach the debug.log file to this message.

    Thread Starter auctmore

    (@auctmore)

    PHP = 7.4.13
    WP = 5.6

    I reverted to 2.58.1 and I no longer have the log file. Moreover, I can’t reinstall 2.59.1 because it is no longer available at ww.wp.xz.cn. So, I can’t reproduce the error either.

    I don’t see an option here to attach a file to this reply.

    Thread Starter auctmore

    (@auctmore)

    No, version 2.59.1 from today doesn’t solve the problem. I had to revert to 2.58.1

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