On Wed, Jan 9, 2013 at 7:13 PM, Madhura Jayaratne madhura.cj@gmail.comwrote:
On Wed, Jan 9, 2013 at 6:43 PM, Rouslan Placella rouslan@placella.comwrote:
On 01/09/2013 12:56 PM, Alex M wrote:
On Tue, Jan 8, 2013 at 6:38 PM, Alex M <alex.ukf@gmail.com mailto:alex.ukf@gmail.com> wrote:
The demo server seems to be working fine, so I guess it's a local problem. I still can't figure it out though. I pulled everythingagain,
and it works just fine on windows 7, but it still doesn't show anything on Ubuntu 12.04 (no matter the browser). Other remote branches don't help either. Anyway, it's my fault somehow.I really don't have any other ideas left. I tried older versions,
nothing
happens. I used the Ubuntu phpmyadmin package, same problem. I rewrote the config.inc.php, and I also used the /setup/ script (/setup/ loads just fine). I've changed all possible permissions. Those resources just won't load.
I've looked in the source file (which seems to be OK) and I've noticed that [1] and [2] are actually the only ones that throw a 355 error. Also, Firefox and Opera show me some links, but there is absolutely no CSS loading.
I'm guessing it's some kind of mix of the latest Ubuntu updates, my apache and/or php. It's a bit frustrating, because now I can't use PMA in any way here. I'm really curious if anyone else will also encounter this problem.
[1]
http://localhost/pma_github/phpmyadmin.css.php?server=1&token=5873545bd6...
[2] http://localhost/pma_github/js/get_image.js.php?theme=pmahomme
Hi Alex,
please take this conversation elsewhere. The "help" or "support request" forums seems to be more appropriate in relation to your issue than the development mailing list.
Bye, Rouslan
Hi all,
I am experiencing the same problem on one of the windows machines, but not on the one I usually use for development. It will be prudent to discuss this matter here if it turns out to the a problem for a large number of users as this is an absolute show stopper. We surely do not want to give the users a broken major version! I will try to do some investigations to see if I can figure out what's causing this.
I tried bisecting and the first bad commit is 44c12545fc863. Still I have no clue what's causing this.