Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7580013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T17:48:41+00:00 2026-05-30T17:48:41+00:00

In a class-base UpdateView in Django, I exclude the user field as it is

  • 0

In a class-base UpdateView in Django, I exclude the user field as it is internal to the system and I won’t ask for it. Now what is the proper Django way of passing the user into the form.
(How I do it now, is I pass the user into the init of the form and then override the form’s save() method. But I bet that there is a proper way of doing this. Something like a hidden field or things of that nature.

# models.py
class Entry(models.Model):
    user = models.ForeignKey(
                User,
                related_name="%(class)s",
                null=False
    )

    name = models.CharField(
                blank=False, 
                max_length=58,
    )

    is_active = models.BooleanField(default=False)

    class Meta:
        ordering = ['name',]

    def __unicode__(self):
        return u'%s' % self.name

# forms.py
class EntryForm(forms.ModelForm):
    class Meta:
        model = Entry
        exclude = ('user',)

# views.py
class UpdateEntry(UpdateView):
    model = Entry
    form_class = EntryForm
    template_name = "entry/entry_update.html"
    success_url = reverse_lazy('entry_update')

    @method_decorator(login_required)
    def dispatch(self, *args, **kwargs):
        return super(UpdateEntry, self).dispatch(*args, **kwargs)

# urls.py
url(r'^entry/edit/(?P<pk>\d+)/$',
    UpdateEntry.as_view(),
    name='entry_update'
),
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T17:48:43+00:00Added an answer on May 30, 2026 at 5:48 pm

    Hacking around like passing a hidden field doesn’t make sense as this truly has nothing to do with the client – this classic “associate with logged in user” problem should definitely be handled on the server side.

    I’d put this behavior in the form_valid method.

    class MyUpdateView(UpdateView):
        def form_valid(self, form):
            instance = form.save(commit=False)
            instance.user = self.request.user
            super(MyUpdateView, self).save(form)
    
       # the default implementation of form_valid is...
       # def form_valid(self, form):
       #     self.object = form.save()
       #     return HttpResponseRedirect(self.get_success_url())
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

class Base { public void add() { System.out.println(Base ADD); } void subtract() { throw
class base{} class child : public base{ **dummyfunction();** } now I am calling a
class base{} class child : public base{ **dummyfunction();** } now I am calling a
class base { public void superMethod() { System.out.println(Hello i m a super class method);
class Base { int i = 99; public void amethod() { System.out.println(Base.amethod()); } Base()
I have simple base class with single static field. I have numerous classes that
class Base { public: Base(){} Base(int k):a(k) { } int a; }; class X:virtual
abstract class base { abstract public function test(); public function run() { self::test(); }
Given a base class with the following interface: public class Base { public virtual
Give a base class Base , I want to write a method Test, like

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.