subject:"Django 1.4\?"

Re: Django 1.4 urls.py deprecated, urlpatterns to change

2019-11-09 Thread Motaz Hejaze

You can use path or re_path
 path for normal urls
 re_path for urls containing regular expressions

urlpatterns = [

path('index' , views.index , name='index)

re_path('index/[a-z]*w/' , views.another_index , name='anotherIndex')



On Sat, 9 Nov 2019, 12:47 am Mdlr,  wrote:

> I try to compile an old code in Django 1.4 Many things are deprecated. I
> manage to change some of them but I don't knwo how to go futher on the
> urls.py
>
> here is the old code
>
>
> *from django.conf.urls.defaults import *
> from django.conf import settings
>
> dynurls = patterns('minesweepr.views',
> (r'^api/minesweeper_solve/$', 'api_solve'),
> )
>
> staticurls = patterns('minesweepr.views',
> (r'^player/$', 'template_static'),
> (r'^query/$', 'template_static'),
> )
>
> urlpatterns = patterns('',
> ('^%s' % settings.BASE_URL, include(dynurls)),
> ('^%s' % settings.BASE_STATIC_URL, include(staticurls)),
> )*
>
>
>
> I know django.conf.urls.defaults is deprecated and I tried to change the
> code like this
>
>
>
> *from django.conf.urls import url, include
> from django.conf import settings
>
> dynurls = ['minesweepr.views',
> (r'^api/minesweeper_solve/$', 'api_solve'),
> ]
>
> staticurls = ['minesweepr.views',
> (r'^player/$', 'template_static'),
> (r'^query/$', 'template_static'),
> ]
>
> urlpatterns = ['',
> ('^%s' % settings.BASE_URL, include(dynurls)),
> ('^%s' % settings.BASE_STATIC_URL, include(staticurls)),
> **]*
>
> But it is not sufficient
> It is said my url patterns are invalid.
> Anybody has an idea ?
> Thank you
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f5ff4194-ae39-4020-ab80-9373ea19d15a%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/f5ff4194-ae39-4020-ab80-9373ea19d15a%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHV4E-dopUZETcCid6%2BzzEB_NU6BRNi%2BN98hP2xjR03U22%2BsJg%40mail.gmail.com.

Django 1.4 urls.py deprecated, urlpatterns to change

2019-11-08 Thread Mdlr

 

I try to compile an old code in Django 1.4 Many things are deprecated. I 
manage to change some of them but I don't knwo how to go futher on the 
urls.py

here is the old code 


*from django.conf.urls.defaults import *
from django.conf import settings

dynurls = patterns('minesweepr.views',
(r'^api/minesweeper_solve/$', 'api_solve'),
)

staticurls = patterns('minesweepr.views',
(r'^player/$', 'template_static'),
(r'^query/$', 'template_static'),
)

urlpatterns = patterns('',
('^%s' % settings.BASE_URL, include(dynurls)),
('^%s' % settings.BASE_STATIC_URL, include(staticurls)),
)*



I know django.conf.urls.defaults is deprecated and I tried to change the 
code like this



*from django.conf.urls import url, include
from django.conf import settings

dynurls = ['minesweepr.views',
(r'^api/minesweeper_solve/$', 'api_solve'),
]

staticurls = ['minesweepr.views',
(r'^player/$', 'template_static'),
(r'^query/$', 'template_static'),
]

urlpatterns = ['',
('^%s' % settings.BASE_URL, include(dynurls)),
('^%s' % settings.BASE_STATIC_URL, include(staticurls)),
**]*

But it is not sufficient
It is said my url patterns are invalid. 
Anybody has an idea ?
Thank you

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f5ff4194-ae39-4020-ab80-9373ea19d15a%40googlegroups.com.

Re: Auth backends don't work with HttpResponseRedirect and Django 1.4+?

2019-05-13 Thread shilpa rani

I am facing similar issue.
How did you check the value of user.backend ??

Thanks,
Shilpa

On Saturday, 14 June 2014 00:26:59 UTC+8, Scott Simmerman wrote:
>
> I faced a similar issue (request.user becoming anonymous after login) and 
> found
> the following solution.  It had to do with the naming convention for the
> auth backend under AUTHENTICATION_BACKENDS in settings.py.  I had a custom
> auth backend class called PamBackend which I had in a file called 
> PamBackend.py.
> I listed it under AUTHENTICATION_BACKENDS as 'auth_backends.PamBackend'. 
>  This
> seemed to work ok--authentication was happening as expected, returning a 
> valid
> user--but the request.user would disappear after a page redirect.
>
> The key is that the backend name is set in the session when authenticate() 
> is
> called (in django.contrib.auth).  It sets the name like this:
>
>user.backend = "%s.%s" % (backend.__module__, 
> backend.__class__.__name__)
>
> So in my case, the name was set to 'auth_backends.PamBackend.PamBackend'.
>
> For a new http request, django checks the session and gets:
> 1) the name of the auth backend, and
> 2) the user id.
> It then calls get_user (in django/contrib/auth/__init__.py) which does the 
> following:
> 1) gets the backend name from the session,
> 2) checks for a match in settings, and
> 3) calls the appropriate get_user method from the appropriate backend.
>
> So at this point, my backend name did not match what was in settings.py and
> it returned an anonymous user.
>
> -Scott
>
> On Monday, October 14, 2013 8:52:57 AM UTC-4, HM wrote:
>>
>> I can't get logging in with alternate auth backends to work with Django 
>> 1.4 or newer.
>>
>> Basically:
>>
>> 1. authenticate() works. request.user.is_authenticated() is True
>> 2. Django's own login() seems to work, as request.user is set, 
>> request.session is set etc.
>> 3. After the HttpResponseRedirect, request.user is AnonymousUser
>>
>> This has happened twice now, with different alternate auth backends. I 
>> can't get rid of Django 1.3 before this is fixed...
>>
>> In one project I can call the next view directly (with render) and it 
>> Just Works. In the current project, the next view contains a form, and the 
>> "login" doesn't survive the POST.
>>
>> What am I missing? See also the non-solution in 
>> http://stackoverflow.com/questions/16119155/django-request-user-not-set-after-redirect
>>
>>
>> HM
>>
>

