Re: newforms-admin branch has been merged into trunk
On Jul 18, 2008, at 6:22 PM, Ariel Mauricio Nunez Gomez wrote: > BTW: Bryan, you've gotta redo the commits visualization[1] for > another big explosion!! I plan on updating the visualization right after we release 1.0. :) --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
On Fri, Jul 18, 2008 at 10:11 PM, Robvdl <[EMAIL PROTECTED]> wrote: > > Thanks very much for this > > I have been running Newforms Admin for a while, so when the big > changeover was going to hit, I would be ready, not changing too much > existing code. > > One thing I noticed now, running SVN 7968 vs my last checkout I did of > the old Newforms Admin branch (7871): > > - The Auth and Sites applications don't show in admin, like they > aren't registered with admin > > However, these do show on the older Newforms Admin branch checkout. > > Do we need to manually register these applications with admin now?? or > is this something that is still to be fixed? Since 7871 (in 7872, in fact) an autodiscover function was added to admin. You can see how it's recommended to be used if you search for autodiscover here: http://code.djangoproject.com/wiki/NewformsAdminBranch I'm guessing you don't call it and that is why the admin bits for those apps are not showing up. (But actually when I neglect to call it and then try to access the admin I get a Site Administration page saying I don't have permission to edit anything, so I can't replicate your symptoms exactly via that explanation...) 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: newforms-admin branch has been merged into trunk
Beers all around! On Jul 19, 2008, at 8:01 AM, Brian Rosner wrote: > > I have just recently merged the newforms-admin branch into trunk as of > r7967 [1]. This is an extremely backward incompatible change. The > entire admin application in contrib has been refactored. The newforms > module has a few new features, but those changes are backward > compatible. The branch also converted django.contrib.auth to use > newforms. I have documented these changes in the usual place [2]. > > I would like to thank Karen Tracey for her tremendous work triaging > tickets, finding the root of problems and supplying patches where > needed. Also, on behalf of the core developers involved with the > branch we would like thank everyone who has tested the branch and > reported bugs. Without your hard work and contribution we couldn't > have made Django this much better without you! Thanks. > > Bugs should no longer be marked with version 'newforms-admin' as the > branch is now closed. > > Onward to 1.0! > > [1]: http://code.djangoproject.com/changeset/7967 > [2]: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges > > > Brian Rosner > http://oebfare.com > > > > > > --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
Thanks for that, had a quick read and it looks like I don't need to import each admin.py from all my own apps that way anymore either in the __init__.py of each app, as autodiscover now handles all that, nice. It bought back the Auth and Sites app too. On Jul 19, 2:36 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Fri, Jul 18, 2008 at 10:11 PM, Robvdl <[EMAIL PROTECTED]> wrote: > > > Thanks very much for this > > > I have been running Newforms Admin for a while, so when the big > > changeover was going to hit, I would be ready, not changing too much > > existing code. > > > One thing I noticed now, running SVN 7968 vs my last checkout I did of > > the old Newforms Admin branch (7871): > > > - The Auth and Sites applications don't show in admin, like they > > aren't registered with admin > > > However, these do show on the older Newforms Admin branch checkout. > > > Do we need to manually register these applications with admin now?? or > > is this something that is still to be fixed? > > Since 7871 (in 7872, in fact) an autodiscover function was added to admin. > You can see how it's recommended to be used if you search for autodiscover > here: > > http://code.djangoproject.com/wiki/NewformsAdminBranch > > I'm guessing you don't call it and that is why the admin bits for those apps > are not showing up. > > (But actually when I neglect to call it and then try to access the admin I > get a Site Administration page saying I don't have permission to edit > anything, so I can't replicate your symptoms exactly via that > explanation...) > > 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: newforms-admin branch has been merged into trunk
Thanks very much for this I have been running Newforms Admin for a while, so when the big changeover was going to hit, I would be ready, not changing too much existing code. One thing I noticed now, running SVN 7968 vs my last checkout I did of the old Newforms Admin branch (7871): - The Auth and Sites applications don't show in admin, like they aren't registered with admin However, these do show on the older Newforms Admin branch checkout. Do we need to manually register these applications with admin now?? or is this something that is still to be fixed? --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
For those who aren't ready to move towards newforms-admin, Jacob has created a notable_moments/pre-newforms-admin tag. A BIG thanks to Brian and all those who had a hand in getting us to this day! Thanks!! -C --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
Thanks a lot!! BTW: Bryan, you've gotta redo the commits visualization[1] for another big explosion!! [1] http://oebfare.com/blog/2008/jun/24/django-code_swarm/ --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
Brian Rosner wrote: > I have just recently merged the newforms-admin branch into trunk as of > r7967 [1]. A BIG Thankyou to all involved !! Cheers / Frank --~--~-~--~~~---~--~~ 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: newforms-admin branch has been merged into trunk
On Jul 18, 8:01 pm, Brian Rosner <[EMAIL PROTECTED]> wrote: > I have just recently merged the newforms-admin branch into trunk as of > r7967 [1]. This is an extremely backward incompatible change. The > entire admin application in contrib has been refactored. The newforms > module has a few new features, but those changes are backward > compatible. The branch also converted django.contrib.auth to use > newforms. I have documented these changes in the usual place [2]. Thank you Brian, and thank you to all the numerous contributors. Your work is very much appreciated. Michael Trier blog.michaeltrier.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
newforms-admin branch has been merged into trunk
I have just recently merged the newforms-admin branch into trunk as of r7967 [1]. This is an extremely backward incompatible change. The entire admin application in contrib has been refactored. The newforms module has a few new features, but those changes are backward compatible. The branch also converted django.contrib.auth to use newforms. I have documented these changes in the usual place [2]. I would like to thank Karen Tracey for her tremendous work triaging tickets, finding the root of problems and supplying patches where needed. Also, on behalf of the core developers involved with the branch we would like thank everyone who has tested the branch and reported bugs. Without your hard work and contribution we couldn't have made Django this much better without you! Thanks. Bugs should no longer be marked with version 'newforms-admin' as the branch is now closed. Onward to 1.0! [1]: http://code.djangoproject.com/changeset/7967 [2]: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges Brian Rosner http://oebfare.com --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
On Jul 16, 6:19 am, Dan <[EMAIL PROTECTED]> wrote: > I'm starting the project in two weeks, hopefully, it will be merge then. Don't worry about it being merged with trunk. From what I understand changes from trunk are merged into newforms-admin branch on a weekly basis (that is, if they are following branch policy[1]). So you will be getting all the 'new' changes incorporating in trunk while not having to worry about code breakage in trunk later on. [1] http://www.djangoproject.com/documentation/contributing/#branch-policy --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
I'm starting the project in two weeks, hopefully, it will be merge then. I cross my fingers. --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
According to: http://code.djangoproject.com/wiki/VersionOneRoadmap#must-have-features newforms-admin is a high priority. If you haven't already, take a look at: http://code.djangoproject.com/wiki/NewformsAdminBranch http://code.djangoproject.com/wiki/NewformsHOWTO They're both *really* helpful, but not the easiest to find. -Jeff On Jul 15, 4:55 pm, Jon Brisbin <[EMAIL PROTECTED]> wrote: > I assumed that trunk would be moving in the newforms-admin direction, > so I've switched already. I would rather do it now than have to > backport stuff later... > > Thanks! > > Jon Brisibnhttp://jbrisbin.com > > On Jul 15, 2008, at 3:50 PM, Dan wrote: > > > Should I start with the nfa branch or with trunk and update the code > > when it is merged? Is there risks of breakage in nfa? Other issues? --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
I assumed that trunk would be moving in the newforms-admin direction, so I've switched already. I would rather do it now than have to backport stuff later... Thanks! Jon Brisibn http://jbrisbin.com On Jul 15, 2008, at 3:50 PM, Dan wrote: > Should I start with the nfa branch or with trunk and update the code > when it is merged? Is there risks of breakage in nfa? Other issues? > > > --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
Should I start with the nfa branch or with trunk and update the code when it is merged? Is there risks of breakage in nfa? Other issues? --~--~-~--~~~---~--~~ 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: Quick question about switching to newforms-admin branch....
On Jul 15, 3:30 pm, Jason <[EMAIL PROTECTED]> wrote: > ...and it is: if I were to switch my current django project over to > newforms-admin branch, would it break all of the old admin pages? Yes. > Or > is there legacy support built in? It isn't. But the following snippet might help create quick starting points for your new admin.py files from your old Admin inner class definitions: http://www.djangosnippets.org/snippets/603/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Quick question about switching to newforms-admin branch....
...and it is: if I were to switch my current django project over to newforms-admin branch, would it break all of the old admin pages? Or is there legacy support built in? Thanks mucho in advance! --~--~-~--~~~---~--~~ 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: About newforms-admin branch
Grupo Django wrote: On 2 jun, 00:26, Jeff Anderson <[EMAIL PROTECTED]> wrote: Grupo Django wrote: When newforms-admin is merged to the trunk, what will happen with all the sites that are currently using the current admin application? It's completely different. Should we change every single project to make them compatible with the newforms-admin version? Short answer: yes Long answer: django is subject to API changes-- a disclaimer that is presented when opting to use the development version. What I'm going to do is when nf-a gets closer, I'll create a branch for each project I have that will continue to follow the development version of django. Do you know when nf-a will be close to merge? Unfortunately, no. I just haven't yet felt inclined to start preparing my projects for nf-a. I follow django-developers as well. That is probably a good resource. Checking the nf-a tickets listed as blockers is a good thing as well. I'd probably start testing and changing my code once that list of tickets shrinks to 6 or 7. It's at about 20 now. Technically, I'd say that it is close to merge now, but I haven't been following it that closely. Jeff Anderson signature.asc Description: OpenPGP digital signature
Re: About newforms-admin branch
On 2 jun, 00:26, Jeff Anderson <[EMAIL PROTECTED]> wrote: > Grupo Django wrote: > > When newforms-admin is merged to the trunk, what will happen with all > > the sites that are currently using the current admin application? It's > > completely different. Should we change every single project to make > > them compatible with the newforms-admin version? > > Short answer: yes > Long answer: django is subject to API changes-- a disclaimer that is > presented when opting to use the development version. > > What I'm going to do is when nf-a gets closer, I'll create a branch for > each project I have that will continue to follow the development version > of django. Do you know when nf-a will be close to merge? Thank you. > I can continue to do development on my main branch, and merge changes > into the newforms-admin branch. > > Once django's newforms-admin branch is merged, I'll merge the branches I > have on my various projects. Code for admin is usually quite short, and > doesn't take too much effort to get it working. It takes very little > effort to tweak it. > > You won't be forced to update to the latest development version > immediately after the merge. You can wait until you are comfortable to > do that. > > Hope this is helpful! > > Jeff Anderson > > signature.asc > 1 KDescargar --~--~-~--~~~---~--~~ 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: About newforms-admin branch
Grupo Django wrote: When newforms-admin is merged to the trunk, what will happen with all the sites that are currently using the current admin application? It's completely different. Should we change every single project to make them compatible with the newforms-admin version? Short answer: yes Long answer: django is subject to API changes-- a disclaimer that is presented when opting to use the development version. What I'm going to do is when nf-a gets closer, I'll create a branch for each project I have that will continue to follow the development version of django. I can continue to do development on my main branch, and merge changes into the newforms-admin branch. Once django's newforms-admin branch is merged, I'll merge the branches I have on my various projects. Code for admin is usually quite short, and doesn't take too much effort to get it working. It takes very little effort to tweak it. You won't be forced to update to the latest development version immediately after the merge. You can wait until you are comfortable to do that. Hope this is helpful! Jeff Anderson signature.asc Description: OpenPGP digital signature
About newforms-admin branch
Hello, I'd like to know the status in the newforms-admin branch, I have seen the todo list: http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&keywords=%7Enfa-blocker&order=priority but it would be great the current state (80%,90%...). The reason I'm starting a new project and newforms admin would suit my current needs, although I think the merge won't happen this month so I'll probably use the current admin. When newforms-admin is merged to the trunk, what will happen with all the sites that are currently using the current admin application? It's completely different. Should we change every single project to make them compatible with the newforms-admin version? Thank you. --~--~-~--~~~---~--~~ 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: has "newforms-admin" branch been integrated?
Point taken, James. You're absolutely right. I should have checked there first. Will do better in the future. Niklas > -Original Message- > From: django-users@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of James Bennett > Sent: den 3 mars 2008 08:50 > To: django-users@googlegroups.com > Subject: Re: has "newforms-admin" branch been integrated? > > > On Mon, Mar 3, 2008 at 1:48 AM, Niklas Collin > <[EMAIL PROTECTED]> wrote: > > I was wondering if (and I quote the manual chapter 17 ;) the > > "newforms-admin"-branch has been integrated yet? > > Have you considered looking for an announcement regarding > that, or perhaps looking at the timeline for a > "newforms-admin merged to trunk" > message? > > > -- > "Bureaucrat Conrad, you are technically correct -- the best > kind of correct." > > > --~--~-~--~~~---~--~~ 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: has "newforms-admin" branch been integrated?
On Mon, 2008-03-03 at 08:48 +0100, Niklas Collin wrote: > Hi! > > I was wondering if (and I quote the manual chapter 17 ;) the > "newforms-admin"-branch has been integrated yet? No, it hasn't. Please don't hijack other threads to start your own topic. Start a new thread. Otherwise, it messes up convenient reading for other people. Malcolm -- He who laughs last thinks slowest. http://www.pointy-stick.com/blog/ --~--~-~--~~~---~--~~ 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: has "newforms-admin" branch been integrated?
On Mon, Mar 3, 2008 at 1:48 AM, Niklas Collin <[EMAIL PROTECTED]> wrote: > I was wondering if (and I quote the manual chapter 17 ;) the > "newforms-admin"-branch has been integrated yet? Have you considered looking for an announcement regarding that, or perhaps looking at the timeline for a "newforms-admin merged to trunk" message? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
has "newforms-admin" branch been integrated?
Hi! I was wondering if (and I quote the manual chapter 17 ;) the "newforms-admin"-branch has been integrated yet? Niklas > -Original Message- > From: django-users@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm Tredinnick > Sent: den 3 mars 2008 02:28 > To: django-users@googlegroups.com > Subject: Re: Ordering by Foreign Key in Admin > > > > On Sun, 2008-03-02 at 09:38 -0800, watusee wrote: > > Thanks for you quick and helpful reply Malcolm! A few > clarifications > > if I may. I couldn't quite figure out how to connect what the admin > > tool does to seeing queries in connection.queries. I can > however see > > the the offending query when I get an error in the admin. > If I do see > > a query that is not what I expect, do I have any recourse? > > Not really. It just means that either your expectation is > wrong or what Django is generating is wrong. Life's like that > sometimes. > > > You also mentioned "bleeding from the eyeballs to fix > something that > > has a better solution" (I'd like to borrow that phrase, it > could come > > in handy in a myriad of situations :-)). Could you point me towards > > the better solution? I feel like I might be missing > something here and > > I'd much prefer the better solution! > > I mean *I* was not going to do any the hard work to fix this > fairly illogical ordering syntax in core when there is a > better solution available to just treat it like normal > filtering. Mixing database table names and model attribute > names is really messy, so fixing any bugs is messy. > Eventually the new syntax will become part of trunk. For now, > you just have to wait a little while. > > Malcolm > > -- > Works better when plugged in. > http://www.pointy-stick.com/blog/ > > > > --~--~-~--~~~---~--~~ 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: newforms admin branch model update
On 12/14/07, djnz <[EMAIL PROTECTED]> wrote: > > > Thanks for your reply. So It could be an issue of my configuration or > code. But What? > My project runs perfect on trunk. I am trying to migrate to the > newforms-admin branch, so i made the required changes in the code as > described in the documentation. I know is very strange, but yes, I > modify a record with admin and click in save and continue editing.The > changes does not display but If I look at the record with pgadmin III > or similar the changes were made. > > I have to run the server on windows and linux with similar results. > . > > U. I have found the problem. I have removed the > 'django.middleware.cache.CacheMiddleware' and now it works. Although i > dont undestand why becouse i didn't have any configuration of the > CACHE_MIDDLEWARE in settings and it worked on trunk. :? Well, enabling the CacheMiddleware caches your entire site: http://www.djangoproject.com/documentation/cache/#the-per-site-cache (Though the doc says you need to also set the required parameters CACHE_MIDDLEWARE_SECONDS and CACHE_MIDDLEWARE_KEY_PREFIX, this doesn't seem to be the case...when I have no CACHE_* settings in settings.py, and simply enable the cache middleware, my entire site starts being cached.) I can confirm the behavior for the admin site is different on newforms-admin vs. trunk (both tested this morning using r6898) when the CacheMiddleware is enabled. With trunk, admin pages don't appear to be cached -- when I make a change I see the effect immediately on the admin pages (though not on my own site pages, since they are being cached -- they take 10 minutes or so to time out and reflect new values). With newforms-admin, the admin pages now appear to also be included in the per-site cache. If I bring up an admin change page and change a value, then press "Save and continue editing", the value reverts to what had originally been displayed. I have to move on to a different admin page to see the message about the value being successfully changed. This behavior seems odd but reading the doc it also seems to be technically correct...there's even a note in there that setting CACHE_MIDDLEWARE_ANONYMOUS_ONLY to True is a way to disable caching of the admin pages. Since I don't have that set, it sounds like caching of admin pages is expected. Only they don't seem to be cached on trunk, even without the CACHE_MIDDLEWARE_ANONYMOUS_ONLY set to True. I don't know why that is, but it seems that the trunk behavior is what doesn't match the docs. 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: newforms admin branch model update
Thanks for your reply. So It could be an issue of my configuration or code. But What? My project runs perfect on trunk. I am trying to migrate to the newforms-admin branch, so i made the required changes in the code as described in the documentation. I know is very strange, but yes, I modify a record with admin and click in save and continue editing.The changes does not display but If I look at the record with pgadmin III or similar the changes were made. I have to run the server on windows and linux with similar results. . U. I have found the problem. I have removed the 'django.middleware.cache.CacheMiddleware' and now it works. Although i dont undestand why becouse i didn't have any configuration of the CACHE_MIDDLEWARE in settings and it worked on trunk. :? Lewis On 14 dic, 01:51, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Dec 13, 2007 5:46 PM, djnz <[EMAIL PROTECTED]> wrote: > > > > > I have just setup part of my project for the newforms-admin branch. > > All seemed ok. But when i modifiy an object with the admin interface, > > the changes do not show neither in admin nor in the public area of the > > web. I have to restart the internal django webserver to see the > > changes. > > > Any ideas? > > Not really. I've been using newforms-admin for many weeks with no such > problems. What do you mean you've set up part of your project for > newforms-admin? You are either running trunk or newforms-admin, you can't > be partly one and partly the other. Can you be a little more specific on > the changes you are making and where they are not being reflected? The fact > that restarting the development server "fixes" things makes it sound like > you are changing code, but the rest of your description sounds like you are > simply changing model data, and I'm baffled as to how that could not be > reflected immediately in the admin interface where you make the change. > > 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: newforms admin branch model update
On Dec 13, 2007 5:46 PM, djnz <[EMAIL PROTECTED]> wrote: > > I have just setup part of my project for the newforms-admin branch. > All seemed ok. But when i modifiy an object with the admin interface, > the changes do not show neither in admin nor in the public area of the > web. I have to restart the internal django webserver to see the > changes. > > Any ideas? > Not really. I've been using newforms-admin for many weeks with no such problems. What do you mean you've set up part of your project for newforms-admin? You are either running trunk or newforms-admin, you can't be partly one and partly the other. Can you be a little more specific on the changes you are making and where they are not being reflected? The fact that restarting the development server "fixes" things makes it sound like you are changing code, but the rest of your description sounds like you are simply changing model data, and I'm baffled as to how that could not be reflected immediately in the admin interface where you make the change. 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 -~--~~~~--~~--~--~---
newforms admin branch model update
I have just setup part of my project for the newforms-admin branch. All seemed ok. But when i modifiy an object with the admin interface, the changes do not show neither in admin nor in the public area of the web. I have to restart the internal django webserver to see the changes. Any ideas? --~--~-~--~~~---~--~~ 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: newforms admin branch ?
On Sun, 2007-10-07 at 14:51 +, Amirouche wrote: > Hello, > > I'm starting a new project and I'm planning to use a lot django's > admin interface. Since I work with the trunk branch I'm wondering > whether I should use the newforms-admin. > > My questions are: > - In which state is currently the newforms-admin > - Should I use it ? > - How should I use id, eg: should I merge the trunk and newforms-admin > branch together. The branch is reasonably well developed. Have a look at the NewformsAdminBranch page in the wiki. That also explains how to get the branch. You do not merge it into trunk -- it's self-contained. To get an idea of current work on the branch and stability, browse django-dev archives and look at the posts about newforms-admin. All of this could have been discovered by searching Google, though. Note, that the code isn't finished yet and there are still a number of tickets open against it -- look in Trac for tickets in the newforms-admin version to see a sample of these. Note that not all of the tickets are necessarily legitimate; some of them are wishlist items, rather than bugs. However, most of them are things that will need to be addressed at some point, possibly after it is merged back into trunk, possibly before. You are going to have to be prepared to pay close attention to changes, existing tickets and your own code to use newforms-admin. There's a reason it isn't the main line yet. That being said, it's perfectly possible to use it -- quite a few people are. Just be aware of the limitations and that you are using code that isn't production ready and where some pieces are still designed. Regards, Malcolm --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
newforms admin branch ?
Hello, I'm starting a new project and I'm planning to use a lot django's admin interface. Since I work with the trunk branch I'm wondering whether I should use the newforms-admin. My questions are: - In which state is currently the newforms-admin - Should I use it ? - How should I use id, eg: should I merge the trunk and newforms-admin branch together. Regards, Amirouche B. --~--~-~--~~~---~--~~ 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: Custom admin field widgets in the newforms-admin branch
On 6/27/07, leif strickland <[EMAIL PROTECTED]> wrote: > After some digging around, it looks like the newforms-admin branch > does not allow widget declarations within the model class itself. Yeah. As you've discovered, one of the big points of newforms-admin is to get as much stuff as possible out of the model -- it doesn't really belong there, and that's why you use a ModelAdmin class and register with an admin site. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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: Custom admin field widgets in the newforms-admin branch
After some digging around, it looks like the newforms-admin branch
does not allow widget declarations within the model class itself.
However, adding a custom widget is quite easy.
In the branch, almost all of the admin app functionality has been
moved out of the inner Admin class and into a separate class called
ModelAdmin. If you want to customize the admin app's behavior, simply
subclass ModelAdmin and override the default functionality.
For example, look at this sample ModelAdmin subclass:
-
from django.contrib import admin
[...]
class ProfileOptions(admin.ModelAdmin):
list_display = ('display_name', 'headline','setup_date')
filter_horizontal = ('techniques', 'products', 'setup')
fields = (('Administrative Settings',{'fields':
('subscriber','active')}),('Contact Information',{'fields':
('phone_numbers','im_accounts','zip_code')}),('Photos',{'fields':
('primary_photo','secondary_photos','private_photos')}),)
def formfield_for_dbfield(self, db_field, **kwargs):
if db_field.name == 'zip_code':
return ZipCodeField(**kwargs)
else:
return
super(ProfileOptions,self).formfield_for_dbfield(db_field,
**kwargs)
def queryset(self, request):
return self.model.user_profiles.get_query_set()
adminsite.register(Profile,ProfileOptions)
list_display and fields are used exactly as they were in inner Admin
classes. filter_horizontal is simply a tuple of fields that will use
the javascript multiple-select filter.
The queryset() function allows you to specify which manager should be
used to obtain the change list objects.
Then there's formfield_for_dbfield(), a function that allows you to
override the default form field types that are returned for your
models' fields. In this example, the function returns a custom field
class (ZipCodeField) for any model field named "zip_code".
Alternatively, you could specify a custom widget like so:
if db_field.name == 'zip_code':
kwargs['widget'] = WIDGET
return
super(ProfileOptions,self).formfield_for_dbfield(db_field,
**kwargs)
Finally, don't forget to register your ModelAdmin subclass for the
model.
You can find more information on the branch's homepage:
http://code.djangoproject.com/wiki/NewformsAdminBranch
I hope this helps! If I am wrong about any of this, please post so
others don't repeat my mistakes.
Cheers,
LS
--~--~-~--~~~---~--~~
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: Custom admin field widgets in the newforms-admin branch
On 6/27/07, leif <[EMAIL PROTECTED]> wrote: > Does anyone have information on this topic? I have a feeling I'm not > the only one who's wondering this. Thanks! Your best bet is probably to read the source right now; when the branch is complete there will undoubtedly be documentation showing the sorts of things you can do with it, but at the moment the code is still under development. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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: Custom admin field widgets in the newforms-admin branch
Does anyone have information on this topic? I have a feeling I'm not the only one who's wondering this. 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: Custom admin field widgets in the newforms-admin branch
By the way, I did find the hook in django/branches/newforms-admin/ django/contrib/admin/options.py for specifying the form field for a given database field. But that's different than allowing a developer to specify the widget for a given field in the model itself. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Custom admin field widgets in the newforms-admin branch
One of the stated goals of the newforms-admin branch ( http://code.djangoproject.com/wiki/NewformsAdminBranch ) is to allow developers to specify custom widgets for particular fields in a model. I have not been able to find documentation regarding this new feature. Has it been implemented yet? 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 -~--~~~~--~~--~--~---
