Content: Blog

We're excited to announce the release of django CMS 5.0.3, alongside significant updates to the djangocms-alias package. This release brings performance optimizations and important bug fixes.

django CMS 5.0.3

⚡ Performance Improvements

Performance remains a key focus with this release. We've implemented optimizations to placeholder and plugin utilities, making your django CMS sites faster and more responsive, especially when editing. These improvements are particularly noticeable in content-heavy applications with multiple placeholders and complex plugin hierarchies.

🐛 Critical Bug Fixes

Several important fixes enhance reliability:

• Placeholder Permission Handling: Fixed an issue where individual placeholder checks weren't being properly respected when determining if placeholders could be changed
• Menu Navigation: Resolved a problem with inactive menu nodes where children weren't being properly cut when the level was less than or equal to 0
• Language Management: The copy_lang management command now properly includes PageUrl objects, ensuring complete language copying functionality
• Migration Stability: Fixed Migration 0033 failures that occurred when empty placeholder objects weren't present in the database

See here for the full upgrade information and change log.

django CMS Alias 3.0.0

The djangocms-alias package has received substantial improvements that enhance both functionality and compatibility:

🎯 Static Aliases Return to Structure Board

One of the most requested features has been restored: static aliases are now visible again in the structure board. This improvement makes content management more intuitive by allowing editors to see and work with static aliases directly within the familiar structure interface.

 

🔒 Enhanced Security Compliance

The package now includes CSP-compliant data bridge functionality for Django CMS 5, ensuring your applications meet modern security standards without compromising functionality. This is particularly important for enterprise applications with strict Content Security Policy requirements.

🔧 Improved Plugin Handling

The alias system now includes better validation for plugin-to-alias conversion, ensuring that only plugins capable of being root plugins can be turned into aliases. This prevents configuration errors and improves the overall stability of alias functionality.

Upgrade Recommendations

For existing django CMS users, upgrading to 5.0.3 is highly recommended. The performance improvements alone make this upgrade worthwhile, and the bug fixes address several issues that could impact production deployments.

django CMS Alias 3.0.0 is recommended for django CMS 5.0 or later. Ensure to have the latest django CMS 5.0.3 (or later) version installed for optimal user experience.

Looking Forward

The restoration of static aliases in the structure board shows responsiveness to user feedback, and the enhanced security compliance features ensure django CMS remains suitable for enterprise deployments with strict security requirements.

blog comments powered by Disqus