#2123: catwalk (sprox) problems updating for many-many relationships
------------------------+---------------------------------------------------
 Reporter:  clemens     |       Owner:  faide
     Type:  defect      |      Status:  new  
 Priority:  normal      |   Milestone:       
Component:  TurboGears  |     Version:  1.9.x
 Severity:  normal      |    Keywords:       
------------------------+---------------------------------------------------
 Actions:

 * new virtualenv --no-site-packages on Ubuntu 8.10

 * cd tg_env; source bin/activate * fresh install of tg-2.0b1 following
 http://www.turbogears.org/2.0/docs/main/DownloadInstall.html

 * paster quickstart demo # with auth

 * cd demo

 * paster setup-app development.ini

 * paster serve development.ini

 * browse to localhost:8080

 * login

 * browse to /admin

 * add group "newgroup"

 * select "Permission"

 * select "manage/edit"

 * select both "managers" and "newgroup" and click "Submit"

 Expected Result:

 "manage" permission is associated with both "managers" and "newgroup"

 Actual Result:

 "manage" permission is still only associated with "managers"

 Notes:

 When "add"ing a new Permission (or a new Group) multiple associated groups
 (or permissions) can be successfully selected.  Just when "edit"ing there
 seems to be a problem.

 This problem also exists with custom many-many objects, though those also
 seem to run into the server error (#2122) that affecs the User-Group
 relatoinship in default quickstarted app.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2123>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to