Could you please tell us what kind of page is the new target?
Did you overwrite the NavigationLogoLink variable into your config file? If you did, can you give us the value?
Thanks.
It seems that the logo (and its link) is managed by \PMA_NavigationHeader::_logo. And the link will be:
- your configuration
- or index.php
So, until now, it's quite hard to understand how the link can be something else.
Except if you went into setup and played with this variable (and even this is not sure), it seems that this configuration variable is not overwritten in the project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't have a scenario to reproduce, I only know that it happens frequently enough to be noticeable. When it happens, I believe that the target is the page I am currently on. I have not changed the target by configuration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Marc for your feedback.
Some other questions:
- Is the link wrong a second time after you noticed it?
- If it is, can you please give us the link, to see if there is something inside to understand why it's wrong? (If possible, get the link from the element, not from the browser navigation bar.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am still seeing this bug (master = cb942d3675c59d55059c132fbdb9cb74f18e4eaa). The link to index.php contains the db, token and goto parameters. db contains the database I am currently on, and goto contains db_structure.php.
Last edit: Marc Delisle 2015-06-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Marc,
Before the fix, I could reproduce the bug by right clicking on the database name in the navigation and opening phpMyAdmin in a new tab. But this seems to be fixed in QA_4_4 and master.
I suppose you still do not know an exactscenario to reproduce?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The scenario that was fixed does not necessarily require right clicking.
Going to db structure and refreshing or simply login back after timeout in db structure page caused the bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you please tell us what kind of page is the new target?
Did you overwrite the NavigationLogoLink variable into your config file? If you did, can you give us the value?
Thanks.
It seems that the logo (and its link) is managed by \PMA_NavigationHeader::_logo. And the link will be:
- your configuration
- or index.php
So, until now, it's quite hard to understand how the link can be something else.
Except if you went into setup and played with this variable (and even this is not sure), it seems that this configuration variable is not overwritten in the project.
I don't have a scenario to reproduce, I only know that it happens frequently enough to be noticeable. When it happens, I believe that the target is the page I am currently on. I have not changed the target by configuration.
Thanks Marc for your feedback.
Some other questions:
- Is the link wrong a second time after you noticed it?
- If it is, can you please give us the link, to see if there is something inside to understand why it's wrong? (If possible, get the link from the element, not from the browser navigation bar.)
Will give more details when I can reproduce.
Should be fixed with https://github.com/phpmyadmin/phpmyadmin/commit/37a40028e3b21bf537799c73c5cbe702ab4d9f1e
I am still seeing this bug (master = cb942d3675c59d55059c132fbdb9cb74f18e4eaa). The link to index.php contains the db, token and goto parameters. db contains the database I am currently on, and goto contains db_structure.php.
Last edit: Marc Delisle 2015-06-18
Marc,
Before the fix, I could reproduce the bug by right clicking on the database name in the navigation and opening phpMyAdmin in a new tab. But this seems to be fixed in QA_4_4 and master.
I suppose you still do not know an exactscenario to reproduce?
Unfortunately, I still don't have a scenario, but I can confirm that it does not involve right clicking.
The scenario that was fixed does not necessarily require right clicking.
Going to db structure and refreshing or simply login back after timeout in db structure page caused the bug.
It has been a while and I haven't seen this bug. Closing for now.