Issue 51: No release of MPTT works with current release of django
Status:  Fixed
Owner: ----
Closed:  Sep 2010
Reported by tevans...@googlemail.com, Jun 8, 2009
What steps will reproduce the problem?
1. Install django 1.0.2
2. Install django-mptt 0.2.1
3. Define trivial MPTT model

class Property(models.Model):
  name = models.CharField(max_length=50)
  parent = models.ForeignKey('self', null=True, blank=True,
related_name='dependent_properties')

mptt.register(Property, order_insertion_by=['name'])

Run syncdb

What is the expected output? What do you see instead?
Expect to create appropriate tables.

Fails to create tables. Traceback:

Traceback (most recent call last):
  File
"/usr/local/lib/python2.5/site-packages/django/core/management/commands/runserver.py",
line 48, in inner_run
    self.validate(display_num_errors=True)
  File
"/usr/local/lib/python2.5/site-packages/django/core/management/base.py",
line 246, in validate
    num_errors = get_validation_errors(s, app)
  File
"/usr/local/lib/python2.5/site-packages/django/core/management/validation.py",
line 28, in get_validation_errors
    for (app_name, error) in get_app_errors().items():
  File
"/usr/local/lib/python2.5/site-packages/django/db/models/loading.py", line
128, in get_app_errors
    self._populate()
  File
"/usr/local/lib/python2.5/site-packages/django/db/models/loading.py", line
57, in _populate
    self.load_app(app_name, True)
  File
"/usr/local/lib/python2.5/site-packages/django/db/models/loading.py", line
72, in load_app
    mod = __import__(app_name, {}, {}, ['models'])
  File "/data2/development/mptt/mptt_test/../mptt_test/attrs/models.py",
line 8, in <module>
    mptt.register(Property, order_insertion_by=['name'])
  File "/home/tom/lib/python2.5/site-packages/mptt/__init__.py", line 73,
in register
    dispatcher.connect(pre_save, signal=model_signals.pre_save, sender=model)
AttributeError: 'module' object has no attribute 'connect'



What version of the product are you using? On what operating system?
0.2.1 / FreeBSD 7

Please provide any additional information below.

This was resolved by  issue 36  last November in trunk, but there is still no
release which works with django 1.0.2, and the last release was 17 months
ago - is this project abandonware? 

Jun 8, 2009
#1 tevans...@googlemail.com
Sorry, it was reported and fixed in  issue 30 , and then re-reported in  issue 36 .
Sep 2, 2010
Project Member #2 craig.ds@gmail.com
The recently added 0.3 release and the source checkout from github work with Django 1.1+

Status: Fixed