Menu

#4710 (ok 4.3.8) Nav tree error after filtering the tables

4.3.7
fixed
None
1
2015-01-24
2015-01-17
keep
No
  1. Log into a server which has many databases
  2. Use pagination arrows or the dropdown to get to another page from the first one
  3. Use the filter to find a database
  4. Click on it
1 Attachments

Discussion

  • Marc Delisle

    Marc Delisle - 2015-01-17

    Cannot reproduce in 4.3.7. I click on "1 other result found".

     
  • keep

    keep - 2015-01-17

    I messed up the title. It happens when you use the database filter not the table filter.
    Here is a short video:
    http://screencast.com/t/bwHoLma14kBr

     
  • Atul Pratap Singh

    I can't reproduce either, the screencast attached appears pretty fast. Can you tell exact steps and whether the database you are searching is necessarily on the same/different page as the pagination ?

     
  • Alexander Kamp

    Alexander Kamp - 2015-01-18

    I can reproduce it:
    It's important to have many databases because then a pagination filter shows up (or lower the databases per page setting).

    In short:
    Navigate to page 2. Enter a filter value of a database which is on page 2.
    Then the error message will appear.

    In case you have a filtered result and pagination at page 2, you can repeat the reproduction by F5 and try to figure out what's going on. Because it also shows up after F5 - no ajax request made - it should be in php code.

    You can extend reproduction and compare requests by doing:
    - Reset filter (X)/navigate back to first page
    - F5
    - Navigate to second page
    - (Open console - network tab)
    - Click on database item (opens)
    - Fill in database name
    - Click on database item (fails - you see error message in response data)

     
  • keep

    keep - 2015-01-19

    Here is a longer screencast
    http://screencast.com/t/3G20WKjo

     
  • Smita Kumari

    Smita Kumari - 2015-01-19

    I am able to reproduce it in current master as well as QA_4_3 . Simply go on next page for database navigation and search a database which is already there then click on that database.

    I am looking into it.

     
  • Smita Kumari

    Smita Kumari - 2015-01-19
    • assigned_to: Smita Kumari
     
  • Smita Kumari

    Smita Kumari - 2015-01-20
    • assigned_to: Smita Kumari --> Atul Pratap Singh
     
  • Atul Pratap Singh

    Please try https://github.com/phpmyadmin/phpmyadmin/pull/1466 which also includes other usability improvement in fast filter.

     

    Last edit: Atul Pratap Singh 2015-01-20
  • Alexander Kamp

    Alexander Kamp - 2015-01-21

    I've applied the PR.

    During usage in a ongoing session I mentioned in 'sessionStorage' the values for navTree and page are 'undefined'. After deleting (or close/open tab) both variables I can see HTML data is set and no more problems appeared.

    You can question yourself the way parts of the navigation pane are saved temporary.
    Generated HTML can be a risk when you don't verify it the next time you use it. (tested by adjusting variables -> it injects code into page). Maybe rebuilding from JSON data or add hash+check is an option.

    I like the new behavior to search all databases on the server. The given label is technically correct, but from user point of view incorrect. It should be something like
    'To search all databases on server, press Enter after a search term'.

     
  • Atul Pratap Singh

    Thanks, opened a bug ticket for the missing checks on sessionStorage: https://sourceforge.net/p/phpmyadmin/bugs/4725/

    And surely the message you suggest makes more sense for the new fast filter behavior, I will modify the message.

     
  • Atul Pratap Singh

    Merged 1466!

     
  • Atul Pratap Singh

    • summary: Nav tree error after filtering the tables --> (ok 4.3.8) Nav tree error after filtering the tables
    • status: open --> resolved
    • Priority: 5 --> 1
     
  • Marc Delisle

    Marc Delisle - 2015-01-24
    • Status: resolved --> fixed