Skip to content

NetBox 4.3.0: Two "Topology" buttons in the button-bar of every DCIM items #627

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

Closed
mathieumd opened this issue May 2, 2025 · 1 comment · Fixed by #628
Closed

NetBox 4.3.0: Two "Topology" buttons in the button-bar of every DCIM items #627

mathieumd opened this issue May 2, 2025 · 1 comment · Fixed by #628
Assignees
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@mathieumd
Copy link

NetBox version

v4.3.0

Topology Views version

v4.2.1

Steps to Reproduce

Use v4.2.1 with NB v4.3.0.

Expected Behavior

Not get double button.

Observed Behavior

I get two "Topology" buttons in every DCIM items, even Tenants:
Image

I guess it's because Topology plugin is not yet available for NetBox 4.3.0, of course.

@mathieumd mathieumd added the type: bug A confirmed report of unexpected behavior in the application label May 2, 2025
@meoww-bot
Copy link

meoww-bot commented May 3, 2025

Hello, can your plugin work properly with Netbox 4.3.0? I just started using Netbox and would like to know if the topology view generated by the plugin meets my expectations. I added a server and a switch and created a connection, but the topology view is empty. I am not sure if it is because Netbox 4.3.0 is not compatible with the 4.2.1 plugin.

UPDATE: I just found out that the topology map needs to be displayed after filtering. Please ignore my question.

BTW, I also encountered the problem of the title. It shows nothing after clicking either "Topology" button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants