> One question though: Could you explain what GUINDILLA_CALENDAR_BASE
> refers to?
When you put an app somewhere it always comes with an urls.py that you
include in your main urls.py.
When you include that urls.py, you can include it under whatever name you want:
(r'^events/', include('guindilla.events.urls')),
In that case, people tend to hardcode teh /event/ part into the
get_absolute_url function of the model.
But what if you want to put it under:
(r'^parties/', include('guindilla.events.urls')),
?
Then your get_absolute_url function will stop to work. And probably
some of your views that use HttpResponseRedirect as well.
A solution to solve this is to simply add the events or parties part
of the url by hardcoding it into the templates. It's what I do in
guindilla.
But there's IMHO a better way (that I am going to add to guindilla as
soon as I have time and will :-) And that's to allow the user to
define in the settings.py what he wants to use as the base (events,
parties,....), while giving a default value.
So, in my case, this is the GUINDILLA_CALENDAR_BASE. If you want your
urls to be of the like /events/whatever then do not define anything
anywhere. but if you want to use the /parties/whatever variant, then
you should define in your settings.py a
GUINDILLA_CALENDAR_BASE='events'
and everything will just work automagically, both the views and the
get_absolute_url.
Hope it's clear...
G
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
