Thread

I’m not sure if I’ve hit a bug or an error in my process. I’d like your assistance in finding out 😊

We recently used the Member Import utility to import a large set of members. The password node in the XML file was set to a type of “text” because the plain text passwords were part of the import. We tested about 10 random users after the import to confirm that they accounts were imported properly and users could log in with the username and password from their old system. All of that worked perfectly.

Until we hit the lovely exception.

Our EE site has slightly different password requirements for minimum password length than the orignal data source’s site. We also have “Require Secure Passwords?” set to Yes for this site.

When logging in as a user whose imported password is shorter than our requirements, the method _check_min_unpwd() in the mod.member_auth.php file is catching it. Unfortunately I’m getting an error on this check due to line 196:

A PHP Error was encountered
Severity: Notice
Message: Undefined property: Auth_result::$member_id
Filename: member/mod.member_auth.php
Line Number: 196

I see this when debugging is enabled. When debugging is not enabled the user gets redirected to the homepage (definitely confusing and undesirable for the user experience).

Is this an EE bug by chance?

Furthermore, I notice that a redirect is hard coded into this method. We aren’t using the Member profile trigger word so I’m concerned that even if/when this particular issue is resolved that it will redirect my members to a useless URL. I realize using a 3rd party solution for member profile management can’t be supported by your team - but I’m at least interested in whether or not the 3rd party solution could/should be able to hook into functions like these. Any thoughts on that?

Details:
I’m on EE 2.2.2
I disabled extensions and still experience this.

Hello Erik,

I was able to recreate the error even with users registered in the EE Control Panel. I created a test user while secure passwords were off and minimum password length was 5. After creating the user and testing that it could login, I turned on require secure passwords and upped the minimum length to 9. Upon trying to login again, I received these errors. I’m pretty sure we can call this one a bug. I have filed this bug report, feel free to follow along 😊

Cheers,

Thanks Dan. Good to know you were able to replicate this. I will follow the progress of that bug to see where things go.

Did you or any of the dev team happen to have any thoughts on the second part of the post?

Furthermore, I notice that a redirect is hard coded into this method. We aren’t using the Member profile trigger word so I’m concerned that even if/when this particular issue is resolved that it will redirect my members to a useless URL. I realize using a 3rd party solution for member profile management can’t be supported by your team - but I’m at least interested in whether or not the 3rd party solution could/should be able to hook into functions like these.

Any thoughts on that?

Erik,

Thanks for pointing that out! I’ll ping the Devs on that particular point. They’ll be able to provide the clearest insight.

Cheers,

Thanks Dan. I look forward to their thoughts.

Erik

If you use the login form tag you can specify the post-login return via parameter, which is what it sounds like you’ll want to do.  Using the member templates, it isn’t a configurable.

That help clarify?

Thanks Robin,

We’re using the return parameter so we should be all set.

Erik

Love it when life is easy 😉.