-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Treebeard 4.5 leads to major issue #6980
Comments
|
mine worked by rolling back to django-treebeard==4.3.1 |
It is interesting to note that wagtail was also impacted by the recent changes wagtail/wagtail#6820. Edit: Just find out this ticket (django-treebeard/django-treebeard#210) that explains the details of why it is still broken |
I am seeing something I believe is related and is stopping us from publishing pages
I have tried rolling back to treebeard 4.3.1 and 4.4.0 (running fix-tree at each stage) and nothing seems to resolve the issue. Django CMS: 3.8.0 |
@DonkeyOatie I was working with a fresh install so I created the project over. By uninstalling treebeard and installing the 4.3.1 version of treebeard as @VeshRaazThapa said, I got it to work. |
@philfuster thanks for the suggestion. That is pretty hard to do for us as we are running inside a docker container on a managed platform. I will see if I can script this to happen before the app starts. Thanks for the info. UPDATE: downgrading pre-run seems to have worked. Phil, I owe you several beers! |
Glad I could help @DonkeyOatie ! How about instead of beers, could I trouble you for some time in the future to discuss what your experiences with djangocms are? This is my first time using it for a marketing site I am building and there are some things I don't understand how I would implement. |
Anytime @philfuster my email is on my profile |
I tried to modify as below with try except.
|
Description
Release of
django-treebeard
4.5 seems introduce breacking change fromdjango-cms
.Steps to reproduce
Steps to reproduce the behavior:
Expected behaviour
I should be able to add a plugin without error.
Actual behaviour
An error occured when I try to save a plugin.
Screenshots
Additional information (CMS/Python/Django versions)
Python: 3.6.11
Django-CMS: 3.8.0
I reproduced this error on a fresh install from Divio.
Quick workaround : Rollback to treebeard 4.4
We identify the following change as potential source of this issue. django-treebeard/django-treebeard#192
The text was updated successfully, but these errors were encountered: