Note: This documentation is still in progress, not reviewed properly, and might contain some errors or outdated images. It's intended for the upcoming 4.0.0 release, so configuration settings might be different from previous versions.

Upgrading to v3.3.0

Overview

Version 3.3.0 is a maintenance and performance release that builds on the improved architecture introduced in v3.0.0 and the logging capabilities of v3.2.0. This update focuses on enhancing stability, security, and user experience.

Upgrade Instructions

  1. Download latest tarball from GitHub
  2. Backup your files and database before proceeding
  3. Replace all files with content from the downloaded archive
  4. Restore your configuration file (inc/config.inc.php) from backup

Improvements

Performance Enhancements

  • Optimized database queries for faster zone and record loading
  • Improved caching mechanisms for frequently accessed data
  • Reduced memory usage for large zone operations
  • Enhanced page load times throughout the application

User Interface Refinements

  • Improved responsive design for better mobile compatibility
  • Enhanced form validation and error messaging
  • Polished visual elements for better user experience
  • Fixed various rendering issues in different browsers

Security Updates

  • Updated dependencies to latest secure versions
  • Enhanced input validation and sanitization
  • Improved session handling and security
  • Fixed potential XSS issues in various forms

Bug Fixes

  • Corrected issues with special characters in record content
  • Fixed sorting and pagination in zone and record listings
  • Resolved problems with DNSSEC key management
  • Addressed compatibility issues with newer PHP versions
  • Fixed various template rendering bugs

Notes

  • No database schema changes are required for this update
  • This release maintains backward compatibility with v3.2.0 configuration files
  • The performance improvements are especially noticeable on systems with many zones
  • Users upgrading from versions prior to v3.2.0 should first upgrade to v3.2.0 before proceeding to v3.3.0