CODEWITHSUNDEEP
pythondjangodjango-urls
remy
remy

Reputation: 4763

Multiple django apps using same url pattern

I'd like to run two apps with the same url patterns. I would like to avoid having an app-specific slug like domain.com/pages/something-here or domain.com/blog/something-there.

I tried this:

# urls.py
urlpatterns = patterns('',
    url(r'^$', 'my.homepage.view'),
    url(r'^admin/', include(admin.site.urls)),
    url(r'^', include('pages.urls')),
    url(r'^', include('blog.urls')),
)

# pages/urls.py
urlpatterns = patterns('',
    url(r'^(.+)/$', views.page),
)

# blog/urls.py
urlpatterns = patterns('',
    url(r'^(.+)/$', views.post),
)

My code doesn't work, whichever include comes first (here, pages.urls) works ok, other urls (for blog) throw 404.

Thanks in advance

EDIT: I did it like this: created glue.py in the same directory as settings.py. It will handle my homepage and this dispatcher view:

def dispatcher(request, slug):
    try:
        page = get_object_or_404(Page, slug=slug)
        return render(request, 'pages/page.html', {'page': page})
    except:
        post = get_object_or_404(Post, slug=slug)
        return render(request, 'blog/post.html', {'post': post})

I don't know if it's ok. I hope there is a better way.

Thanks for the comments.

Upvotes: 1

Views: 4428

Answers (3)

zaidfazil
zaidfazil

Reputation: 9245

I don't know if this is a better answer. But, if these situations are satisfied for you..

  1. if your django app is based on django template rendering.

  2. The url you are talking about, need not be accessed directly by typing the endpoint in the browser itself.

Then, maybe you could consider url namespaces and template redirections.

https://docs.djangoproject.com/en/1.11/topics/http/urls/#url-namespaces

Upvotes: 1

Mirko Rossini
Mirko Rossini

Reputation: 409

This doesn't work because django urls are resolved in order, meaning that the first url that matches the regexp will be the resolved one. In your case, the the urls included from the blogs application will never be searched, as django already resolved the url on the pages includes line.

Also, the django url module is not supposed to know if a certain page or blog post exists, as i believe in your application this is determined with a database lookup.

The urls module just executes the view that is connected to the first regexp that matches.

You should change your logic, e.g. with perpending "blog/" to blog urls (what's wrong with that?)

   url(r'^blog/', include('blog.urls')),
   url(r'^', include('pages.urls')),

Notice that the i moved the blog url up, as most generic regxexp should always be the last to be tried by django url resolver.

Alternatively, you could code a proxy view that tries both blog posts and pages. but it doesn't seem the best way to do it to me.

Upvotes: 0

jeffknupp
jeffknupp

Reputation: 6304

How would you like this to work? They're both using the same URL (which of course is causing problems). How would a user get to a "page" rather than a "blog" or vice versa?

In general, you can't have overlapping URLs in your URL patterns (without including additional data).

EDIT:

So you want the first app to check if it has a view to match the URL and next to take over if the first doesn't? You could do something complicated like writing a "view matcher" to do want you want, but there are much more straigtforward solutions.

The easiest way would be to alter the slug generation function for one of your apps. Have one use some delimeter other than underscores, or always append the name of the app to the slug. This way you could find pages because their url would be "some-slug-page" and blogs would be "some-slug-blog", which you could then write a URL pattern for. If you don't want to add the entire URL, you can append/prepend just the first letter, or whatever you want.

Just think about a way that's acceptable to you to generate URLs for each app which, just by reading the URL, lets you know which app the page belongs to.

Upvotes: -1

Related Questions