Bug 41449 – phpmyadmin-2.5.6_rc1 startup error

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Roy Marples (RETIRED) 2004-02-13 02:05:22 UTC]

After emerging to phpmyadmin-2.5.6_rc1 from the prior version, I get the following error after logging in

Fatal error: Unknown function: pma_sqp_iserror() in /var/www/localhost/htdocs/phpmyadmin/libraries/common.lib.php on line 488

Going back to the prior version works.

The only think I've changed from the default install is the password for pma to match the password in the database.

Reproducible: Always
Steps to Reproduce:
1. Emerge phpmyadmin-2.5.6_rc1
2. Configure user pma to access your mysql database
3. Get the error

Actual Results:  
Fatal error: Unknown function: pma_sqp_iserror() in
/var/www/localhost/htdocs/phpmyadmin/libraries/common.lib.php on line 488

Expected Results:  
phpmyadmin screen

[Comment 1 Martin Holzer (RETIRED) 2004-02-13 03:59:14 UTC]

emerge (and read einfo msg)
etc-update
make sure mysql is running
ebuild /var/db/..... config
type in mysql root passwort

[Comment 2 Roy Marples (RETIRED) 2004-02-13 04:23:58 UTC]

I found out what I was doing wrong - editing the config file and putting the OLD pma password in it's place before doing the ebuild config thingy.

Maybe a note on the ebuild saying don't edit the config until this is done?

[Comment 3 SpanKY 2004-02-13 09:35:59 UTC]

well, portage doesnt overwrite your config file by default, you had to tell it to do so ...

it isnt 100% no obvious that when doing so you overwrite the admin password, but we're not exactly in the business of explaining config files to people ...

[Comment 4 Roy Marples (RETIRED) 2004-02-13 09:51:28 UTC]

No you mis-understand - this is what I meant

1. emerge phpmyadmin
2. etc-update (-5 to merge both files)
3. edit /etc/phpmyadmin/config.inc.php to change pma's password, disable warning and enable compression
4. ebuild foo bar config

Step three is what causes the error in my case.
Avoiding step 3 gives works fine and editing the config file after is fine.

Why this is the case I don't know, but a note on the ebuild to state "don't edit the config file before ebuild foo bar config" wouldn't go amiss as the reason why I did this was to change pma's password to the current one I had manually set - which is standard for the rest of the PHP/mysql apps I have (horde, prelude-nids, piwi).

[Comment 5 Eduard Warkentin 2004-03-13 19:29:05 UTC]

I solved this issue with grabbing the right file for the ebuild config after emerging it.

Category for php should be 'dev-db' and not 'phpmyadmin...' as displayed in the info text after emerging phpmyadmin.

Eduard
[e-mail]