starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

GetReturnURLMixin Support for Plugin Views #9681

New Issue
Closed
opened 2025-12-29 21:20:47 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:20:47 +01:00
Owner
Copy Link

Originally created by @9er-tom on GitHub (May 15, 2024).

Originally assigned to: @renatoalmeidaoliveira on GitHub.

NetBox version

v3.7.3

Feature type

Change to existing functionality

Proposed functionality

The automatic return URL generation for views (specifically object edit views) should be compatible with plugin views.

Currently only core views are supported as get_return_url() in netbox/utilities/views.py:137 does not include the "plugins:" namespace

Use case

This would alleviate the need for specifying default_return_url for plugin views

Database changes

No response

External dependencies

No response

Originally created by @9er-tom on GitHub (May 15, 2024). Originally assigned to: @renatoalmeidaoliveira on GitHub. ### NetBox version v3.7.3 ### Feature type Change to existing functionality ### Proposed functionality The automatic return URL generation for views (specifically object edit views) should be compatible with plugin views. Currently only core views are supported as `get_return_url()` in [netbox/utilities/views.py:137](https://github.com/netbox-community/netbox/blob/develop/netbox/utilities/views.py#L137) does not include the "plugins:" namespace ### Use case This would alleviate the need for specifying `default_return_url` for plugin views ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featuretopic: pluginsnetboxcomplexity: low labels 2025-12-29 21:20:47 +01:00
adam closed this issue 2025-12-29 21:20:47 +01:00
adam commented 2025-12-29 21:20:48 +01:00
Author
Owner
Copy Link

@alexblaeuer commented on GitHub (Mar 13, 2025):

I also run into this issue while developing a plugin and added the feature in my fork by getting the viewname of the model (693b10bd79). Can I open a PR for this issue?

@alexblaeuer commented on GitHub (Mar 13, 2025): I also run into this issue while developing a plugin and added the feature in my fork by getting the viewname of the model (https://github.com/alexblaeuer/netbox/commit/693b10bd79ed8a4630da6d960a113bcc8db4b9ed). Can I open a PR for this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low netbox status: accepted topic: plugins type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9681
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?