-- 
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/d05a4aa8-60dd-484c-88d3-90bc1dfba2c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Form on each page problem when upgrading from Django 1.4

2017-11-15 Thread yakkadesign

Anyone else have ideas using the Django backend?

On Sunday, November 12, 2017 at 12:56:53 PM UTC-5, yakka...@gmail.com wrote:
>
> I'm in the process of upgrading a website from Django 1.4 and I'm run into 
> a problem of getting my code that shows a form on almost every page 
> migrated.  I eventually want to upgrade to Django 1.11 but I'm currently 
> working on upgrading from Django 1.4 to Django 1.5.  I have a “request 
> information” form on each page except for a few sign-up pages.  
>
> In Django 1.4 I used direct_to_template for most of the website.  I have a 
>  that is inheirted by each page.  For example , 
> , etc. inherit  from .  In  I load the 
> right columns html with 
> “{% block rightColumn  %} {%include "site/rightColumn.html"%}  
> {%endblock%}” 
> and then in  I load the form's html with 
> “{%include "site/reqInfoForm.html"%}”.  
>
> To get the from on each page I used middleware similar to this 
> http://stackoverflow.com/questions/2734055/putting-a-django-login-form-on-every-page.
>   
> I created a class with a method “def process_view(self, request, view_func, 
> view_args, view_kwargs)”.  In the method if a POST request and not one of 
> the signup pages then I create a form instance from the request and if the 
> form is valid then process it then redirect to thanks page, otherwise 
> attach the form to the request so that I can show the errors in the form 
> template.  
>
> This worked perfectly in Django 1.4 though it seemed like a hack.
>
> While upgrading to Django 1.5 in the url.py I switched from 
> “direct_to_template” to “TemplateView.as_view”.  Now when there is an error 
> in the form (i.e., leave a required field blank), I get an error “"POST / 
> HTTP/1.1" 405 0” while running with the local server.  When I did some 
> research, it appears TemplateView doesn't have a POST method.
>
> It seems one way may be to add TemplateView for each page but it seems 
> like I would have to add a post method for each page(or maybe a mixin).  
> Any thoughts on this method?  I found another method using context 
> processors but I'm not following it.  Also any suggestions on other ways of 
> adding a form to almost all pages?
>

