Renaming the current DB causes problems
Issue #188
resolved
Originally reported on Google Code with ID 188
I cannot change database.
1. set password to empty
2. set 1 database in $databases
3. access PLA (you will get to DB with autologin)
4. change db in config
5. refresh PLA. It asks to logout, db not found. Really?
6. Click logout. Nothing happens
Reported by ykorotia
on 2013-03-05 21:24:04
Comments (6)
-
Account Deleted -
Account Deleted why do you use such technique $_SESSION[COOKIENAME.'currentDB'] ?
Reported by
ykorotia
on 2013-03-07 07:16:02 -
Hmm. I cannot exactly reproduce this. It creates an empty db with the old name for me - which is also not what should happen. I will have a look at it. > why do you use such technique $_SESSION[COOKIENAME.'currentDB'] ? So is the question "why is COOKIENAME there?"? Then the answer would be: You might have multiple php-scripts on your domain that use sessions or even multiple PLA installations. We prefix our session-variables with COOKIENAME to make sure we don't get into conflict with session-variables set by other scripts or PLA installations.
Reported by
crazy4chrissi
on 2013-03-09 13:28:06 - Status changed:Accepted
-
Reported by
crazy4chrissi
on 2013-03-09 13:28:16 -
Reported by
crazy4chrissi
on 2013-03-09 13:43:49 -
This issue was closed by revision r350.
Reported by
crazy4chrissi
on 2013-03-09 13:45:31 - Status changed:Fixed
- Log in to comment
Reported by
ykorotia
on 2013-03-05 21:33:03