-
Notifications
You must be signed in to change notification settings - Fork 193
django CMS 4 and 5 compatibility #821
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
base: release-5
Are you sure you want to change the base?
Conversation
…n't yet occured but the code is trying to run in Docker
…es and option to sort posts
Add: pinned_posts property to BlogCategory
Add: CategoryListView only starts with top-level categories Fix: settings.py
Fix: Only categories with a not None priority are shown in the CategoryListView
|
Any idea when the new release compatible with django cms 5 will be available? The main issue is the installation that cannot find the table of django-cm-blog configuration. |
|
@alefiori82 Yes, this comes from a competing migration. To get a working install without that conflict, try installing from https://github.com/fsbraun/djangocms-blog |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
Note from my side: Installation from cms3.11->cms4.x with changing djangocms-blog==1.2.3 to your fork worked with the branch |
Description
This is a django CMS 4+ compatible version of djangocms-blog based on djangocms-blog 1.2.3.
It removes the following dependencies:
Since djangocms-blog 2.0 introduced new plugins, migrations are not in sync.
References
Provide any github issue fixed (as in
Fix #XYZ)Checklist
inv lintchangesfile included (see docs)