-- 
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/7115a66a-a38d-4772-b9bd-02086718b945%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Form on each page problem when upgrading from Django 1.4

2017-11-15 Thread yakkadesign

 

@Matthew,


It's not a login form. It's a normal form. I don't like the AJAX way. It 
adds moving parts and requires a front end rework (and more tests, browser 
compatibility tests, potential issues with plugins blocking, etc.). 



On Sunday, November 12, 2017 at 12:56:53 PM UTC-5, yakka...@gmail.com wrote:
>
> I'm in the process of upgrading a website from Django 1.4 and I'm run into 
> a problem of getting my code that shows a form on almost every page 
> migrated.  I eventually want to upgrade to Django 1.11 but I'm currently 
> working on upgrading from Django 1.4 to Django 1.5.  I have a “request 
> information” form on each page except for a few sign-up pages.  
>
> In Django 1.4 I used direct_to_template for most of the website.  I have a 
>  that is inheirted by each page.  For example , 
> , etc. inherit  from .  In  I load the 
> right columns html with 
> “{% block rightColumn  %} {%include "site/rightColumn.html"%}  
> {%endblock%}” 
> and then in  I load the form's html with 
> “{%include "site/reqInfoForm.html"%}”.  
>
> To get the from on each page I used middleware similar to this 
> http://stackoverflow.com/questions/2734055/putting-a-django-login-form-on-every-page.
>   
> I created a class with a method “def process_view(self, request, view_func, 
> view_args, view_kwargs)”.  In the method if a POST request and not one of 
> the signup pages then I create a form instance from the request and if the 
> form is valid then process it then redirect to thanks page, otherwise 
> attach the form to the request so that I can show the errors in the form 
> template.  
>
> This worked perfectly in Django 1.4 though it seemed like a hack.
>
> While upgrading to Django 1.5 in the url.py I switched from 
> “direct_to_template” to “TemplateView.as_view”.  Now when there is an error 
> in the form (i.e., leave a required field blank), I get an error “"POST / 
> HTTP/1.1" 405 0” while running with the local server.  When I did some 
> research, it appears TemplateView doesn't have a POST method.
>
> It seems one way may be to add TemplateView for each page but it seems 
> like I would have to add a post method for each page(or maybe a mixin).  
> Any thoughts on this method?  I found another method using context 
> processors but I'm not following it.  Also any suggestions on other ways of 
> adding a form to almost all pages?
>

-- 
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/d6a505aa-a828-463e-9fcd-b279b399469f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Form on each page problem when upgrading from Django 1.4

2017-11-13 Thread Matthew Pava

That is an interesting setup.  We just use login middleware that automatically 
redirects to the LogIn view with a next GET parameter.

In your situation, I would probably treat the form as ajax and create an ajax 
view for handling the login form processing.  Just change your action URL to 
your ajax login view url.  You would still include the form in the way you have 
and just add some Javascript to the form file.

From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On 
Behalf Of yakkades...@gmail.com
Sent: Sunday, November 12, 2017 11:57 AM
To: Django users
Subject: Form on each page problem when upgrading from Django 1.4

