3.4.0

Changelog for Nodify 3.4.0

📅 Release Date: February 22, 2026

We're excited to announce the release of Nodify 3.4.0! This version brings visual enhancements to the user interface and critical bug fixes for WebSocket authentication.

---

✨ UI/UX Improvements

🆕 Help Center Redesigned

• New tabbed interface - Split documentation for Developers and Marketing specialists
• Markdown rendering - Clean, readable documentation with syntax highlighting
• Loading states - Smooth transitions while content loads
• Error handling - User-friendly error messages with retry options
• Responsive design - Optimized for desktop, tablet, and mobile

🎨 Visual Updates

• Tab navigation - Clear active state indicators
• Code blocks - Better syntax highlighting and copy buttons
• Tables - Improved readability with alternating row colors
• Alerts - New warning banners for important information
• Spacing - Consistent padding and margins across components

🔧 Bug Fixes

WebSocket Authentication

• Fixed WebSocket connection dropping after 60 seconds
• Resolved "405 Not Allowed" errors on login endpoint
• Corrected token validation during WebSocket handshake
• Added proper reconnection mechanism

Graphical Issues

• Fixed layout shift during content loading
• Corrected markdown table rendering on mobile
• Resolved code block overflow on small screens
• Fixed tab highlight inconsistency
• Improved spinner animation smoothness

---

📦 Download

GitHub Releases

# Download the latest release
https://github.com/AZIRARM/nodify/releases/tag/v3.4.0

Docker

docker pull azirarm/nodify:3.4.0

---

📋 Summary of Changes

Component	Change
Help Center	New tabbed interface with Developer/Marketing sections
Documentation	Markdown rendering with syntax highlighting
Loading States	Added spinners and progress indicators
Error Handling	User-friendly error messages with retry
Mobile View	Responsive design improvements
WebSocket	Fixed authentication and connection drops
Login	Resolved 405 errors on authentication

---

Thank you for using Nodify! ❤️

3.8.0

🚀 New Features & Improvements

• Infrastructure & Performance
• Redis Integration Enhancement: Improved Redis caching layer with better connection management and failover support
• Real-time Updates: Implemented silent updates via WebSocket connections for seamless content synchronization
• Performance Optimization: Reduced latency for content delivery through optimized caching strategies
• UI/UX Foundation
• PrimeNG Migration Prep: Laid the groundwork for upcoming graphical overhaul with PrimeNG components
• Component Architecture: Restructured frontend architecture to facilitate smooth transition to PrimeNG
• Design System Foundation: Implemented necessary dependencies and configuration for future UI modernization

🐛 Bug Fixes
Import & Deployment Improvements
Fixed intermittent asynchronous issues in node imports that could cause incomplete or failed imports
Resolved deployment race conditions where asynchronous operations would occasionally fail to complete properly
Improved error handling and retry logic for both import and deployment processes

Minor Bug Fixes

• Various small bug fixes and performance improvements
• Enhanced stability across core CMS operations

Technical Details

• Async Operations: Fixed promise handling in critical paths to ensure consistent execution
• Error Recovery: Added better recovery mechanisms for failed import/deployment attempts
• Performance: Optimized background processes to prevent timing-related issues
• Real-time Sync: WebSocket implementation for instant content updates across connected clients
• Redis Optimization: Enhanced cache invalidation and connection pooling

3.7.0

Summary
This release focuses on performance optimization, automated data management, and UI refinements. The most significant architectural change is the migration of high-frequency data calls to WebSockets to reduce server overhead.

🌟 New Features
Auto-Cleanup System: Automated background tasks now handle the cleaning of orphaned nodes and content, keeping the database lean.

History Management: Added a "Max History" configuration. You can now define the maximum number of revisions to keep for both nodes and content to prevent data bloat.

Content Publishing: Fully implemented the publishing workflow for nodes and content.

⚡ Performance Improvements
WebSocket Migration: Optimized the application by moving heavy and frequent API calls to WebSockets. This significantly reduces latency and server load for real-time updates.

🐞 Bug Fixes
Plugin Date View: Fixed a display issue where dates were not rendering correctly within the plugin interface.

UI/UX Polishing: Resolved several minor UI errors and inconsistencies across the dashboard for a smoother user experience.

3.6.2

Features

• feat: translation notifications WebSocket done
  • Added support for translating notification messages sent via WebSocket.
  • Notifications now respect the user’s locale when streamed in real-time.
  • Compatible with existing WebSocket subscription for count and unread notifications.

3.6.1

Features

• feat: notifications sync via WebSocket
  • Added real-time updates for notification count and unread notifications.
  • WebSocket endpoint /ws/notifications streams both the number of unread notifications and the paginated list of notifications.
  • Angular client can subscribe to WebSocket to automatically update notification count and table in real-time.
  • Supports optional pagination parameters (page and limit) via query string.
  • Works behind Nginx reverse proxy with proper WebSocket headers (Upgrade / Connection).

3.6.0

Changelog
This version introduces a complete overhaul of the notification system, now powered by Redis for real-time performance.

Features:

• Redis Integration: A new notification system has been implemented, using Redis for faster and more efficient management.
• Real-Time Notifications: Users now receive instant notifications.
• Improved Stability: The entire notification system has been optimized and tested for better reliability.

3.5.2

Fixes:

• Find by childrens done and update Template Market

3.5.1

🚀 Features

• Allow deploying a child alone in an environment; once its parent is deployed, the previously deployed child is automatically attached to that parent.

3.5.0

🚀 New Features

• Implemented resource locking mechanism to prevent concurrent edits.
• Added ability to force unlock a resource manually or automatically after TTL expiration.
• Integrated periodic lock checks on the frontend to automatically close the dialog if the resource is locked by another user.

🔧 Technical Improvements

• Full synchronization between backend and frontend for lock management.
• Scheduled cleanup to handle cases where users keep a resource open for too long.
• Added proper lock status handling in API responses and frontend services.

🧪 Tests & Quality

• Added backend unit tests for acquiring, refreshing, and releasing locks.
• Validated concurrency scenarios (multiple users opening the same resource).
• Improved i18n translations for lock/unlock events (RESOURCE_LOCKED, RESOURCE_RELEASED).

3.3.2

🚀 Features

• Add cache done 5 on files and pictures and 1min on other contents and nodes, api only