lambdalisue/django-inspectional-registration

Accepting a user raises TransactionManagementError

Closed this issue · 5 comments

I get this error when I try to accept a user. I am up to step 2 here.

TransactionManagementError at /admin/registration/registrationprofile/4/ This is forbidden when an 'atomic' block is active.

It happens at L173 of ``registration/backends/default/init.py` when selecting the "accept" or "force" options.

I'm using Django 1.6 on postgres.

Any ideas?

Thanks for reporting the issue. It seems a little bit complicated issue.

The transaction system has been changed from Django 1.6.
So I need to read the documentation (https://docs.djangoproject.com/en/dev/topics/db/transactions/) and understand the principle to keep the compatibility before make it available on Django 1.6

I'll check it out but today and tomorrow is a little bit busy so I will think about next week.

Related issues:
http://stackoverflow.com/questions/20039250/django-1-6-transactionmanagementerror-database-doesnt-behave-properly-when-aut
https://github.com/benjaoming/django-wiki/issues/225

Thanks for looking into it. Your app does exactly what I need (django-registration doesn't quite do it, and it's future seems uncertain). I look forward to any progress you make - I'd like to do some work on internationalizing it for US English too if I make use of it.

Hopefully others attempting to get this working on 1.6 can find this too (docs say 1.6 is supported).

I add a support of the new transaction system introduced from Django 1.6 thus this commit might fix this issue.
However, the test code (test_admin.py) did not raise any exception even with this issue so I cannot confirm whether this commit fix this issue or not in your case.

So please install the latest version of django-inspectional-registration from git with the following command and tell me if this commit fix your problem.

$ pip uninstall django-inspectional-registration
$ pip install git+https://github.com/lambdalisue/django-inspectional-registration.git

I'll update the PyPI version after you confirm the fix.

Thanks

I was having the same issue as Chris (using 1.6) and can confirm that your latest commit did fix the problem above.

Thanks

Nice. I'll update the PyPI version. Thanks!