django-cms | The easy-to-use and developer-friendly enterprise CMS | Content Management System library

In Django, the gettext_lazy(…) function [Django-doc] is often imported as _ to manage translations. This is explained in the Standard translation:

Python’s standard library gettext module installs _() into the global namespace, as an alias for gettext(). In Django, we have chosen not to follow this practice, for a couple of reasons

(…)

Because of how xgettext (used by makemessages) works, only functions that take a single string argument can be imported as _:

• gettext()
• gettext_lazy()

You thus should add:

I think a way without hacking Django too much would be to use URL rewrite facility provided by the webserver you run, for example, for mod_wsgi you can use mod_rewrite, similar facility exists also for uWSGI.

You may need to also post-process the output from Django to make sure that any links are also correctly re-written to follow the new schema. Not the cleanest approach but seems doable.

Downgrade to django-treebeard version below 4.5.1, e.g. 4.4. Version 4.5.1 seems to be incompatible.

This is definitely doable, but there are a few things you should consider:

• This isn't really what a change-view is meant for. It feels weird from a UX perspective to have (on a page which is essentially one big form) form-elements unrelated to the form you are submitting.
• django admin is not meant to be a user-facing production ready environment. If you're trying to make it do things it's not easy to do, it's normally a good sign you should be making your own views here.

The modelAdmin.form attribute, is meant to be a form which displays data from an instance of the relevant model, and which saves the returned POST data back to that same instance.

It isn't the form the view actually uses in the end. It is the form django-admin uses to build the form that is finally used though. The admin app does quite a bit of processing along the way, based off attributes that are set on modelAdmin so adding (unrelated) fields to modelAdmin.form won't necessarily correspond to fields on the finally rendered form.

If you want to add in to_date and from_date it should be done in a separate form. (For one thing, you otherwise wouldn't be able to change the dates without submitting your whole form).

You are far better to add a separate form, and use GET query parameters to update your dates. Something like this:

@lazdins This could be fixed in 3.7.1: "Fixed a bug where the menu would render draft pages even if the page on the request was a public page. This happens when a user without change permissions requests edit mode." https://github.com/divio/django-cms/blob/develop/CHANGELOG.rst#371-2019-11-26

3.4 I also no longer supported, It is advised that you move to 3.7 as it is an LTS release that is currently supported and the recommended version at the time of my comment: https://www.django-cms.org/en/roadmap/

I have posted this into the issue as well. https://github.com/divio/django-cms/issues/6004#issuecomment-702052627

What version of Django are you using?

I assume you are using Django 3.1.2? if so then downgrade to 3.0 because DjangoCMS does not is not compatible with 3.1 at the moment.

This should help : pip install Django==3.0

http://docs.django-cms.org/en/latest/index.html#requirements

Your plugin needs to set the allow_children attribute, and then you can control what children the plugin can have, if you want to, by specifying plugin classes in a list of child_classes as you'll see below.

You need to load the editable parts of CMS. Primarily this would be a placeholder so that you can add content via the structure view.

Change newpage.html to something like;

python_2_unicode_compatible was removed from Django in 3.0: https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility-apis

It looks like you need to update one of your packages that's using it. From the traceback, that would be aldryn_apphooks_config. I'm not sure where that comes from, would need some more details for that. I would suggest checking your requirements file and trying to upgrade packages until it works, but you might have to end up removing some.