Hello,
Thanks for the report.
For information too, this is due to the use of PHP 8 for which phppgadmin is not yet completely ready.

CC: (none) => yves.brungard_mageia
Summary: user can't connect with login/password, error "Virtual Class -- cannot instantiate" => phppgadmin: user can't connect with login/password, error "Virtual Class -- cannot instantiate"

Thank you for the report + reference.
That was somewhat vague about PHP8. Nothing we can do before they move.

Assigning to Marc for the package.

Assignee: bugsquad => mageia
Status: NEW => UPSTREAM
Severity: normal => major

I think we can apply those changes - e.g. each was deprecated years ago.

Updated phppgadmin

Applied some upstream patches, to support latest installed php-version


Files located in core/updates_testing:
phppgadmin-7.13.0-1.1.mga8.rpm

SRPM:
phppgadmin-7.13.0-1.1.mga8.src.rpm

Assignee: mageia => qa-bugs

I tried the new package, but the issue remains.

I had to fix it with the same workaround :
https://github.com/phppgadmin/phppgadmin/issues/119

I had to replace /var/www/phppgadmin/libraries/adodb directory with this one :
https://github.com/ADOdb/ADOdb/

(In reply to regis carles from comment #5)
> I tried the new package, but the issue remains.
> 
> I had to fix it with the same workaround :
> https://github.com/phppgadmin/phppgadmin/issues/119
> 
> I had to replace /var/www/phppgadmin/libraries/adodb directory with this one
> :
> https://github.com/ADOdb/ADOdb/

Thank you this is working for me.

CC: (none) => dieter

We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Resolution: (none) => OLD
Status: UPSTREAM => RESOLVED

This issue is still present in Mageia 9, but the workaround from comment 5 cures it. Cann(t this be correctef in M9

CC: (none) => herman.viaene
Resolution: OLD => (none)
Status: RESOLVED => REOPENED

Changing the version to Mageia 9, and assigning it back to Marc Kramer.

Version: 8 => 9
CC: (none) => andrewsfarm
Assignee: qa-bugs => mageia

Suggested advisory:
========================
Fixed an issue which prevents executing pgadmin on php 8.
Note that there is no active development upstream.


Updated packages in core/updates_testing:
========================
phppgadmin-7.13.0-2.1.mga9.noarch.rpm

SRPM:
phppgadmin-7.13.0-2.1.mga9.src.rpm

Assignee: mageia => qa-bugs

It seems that there is a maintained fork: https://github.com/ReimuHakurei/phpPgAdmin
For cauldron, we need to commute to such a fork or withdraw this package.

It seems that there is a maintained fork: https://github.com/ReimuHakurei/phpPgAdmin
For cauldron, we need to commute to such a fork or withdraw this package.

The fork appears also far from beeing maintained actively. Last activity 2023.

(In reply to sturmvogel from comment #13)
> The fork appears also far from beeing maintained actively. Last activity
> 2023.

The last release but not the last commit that is Nov 23 2024

Ok, if you call changing a URL as maintaining code actively, than you are right.

(In reply to sturmvogel from comment #15)
> Ok, if you call changing a URL as maintaining code actively, than you are
> right.

I not check the commit message sorry, but if we decide to swicht and keep this the 71 commits from the original version could be a good motive, but I will not check if that changes are meaningful that is for more skilled than me ;)

MGA9-64 Plasma Wayland on Compaq H000SB
No installation issues.
To test, installed postgres 15 , but then after logging in I get "Version of PostgreSQL not supported. Please upgrade to version or later."
15  is the latest we have, so I will try 13.

Deleted postgres15, installed postgres13.
Now phppgadmin can connect and I can create a database and a table in the public schema and insert a few records.
So IMHO, we could release that with the caveat that postgres15 is not supported.
But it is less than I would expect.

So, what is the conclusion?? As far as I am concerned, it can go, doesn't it??

Looks good to me, Morgan please write the Errata about this just works with postgres13

CC: (none) => fri
Whiteboard: (none) => MGA9-64-OK

Not my area of expertise, but this reads like it's better than it was. I guess making it work with postgres15 would be something for another bug.

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Confused: after update. do it work with postgresql15 or need 13 ?

Confusion 2: You guys talk about postgres 13 and 15, but we only have postgresql13 and postgresql15 (the additional "ql" part) packages - Is this what you mean?


Suggestion for errata (if needed)

{{Bug|28582}} - ''phppgadmin'' (umaintained upstream) do not work with postgresql15. WORKAROUND: downgrade to postgresql13. Both are in Mageia 9.

(In reply to Morgan Leijström from comment #22)
> Confused: after update. do it work with postgresql15 or need 13 ?
> 
Don't work with 15 just with 13
> Confusion 2: You guys talk about postgres 13 and 15, but we only have
> postgresql13 and postgresql15 (the additional "ql" part) packages - Is this
> what you mean?
> 
> 
That surly was a typo that I repeat because I just copy from Herman's test

> Suggestion for errata (if needed)
> 
> {{Bug|28582}} - ''phppgadmin'' (umaintained upstream) do not work with
> postgresql15. WORKAROUND: downgrade to postgresql13. Both are in Mageia 9.

Could you add that current version was not working with php 8 even with postgresql13 and that is what is fixed by this update

Thank you :) Top in
https://wiki.mageia.org/en/Mageia_9_Errata#Various_software

(I wrote it as it is already in updates, expecting it to be moved very soon.)

Keywords: FOR_ERRATA9 => IN_ERRATA9

The advisory text doesn't say anything about postgresql13 which probably isn't a bad idea to have there.

CC: (none) => dan

(In reply to Dan Fandrich from comment #25)
> The advisory text doesn't say anything about postgresql13 which probably
> isn't a bad idea to have there.

Added a note about it, please note the in web the message says Add instead Update, a mistake by my part I fix the message but will not change for the web

(In reply to katnatek from comment #26)
> (In reply to Dan Fandrich from comment #25)
> > The advisory text doesn't say anything about postgresql13 which probably
> > isn't a bad idea to have there.
> 
> Added a note about it, please note the in web the message says Add instead
> Update, a mistake by my part I fix the message but will not change for the
> web

I detect a typo just in time

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2025-0006.html

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Dan my changes don't end in the published advisory

They'll be in the web version after the next push, which I'm doing now so in half an hour.