Re: [ANNOUNCE] Django 1.7 released

[Thomas Leo]

Keep up the great work!

On Tuesday, September 2, 2014 6:13:21 PM UTC-4, James Bennett wrote:
>
> Django 1.7 is now available:
>
> https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/
>
> Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5 
> release is the final releae in the 1.5 series, as Django 1.5 has now 
> reached end-of-life.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b9782210-94e3-41ed-97d9-76992319c9a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ANN: Django website redesign launched

[Thomas Leo]

The new Design looks great! Awesome job!

One thing I really like about https://docs.python.org/3/ is the ability to 
show/hide the side bar. The new design features a very large sidebar, being 
able to toggle it would be awesome. 

Also as previously mentioned trac doesn't look right yet.

On Tuesday, December 16, 2014 11:09:55 AM UTC-5, Jannis Leidel wrote:
>
> Hi everyone, 
>
> We're incredibly proud to share with you the new design of the Django 
> website, the documentation and the issue tracker. 
>
> This is a long time coming and we couldn't be happier to finally ship it 
> :) 
>
> As you can imagine, there will be bugs, so please bear with us and report 
> issues to the issue tracker at 
> https://github.com/django/djangoproject.com/issues 
>
> More infos about the redesign and its history can be found in the blog 
> post: 
>
>   
> https://www.djangoproject.com/weblog/2014/dec/15/announcing-django-website-redesign/
>  
>
> Happy coding, everyone! 
>
> Jannis 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c9438430-7908-464f-82ce-b89131e3bbea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django application hosted on godaddy don't display the site models in admin page

[Thomas Leo]

Can you give a little more info on your application stack?

On Wednesday, February 12, 2014 9:08:17 AM UTC-5, Mironiuc Sergiu wrote:
>
>
> I have a problem. I moved a django site from one hosting to godaddy. On 
> the GoDaddy hosting it doesn't display in the admin page the site models.
>
> settings code:
>
> INSTALLED_APPS = 
> ('django.contrib.auth','django.contrib.contenttypes','django.contrib.sessions','django.contrib.messages','django.contrib.sitemaps','django.contrib.staticfiles',#
>  Uncomment the next line to enable the 
> admin:'mysite','django.contrib.admin',# Uncomment the next line to enable 
> admin documentation:# 'django.contrib.admindocs',
> 'storages',
>
> )
>
> urls.py code:
>
> > from django.conf.urls import patterns, include, url from> django.contrib 
> > import admin from django.conf import settings from> .sitemaps import 
> > StaticViewSitemap from .sitemaps import OfertaSitemap> 
> > admin.autodiscover()> > sitemaps = {> 'ro' : StaticViewSitemap,> 
> > 'oferte':OfertaSitemap> }> > urlpatterns = patterns('',> ...> 
> > url(r'^admin/', include(admin.site.urls)),> ... )
>
> Can anybody help me?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/898fde65-996b-4b1e-bb3f-f7aa39762afb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Using Django User Authentication from an Android App (CSRF issue?)

[Thomas Leo]

>> Obviously this isn't an ideal or secure way of doing things and what I 
originally tried was sending a POST request, but this gets denied with a 
403 and a message about not having a CSRF cookie attached.

I haven't developed anything with Android but it sounds like you need to 
send a CSRF in your post request, this can be done in JS, see: 
https://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ajax
See also this: 
http://stackoverflow.com/questions/9252360/android-sending-post-requests-to-django-server-csrf-failing

On Wednesday, February 12, 2014 8:41:24 AM UTC-5, Ethan Lowry wrote:
>
> Hi there,
>
> I have a bare-bones Django app set up and am planning on using the built 
> in Django user auth to manage log in and registration via the Android app 
> I'm developing. 
>
> I've tried this a number of ways and can, for example, log in by sending a 
> GET request such as ([url]/login?username=[username]&password=[password]) 
> and returning a JSON representation of the user if its valid.
>
> Obviously this isn't an ideal or secure way of doing things and what I 
> originally tried was sending a POST request, but this gets denied with a 
> 403 and a message about not having a CSRF cookie attached.
> I did some reading up and get roughly what this is but could not find any 
> mention of how to get around this issue if you have to send post request 
> from another application as in my case - is it possible to do something 
> like make a get request to Django and take a usable cookie from the 
> response and attach it to my POST request before sending?
>
> If anyone knows much about this issue, or has any general advice or best 
> practices regarding Django authentication on a mobile app, I'd much 
> appreciate it.
>
> Thanks,
> Ethan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/de2a1ccf-04cb-4ddb-adcb-ec1171ae6bbc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Login at the end of form wizard

