"Browse" returns no rows, even if there are rows
joachimtingvold opened this issue · 9 comments
PostgreSQL 9.6.15
phpPgAdmin6 on latest master-branch (16b6650)
nginx/1.18.0
php7.3 (7.3.19-1~deb10u1)
Trying to hit "Browse" on a table returns "No rows found";
Using the same query in the "SQL" (sqledit, top right corner), results in correct rows being returned;
Video showing the issue (including issue #334 and #335): https://files.jocke.no/debug/phppgadmin6-issues_20200909.mov
Not the best comparison, but this works fine using phpPgAdmin v6.0.0-b28 on PostgreSQL 9.6.10.
I can add that this also works in phpPgAdmin6 v6.0.0-beta.47 (while broken in the release version for me).
Can you check if it does work for you in release v6.1.x?
I having trouble getting 6.1.2 to run at the moment. I'm getting:
The requested URL /src/views/login was not found on this server.
when I try to login. When I copy back a different version, it works immediately. By "copy" I'm just moving my different directories for v6-beta47, v6-release, and v6.1.2-tag into the path name for my apache alias directory.
I can at least confirm that when I get logged in to 6-release and get the rows issue, I can copy 6.1.2 into position on my web server, and the rows will display now - indicating the issue may be resolved. (It seems my issue with 6.1.2 is just getting through the sever login.)
weird... are you running it inside a subfolder?
Yes, I am running it within a sub-folder. With the sub-folder set in the config.
is your subfolder config defined with a leading slash ?
I'm pretty lost anyway. I've been trying to implement an url helper to output absolute urls for everything, but sometimes the subfolder is lost (therefore, I can't trust that relative urls will figure themselves out), others it's repeated (therefore, I can't just prepend the subfolder to every path).
Yeah it does have a leading slash. I tried with and without a trailing slash as well.
For now - to stay on task with this specific issue, I moved the project to the web root and tried again. In the 6.1.3 version, this rows issues is fixed!