I have a multi-server setup, so I use "$cfg['ServerDefault'] = 0;" in my configuration file. This already lead to some problems, so I just want to make sure I mention this.
Reproduction:
- open phpMyAdmin "root" installation
- "General Settings" page is shown, the theme can be selected and a server can be selected
- select a server ("Replication Master" in my case)
- the actual login screen is shown along with an error - see attachment
Reproduction 2:
- open phpMyAdmin "root" installation in another tab
- "General Settings" page is shown, the theme can be selected and a server can be selected
- select the same server as in "reproduction"
- There is no login screen anymore, as the session is still valid.
- The PHP warnings are shown in the main window on the right. - Same warnings as before.
Cannot reproduce with 4.4.1.1 and ServerDefault set to 0.
Did you install your 4.4.1 in an empty directory, or did you overwrite a previous installation?
Which PHP version are you using?
I reproduced the problem with phpMyAdmin 4.4.2 on another computer (but same server):
My installation work-flow is as follows:
So in short, I never install an archive on top of another one - all into separate directories.
I am using a nearly stock Ubuntu 14.04 LTS installation.
PHP 5.5.9-1ubuntu4.7 (cli) (built: Mar 16 2015 20:47:39)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
I am using Apache and mod_php5. I have a gut feeling that it possibly could be related to OPcache which possibly might not like me changing the "htdocs" symlink. I stopped and started again Apache, so the shared memory OPcache cache should be emptied. Still, I could reproduce the problem.
I have configured my browsers to remove the browser cache on each shutdown. So by tomorrow, I expect OPcache to have a new cache (Apache restart) and my browser to have a new cache as well (shutdown cleanup).
Besides that, I am out of ideas.
Last edit: Alexander Schuch 2015-04-14
I've seen that this bug has been fixed already. Great!
Just for the sake of completeness, I can reproduce the issue with my very first reproduction steps.
As nothing changed at the server since yesterday, and my browser has an empty cache, I for the moment do not believe anymore that OPcache is the culprit. But I keep an eye on it, though.
Should be fixed with https://github.com/phpmyadmin/phpmyadmin/commit/fe3a103767bd5f68a89d2527c29ad1f2bcffc54a