Re: Strategies for staying current with django development
What I started to think about is my life after 1.0. First of all, I will be much more relaxed, but then haven't heard anything about the way the community plans to support th 1.0 release with security fixes, etc. I presume that the 1.0 release will be tagged in SVN (just like to pre-1.0 releases are), but should we expect security updates in the tag? Or something like 1.0.1, etc? Could someone give us a pointer on this? V On Aug 26, 4:22 am, "Jay Parlar" <[EMAIL PROTECTED]> wrote: > Another good idea is to listen to the "This Week in Django" podcast > (www.thisweekindjango.com). > > They cover all the major things that have happened to trunk in the > last week, as well as things happening in the community, snippets > they've run across, etc. It's put together really well, and fun to > listen to. This is what I use to keep up to date, esp. when I have to > take some time away from Django work. > > Jay P. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Strategies for staying current with django development
Another good idea is to listen to the "This Week in Django" podcast (www.thisweekindjango.com). They cover all the major things that have happened to trunk in the last week, as well as things happening in the community, snippets they've run across, etc. It's put together really well, and fun to listen to. This is what I use to keep up to date, esp. when I have to take some time away from Django work. Jay P. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Strategies for staying current with django development
On Aug 25, 8:06 pm, Gremmie <[EMAIL PROTECTED]> wrote:
> Karen, I am using a customized admin template, so perhaps my auth
> problem is related to that.
Indeed, my admin/index.html needed an update. The {%
get_admin_app_list as app_list %} stuff is now obsolete. Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Strategies for staying current with django development
Thanks for the replies so far. I'm glad to hear someone thinks a dump and reload of the auth tables isn't necessary. Can I also assume that the model to database mapping hasn't changed, and I don't need to drop my model tables and reload? I did make a careful note of what rev I had django pinned at before I did an update as a fall back. :-) Karen, I am using a customized admin template, so perhaps my auth problem is related to that. I am using admin.autodiscover(). I will scan the docs for how to customize the new admin interface, perhaps my template needs updating. My own conversion to newforms-admin seemed to go pretty well. I followed the advice on the wiki page, and also found this screencast extremely helpful: http://oebfare.com/blog/2008/jul/20/newforms-admin-migration-and-screencast/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Strategies for staying current with django development
On Mon, Aug 25, 2008 at 5:01 PM, Steve Potter <[EMAIL PROTECTED]>wrote: > If you look in the django-users archive I think I remember a few other > people having the same auth problems you are describing, however I > don't remember the solution. > As I recall a lot of people reported this error, but it ultimately turned out to be due to either 1 - not calling admin.autodiscover() 2 - not updating customized admin templates 3 - perhaps other incomple admin migrations There certainly was not any requirement to dump/reload tables. As for strategies to migrate forward, beyond carefully following the instructions in backwards-incompatible changes, searching the user's group for similar error messages will likely turn up people who ran into and solved the problem before you hit it, especially for any changes that are more than a few days old. Also, when you're doing a big jump forward, note the revision you are updating from. That way you can 'svn -r up' back to that if you run into a temporarily unsurmountable problem. Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Strategies for staying current with django development
Personally when the newforms-admin was merged I quit updateing django so I wouldn't have to make multiple changes to my code before the 1.0 release. Then I planned to move everything to 1.0 and stay with it until another major release (or until there was a new feature I couldn't live without :-). Since the date for the 1.0 release is nearing I decided yesterday to try to port some of my code to the current SVN to see how hard it was going to be. It turns out it wasn't bad at all. To answer some of your other questions below; I don't think there are any changed to the auth table. To get he newforms admin working I just removed all of my Admin classes from the models.py and created new ones in the admin.py as per the Django documentation. As well as updating the urls.py to the new format for admin and adding the admin to the installed apps list. Then is just worked. If you look in the django-users archive I think I remember a few other people having the same auth problems you are describing, however I don't remember the solution. Steve On Aug 25, 3:43 pm, Gremmie <[EMAIL PROTECTED]> wrote: > I checked out the latest django from SVN some 14 weeks ago and built a > site with it. It rocks. :-). Yesterday, I decided to port my code to > the latest to take advantage of the newforms-admin. I had to update my > Photologue app also. A lot of stuff has changed! I am not quite there > yet, but I can finally get my admin page to come up, but django is now > saying my user doesn't have permission to edit anything. I am aware of > the backwards incompatible change list on the wiki, but to be honest, > a lot of it is over my head as a newbie. I don't speak django- > developer (yet). Nothing jumped out at me regarding authorization > changes. So my current theory is that there must be some auth database > table changes. I am thinking that I should save off all my site > database data, then drop all my tables and syncdb again. Or perhaps > point my site to a blank database and syncdb. Then use mysqldiff to > compare old and new databases and see what changed. I can possibly re- > import my data by re-running the old SQL, although I may need to > rename fields and do other fiddling, etc. > > I was able to save my Photologue data by saving it with phpMyAdmin, > dropping the tables, syncdb, then studying the new structures. I could > then re-run my saved SQL to get my data back, but I did have to make a > few tweaks. In one case, I had to add back 2 columns to a table, re- > import, then dropped those 2 columns to avoid fiddling with the saved > SQL. > > What strategies do people use to keep up with the moving target that > is django? Are there easier ways than what I am doing? > > Updating more often than once every 14 weeks is a good idea. :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Strategies for staying current with django development
I checked out the latest django from SVN some 14 weeks ago and built a site with it. It rocks. :-). Yesterday, I decided to port my code to the latest to take advantage of the newforms-admin. I had to update my Photologue app also. A lot of stuff has changed! I am not quite there yet, but I can finally get my admin page to come up, but django is now saying my user doesn't have permission to edit anything. I am aware of the backwards incompatible change list on the wiki, but to be honest, a lot of it is over my head as a newbie. I don't speak django- developer (yet). Nothing jumped out at me regarding authorization changes. So my current theory is that there must be some auth database table changes. I am thinking that I should save off all my site database data, then drop all my tables and syncdb again. Or perhaps point my site to a blank database and syncdb. Then use mysqldiff to compare old and new databases and see what changed. I can possibly re- import my data by re-running the old SQL, although I may need to rename fields and do other fiddling, etc. I was able to save my Photologue data by saving it with phpMyAdmin, dropping the tables, syncdb, then studying the new structures. I could then re-run my saved SQL to get my data back, but I did have to make a few tweaks. In one case, I had to add back 2 columns to a table, re- import, then dropped those 2 columns to avoid fiddling with the saved SQL. What strategies do people use to keep up with the moving target that is django? Are there easier ways than what I am doing? Updating more often than once every 14 weeks is a good idea. :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