[Thomas Leo]

>> when a user logs in and gets redirected to the order page the wizard 
starts again from the beginning (loosing all the data inserted the first 
time).

The issue is that in WizardView, triggering the get function causes the session 
to 
reset.
 
I would suggest that you switch from using a plain SessionWizardView to 
a NamedUrlWizardView.

>> Can I keep/move the wizard session data from the anonymous user to the 
logged user?

I believe that session data is only cleaned when you log out, however when 
logging in you should not loose that data.

On Thursday, February 13, 2014 9:51:08 AM UTC-5, parnigot wrote:
>
> Hello fellow django users,
>
> I’m using a form wizard (a very basic SessionWizardView) to create a 
> simple “order page”.
> The four steps of the wizard must be accessible to both logged in and 
> anonymous users, but to complete an order the user must authenticate 
> himself (think something like an online shop where you can add what you 
> want to the basket but to complete an order you have to log in).
>
> To accomplish this, in the wizard’s done() method, I redirect anonymous 
> users to the login page with a ?next=/order-page/ parameter.
> But this doesn’t work very well, because when a user logs in and gets 
> redirected to the order page the wizard starts again from the beginning 
> (loosing all the data inserted the first time).
>
> Can I keep/move the wizard session data from the anonymous user to the 
> logged user?
>
> ---
> Best regards,
> e.p.
> 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ec968123-98f8-4905-b621-0aa93bd8cf4e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Login at the end of form wizard

[Thomas Leo]

Sorry I meant to say NamedUrlSessionWizardView not NamedUrlWizardView

On Thursday, February 13, 2014 11:08:36 AM UTC-5, Thomas Leo wrote:
>
> >> when a user logs in and gets redirected to the order page the wizard 
> starts again from the beginning (loosing all the data inserted the first 
> time).
>
> The issue is that in WizardView, triggering the get function causes the 
> session 
> to 
> reset<https://github.com/django/django/blob/master/django/contrib/formtools/wizard/views.py#L243>.
>  
> I would suggest that you switch from using a plain SessionWizardView to 
> a NamedUrlWizardView.
>
> >> Can I keep/move the wizard session data from the anonymous user to the 
> logged user?
>
> I believe that session data is only cleaned when you log out, however when 
> logging in you should not loose that data.
>
> On Thursday, February 13, 2014 9:51:08 AM UTC-5, parnigot wrote:
>>
>> Hello fellow django users,
>>
>> I’m using a form wizard (a very basic SessionWizardView) to create a 
>> simple “order page”.
>> The four steps of the wizard must be accessible to both logged in and 
>> anonymous users, but to complete an order the user must authenticate 
>> himself (think something like an online shop where you can add what you 
>> want to the basket but to complete an order you have to log in).
>>
>> To accomplish this, in the wizard’s done() method, I redirect anonymous 
>> users to the login page with a ?next=/order-page/ parameter.
>> But this doesn’t work very well, because when a user logs in and gets 
>> redirected to the order page the wizard starts again from the beginning 
>> (loosing all the data inserted the first time).
>>
>> Can I keep/move the wizard session data from the anonymous user to the 
>> logged user?
>>
>> ---
>> Best regards,
>> e.p.
>> <https://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/#django.contrib.formtools.wizard.views.SessionWizardView>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/feda2bb8-031f-4875-919a-a0f65fa23502%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Migration Issues when updating model's default primary key from id to uuid

[Thomas Leo]

I'm running django 1.11, have this same issue. Has this issue been fixed in 
later versions of django? Is there a workaround for 1.11?

On Sunday, November 12, 2017 at 7:30:45 AM UTC-5, Liuyang Wan wrote:
>
> Thanks for the link. It’s interesting that two years past the bug is still 
> unresolved.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/361af02d-2b75-41fa-9a4b-de248cb71dbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.