KeyError Context about django-admin-shortcuts HOT 5 CLOSED

Hey, thanks for using my app :D. I'm just not entirely sure HOW you are using it. Since the context should always be available in the admin, I assume you must be using the template tag directly, on some other page than the admin. I'm really interested since I never thought about using it for anything else :)

from django-admin-shortcuts.

Hey, thanks for writing this app. I am also having that same error: KeyError: Context.
Do you mind explaining how to set up the "context"?

from django-admin-shortcuts.

Hey guys,
Alesdotio was correct, 'the context should always be available in the admin'. What I was doing was expanding the admin to include some more pages which is what I guess Kikin81 is doing too. Now the pages I was adding didn't technically count as admin pages as I was using another app to create them. Although I can't remember which now because I eventually took a different route with that site. (Still using admin-shortcuts!)

...(goes to look at site)...

That's right, I was using dbsettings (https://github.com/sciyoshi/django-dbsettings) Which created new pages and tables in the db used to edit global site settings instead of lumping stuff in the settings.py
The problem is that these pages weren't strictly admin pages and the context wasn't passed through to them. This meant that when admin-shortcuts wanted to use the context it couldn't find it.

I ended up dropping dbsettings because it wasn't quite as versatile as what I wanted. I ended up creating models wherein the the site itself was a foreign key and the settings attributed to that key (I have examples if wanted).

Alesdotio, do you find that having the context in there is particularly beneficial? The problem being that it ties the use of the app to the django admin as opposed to being able to use it elsewhere. Obviously the name of the app is admin-shortcuts so it is implied that it provides shortcuts for the admin! But food for thought I guess.

from django-admin-shortcuts.

the context was added in this pull request #5

from django-admin-shortcuts.

Now it shouldn't raise a KeyError anymore. Does that help?

from django-admin-shortcuts.