django-class-based-views

I have a page with a list of users, and would like to be able to click a link to update their profile. When 'update' is clicked, I should be able to edit the username, first name, ... email, phone number, department etc, in a single page, using a single submit button. I accomplished this by using two forms, one for User, and one for the extra information. The ListView, DeleteView and CreateView work perfectly with these two forms, but not the UpdateView. I am not able to instantiate the two forms with initial data. The question is: how do I instantiate the two forms with data? Overwrite self

i've two concatenated form. Basically user fills in the first form and then is redirected to the second one which adds value to the data of the first form. E.G. I've a form Movie (first form) and then i'm redirected to the form (actor) which add the actor to the movie. in my case the Movie = Chiamata and Actor = Offerta (i keep the italians name for what i need :D) fine. those are my urls in the urls.py url(r'^chiamata/$', ChiamataCreate.as_view(),name='chiamata_create'), url(r'^chimamata/(?P<pk>\d+)/offerta$', OffertaCreate.as_view(), name='offerta_create'), i've this create view class

I'm following a tutorial where my urlpatterns are: urlpatterns = patterns('', url(r'^passwords/$', PasswordListView.as_view(), name='passwords_api_root'), url(r'^passwords/(?P<id>[0-9]+)$', PasswordInstanceView.as_view(), name='passwords_api_instance'), ...other urls here..., ) The PasswordListView and PasswordInstanceView are supposed to be class based views. I could not figure out the meaning of the name parameter. Is it a default parameter passed to the view? No. It is just that django gives you the option to name your views in case you need to refer to them from your code, or your

I'm trying to create a dialog which uses jquery's .load() function to slurp in a rendered django form. The .load function is passed the pk of the "alert" object. Also available in the class functions are things like self.request.user so I can pre-fill those fields, shown below in the Message model (models.py): class Message(models.Model): user = models.ForeignKey(User) alert = models.ForeignKey(Alert) date = models.DateTimeField() message = models.TextField() Subclassing django's CreateView makes it pretty easy to generate a context with an instance of the ModelForm (views.py): class

I am trying to update the Django User model with the class based UpdateView that automatically renders with the current user but am getting an error that a pk or slug is required. The form work and renders with the proper current user context but throws the error when I try to submit the changes. Below is the view I am using: class UserUpdateView(UpdateView): form_class = UserForm model = User template_name = 'members/user_update.html' def get(self, request, **kwargs): self.object = User.objects.get(username=self.request.user) form_class = self.get_form_class() form = self.get_form(form_class)

I read today that Django 1.3 alpha is shipping, and the most touted new feature is the introduction of class-based views . I've read the relevant documentation , but I find difficult to see the big advantage™ that I could get by using them, so I'm asking here for some help in understanding them. Let's take an advanced example from the documentation. urls.py from books.views import PublisherBookListView urlpatterns = patterns('', (r'^books/(\w+)/$', PublisherBookListView.as_view()), ) views.py from django.shortcuts import get_object_or_404 from django.views.generic import ListView from books

Some details: Request Method: GET Request URL: http://localhost:8080/user/create Django Version: 1.5.1 Exception Type: TypeError Exception Value: ____init____() got an unexpected keyword argument 'instance' Exception Location: /place/venv/local/lib/python2.7/site-packages/django/views/generic/edit.py in get_form, line 35 Python Executable: /place/venv/bin/python Python Version: 2.7.3 views.py class UserCreateView(CreateView): model = models.User form_class = forms.UserForm urls.py url(r'^user/create$', UserCreateView.as_view(), name='user_create'), forms.py class UserForm(forms.Form): GROUP