-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
Admin page History button has broken link for historical objects. #527
Comments
Thanks for this @ahmed1293 ! I don't think that button ever worked. It's just there by default. You're more than welcome to submit a PR removing it or making it work. Thanks! |
rossmechanic
added
bug
Issues related to confirmed bugs
accepted
Issue accepted for completion
labels
Feb 15, 2019
Thanks for the response! Happy to help - will try to make time for this soon :) |
trumpet2012
added a commit
to trumpet2012/django-simple-history
that referenced
this issue
Oct 4, 2024
…iewing a historical entry
trumpet2012
added a commit
to trumpet2012/django-simple-history
that referenced
this issue
Oct 4, 2024
…iewing a historical entry
trumpet2012
added a commit
to trumpet2012/django-simple-history
that referenced
this issue
Oct 4, 2024
…iewing a historical entry
11 tasks
trumpet2012
added a commit
to trumpet2012/django-simple-history
that referenced
this issue
Oct 4, 2024
…iewing a historical entry
tim-schilling
pushed a commit
to trumpet2012/django-simple-history
that referenced
this issue
Dec 5, 2024
…viewing a historical entry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug
When viewing a historical object in the admin, the "HISTORY" button on the top right does nothing on-click.
To Reproduce
Expected behavior
On clicking the button, you return to the list of historical objects.
Screenshots
HTML from Chrome developer, showing an empty href:
Environment
Additional context
I'm not 100% sure if this is coming from your side or mine. Every other piece of history-functionality appears to be working - I cant see what would cause this bug.
The text was updated successfully, but these errors were encountered: