Yeah I think I get what you're saying now. I found a few tutorials that used template tags to get data out of a model. Do you know if there are any examples of how to do this with a form?
On Feb 1, 2:56 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Adamr, I still think you're looking for template tags. My index page, > for example, just goes direct_to_template, then is filled up with > various things from all over... login form, and at least three other > apps. > > On Feb 1, 1:45 pm, "ashwoods" <[EMAIL PROTECTED]> wrote: > > > as far as i get it, its 1 view per url. - a view is a response to a > > request, you ALWAYS get only one request, and for each posible request > > (url) you make one view. > > so if there is something you want to use over and over again in more > > than one view (as a form), you just make a custom tag or a context > > processor. this creates a "variable", in your case a form, that will > > be available for all your "template-views". the form _should_ redirect > > to 1 view that processes the form, and then redirects you where ever > > you want. > > > On Feb 1, 8:38 pm, "adamr" <[EMAIL PROTECTED]> wrote: > > > > I still don't really grasp how that applies. > > > > For example, my url processor will use the included view which auto- > > > generates the login form when I go to "accounts/login/" > > > > Alternatively, when someone goes to the index page, the url processor > > > uses the "news" view so it can display the recent news from the > > > database. > > > > In my base.html template, I've made room for the login form. When > > > someone goes to the index page, all I want django to do is use the > > > view that generates the news, as well as use the view that will insert > > > the login form. > > > > On Feb 1, 2:04 pm, "ashwoods" <[EMAIL PROTECTED]> wrote: > > > > > i might not be understanding exactly what you mean, but i think what > > > > you want is > > > > this:http://www.b-list.org/weblog/2006/06/14/django-tips-template-context-... > > > > > On Feb 1, 7:54 pm, "adamr" <[EMAIL PROTECTED]> wrote: > > > > > > Sorry, django.contrib.admin.urls is the wrong view, I am trying to use > > > > > the correct login view. > > > > > > On Feb 1, 1:51 pm, "adamr" <[EMAIL PROTECTED]> wrote: > > > > > > > This seems like it should be a pretty easy concept, but I cannot > > > > > > figure it out. I've spent the past day searching for how to > > > > > > incorporate multiple views on the same page with absolutely no luck. > > > > > > This seems like a topic that would be crucial to incorporate into > > > > > > the > > > > > > documentation and/or tutorials. > > > > > > > On my website I want to have a persistent login form that's on one > > > > > > side of the page. So for example, my index page uses a view to > > > > > > display > > > > > > "news" posts from the database. How do I then also include the > > > > > > built- > > > > > > in authentication form on the side which uses the > > > > > > django.contrib.admin.urls view? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
