Pixrael Posted October 11, 2019 Share Posted October 11, 2019 In the Login/Register module I receive this error when the email exist but the password is incorrect. Any solution? Because the module has no new updates. Notice: Trying to get property 'name' of non-object in /var/www/vhosts/pdhvac.com/wms.pdhvac.com/site/modules/LoginRegister/LoginRegister.module on line 394 Link to comment Share on other sites More sharing options...
adrian Posted October 11, 2019 Share Posted October 11, 2019 In my version of this module I have changed so many things that it is almost unrecognizable, but I do see that I added: if($user) to the beginning on line 394 which should fix what you are seeing. 3 Link to comment Share on other sites More sharing options...
Pixrael Posted October 11, 2019 Author Share Posted October 11, 2019 @adrian I tried this and works with wrong password entries, but if both parameters are ok, then I get a fatal error: Error: Exception: Login not attempted due to overflow. Please wait at least 20 seconds before attempting another login. (in /var/www/vhosts/domain.com/app.domain.com/wire/modules/Session/SessionLoginThrottle/SessionLoginThrottle.module line 150) Link to comment Share on other sites More sharing options...
Pixrael Posted October 11, 2019 Author Share Posted October 11, 2019 Link to comment Share on other sites More sharing options...
szabesz Posted October 12, 2019 Share Posted October 12, 2019 17 hours ago, adrian said: In my version of this module Could you please share it via Github? If you were to maintain it publicly that would be graceful to say the least. It would probably be a good idea to rename it first, though. Thanks for considering! Link to comment Share on other sites More sharing options...
adrian Posted October 12, 2019 Share Posted October 12, 2019 1 hour ago, szabesz said: Could you please share it via Github? If you were to maintain it publicly that would be graceful to say the least. It would probably be a good idea to rename it first, though. Thanks for considering! Unfortunately my version doesn't just contain fixes but I've also hacked it to handle redirection to payment and lots of custom changes to the user's profile based on specific things to the site I am using it on. This is the first time I have used this module and unfortunately I don't think I'll be using it again - I know there are hooks to add custom behavior but they just aren't flexible enough and there are also just too many broken things. 1 Link to comment Share on other sites More sharing options...
szabesz Posted October 12, 2019 Share Posted October 12, 2019 6 minutes ago, adrian said: Unfortunately my version doesn't just contain fixes but... I see. Thanks for clarifying! Side-note: I did have a strong feeling that the module would not see too much maintenance, if any. That is why two years ago – when it was released – my first reaction to it was asking for adding it to the core. However, I did not know that the codebase in its current state just does not cut it... Link to comment Share on other sites More sharing options...
JeevanisM Posted May 16, 2020 Share Posted May 16, 2020 On 10/12/2019 at 2:05 AM, adrian said: In my version of this module I have changed so many things that it is almost unrecognizable, but I do see that I added: if($user) to the beginning on line 394 which should fix what you are seeing. Confirmed, this fixed the issue.. thanx for the lifeboat ? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now