On Sat, 2009-02-14 at 10:39 -0800, yuccaplant wrote:
> Hi all,
>
> I want to develop a cms and I want my urls partially to be user-
> defined, for example:
>
> /home/info
> /home/blog/-/post/
> /frank/blog/-/articles/2003
> /frank/bio
>
> The first part (the part before '/-/' if any) would map to an
> application in the database and is user defined (it could be
> anything). That first part could also define additional information to
> be passed to the application, in the case of a blog-application this
> could be the blog-id. So:
I think you're designing the implementation a bit in what follows,
rather than the functionality. All this talk of database lookups in
URLConf isn't appropriate, unless you want to write your own URL
resolver.
> /home/info
> A lookup in the database would return the application name: 'Page' and
> the page-id: '23'. The url conf of application Page should be included
> and the page-id passed to it.
How do we know what Page and page-id correspond to here? You haven't
explained what this is going to do.
If /home/ is the generic base URL, you could create a pattern that goes
before all the user-specific ones (below) that captures it and any
following information and passes the processing to a view function which
works out that it needs to return Page and 23 and then calls a
subsequent function.
>
> /home/blog/-/post
> A lookup in the database would return the application name: 'Blog' and
> the blog-id: '54'. The url conf of application Blog should be included
> and the blog-id passed to it. The included url conf takes care to map
> the second part of the url (post) to a view.
>
> /frank/blog/-/articles/2003
> A lookup in the database would return the application name: 'Blog' and
> the blog-id: '22'. The url conf of application Blog should be included
> and the blog-id passed to it. The included url conf takes care to map
> the second part of the url (articles/2003) to the apropriate view.
>
> /frank/bio
> A lookup in the database would return the application name: 'Page' and
> the page-id: '455'. The url conf of application Page should be
> included and the page-id passed to it.
Again, using an initial view to further refine things will work here.
The URL pattern will look like
url('^(?P<user>.*?)/(?P<application>.*)$', user_app_mapping),
and the user_app_mapping view could do something like this:
def user_app_mapping(request, user, application):
app_name, object_id = get_data_from_inputs(user,
application)
return real_view(app_name, object_id)
> So I would to have something like:
>
> urlpatterns = patterns('',
> (r'^(.*)$', include(<application-name>, <additional-info>)),
Except that include() doesn't work like that. You would need to write
your own function to do that.
> )
> (where <application-name> and <additonal-info> are found by a database
> lookup of the first part of the url.)
>
> I can't firgure out how the database lookup would fit in and how I
> could pass something like a blog-id to the included application url
> conf.
>
> Any ideas how I could accomplish this?
Either use intermediate views or look into writing your own URL resolver
subclass. The former is easier. The latter might allow you to write
everything in your URL Conf file, although whether that will be clearer
or not remains to be seen. It will also be a lot more work (and will
require reading the existing code and working out how to do it).
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
