well, here's the thing. for this application, we are using database templates and a CMS system we created to manage content. so basically we have all of our urls in the urls.py file for things like a blog, a portfolio manager, tags, authentication, etc listed first. the last item in the urls.py file is for the CMS pages, and grabs everything in the URI with the following reg ex:
(r'^%s(?P<path>[^?#]*)' % (root_url), 'apps.cms.views.render'), in the render view we munge the URI from parent through child pages to find the final slug that tells us what page to retrieve for viewing. i suspect that something is going wrong in that department. what do you think? On Apr 23, 5:06 pm, Michael K <[EMAIL PROTECTED]> wrote: > On Apr 23, 10:13 am, plungerman <[EMAIL PROTECTED]> wrote: > > > > > greetings, > > > i am attempting to do a simpleredirectusing django'sredirect > > middleware. everything works fine if you want toredirectfrom one > > distinct URI to another, for example, > > > /big/ --->http://www.example.com/labowski/ > > > however, if you want toredirectto a child page in terms of the URI > > structure, it does not seem to work for me. for example: > > > /about/ --->http://www.example.com/about/broscoen/ > > > what we have here, is an about page that is not finished, so we want > > folks who request /about/ to go to a subpage but instead you see the / > > about/ page. > > Steve, > > I've had a similar problem before, unrelated toredirectmiddleware, > but related to urlconfs. What do your urlconfs look like for the > about pages/sub-pages? > > Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
