-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
[BUG] Unable to find manual scan button #488
Comments
The scan button in that location was removed, I believe it was during the library settings redesign (3ab0593). I meant to add one to the
In the meantime, assuming you are not a managed user on a stump instance without permission to scan, you have access to scan using the primary sidebar (3 dots next to library name opens a menu, click |
Is there any way to do a manual scan if a user has the primary topbar option selected in appearance settings? I now see the manual scan option after switching from topbar to sidebar, but I personally prefer the look of the topbar better. That would explain why I couldn't find that button before. Thanks for clarifying. |
Now that you mention it, I don't think there is! I've edited my previous checklist to include adding something there. The topbar is one of those things I added a while ago after being asked for it, but haven't had the time to revisit it. No promises, but I'll aim to get some of these changes sometime before |
* wip: give topbar love, add layout docs initial effort towards #488 * small misc improvements
Description of the Bug
Hi, according to the Libraries section of the documentation:
However, I am not able to find any buttons that would allow me to manually scan a library.
In addition, clicking on the filesystem scanning link in the documentation goes to a page that does not exist.
Expected Behavior
A button to manually scan a library should be present in the library overview page according to the documentation.
To Reproduce
Steps to reproduce the behavior:
Environment:
Build Details:
The text was updated successfully, but these errors were encountered: