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 in custom AdminSite #101

Closed
pandichef opened this issue Jan 18, 2023 · 2 comments · Fixed by #110
Closed

Bug in custom AdminSite #101

pandichef opened this issue Jan 18, 2023 · 2 comments · Fixed by #110

Comments

@pandichef
Copy link

I have multiple admin sites as described here.

I'm getting Reverse for 'djangoql_syntax_help' not found. 'djangoql_syntax_help' is not a valid view function or pattern name.

It's happening at <a href="{% url 'admin:djangoql_syntax_help' %}" class="djangoql-help"> in error_message.html.

I fixed it by creating a regular admin for now (which I only use to patch this error).

@stebunovd
Copy link
Member

Hi @pandichef,

thank you for reporting this. I have never used multiple admin sites before, so not sure what would be the proper way to fix this. Do you have any ideas?

@pandichef
Copy link
Author

Proper, no. I just created a regular admin for now to handle the exception.

Btw, as an aside, I couldn't get "suggest_options" to work in a schema used in a non-admin view. It's not critical for my use case, but I wanted you to know.

Notwithstanding the above, super package!

eliasfank added a commit to eliasfank/djangoql that referenced this issue Dec 6, 2023
Resolve ivelum#101

I'm also working with multiple sites and my solution was to use the name of the site according to the admin_site of the class.

This way it could make the app more dynamic and without any negative effects.
GreyZmeem pushed a commit that referenced this issue Dec 7, 2023
Resolve #101

I'm also working with multiple sites and my solution was to use the name of the site according to the admin_site of the class.

This way it could make the app more dynamic and without any negative effects.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants