[GH-ISSUE #32] Delete fails from web interface #21

New issue

Closed

opened 2026-02-25 23:33:16 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:33:16 +03:00

Owner

Originally created by @csterritt on GitHub (Mar 2, 2018).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/32

I created several test links with the web front end, and tried deleting one. I got an error message, "no token present in request".

Originally created by @csterritt on GitHub (Mar 2, 2018). Original GitHub issue: https://github.com/go-shiori/shiori/issues/32 I created several test links with the web front end, and tried deleting one. I got an error message, "no token present in request".

kerem

2026-02-25 23:33:16 +03:00

closed this issue
added the
type:bug

component:frontend
labels

kerem commented

2026-02-25 23:33:16 +03:00

Author

Owner

@RadhiFadlillah commented on GitHub (Mar 5, 2018):

Hi @csterritt, sorry for late response.

So, while using the web interface, you succeed on adding several new bookmarks, but failed when deleting one of them ?

I got an error message, "no token present in request".

That message means that user session already ended, which makes the token expired and you have to login again. Do you delete the bookmark right after adding it, or several hours after adding it ?

Thanks.

@RadhiFadlillah commented on GitHub (Mar 5, 2018): Hi @csterritt, sorry for late response. So, while using the web interface, you succeed on adding several new bookmarks, but failed when deleting one of them ? > I got an error message, "no token present in request". That message means that user session already ended, which makes the token expired and you have to login again. Do you delete the bookmark right after adding it, or several hours after adding it ? Thanks.

kerem commented

2026-02-25 23:33:16 +03:00

Author

Owner

@csterritt commented on GitHub (Mar 5, 2018):

Hi @RadhiFadlillah -- it was pretty much immediate, within a minute.

@csterritt commented on GitHub (Mar 5, 2018): Hi @RadhiFadlillah -- it was pretty much immediate, within a minute.

kerem commented

2026-02-25 23:33:16 +03:00

Author

Owner

@RadhiFadlillah commented on GitHub (Jun 7, 2018):

@csterritt sorry for late response.

After checking around, I don't think this issue is a bug. The error message no token present means the user session already ended, so user have to login again, and this is the intended behaviour.

For now I've added better error message for clarity, and redirected user to login page when token expired (commit 4deed23).

@RadhiFadlillah commented on GitHub (Jun 7, 2018): @csterritt sorry for late response. After checking around, I don't think this issue is a bug. The error message `no token present` means the user session already ended, so user have to login again, and this is the intended behaviour. For now I've added better error message for clarity, and redirected user to login page when token expired (commit [`4deed23`](https://github.com/RadhiFadlillah/shiori/commit/4deed23fd45f10566968a6debf9e4fa5c6343258)).

kerem referenced this issue

2026-02-25 23:34:31 +03:00

[PR #21] [MERGED] Cleaned up command imports and descriptions #495