django-cms / djangocms-column

Column Plugin for django-cms

django CMS

Open source enterprise content management system based on the Django framework and backed by the non-profit django CMS Association (Sponsor us!).

Contribute to this project and win rewards

Because django CMS is a community-driven project, we welcome everyone to get involved in the project. Become part of a fantastic community and help us make django CMS the best open source CMS in the world.

Attention!

Please use the develop-4 branch as the target for pull requests for on-going development.

Security fixes will be backported to older branches by the core team as appropriate.

Features

• hierarchical pages
• extensive built-in support for multilingual websites
• multi-site support
• draft/publish workflows
• version control
• a sophisticated publishing architecture, that's also usable in your own applications
• frontend content editing
• a hierarchical content structure for nested plugins
• an extensible navigation system that your own applications can hook into
• SEO-friendly URLs
• designed to integrate thoroughly into other applications

Developing applications that integrate with and take advantage of django CMS features is easy and well-documented.

More information on our website.

Requirements

See the Python/Django requirements for the current release version in our documentation.

See the installation how-to guide for an overview of some other requirements and dependencies of the current release.

Getting started

These tutorials take you step-by-step through some key aspects of django CMS.

Documentation

Our documentation working group maintains documentation for several versions of the project. Key versions are:

• stable (default), for the current release version
• latest, representing the latest build of the develop-4 branch

For more information about our branch policy, see Branches.

Our documentation is hosted courtesy of Read the Docs.

The dependencies for the docs are compiled by pip-tools.

Test django CMS in our demo

The demo platform is kindly provided by Divio, platinum member of the django CMS Association.

Getting Help

Please head over to our Discord Server or Stackoverflow for support.

Professional support

Choose from a list of trusted tech partner of the django CMS Association to get your website project delivered successfully.

Choose a trusted web host for your django CMS project and get your website online today.

The django CMS Association

The django CMS Association is a non-profit organization that was founded in 2020 with the goal to drive the success of django CMS, by increasing customer happiness, market share and open-source contributions. We provide infrastructure and guidance for the django CMS project.

The non-profit django CMS Association is dependent on donations to fulfill its purpose. The best way to donate is to become a member of the association and pay membership fees. The funding will be funneled back into core development and community projects.

Join the django CMS Association.

Credits

• Includes icons and adapted icons from Bootstrap.
• Includes icons from FamFamFam.
• Python tree engine powered by django-treebeard.
• JavaScript tree in admin uses jsTree.
• Many thanks to all the contributors to django CMS!

djangocms-column's Issues

Pypi Version

The current version on pypi supports Django<1.10

But the latest on github supports Django<2
https://github.com/divio/djangocms-column/blob/master/setup.py#L9

It seems the pypi version needs to be updated

save_model() on develop branch?

I just started looking at the source to try to figure out an issue I've logged on CMS (django-cms/django-cms#4117) & was going to do some PEP8/formatting changes as things were a nightmare to read, but noticed code on master (https://github.com/divio/djangocms-column/blob/master/djangocms_column/cms_plugins.py#L24) doesn't exist on develop.

What's the state of affairs with the branches? Have changes been applied to master instead of dev?

NUM_COLUMNS choices is hardwired in the code - would like to be able to limit them

At present the forms.py has NUM_COLUMNS set from 1-10 but the choices are hard-coded. Ideally it should be customizable (e.g., to limit the choices from 1-4 instead of the default 1-10), without having to hack the code.

Release new version with supporting django 1.11

So, I think it's a good idea to release new minor version with supporting django 1.11 even if nothing is done. How do you thing, @czpython?

Move migration files from migrations_django to its original place

According to django 1.7 inclusion of migration module:
Please change

1. migrations_django to migrations
2. migrations to south_migrations

No Class name on MultiColumn and Column

Hi there,

First of all, let me point out that this is NOT an issue and I trully appreciate your plugin. I do have a question / request however and I didn't quite know how to go about it so I am posting here. If it is not a good place for it I apologize in advance.

I have discovered that I am unable to add custom class name or id to multicolum and column YET I found myself in mutiple situations where I need this very much.

Would there be a simple way to extend the functionality of the plugin to allow for that?

Thank you!

New Release

Could please make a new release. When I upgrade to Django 3.2.13, my pip complains that there is a conflict. From my current deduction, djangocms_column is causing this, because its version 1.11.0 only allows django<=3.2.

Best Regards,

Adrian

Is this available on Divio?

