Menu
▾
▴
#1680 (ok 4.5) Human readable/writable URLs
It would be nice to have pretty URLs in phpMyAdmin.
for example, something like /table/db-name/table-name/structure for tbl_structure and so on.
Currently, It is not easy to hand-write a URL and go to specific page. We have to go through the UI all the way from index and it is painful sometimes on slow connections. Most of the time, it is not even possible to easily know the URL of current page.
Or at least, I would suggest to get rid of the microhistory part of the URL with html5 history API whenever possible.
About pretty URLs, I think that would necessitate web server level manipulation, so quite outside our scope..
Further, I agree in principle about replacing hash microhistory with HTML5 history API, but there can be concerns about backward browser compatibility..
Also, since https://sourceforge.net/p/phpmyadmin/bugs/4057/ has been fixed, user can use URL manipulation to reach db=>table..
All major browsers except IE 9- supports HTML5 history API. See http://caniuse.com/#feat=history, and we can easily have different mechanism for older browsers.
Also, about pretty URLs. No, we can pretty much arrive at this without a web server level manipulation. Without any web server manipulations, the URLs will look like
/index.php/table/...And a simple rewrite rule on web server can removeindex.php/.Well, about browser compatibility, of course you are right, I took it as a concern to be taken care of, not a limitation in principle or implementation.
About the index.php/table/ solution, it did cross me, but I personally find it an unnatural looking URL with .php/ and prefer the usual query string way.. so indeed if majority feels for this solution, we can consider discussing it..
Also, it's not about a simple or complex rewrite rule, its that we can't impose or expect web server privileges from our users.
Yes,
index.php/table/indeed looks unnatural.By simple rewrite rule, what I wanted to say was that permissions to write rewrite rule are commonly available even in shared hosting. But still, a valid concern.
In the meeting, we decided to implement the HTML5 history API and to not directly implement the rewriting.
About cleaning up the URL, see https://sourceforge.net/p/phpmyadmin/feature-requests/1684/ about removing the token.
When adding the history API, please also update https://wiki.phpmyadmin.net/pma/Microhistory accordingly
Just to note, we would need to keep the existing microhistory mechanism as a fallback if new API functions are unavailable in a browser.
Merged https://github.com/phpmyadmin/phpmyadmin/pull/1779