Closed GoogleCodeExporter closed 9 years ago
Not at all, it is just base64 encoded and is decoded before processed. Don't
know why would you want to send password back to the user, but with the
attached version you can use the parameter %password%.
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 7:21
Attachments:
It's mostly just for record keeping, thank you so much! (and I gave you some
euros for this excellent project, buy yourself a beer!).
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 7:30
[deleted comment]
so I tried it out, and it looks like it's still encoded:
†ïyÎ7m·¶iïZi®\sá͡ovº
for a password I generated via the backend of mollify.
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 7:41
I tried it myself, and got plain password. Which version are you using?
Password strategy was changed at some point, but it was quite a long time ago
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 7:43
I'm using mollify 1.8.5.3 ( upgraded just as you were posting 1.8.6 :P ) would
upgrading fix it?
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 7:51
1.8.5.3 isn't that old, it should have the same password strategy.
Are we talking about the same thing? I was wondering what did you mean with
"for a password I generated via the backend of mollify", because registration
does not create passwords in backend, it uses the one user gives in the browser.
You are not talking about the lost password plugin?
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 7:57
Alright so I tested the actual registration page versus adding a person via the
admin panel, and it looks like it MD5 encodes the password before it submits
the pending registration when you do it via the admin screen, the registration
page shows the password as plain text.
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 7:58
Oh yes, you meant the admin tool. You are right, it does md5 and it shouldn't.
I'll fix that.
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 8:01
This fixes that one as well.
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 8:05
Attachments:
And registrations.js goes into the "backend/plugin/Registration/admin"
Original comment by samuli.j...@gmail.com
on 3 Feb 2012 at 8:06
Thank you, you're the best!
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 8:06
[deleted comment]
Nevermind about the previous statement, i had to reset my browser to get around
the caching but it works now.
Original comment by spacer...@gmail.com
on 3 Feb 2012 at 10:39
Fixed in 1.8.6.2
Original comment by samuli.j...@gmail.com
on 24 Feb 2012 at 5:38
Original issue reported on code.google.com by
spacer...@gmail.com
on 1 Feb 2012 at 10:37