recursive post_save signals seem to confuse mptt..

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by bir...@gmail.com on 12 Mar 2009 at 4:24

[GoogleCodeExporter]

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.

Original comment by bir...@gmail.com on 16 Mar 2009 at 7:05

Attachments:

• mptt_sync_parent_bug.tar.gz

[GoogleCodeExporter]

Reproduced, thanks for the test app

Original comment by craig.ds@gmail.com on 3 Sep 2010 at 11:34

• Changed state: Accepted

[GoogleCodeExporter]

Migrated to https://github.com/django-mptt/django-mptt/issues/#issue/73

Original comment by craig.ds@gmail.com on 19 Dec 2010 at 1:08