Databases
StackOverflow2013
Postsdbo
POnext url in django doesn't exist
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POnext url in django doesn't exist
    primarykey
    data
    text
    <p>i have successfully set the app to send me to url like </p> <pre><code>http://localhost:8000/log_in/?next=/task/1/ </code></pre> <p>i have defined the context processors as following</p> <pre><code>TEMPLATE_CONTEXT_PROCESSORS = ( "django.contrib.auth.context_processors.auth", "django.core.context_processors.debug", "django.core.context_processors.i18n", "django.core.context_processors.media", "django.core.context_processors.static", "django.core.context_processors.tz", "django.contrib.messages.context_processors.messages", "django.core.context_processors.request", ) </code></pre> <p>but when i login it redirects me instead to the home page, i printed the <code>request</code> in my login view and i got the <code>GET</code> is empty query set which is strande, any ideas why !?</p> <p>i also tried adding</p> <pre><code>&lt;input type="hidden" name="next" value="{{next}}" /&gt; </code></pre> <p>to the login.html, but this added the next to the <code>POST</code> request as an empty parameter</p> <p><strong>Edit 1</strong> The login view, and i try to print the 'next' parameter and it returns null, because the the <code>GET</code> is an empty queryset</p> <pre><code>def log_in(request): """ This method checks for the input username(email) and password. If they are empty the user id redirected to the login page, else checks whether the user is authenticated. If the user is not found in the database, it renders the login page with an error_message that the email or password are invalid. Further, it checks if the user's account is activated, it not he is redirected back to login and notified. If the user is activated, it checks for the field remember_me, if it is not checked, then the expiry date of the session is set to when the browser is closed. Then the user is logged in using the login in django backends and it checks on the session value if it is his first time or not to open the getstrated instead of the normal profile. """ print request.GET['next'] base_login=True if request.POST.has_key('username') and request.POST.has_key('password'): username = request.POST['username'] password = request.POST['password'] user = authenticate(username=username, password=password) if user is None: error_message = "The Email/Password is incorrect." return render(request, 'userprofiles/registration.html', {'error_message': error_message}) else: if user.is_active: if not request.POST.get('remember_me', False): request.session.set_expiry(0) login(request, user) request.session['DEPLOYED_ADDRESS'] = settings.DEPLOYED_ADDRESS first_week = False logged_user = UserProfile.objects.get(username=request.user.username) if (((request.user.last_login - request.user.date_joined).days) &lt; 8) and (logged_user.got_started == False): first_week = True if first_week: return redirect('/getting_started/', RequestContext(request)) else: return redirect('/', RequestContext(request)) else: error_message = "This Email Hasn't Been Activated Yet. Please Check The Activation Mail Sent To You." return render(request, 'userprofiles/registration.html', {'error_message': error_message}) else: RegistrationForm = get_form_class(up_settings.REGISTRATION_FORM) if request.method == 'POST': form = RegistrationForm(data=request.POST, files=request.FILES) if form.is_valid(): new_user = form.save() username = form.cleaned_data['username'] password = form.cleaned_data['password'] request.session['login'] = "first" # Automatically log this user in if up_settings.AUTO_LOGIN: if up_settings.EMAIL_ONLY: username = form.cleaned_data['email'] user = authenticate(username=username, password=password) if user is not None: if user.is_active: login(request, user) calculate_profile_completion(request) return redirect(up_settings.REGISTRATION_REDIRECT) else: form = RegistrationForm() return render(request, 'userprofiles/registration.html', {'form': form,'base_login': base_login}) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFady Kamal
    1. USFady Kamal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POnext url in django doesn't exist
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would recommend using the built in login view instead of trying to write your own. If you do use your own login view, how can we help you debug it when you don't show it here?
      singulars
      1. POnext url in django doesn't exist
      1. USAlasdair
    2. CO@Alasdair i have extra scenarios more than the oridnary login, and i have added the login view,check the edit, Thanks in advance
      singulars
      1. POnext url in django doesn't exist
      1. USFady Kamal
    3. CO@FadyKamal Can you try `request.REQUEST['next']`? I'm curious to see if that works.
      singulars
      1. POnext url in django doesn't exist
      1. UShayavuk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload