Bug 12906

Summary: this phpmyadmin release is totally broken
Product: Mageia Reporter: Marc Krämer <mageia>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: critical    
Priority: Normal CC: oe, tmb
Version: 3   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: phpmyadmin-4.1.8-1.mga3.src.rpm CVE:
Status comment:

Description Marc Krämer 2014-02-28 17:24:22 CET 
in almost every query exists js errors.
Can't show structure of tables, or add new columns.

This package should be removed immediately! Tools, essential as database frontends must work!

Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2014-02-28 21:10:18 CET 
No problems here.

it works for me on both mga3 x86_64 and mga4 x86_64, so you need to be more specific

What errors do you get ?

CC: (none) => tmb

Comment 2 Marc Krämer 2014-03-01 10:37:39 CET 
On Serverside only one error was raised:
Call to undefined function PMA_persistOption() in /usr/share/phpmyadmin/error_report.php on line 88

But in Frontend application a Box saying "an JS error appeared" is visible very often.
A few tables, with ~80 Columns & many enums/sets the structure is never shown. I don't know if this is the reason or anything else. But it was very annoying, if you have to change one of these fields and your tool doesn't work. I did a downgrade of that package to be able to work again.

It was a good insight for me, to keep an older version of that tool. That fancy JS-Framework they are using might look nice, but is worse in usage than the old simple html-version.

Anyway, I thought in one release of mageia no major updates are published through update-source. But this was one, in version (3.5 -> 4.1) and in usage.
David Walser 2014-03-03 21:02:07 CET

CC: (none) => oe

Comment 3 David Walser 2014-07-18 20:21:54 CEST 
4.1 uses JS whereas 3.5 didn't, but if it doesn't work, it's a browser issue.

Status: NEW => RESOLVED
Resolution: (none) => INVALID