SylvainTI / phpliteadmin

Automatically exported from code.google.com/p/phpliteadmin
0 stars 0 forks source link

Renaming the current DB causes problems #188

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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

Original issue reported on code.google.com by ykoro...@gmail.com on 5 Mar 2013 at 9:24

GoogleCodeExporter commented 9 years ago
4. change db in config
in fact, rename it to db-name2 and change in config to db-name2 (for example)

Original comment by ykoro...@gmail.com on 5 Mar 2013 at 9:33

GoogleCodeExporter commented 9 years ago
why do you use such technique $_SESSION[COOKIENAME.'currentDB'] ?

Original comment by ykoro...@gmail.com on 7 Mar 2013 at 7:16

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
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.

Original comment by crazy4ch...@gmail.com on 9 Mar 2013 at 1:28

GoogleCodeExporter commented 9 years ago

Original comment by crazy4ch...@gmail.com on 9 Mar 2013 at 1:28

GoogleCodeExporter commented 9 years ago

Original comment by crazy4ch...@gmail.com on 9 Mar 2013 at 1:43

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r350.

Original comment by crazy4ch...@gmail.com on 9 Mar 2013 at 1:45