Is it still really Django-Cms 3.11 compatible ?

[rolandf]

If I'm correct, it require djangocms-alias but I tried to install it but djangocms-alias doesn't install well with djangocms 3.11. The error rmesage in djangocms-alias is related to a placeholders class that is not available in CMS models. If I remove djangocms-alias when I migrate manage.py complain that a template .../bootstrap5/form.html is missing but then when I search for it I find it. I don't understand why it doesn't find it.

[fsbraun]

@rolandf Thanks for the comment!

(a) Djangocms-alias should work with django-cms 3.5+. I have used it with 3.10 successfully, but have not tested with 3.11. This potentially might be an issue for djangocms-alias (b) Djangocms-alias is very helpful but not required to use with djangocms-form-builder (c) Can you provide more info the the output if the ./manage.py migrate command?

I ask for a bit of patience. While djangocms-form-builder is in the making it is by far not stable yet.

[fsbraun]

OK, upon researching a bit more I realize that the currently available djangocms-alias repo is targeted at django CMS v4. In that case do not include it in any cms 3.x project. There used to be an alias app for django CMS v3.x but I am unsure where to find it.

[rolandf]

There is a create alias function in Django-Cms 3.11 without having to install an app in INSTALLED_APPS but it copy the alias in the clipboard then you can paste it.

As you said b) it's not required to have djangocms-alias, I'll give an other try to djangocms-form-builder asap. I noticed that I have other templates related issues in my project so I'll try to fix those and maybe all problems will be gone (I hope).

[fsbraun]

After experimenting a bit I agree that the alias function of v3 is not quite as practical as the djangocms-alias package for v4. But it works. 🙂