Open GoogleCodeExporter opened 8 years ago
* Are you using version 0.8?
* To be clear, did you both reset the data and load the default site?
* Did you change the default account password before it was removed?
* To be clear, did you try to login using the new administrator?
* Were you working on a site before the reset/load? (Did you restore a backup?)
If none of these work, I can try to replicate the problem on a test site.
-Ted.
Original comment by ted.husted
on 11 Jan 2011 at 11:33
Thanks for the quick response.
*
*
* I tried changing the version and updating the existing one,but with the
new version also I couldn't logged in. *
* I haven't used a backup.*
*
*
* If you can guide me to isolate the problem.I can go through the code and
fix the bug.*
--
* Best Regards,*
* Ashan Fernando*
* *
* Undergraduate *
* **Department of Computer Science & Engineering*
* University of Moratuwa Sri Lanka.*
*Google Talk Chatback:Google Talk Username:Ashan256 Yahoo! ID:Ashan256 Live
Messenger Id:Ashan.Fernando Skype User Id:AshanFer
*
* facebook:http://www.facebook.com/Ashan.Madushanka Linkdin:
http://lk.linkedin.com/in/ashanfernando*
*
*
Original comment by ashan256
on 12 Jan 2011 at 1:48
I have experienced the same two times during fresh install of current trunk
version.
- Uploaded Vosao to new appspot
- Logged in as admin@test.com
- Configuration -> Reset
- Can't login using admin@test.com - says 'Incorrect password'
What I tried to do but without success:
- using datastore viewer I updated name, email and password fields of
UserEntity (copied from working Vosao instance)
- still 'Incorrect password' (although user name recognized)
What I did to restore access:
- Press 'Forgot password', entered test@admin.com
- Mail not sent but I can see 'forgotPasswordKey' property in datastore viewer
- issued /_ah/changePassword?key=... request - success
- changed password to new one
The same scenario repeated when running Vosao on development server locally on
my PC. This time I went straight to 'Forgot password'.
Original comment by yaro...@gmail.com
on 20 Feb 2011 at 9:13
Original issue reported on code.google.com by
ashan256
on 11 Jan 2011 at 8:38