I searched the addons on Divio to add it to my project but I couldn't find it.

Doesn't delete children when removing Column

When a Column is deleted, its contents become undeletable.

Reproduce the problem:

1. Create a MultiColumn
   2 . Create 2 Columns inside

2. add TextPlugin with some content into each Column

3. Delete one Column without deleting its child plugins.

   Children don't get deleted and become orphans.

MultiColumnPlugin causes AttributeError

Sometimes after adding a MultiColumnPlugin the page containing it completely breaks and only throws

AttributeError at /en/home/
'NoneType' object has no attribute 'get_plugin_class'

in https://github.com/divio/django-cms/blob/develop/cms/middleware/toolbar.py#L29
'instance' in this context comes from https://github.com/divio/django-cms/blob/develop/cms/models/pluginmodel.py#L171 where a "DoesNotExist" exception is raised and so instance = None. I tried to figure out how to fix it but I wasn't successful. The problem only seems to occur with MultiColumnPlugin - maybe it doesn't save something I think. Somebody who knows the code better should look after it. Unfortunately I don't know how to reproduce it - I just added a MultiColumn and it broke (using the cms from git in branch develop).

py3k failure: refers to xrange

http://dpaste.com/hold/1731570/

python3.3/site-packages/djangocms_column/cms_plugins.py" in save_model

1.     for x in xrange(int(form.cleaned_data['create'])):
   

Can't create multiple column

Hello !

Sorry for asking but i can't fix this by myself.

I want to create a multiple column like when you create a new project with djangocms and you answer yes to this question : "Load a starting page with examples after installation".

So the example page works fine with the multiple column but with a new page, i try to put a MultiColumn plugin, it ask me how many column i want and their width (i choose 3, 33%) and during create, i see the bottom-right buttom become red with its title 'Share this traceback on public website' but i can't catch the traceback and my MultiColumn is empty..

Really annoying

I'm using django-cms 3.0.2 and djangocms-column 1.3 and it doesn't work on any browser.

The migrate command in the README fails due to app name

remove/fix import `python_2_unicode_compatible`

It seems that a jump from django-cms 3.7.1 to 3.7.2 causes djangocms-column to break, as they removed python_2_unicode_compatible from cms/utils/compat/dj.py (django-cms/django-cms@6c92fbe#diff-e23ce56a2a8ee3898d5da04c957ccd6c)

Can someone confirm this?

TemplateSyntaxError

If i add the Plugin i get an this Error. Is there something wrong with my conf?

Exception Type: TemplateSyntaxError
Exception Value:
Invalid block tag: 'render_plugin', expected 'empty' oder 'endfor'
Exception Location: /Users/Roland/PythonEnvs/django14-bluetechnix/lib/python2.7/site-packages/django/template/base.py in invalid_block_tag, line 320
Python Executable: /Users/Roland/PythonEnvs/django14-bluetechnix/bin/python

Add and release support for Django 2.2

Please merge e964416 from https://github.com/isotoma/djangocms-column and release to PyPI to add support for Django 2.2 which is the current Django LTS release.

Untranslated help_text in MultiColumnForm

help_text in the create_width field of MultiColumnForm is not marked for translation ("_" character is missing)

https://github.com/divio/djangocms-column/blob/d33265e1ff78c9a983fe727546c95f024aa375ac/djangocms_column/forms.py#L22

support django 1.10?

or is it abandoned?

Support for Django 3?

Currently, setup.py has the following requirement:

'Django>=1.11,<3.0'`

Does djangocms-column specifically NOT support Django 3+, or can the requirement be changed? I'm using CMS on Django 3.0.7 and would like to be able to use column as well. I see PR #43 only has one minor change to models.py requiring six, which I believe CMS already requires, plus the change to setup.py. Is there any reason this PR can't be merged?

Edit "plugins in plugins" in the admin panel

Can you add the feature to edit the "plugins in plugins" in the Django CMS admin? Or do you have suggestions how I can implement it?

Django 4.2 / DjangoCMS 3.11 support

If I ran python manage.py makemigrations after updating to Django 4.2 / DjangoCMS 3.11, new migrations will be generated.

MultiColumn doesn't remove children when it's deleted.

When a MultiColumn is deleted, its contents (Columns and their contents) become undeletable.

Reproduce the problem:

1. Create a MultiColumn
   2 . Create 2 Columns inside

2. add TextPlugin with some content into each Column

3. Delete MultiColumn without deleting its child plugins.

   Children don't get deleted and become orphans.