I'm in the process of upgrading a website from Django 1.4 and I'm run into a 
problem of getting my code that shows a form on almost every page migrated.  I 
eventually want to upgrade to Django 1.11 but I'm currently working on 
upgrading from Django 1.4 to Django 1.5.  I have a “request information” form 
on each page except for a few sign-up pages.

In Django 1.4 I used direct_to_template for most of the website.  I have a 
 that is inheirted by each page.  For example , 
, etc. inherit  from .  In  I load the 
right columns html with
“{% block rightColumn  %} {%include "site/rightColumn.html"%}  {%endblock%}”
and then in  I load the form's html with
“{%include "site/reqInfoForm.html"%}”.

To get the from on each page I used middleware similar to this 
http://stackoverflow.com/questions/2734055/putting-a-django-login-form-on-every-page.
  I created a class with a method “def process_view(self, request, view_func, 
view_args, view_kwargs)”.  In the method if a POST request and not one of the 
signup pages then I create a form instance from the request and if the form is 
valid then process it then redirect to thanks page, otherwise attach the form 
to the request so that I can show the errors in the form template.

This worked perfectly in Django 1.4 though it seemed like a hack.

While upgrading to Django 1.5 in the url.py I switched from 
“direct_to_template” to “TemplateView.as_view”.  Now when there is an error in 
the form (i.e., leave a required field blank), I get an error “"POST / 
HTTP/1.1" 405 0” while running with the local server.  When I did some 
research, it appears TemplateView doesn't have a POST method.

It seems one way may be to add TemplateView for each page but it seems like I 
would have to add a post method for each page(or maybe a mixin).  Any thoughts 
on this method?  I found another method using context processors but I'm not 
following it.  Also any suggestions on other ways of adding a form to almost 
all pages?
--
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<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to 
django-users@googlegroups.com<mailto: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/52c882b9-09d5-4b58-8234-b967785650de%40googlegroups.com<https://groups.google.com/d/msgid/django-users/52c882b9-09d5-4b58-8234-b967785650de%40googlegroups.com?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
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/fe308cea8d434d34add82c57a43210e4%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.

Form on each page problem when upgrading from Django 1.4

2017-11-12 Thread yakkadesign

I'm in the process of upgrading a website from Django 1.4 and I'm run into
a problem of getting my code that shows a form on almost every page
migrated. I eventually want to upgrade to Django 1.11 but I'm currently
working on upgrading from Django 1.4 to Django 1.5. I have a “request
information” form on each page except for a few sign-up pages.

In Django 1.4 I used direct_to_template for most of the website. I have a
that is inheirted by each page. For example ,
, etc. inherit from . In I load the
right columns html with
“{% block rightColumn %} {%include "site/rightColumn.html"%}
{%endblock%}”
and then in I load the form's html with
“{%include "site/reqInfoForm.html"%}”.

To get the from on each page I used middleware similar to this
http://stackoverflow.com/questions/2734055/putting-a-django-login-form-on-every-page.

I created a class with a method “def process_view(self, request, view_func,
view_args, view_kwargs)”. In the method if a POST request and not one of
the signup pages then I create a form instance from the request and if the
form is valid then process it then redirect to thanks page, otherwise
attach the form to the request so that I can show the errors in the form
template.

This worked perfectly in Django 1.4 though it seemed like a hack.

While upgrading to Django 1.5 in the url.py I switched from
“direct_to_template” to “TemplateView.as_view”. Now when there is an error
in the form (i.e., leave a required field blank), I get an error “"POST /
HTTP/1.1" 405 0” while running with the local server. When I did some
research, it appears TemplateView doesn't have a POST method.

It seems one way may be to add TemplateView for each page but it seems like
I would have to add a post method for each page(or maybe a mixin). Any
thoughts on this method? I found another method using context processors
but I'm not following it. Also any suggestions on other ways of adding a
form to almost all pages?

--
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/52c882b9-09d5-4b58-8234-b967785650de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

1 2 3 >

1 - 100 of 249 matches

Mail list logo