My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 50: recursive post_save signals seem to confuse mptt..
1 person starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  craig.ds@gmail.com


 
Reported by bir...@gmail.com, Mar 12, 2009
What steps will reproduce the problem?

1. register model M to mptt
2. connect a post_save signal where sender is M
3. call save() on the instances' parent in the signal handler

What is the expected output? What do you see instead?

Since I'm just updating some fields in the parents, (not mptt related
fields) I would expect this to work just fine. Instead if I create a new
node, the lft and rght fields are miscalculated (as if the node were a root
node), while the parent field points to the right target.

What version of the product are you using? On what operating system?

I'm on kubuntu 8.04, django 1.0.2, mptt 0.3-pre

Please provide any additional information below.
Mar 16, 2009
#1 bir...@gmail.com
I made a test application (sorry i don't know how to write a test case yet..). I hope
this will help to reproduce the problem.

and I use postgres 8.3 whith psycopg2.
mptt_sync_parent_bug.tar.gz
4.1 KB   Download
Sep 3, 2010
Project Member #2 craig.ds@gmail.com
Reproduced, thanks for the test app
Status: Accepted
Owner: craig.ds

Powered by Google Project Hosting