giangel84

In order to fix this issue, you just need to update the code like this:

class Screen_Option_Hooker implements Hooker {

private $hook_suffix;
private $screen_help_tabs;
private $screen_option; //add this declaration

Hope this help.

In order to fix this issue and update the plugin, you just need to add these lines inside ACF_City_Selector Class:

class ACF_City_Selector {

    // Properties declaration
    public $settings;
    public $l10n;

This will maintain compatibility with PHP 8.2 (and earlier versions), and keep the logs cleaner.

Hi thank you for the quick reply, the update fixed it!

Best regards

Fixed!

The missing hook was this: woocommerce_after_checkout_form

By adding this hook to the custom checkout, the plugin is working properly!
Hope this can help others!

I had the same issue: error 400 while calling wp-json endpoint in order to connect the WP account (first step).

I managed that behaviour by switch off every plugin until I found which one was causing the conflict.
So I was be able to complete all the connections and then I re-enabled the conflicting plugin without any errors.

Hi @sanjuacharya77 ,

thanks for your reply, I submit the new request.
I hope the feature will be available soon.

Regards!

I don’t know if the concept is clear.

At the time there’s only one email that Admin can receive and it’s sent just after user is registered (even if their account is not confirmed).

There should be an additional kind of email, in addition to the existing “Admin email”. For example: adding an “Admin email after approval” or “Admin email after auto-approval”, in this way it is possible to disable the primary “Admin email” and enable only the other one.

Or keep both but with two kind of emails, you would have the possibility to have different contents.

I hope this explanation can remove any doubts.

Hi @sanjuacharya77,

I don’t want a manual approval from the Admin, I’m fine with the approval being automatic after the user has confirmed their email. The problem is the notification that arrives to the admin.

Currently a notification arrives to the admin immediately after the user has registered, even if they haven’t confirmed their account. This is the flow:

1) New user registered
2) Approval email with confirmation link is sent to user
3) Also the admin receive the email which inform the new user is registered.

Concept: if the user sent wrong information (bad email address), it can’t be able to confirm its account, but the admin receive the email notification as well…this is the issue.

I would like the notification email to the admin is be sent only after the user has confirmed their email, with this flow:

1) New user registered
2) Approval email with confirmation link is sent to user
3) The new user click the link to confirm its account
4) Now the admin receive the email which inform a new user is registered/confirmed.

Is it possible with the pro version?

Thank you.

It should be something like this:

add_filter('user_registration_after_register_admin_email', 'disable_admin_email');
function disable_admin_email() {
return false;
}

add_action( 'user_registration_check_token_complete', 'user_registration_after_email_confirmation', 10, 2 );
function user_registration_after_email_confirmation( $user_id, $user_reg_successful ) {
if ( ! $user_reg_successful ) { return; }
// send admin confirmation
user_registration_send_admin_confirmation_email($user_id);
}

I’ve practically resolved all the issues, except for the notification that remains completely white/blank.

By disabling the Litespeed cache plugin, all the other problems have disappeared. However, I would like to emphasize that CTX is the only plugin that experienced these issues; all the others are functioning without any problems. I should note, though, that even after disabling the cache at various levels, the problem persists, and it was necessary to completely disable Litespeed cache.

Solved:

The correct way is getting cart by using:

WC()->cart->get_cart_contents(); instead of WC()->cart->get_cart();

Meanwhile I fix the issue by editing the file “wp-megamenu/classes/class.wp-megamenu-base.php”.

I just embody the foreach loop content (line 382 to 420), with:

if (is_array($widget_item)) { //loop }

Bye!

I’m using PHP 7.4 which is the minimum version I must use for security and compatibility reason.

There’s no planned update for this plugin?

@dholovnia You don’t read my thread. ??

I repeat: Only “WooCoomerce” and “WooCoomerce Ajax Filters” active plugins.
No cache (neither with server or other ways).
Default wordpress theme.
Apache PHP 7.4

If you replicate this basic environment, you should get the same error.

You can’t see the error anymore, since the website is under development and I had to use another plugin after 24h.

Hello @rafinkhan thanks for your reply.

I did the update to v2.0.12 as suggested and tested a bit on both backend and frontend.
Now all is working fine!

Thank you very much for the quick fix!
Have a nice day. ??