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

SLM Under Different Navigation Field #37

Closed
rudradevpal opened this issue Apr 22, 2024 · 2 comments · Fixed by #41
Closed

SLM Under Different Navigation Field #37

rudradevpal opened this issue Apr 22, 2024 · 2 comments · Fixed by #41
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@rudradevpal
Copy link

I have Just Started Using this plugin With Netbox 3.7.5 for managing Licenses in my organisation. Everything looks good and it's a perfect fit for my needs.
I just have 2 Queries regarding this:

  1. How I can Move it to a different Navigation Field? As of now, it's coming under Plugins. Is there any way that I can move it under some different or new field?
    image

  2. When In noebox we are not logged in it Shows the Plugin tab and SLM under this. Anyway to hide this
    image

@MartVisser
Copy link

Hi @rudradevpal

  1. I don't think you can adjust this via the GUI. Perhaps by adjusting the code, but this is a plugin after all, so it makes sense for us that it is under 'Plugins'. But suppose we will move it, if possible, what do you think would be a better place?

  2. I think there is a permission check missing on the menu items for the plugin. Can you take a look at this @wkoot? I think a 'permissions' variable is missing on the 'PluginMenuItem' items in netbox_slm/navigation.py.

@rudradevpal
Copy link
Author

@MartVisser Thanks for the reply.

  1. I guess a section called "Software" will be a better option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants