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.

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

Closed
slavexe opened this issue Oct 22, 2024 · 3 comments · Fixed by #540
Closed

[BUG] Unable to find manual scan button #488

slavexe opened this issue Oct 22, 2024 · 3 comments · Fixed by #540
Labels
bug Something isn't working

Comments

@slavexe
Copy link

slavexe commented Oct 22, 2024

Description of the Bug

Hi, according to the Libraries section of the documentation:

To manually initiate a scan job, you can click the action button library selection menu on the sidebar and select "Scan". You may also navigate to the library's overview page and click the action button and select "Scan".

For more thorough information on library scans, see the filesystem scanning guide.

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:

  1. Go to library overview page
  2. Scan button missing

Environment:

  • OS: Linux

Build Details:

@slavexe slavexe added the bug Something isn't working label Oct 22, 2024
@aaronleopold
Copy link
Collaborator

aaronleopold commented Oct 22, 2024

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 scanning section of a library's settings, but looks like I forgot. I'll leave this open as a reminder to:

  • Update the documentation to point people to the right location
  • Add a button in the settings page
  • Revisit topbar navigation and give it some love

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 Scan).

@slavexe
Copy link
Author

slavexe commented Oct 22, 2024

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.

@aaronleopold
Copy link
Collaborator

Is there any way to do a manual scan if a user has the primary topbar option selected in appearance settings?

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 0.0.10 is released

@github-project-automation github-project-automation bot moved this to Backlog in v0.1.x Oct 22, 2024
@aaronleopold aaronleopold moved this from Backlog to Up Next in v0.1.x Oct 22, 2024
@aaronleopold aaronleopold moved this from Up Next to In Progress in v0.1.x Dec 24, 2024
aaronleopold added a commit that referenced this issue Dec 24, 2024
aaronleopold added a commit that referenced this issue Dec 26, 2024
@aaronleopold aaronleopold linked a pull request Dec 26, 2024 that will close this issue
aaronleopold added a commit that referenced this issue Dec 26, 2024
* wip: give topbar love, add layout docs

initial effort towards #488

* small misc improvements
@github-project-automation github-project-automation bot moved this from In Progress to Done in v0.1.x Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants