Changelog
The Akrobotic Changelog documents every major milestone in the evolution of our modern ColdFusion framework. From core system migrations and architectural redesigns to package enhancements and security updates, this living record shows how Akrobotic continues to grow stronger, faster, and more capable with every release.
(Draft — Will be revised until official release on January 1, 2026)
Overview
This quarter’s focus builds on the Master Build Migration and prepares the framework for the 2.1.0 release cycle. Work in progress includes system-level optimizations, modular packaging improvements, and new developer utilities designed to make Akrobotic even more scalable and maintainable.
Planned Highlights
- Performance & Optimization – Streamlining query handling, caching, and internal request routing.
- Developer Experience – Expanding command-line utilities and setup automation.
- Security & Standards – Updating cryptographic defaults and strengthening API key handling.
- UI & Theming – Refining default templates for light/dark mode and accessibility.
- Documentation & Onboarding – Drafting new quick-start guides and framework diagrams.
Release Timeline
The finalized Q4 2025 changelog will publish January 1, 2026 as part of the official Akrobotic 2.1.0 release. Updates will continue to appear here throughout the quarter.
November 6, 2025
Overview. Post-migration cleanup and modernization across framework packages, with emphasis on email template standardization, package consistency, and deployment alignment ahead of the 2.1.0 release.
Highlights
Bug Fixes & Refinements
- Centris Company Logo Upload — Fixed upload title error and corrected tracking behavior.
- Messages Not Sending — Resolved
centrisProfileInstantiateerror affecting outgoing message delivery. - Framework Email Templates — Standardized header/footer paths; resolved inconsistent rendering across packages.
Framework & Package Maintenance
- Framework | Packages Cleanup / Modernization — Consolidated legacy functions, reduced redundant logic, and aligned structure with Master Build standards.
- Packages | Default Response Views / Layouts — Cleaned legacy markup and improved Bootstrap 5 layout consistency.
- Communications Module — Updated shared email templates to use the unified header/footer format.
Project Management & Coordination
- PM & Communications — Consolidated framework/communications notes for clearer internal reference; updated task tracking for package modernization.
- GIT Updates / Sync to Production — Completed repository syncs to establish a stable deployment baseline.
Summary. Standardized email structures, aligned layouts, and improved package cohesion strengthen Akrobotic’s reliability and prepare the codebase for the 2.1.0 release.
Master Build
-
Completed full System migration and environment setup for the master repository
-
Configured base directories, initialized default settings, and streamlined the framework for consistent deployments across environments
Application Framework
-
Standardized index structure, meta tags, CSS, JS includes, and top/bottom layout templates into the new System folder
-
Standardized package structure and datasource configuration across the application
-
Moved core CSS from
maintouserand introduced dark mode defaults -
Removed unused code to reduce clutter and improve maintainability
Users Module
-
Implemented
users*Internalfor improved security and authentication handling -
Cleaned up and simplified the account page, fully deprecating legacy Centris references
-
Performed broad cleanup and refactoring ahead of the upcoming
2.0.2.5-10release
Packages
-
Created the initial commit for the default package to support modular expansion
Users Module
-
Added configurable option to enable or disable user registration
-
Integrated and standardized Users package (v2.0.2.5) with controller logic, SESSION message handling, and modal interfaces
-
Improved LOCAL scoping in functions and updated email templates
-
Removed deprecated fields (
account_type) and cleaned up registration form code -
Consolidated and renamed files for consistency (
users-create.cfm, modal cleanup, general refactoring) -
Cleaned up and optimized related database tables for improved reliability
Configuration System
-
Created centralized configuration file for application settings
-
Standardized configuration naming (
APPLICATION.company_url→APPLICATION.company_domain; addedcompany_domain_sld) -
Added new configuration options (
package_users_login_redirect) for login routing control
System Framework
-
Introduced standardized error handling across the framework
-
Consolidated
onErrorlogic withinApplication.cfcfor unified error processing -
Aligned
error.cfmtemplates to ensure consistent error responses, clearer error logging, and improved debugging -
Refined existing
error.cfmtemplates for consistent error handling -
Updated
Application.cfcto unify error logic and improve debugging -
Updated baseline system files (
index.cfm,.htaccess) to support this branch’s environment -
Cleaned up
cflocationformatting and general application scoping practices -
Added
cfparamhandling forURL.routeto improve debugging workflows
Framework Controllers
-
Cleaned and optimized the Trace model’s queries for
system_trace -
Updated Security controller to use
key_lengthinstead ofstrLengthfor enhanced security -
Cleaned scope usage in Access controller for improved maintainability
-
Refactored Default controller by converting
systemDisplayBuildto a struct-based pattern
Repository Maintenance
-
Updated
.gitignoreto exclude media files, configuration files, and development-only directories -
Performed broad cleanup of obsolete files and reorganized project structure for clarity
System Framework
-
Introduced Official Navigation v2.0.2.5, consolidating the system navigation structure for all packages
-
Updated
.htaccessrouting to support package changes (Blog, Centris, Credentials) -
Removed legacy marketing menu entries and deprecated unscoped headers/footers
-
Renamed and cleaned up application references, aligning app naming and URLs
-
Fixed and improved
accessAuthenticatehandling and return logic across multiple packages -
Enhanced scoping practices (
cfargument,cfparam,LOCALusage) and standardized variable handling -
Updated
.gitignorerules to exclude sensitive files (configuration.cfm) and development artifacts
Framework Controllers
-
Refactored Access, Default, and Framework controllers with improved scope handling, argument management, and code cleanup
-
Cleaned and optimized the Trace model queries (
system_trace) -
Updated Security controller to use
key_lengthfor improved cryptographic handling -
Performed general controller-wide modernization and codebase cleanup
Packages
-
Performed widespread cleanup, modernization, and Bootstrap 5 conversions across core packages:
-
Credentials — Rebuilt UI with Bootstrap 5 modals, added realtime search filter, cleaned and reorganized code
-
Projects — Cleaned, modernized codebase, added Unsnooze feature to main menu
-
Transactions — Code cleanup, scoping improvements, and modernization
-
Invoices — Cleaned controllers, views, and models; fixed decimal scaling, added comments, standardized function naming, and improved data encoding
-
Documents, Blog, Scheduler, Events, Geolife, Hosting, Compilations, Checkout, Commander, Backups, Developer, Default, Home, Centris — Broad code cleanup, scoping fixes, and AccessAuthenticate updates
-
Deprecated Commander and other older packages to the development area for archival
-
Migrated Centris back into the Development workspace
-
Repository Maintenance
-
Updated and consolidated
.gitignorerules for credentials, messages, and other sensitive or transient files -
Performed broad cleanup of obsolete files, reorganizing directories for clarity and consistency
Modernized Application Core. Migrated from application.cfm to Application.cfc, introducing structured application lifecycle methods, centralized configuration, and improved request handling. These changes enhance session management, variable scoping, and error handling while aligning the framework with modern ColdFusion security and performance standards.
Migrate all applications to:
framework/accessframework/communicationframework/devicesframework/geographicsframework/mainframework/packagesframework/securityframework/security & framework/debugframework/security/firewallframework/traceframework/uploaderframework/xlc
Undertook a large-scale restructuring of the framework to organize application logic into specialized controllers. This upgrade separated core functionalities into dedicated directories, improving maintainability, security, scalability, and development workflows across all applications.