phpPgAdmin do not work any more in 11.28.28

[kjg]

After upgrade, accessing databases via cpanel - phpPgAdmin do not work any more

I see the databases, and when clicking one of them, I can see tables etc

I cannot see any data in the databases and not run SQL queries

In the left column there is only the text Servers and under that a X-d database icon plus the text PostgreSQL

Usually this expands into the different databases on the account and down via public - tables etc

The only thing happening when clicking "PostgreSQL" in left column is that the login form shows for a second or two in right column (main window) and after that the list of DB is shown in the right column.
Same thing if I click any of the database names and the "public" row is shown to the right. Etc etc In the left column, nothing happends.

But, I cannot browse any data, nor change, insert, query etc. And since I cannot open privileges settings, I cant add user or check settings

Is there another way to open phpPgAdmin until this is fixed?

// kjg

[kjg]

Updated:
Tested on another server and the same error occurs.

Tested with and without SSL and the same error occurs.

Server info:
Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8e-fips-rhel5
CentOS 5.5
WHM 11.28.28 (or 11.28.15 as it say in change log)
PostgreSQL 8.1.22
suphp
php 5.2.14

// kjg

[kjg]

Update again:
Tested to add the database via the Database Map Tool in WHM, but no success

Same error still.

Would really appreciate if someone could give me a hint in how to solve this. Our users really need to have phpPgAdmin access to the databases.

// kjg

[kjg]

For all of you that have the same issues, here are some good news:

I opened a support ticket for this and just got the reply:

"This issue has been repaired in the latest RELEASE build, if you run a '/scripts/upcp --force' this issue should be resolved."

//kjg

[kjg]

Unfortunately the new build did not solve the phpPgAdmin issue as it was supposed to do.

Upgraded all servers to 11.28.35 but it did not help.

Still no account can use phpPgAdmin

I am waiting for the cPanel support to give a new reply on this issue, but until then: If anyone has a solution on how to bypass the problem it would be appreciated.

// kjg

[cpanelnick]

kjg, Could you please post the ticket #?

Thanks

[kjg]

The latest response I got in the ticket was:

"I've replicated this behavior on a test server and created internal case #44688"

So I guess that is the number you need? Or?

// kjg

[cpanelnick]

Thanks, I was able to find your ticket number in the case. I will keep watching as it progresses to make sure you get resolution.

[kjg]

Got another reply yesterday from the excellent cPanel support staff.
It seems this is a browser related issue.

If you use Chrome, it works fine.

So until it is fixed in a coming release, you can use chrome.

// kjg

[cpanelkenneth]

This should be resolved in our next 11.28 build. There was some javascript doing the wrong thing, which would result in logging the user out of phpPgAdmin.

[deddy]

Chrome is no longer working since update to 11.28.39
In the meantime a real desaster.

[cpanelnick]

The fixed for this issue was merged into 11.28 @ 11/17/2010 (Today) 11:13 AM Central Time. It should be available in the next public 11.28 build.

[deddy]

No access to database(s).
phpPgAdmin page blinks as soon as open
although username/password seems to be
available now.

We return to stable where necessary.

[cPanelDon]

No access to database(s).
phpPgAdmin page blinks as soon as open
although username/password seems to be
available now.

We return to stable where necessary.

To the best of my knowledge the phpPgAdmin difficulty discussed in this thread should be fully resolved as of cPanel 11.28.42, while the latest available version is cPanel 11.28.45 as of the time of writing. I recommend to ensure that your cPanel installation is using the latest version available with automatic updates enabled. While it always an option to switch between update tiers, I would not consider reverting to a different update tier when it involves a significant downgrade (e.g., from 11.28 down to 11.26).

[deddy]

I'm so sorry but it is still not working.

Current version 11.28.45