-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "last page" link in bukuserver doesn't use the current index #606
Comments
i can't decide about this one first this is flask-admin feature quick search for if we want to implement this, it mean several things
looking at that i don't know if the change is worth it @jarun comment? e: TIL it is called double angle quotation mark |
Please leave it as it is. Not a big deal. |
i think this issue can be closed for now reopen this if flask-admin have easier method to implement |
…After I've done some fiddling with flask/flask-admin, I can say for sure that this URL can be modified at runtime (i.e. after the page is rendered) to point at a custom redirect endpoint (or just set page number as |
…Correction: apparently redirects only work as return values, so |
…I've made a working implementation in a feature branch; it can be adopted as a pull request should you decide to go through with it. |
Please raise the PR. |
reopen this because there is ongoing pr |
* [#606] implemented a generic last-page endpoint * PR edit
When clicking on the "last page" link in bukuserver pagination (
»
), the page that's being opened isn't the current last page but the one that was last at the time of the current page rendering; if the bookmarks DB had been updated since then (i.e. there was enough bookmarks added/removed to change the amount of pages), the link would be pointing on a page which isn't the last one, or even a non-existing one.A correct way to open the last page in the list would be to send a parameter requesting the actual last page (such as
page=last
), to which the server could redirect to the current last page (e.g. using HTTP 302), or the URL could be updated by the client in-browser.The text was updated successfully, but these errors were encountered: