07776: I can not log in after upgrade - LimeSurvey bugs and feature requests

This issue affects 1 person(s).

252

ID	Project	Category	View Status	Date Submitted	Last Update
07776	Bug reports	Security	public	2013-04-18 17:17	2013-04-19 14:03

Reporter	ong	Assigned To	mdekker
Priority	high	Severity	crash
Status	closed	Resolution	not fixable
Product Version	2.05 RC

Summary	07776: I can not log in after upgrade
Description	Hi I downloaded github master version with "latest commit 5dffe586bc limesurvey-translations authored 17 hours ago" Before I used 2.05 beta with the sorting error. I ran the setup routine. It told me my database is up to date and I would be forwareded. Error occured: user superadmin not found When I tried to refresh the page this error showed: CDbCommand failed to execute the SQL statement: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbtablename.lime_survey_permissions' doesn't exist (seems similar to this : https://github.com/LimeSurvey/LimeSurvey/commit/be5fced4a5f8f17c912a1bc70c1f856ad8dd9d0f )
Steps To Reproduce	don't know
Additional Information	the build number here is incorrect! I was not able to enter "master" (as the copy came directly from master/github (see above)
Tags	No tags attached.

Bug heat	252
Complete LimeSurvey version number (& build)	130325
I will donate to the project if issue is resolved	No
Browser	opera
Database type & version	mysql 5
Server OS (if known)	linux
Webserver software & version (if known)	apache
PHP Version	5.4

User List	There are no users monitoring this issue.

Date Modified	Username	Field	Change
2013-04-18 17:17	ong	New Issue
2013-04-19 14:02	mdekker	Note Added: 24990
2013-04-19 14:03	mdekker	Status	new => closed
2013-04-19 14:03	mdekker	Assigned To	=> mdekker
2013-04-19 14:03	mdekker	Resolution	open => not fixable

mdekker 2013-04-19 14:02 reporter ~24990	You were probably running on github, and not a released beta. In the 2.05 branch somewhere in time the database was changed (in dbversion between 2.00+ and latest dbversion on 2.05) and all dev. had to recreate the database. There was no such change after the first beta was released. Only solution is to reinstall with a clean database.