Skip to content
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.

Sign up for GitHub

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

Jump to bottom

"Move to archive" action triggers directory metadata and cover refresh #11772

Closed
offset-torque opened this issue May 8, 2024 · 1 comment · Fixed by #11774
Closed

"Move to archive" action triggers directory metadata and cover refresh #11772

offset-torque opened this issue May 8, 2024 · 1 comment · Fixed by #11774
Labels
enhancement

Comments

@offset-torque
Copy link

koreader_movetoarchive

Choosing Cancel in this dialog opens the File Browser at the last used directory and starts a metadata and cover refresh. I think this is an unintended behavior. Because when I tap OK instead of Cancel and then open the File Browser manually, this refresh doesn't happen and everything still works ok.
@hius07
Copy link
Member

hius07 commented May 8, 2024

Thank you, confirmed.
After testing the issue, I've got the directory records in the bookinfo_cache.sqlite3:

/mnt/us/books/
/mnt/us/books//
/mnt/us/books///

for every book.

@hius07 hius07 mentioned this issue May 8, 2024
Merged
Frenzie pushed a commit that referenced this issue May 16, 2024
@hius07
FileManager: safe initial path (#11774)
db63db1 
We do not like trailing slash in the path (except root).
Closes #11772.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FileManager: safe initial path hius07/koreader
2 participants
@hius07 @offset-torque