Clean up deprecated code

[s-ramaswamy]

http://djangodocs.com/1.3/releases/1.2-alpha-1/

SMTP connection has been deprecated since 1.3 and went out of the window in 1.4 . Since we are soon switching to django 1.4 please fix all the backwards incompatible code.

[pragathip]

e-mail reminder system works fine on the server now

[s-ramaswamy]

There are lots of deprecated things. Things which will not work in Django 1.5 etc. Fix those.

[akshayrangasai]

Status?

[pragathip]

I have made some changes related to:

• use of simplejson, in erp for shoutbox
• URLField must not have verify_exists
• patterns, url and include not to be imported from django.conf.urls.defaults, rather from django.conf.uls
• change in manage.py format, will throw up deprecation error in django 1.5 if current format is used (added text file with new format at erp/scripts/django1.5-imp.txt)

[pragathip]

according to django docs, The previous manage.py called functions that are now deprecated, and thus projects upgrading to Django 1.4 should update their manage.py. (The old-style manage.py will continue to work as before until Django 1.6. In 1.5 it will raise DeprecationWarning).

so i updated it and got it working on my local host. The main issue is that If settings, URLconfs and apps within the project are imported or referenced using the project name prefix (e.g.myproject.settings, ROOT_URLCONF = "erp.urls", etc), the new manage.py will need to be moved one directory up, so it is outside the project package rather than adjacent to settings.py and urls.py. In ERP, everywhere it is erp.dashboard.models , erp.feedback.views etc. so I placed my manage.py one directory up and made some changes in some of the apps and it works.

On the server though, initially I was confused because the equivalent of python manage.py runserver would have to be done from one directory up on the server. But there seemed to be no link between manage.py and django.fcgi. Karthik confirmed that only django.fcgi starts the erp site by invoking its settings and the absence of manage.py makes no difference.

So the problem will occur only on local host, on django 1.5+. So currently, I have made no changes to the manage.py. I have added the new manage.py in a text file in /erp/scripts/