manojmohandev
Forum Replies Created
-
Thanks for the response. 12.9 beta version fixed the issue.
What did you mean by “Back 12.7.1”? Did this issue start happening from 12.7.1 or to revert back my jetpack plugin version to 12.7.1?
Looking forward to it.
Hi @bizanimesh,
Thanks for the response.
I was talking about the admin dashboard page (/wp-admin/). Check this image. You can see I have disabled the Jetpack Stats option, and then also request to the API is made. If I have disabled the Stats module, it should not send request to Stats API.
This is the link
Here is the screenshot of the request for stats being sent when user is in dashboard.
https://prnt.sc/7bAbsFiKdUXROkay. Thanks for the information. Hope it will get resolved ASAP.
Thanks for the update.
Thanks for the consideration. Looking forward for the release.
It is basically a security concern to give the permission to upload directory which is the default directory used by wp-cerber plugin for report generation.
@gioni,
Thanks for the update. Looking forward for the bug fix.Does WP-Cerber consider this issue as a bug or not? Does the changes suggested is an ideal solution or do we need to change anything else as well?
Any update on this? I am also facing similar issue after upgrading to PHP 8.1.
Got error 'PHP message: PHP Fatal error: Uncaught Error: Undefined constant "AUTOSAVE_INTERVAL" in /wp-includes/script-loader.php:1804\nStack trace:\n#0 /wp-includes/class-wp-hook.php(308): wp_just_in_time_script_localization()\n#1 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters()\n#2 /wp-includes/plugin.php(517): WP_Hook->do_action()\n#3 /wp-includes/script-loader.php(2012): do_action()\n#4 /wp-content/plugins/wp-cerber/cerber-2fa.php(472): print_head_scripts()\n#5 /wp-content/plugins/wp-cerber/cerber-2fa.php(349): CRB_2FA::show_2fa_page()\n#6 /wp-content/plugins/wp-cerber/cerber-load.php(1750): CRB_2FA::restrict_and_verify()\n#7 /wp-content/plugins/...', referer: https://test.com/wp-login.php
in the console.I also found out on enabling “Defer rendering the custom login page” solves the problem. The issue happens when you are having custom login page and if you are not deferring the render of the login page, no function hooked in init action will work.
I can see the form action (html form action) itself has been modified to custom login url. I think for this feature, it would have been better to have one more check to disallow authentication whenever wp-login.php is on the referrer as well.
I think we should improve this confusing humans behavior so the form will use
the default login URL, not the configured one.It would be better.