Notice: Undefined variable: wll_settings in when-last-login.php on line 244

Hi Jack,

Thank you for using When Last Login, I’m really sorry you are experiencing this issue.

I have just tested this with 0.8 on my local environment and I am unable to recreate this issue.

In version 0.8, the code surrounding line 244 is one of our actions –

do_action( 'wll_logged_in_action', array( 'login_count' => $wll_new_value, 'user' => $users ), $wll_settings );

What version of When Last Login are you currently using?

Hi @andrewza,
Thanks for your reply.

Yes, I’m using the latest version of WLL.
My concern is that it records the login time at login and so shows you that time rather than the previous time.

Thanks,
Jack

Thank you for the feedback Jack, I have tried to recreate this issue and I am unable to do so.

I had also installed both free add-ons that are available on the repository but still this issue doesn’t get recreated.

Please can you install https://www.ads-software.com/plugins/debug-my-site/ and send through all the information that this plugin provides so I may try and recreate this issue for you.

Hi @andrewza,
Thanks.

On closer inspection, it’s possible that it’s a conflict with MemberPress – do you have a way to test this?

Notice: Undefined variable: wll_settings in /app/public/wp-content/plugins/when-last-login/when-last-login.php on line 244
Call Stack
# Time Memory Function Location
1 0.0003 366880 {main}( ) …/index.php:0
2 0.0010 367168 require( ‘/app/public/wp-blog-header.php’ ) …/index.php:17
3 0.0013 367520 require_once( ‘/app/public/wp-load.php’ ) …/wp-blog-header.php:13
4 0.0017 368256 require_once( ‘/app/public/wp-config.php’ ) …/wp-load.php:37
5 0.0021 372400 require_once( ‘/app/public/wp-settings.php’ ) …/wp-config.php:85
6 2.3967 19614936 do_action( ) …/wp-settings.php:448
7 2.3967 19615312 WP_Hook->do_action( ) …/plugin.php:453
8 2.3967 19615312 WP_Hook->apply_filters( ) …/class-wp-hook.php:323
9 3.0803 24761208 MeprAppCtrl::parse_standalone_request( ) …/class-wp-hook.php:298
10 3.0804 24761288 MeprLoginCtrl->process_login_form( ) …/MeprAppCtrl.php:664
11 3.0954 24937856 wp_signon( ) …/MeprLoginCtrl.php:169
12 3.1077 24964744 do_action( ) …/user.php:104
13 3.1077 24965120 WP_Hook->do_action( ) …/plugin.php:453
14 3.1077 24965120 WP_Hook->apply_filters( ) …/class-wp-hook.php:323
15 3.1086 24893680 When_Last_Login->last_login( ) …/class-wp-hook.php:298

Thanks,
Jack

Thank you for the feedback Jack, if you disable Memberpress does the issue still persist?

Please let me know – I have tried multiple ways to recreate this issue and I am unable to do so.

Thank you for your patience.

Hi @andrewza,

I think the problem might be caused by front-end forms that redirect afterwards.
Can you test with a wp_login_form() that redirects to a page on successful login and WP Debug switched on?

Thanks,
Jack

Thanks for the feedback Jack, I will be testing this during the course of today and revert as soon as I have more information regarding this.

Thank you for your patience Jack, I have tested a front-end login using the wp_login_form() and I am unable to recreate this issue. I created a simple shortcode to display this login form and it did not throw any errors when logging in via this form.

Are you using any of our When Last Login extensions?

Please keep me posted.

Thanks Andrew,
I don’t support you then have a copy of MemberPress to test this with do you?

Perhaps a login prompt created by a 3rd party plugin, such as Theme My Login?

Thanks,
Jack

I will work on getting a copy of MemberPress to test this further.

I have tested this with TML (I use this on my local environment) and there are no further issues.

I’m really sorry for this and working on resolving this really soon (after testing with MemberPress).

Thanks for your understanding Jack, I appreciate it ??

Not a problem. Look forward to seeing what you find out.

Thanks,
Jack

Hi @andrewza,
Thanks but is there any reason why we can’t continue this thread here? Might be useful for someone else in the future, you know?

Thanks,
Jack

Thanks for all your help.
This was fixed in the recent update (0.9)!

Great support!
Jack