[{"version":"2026.1 ","name":"Cascade CMS 2026.1 ","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/2026.1.html","date":"2026-04-07","eolDate":"2027-04-07","description":"Cascade CMS version 2026.1 is a feature release that contains Snippets, new Query API directives, an upgraded Siteimprove plugin, and a number of performance improvements related to rendering and editing of assets.","slug":"2026.1","featureCount":"2","improvementCount":"9","fixCount":"15","intro":"\n\nImportant\nBeginning with this release, the following database versions are no longer supported:\n\nMySQL 5.6, 5.7\nSQL Server 2016\nOracle 12c, 18c\n\nYou must upgrade to a supported database version prior to upgrading to Cascade CMS 2026.1 or newer. Failing to do so will prevent the application from starting.\n\n\n\n\nUpgrading from versions prior to 8.12\nIf you're upgrading from a version of Cascade CMS prior to 8.12, you cannot go directly to 2026.1 or newer. Instead, you must first upgrade to 2025.x as an intermediate step and confirm that the Structured Data Upgrade process completes.\nThe status of that process can be viewed under Menu → Administration → Logs and System Information in the Status of structured page and block content upgrade area. The first field's value must be true and the second field's value must be 0 before you can stop the CMS and then apply the upgrade to 2026.1 or beyond.\nPlease reach out to our Support team if you need to obtain a 2025.x installer.\n\n","highlights":"\nSnippets — Centrally manage small bits of reusable content across your Sites. Create once, use everywhere, update in one place.\nNew Query API Directives — Handle large datasets with up to 100,000 results using new directives for pagination and batch processing.\nPerformance Improvements — Significant backend optimizations to rendering, editing, and database operations result in faster page loads and editing experiences.\n","features":"\nSnippets are now available for centrally managing small bits of content throughout your Sites.\nNew Query Tool Directives provide ways for handling large datasets (up to 100,000 results).\n","improvements":"\nBackend: Batch load linked-to assets when enriching, purifying, and parsing XML.\nBackend: Fewer bulk queries to the database when saving Structured Data fields for an asset.\nBackend: Fix for LazyInitializationException during Velocity Format transformation and during page editing increases performance.\nBackend: Legacy Structured Data Node related code has been removed which speeds up editing and rendering.\nBackend: Background Relationship tracking fixes on Page and File renders improves performance.\nAdvanced Submit dialog box now loads much faster in the UI.\nClient side loading of Edit modals with many Structured Data text fields has been enhanced for better performance.\nNew CSV library results in faster CSV Export operations from various areas in the app.\nJDeli Image library has been upgraded.\n","fixed":"\nFixed a number of minor issues related to the Data Definition Builder including inconsistencies with Calendar and Datetime fields' default value settings.\nFixed an issue where clicking the \"Add Content\" link while on the WYSIWYG Editor Configuration screen did not work properly.\nFixed an issue where Drafts of Formats would automatically be saved\/overwritten without making changes.\nUpgraded the Siteimprove plugin and fixed issues with the prepublish functionality for US-based customers.\nRendering Metrics will now properly include metrics associated with Structured Data Blocks.\nFixed a Velocity Format issue regarding UnsupportedOperationException errors due to API objects returning an immutable list.\nMySQL: Fixed performance issues related to queries generated by the Query API.\nFixed an issue where moving a Folder would not properly trigger search index updates for child assets within the Folder.\nOracle: Fixed an issue where \"Create\" Draft previews would throw a NullPointerException if a System Name plugin was in use.\nFixed an issue where deleting a WYSIWYG Editor Configuration would not properly refresh the table to reflect that change in the UI.\nFixed an issue where Group IDs would appear instead of their names in the My Content → Workflows area.\nThe Content Inventory Report will now properly display assets' Titles rather than their Paths.\nFixed an issue in the Content Inventory Report where the \"Restrict to folders\" option would reset other filter selections.\nFixed an issue in the Workflows Report where Workflows would not appear when filtering by Start Date only.\nFixed an exception in the Workflows Report when combining the \"Assigned to\" filter with search text.\nFixed a problem where OkHttp leaked connections in ConnectionPool during link checks.\n","rows":[{"heading":"Upgrade Guide","content":"First time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n"},{"heading":"Requirements & Supported Platforms","content":"Server Requirements\nSummary of system requirements for Cascade CMS.\n\n\nComponent\nRequirement\nNotes\n\n\n\n\nCPU\n8-core (recommended), Quad core (minimum)\nCan be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n8 GB RAM (recommended), 6 GB RAM (minimum)\nRecommended to allocate approximately 1\/2 of the server's total memory to Cascade.\n\n\nHard Drive\n25 GB (recommended), 15 GB (minimum)\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\nCategory\nPlatform\nSupported Versions\nNotes\n\n\n\n\nJava\nOpenJDK\n21.0.5+11\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n2025, 2022, 2019, 2016\n \n\n\nmacOS Server\n10.4 or later\n \n\n\nLinux\n64-bit\n \n\n\nDatabases\nMySQL\n8.0\n \n\n\nMicrosoft SQL Server\n2022, 2019, 2017\n \n\n\nOracle\n19c\n \n\n\nWeb Servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb Browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft Edge\nLatest Stable\n \n\n\nMozilla Firefox\n115+\n \n\n\nSafari\n16+\n \n\n\n"}]},{"version":"2025.2.2","name":"Cascade CMS 2025.2.2","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/2025.2.2.html","date":"2025-10-10","eolDate":"2026-10-10","description":"Cascade CMS 2025.2.2 is the second patch for the 2025 Q2 on-premise release. It includes a variety of performance improvements for everyday editing, publishing, and more — with specific focus on SQL Server and Oracle database customers.","slug":"2025.2.2","featureCount":"","improvementCount":"6","fixCount":"5","intro":"","highlights":"\nSQL Server & Oracle Performance — Strongly recommended for all customers running SQL Server and Oracle databases due to targeted performance improvements addressing those vendors specifically.\nEveryday Editing & Publishing — A variety of performance improvements improve the reliability of many everyday tasks and reduce the impact of background processes on the user experience.\n","features":"","improvements":"\nAdditional performance improvements of publish queue screen loading and pagination.\nUpdated image editor for August release of JDeli.\nImproved reliability of link rewriting when using system-asset pseudo tags.\nPerformance improvements when accessing scheduler on edits and draft saves prevents \"lock wait timeouts\" in logs and in interface.\nImproved performance when accessing entity relationships on SQL Server and Oracle databases.\nImproved performance when interacting with the background scheduler on Microsoft SQL Server and Oracle databases.\n","fixed":"\nAccessing asset permissions through the Cascade API will no longer throw an error.\nErrors encountered when a Google Analytics Connector attempts to find a matching asset will no longer prevent the sync from completing.\nRestoring a previous version of a Content Type will now properly persist the Editable Fields and Publish Options from the previous version.\nYou can now apply simple CSS Class Formats to figure elements in the WYSIWYG.\nFixed various Cross-Site Scripting (XSS) security issues in notifications and tasks.\n","rows":[{"heading":"Upgrade Guide","content":"First time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n"},{"heading":"Requirements & Supported Platforms","content":"Server Requirements\nSummary of system requirements for Cascade CMS.\n\n\nComponent\nRequirement\nNotes\n\n\n\n\nCPU\n8-core (recommended), Quad core (minimum)\nCan be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n8 GB RAM (recommended), 6 GB RAM (minimum)\nRecommended to allocate approximately 1\/2 of the server's total memory to Cascade.\n\n\nHard Drive\n25 GB (recommended), 15 GB (minimum)\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\nCategory\nPlatform\nSupported Versions\nNotes\n\n\n\n\nJava\nOpenJDK\n21.0.5+11\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n2022, 2019, 2016, 2012 \/ 2012 R2\n \n\n\nmacOS Server\n10.4 or later\n \n\n\nLinux\n64-bit\n \n\n\nDatabases\nMySQL\n8.0\n \n\n\nMicrosoft SQL Server\n2019, 2017, 2016\n \n\n\nOracle\n19c, 18c, 12c\n \n\n\nWeb Servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb Browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft Edge\nLatest Stable\n \n\n\nMozilla Firefox\n115+\n \n\n\nSafari\n16+\n \n\n\n"}]},{"version":"2025.2.1","name":"Cascade CMS 2025.2.1","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/2025.2.1.html","date":"2025-07-29","eolDate":"2026-07-29","description":"Cascade CMS version 2025.2.1 is a patch release that makes searching content with punctuation marks more reliable and improves the user experience when creating and editing sites. This release also includes better handling of invalid structured data and dynamic metadata values, plus fixes for the Content Inventory Report pagination on SQL Server and various missing\/deleted group reference issues. We've also upgraded to Tomcat 9.0.107 for enhanced security and performance.","slug":"2025.2.1","featureCount":"1","improvementCount":"2","fixCount":"3","intro":"","highlights":"","features":"\nThis release contains an upgrade to Tomcat 9.0.107\n","improvements":"\nImproved UX of Site create and edit by making the two forms consistent in structure.\nImproved handling of invalid values for Dynamic Metadata and Structured Data fields.\n","fixed":"\n\nSearching content with punctuation marks will now return correct results.\nAddressed an issue in which errors during Folder creation would be momentarily visible.\nPaginating the Content Inventory report will no longer display an error for SQL Server customers.\n\n\n\n \n","rows":[{"heading":"Upgrade Guide","content":"\n\nFirst time installation?\nUpgrade Steps\n\nFirst time installation?\nBe sure to  import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate  installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you   back-up your production database  as well as  set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for  all releases between your version and the latest version.\n\n"},{"heading":"Requirements & Supported Platforms","content":"\n\n\nServer Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 21.0.5+11\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nMicrosoft SQL Server\n\n\n2022\n2019\n2017\n2016 (deprecated)\n\n\nSupport for SQL Server 2016 will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation.\n\n"}]},{"version":"2025.2","name":"Cascade CMS 2025.2","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/2025.2.html","date":"2025-06-30","eolDate":"2026-06-30","description":"Cascade CMS version 2025.2 is a feature release that delivers a new Content Inventory Report, the ability to rename groups, a new Velocity Json Tool, and notable performance improvements including faster report loading, more efficient publishing, and expanded search capabilities that now return up to 5,000 results instead of 250. We've updated various core libraries for performance, stability and security, and included user experience enhancements like streamlined report filtering, fixes for editing Data Definitions and Workflows, and improvements to reporting accuracy.","slug":"2025.2","featureCount":"3","improvementCount":"11","fixCount":"6","intro":"","highlights":"","features":"\nA new Velocity Json Tool can be used for fetching remote JSON resources\nIt is now possible to rename Groups\nA new Content Inventory Report allows reporting on assets in the system based on filters such as by site, asset type, publish dates, review dates, ownership, and other criteria\n","improvements":"\nAdded support for OpenJDK 21.0.5+11\nThis release contains an upgrade to Tomcat 9.0.98\nThe library used for SFTP Transports has been upgraded for improved security and support for newer algorithms\nImproved efficiency of Destination pool used during publishing\nSearching the audits table will now match content within the information column\nImproved performance of publish queue screen loading and pagination\nImproved performance of exporting Content Inventory Report to CSV\nImproved UX when updating filtering for various reports by automatically closing the filter flyout when clicking the apply button\nImproved load times of Content Inventory Report\nUpgraded image editing library to the latest version, 2025.06\nIncreased the maximum number of search results returned from 250 to 5,000, including searching via Web Services\n","fixed":"\n\nAddressed a situation in which editing an asset followed by using a chooser and datetime field prevented from being able to focus within WYSIWYG components.\nThe Edit with Preview frame will no longer become blank after it reloads from content changes.\nThe Add Content menu will now work on the publish queue and scheduled publish jobs screens.\nUnused Assets Report now correctly filters by the selected asset type(s).\nUnzip file report will now indicate if an error was encountered while attempting to unzip vs individual results errors.\nAddressed an issue in which deleted groups could not be fully removed from the Destination and Workflow Definition Applicable Groups setting.\n\n\n\n \n","rows":[{"heading":"Upgrade Guide","content":"\n\nFirst time installation?\nUpgrade Steps\n\nFirst time installation?\nBe sure to  import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate  installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you   back-up your production database  as well as  set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for  all releases between your version and the latest version.\n\n"},{"heading":"Requirements & Supported Platforms","content":"\n\n\nServer Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 21.0.5+11\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nMicrosoft SQL Server\n\n\n2022\n2019\n2017\n2016 (deprecated)\n\n\nSupport for SQL Server 2016 will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in an upcoming on-premise release. We will notify ahead of time.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation.\n\n"}]},{"version":"8.26","name":"Cascade CMS 8.26","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.26.html","date":"2024-12-30","eolDate":"2025-12-30","description":"Cascade CMS version 8.26 is a feature release introducing several new features, including CSV export capabilities for the Users table, user-specific insights in the Sites Listing screen, new Velocity tools. Additionally, this release includes improvements for SFTP Transports, upgrades to Tomcat 9.0.97, improves XHTML\/XML search accuracy, scheduled asset publishing, and smart field behavior, deprecates the Spectate Connector, among various other enhancements and fixes.","slug":"8.26","featureCount":"5","improvementCount":"4","fixCount":"12","intro":"","highlights":"","features":"\nAdded Content Tips which offer real-time SEO guidance as you edit assets with visible metadata fields.\nIt is now possible to export the Users table within the System Administration area to a CSV file.\nIt is now possible to view the users assigned to a particular Site by clicking on the number of users in the Sites Listing screen.\nAdded new Velocity Tool methods to the Property Tool and Number Tool. Also added new convenience methods when working with the Structured Data Nodes using Cascade API.\nAdded $_.NumerTool.sortable Velocity Tool method to be used for string-based sorting, such as with the new #querysortvalue Query API directive.\n","improvements":"\nImproved efficiency of SFTP Transports when reading remote directories and files.\nThis release contains an upgrade to Tomcat 9.0.97\nPerformance and reliability updates to remote link checking and Feed Block fetching\nThe Broken Link Report now considers external links beginning with the System URL as allowed to prevent from checking internal application URLs.\n","fixed":"\nAddressed an issue in which searching content within HTML\/XML markup would not return the correct results.\nFixed issue where individual asset scheduled (un)publish dates would persist after the scheduled date.\nStructured data fields hidden by smart field rules will no longer undergo content checks on submit.\nThe Spectate Connector is now deprecated and it will be removed in the next release.\nAddressed an issue in which URL parts (i.e. parameters and anchor) would be removed while rewriting root relative links added to WYSIWYG fields.\nAddressed an issue in which initial group preview states while editing structured data may not reflect current smart field rules.\nRoot relative links inserted into WYSIWYG fields will be considered external.\nAddressed a race condition in which sending WebSocket messages prevented the publish queue from processing jobs and resulted in general performance degradation\nAddressed an issue in which Page Metadata would be empty when accessed within Asset Factory Plugins.\nIt is no longer possible to enter a name with invalid characters when importing a Site. Additionally, updated various places in the application to better handle existing Sites that have invalid characters in their name.\nAddressed an issue in which Text Blocks created via Site copy would not render properly.\nKeyboard shortcuts are now disabled when a modal or flyout panel is open to prevent accidental execution.\n","rows":[{"heading":"Upgrade Guide","content":"\nFirst time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n\n"},{"heading":"Requirements & Supported Platforms","content":"\n\n\nServer Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nMicrosoft SQL Server\n\n\n2022\n2019\n2017\n2016 (deprecated)\n\n\nSupport for SQL Server 2016 will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation.\n\n"}]},{"version":"8.25.0","name":"Cascade CMS 8.25.0","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.25.0.html","date":"2024-09-18","eolDate":"2025-09-18","description":"Cascade CMS version 8.25.0 is a feature release containing SQL Server 2022 support, updated SFTP Transports for enhanced security, and content check improvements related to broken link checking reliability\/performance. Additionally, the release contains Cascade API and Web Services improvements, upgrades to front-end and server-side libraries, and various other enhancements and fixes.","slug":"8.25.0","featureCount":"2","improvementCount":"13","fixCount":"15","intro":"","highlights":"","features":"\nUploading images and other files through the asset chooser will no longer pre-fill the File's Display Name with its System Name. This will force users who upload images through the chooser to set Image Description or \"alt\" text.\nIt is now possible to unpublish from Destinations using a Database Transport during asset move, rename and delete.\n","improvements":"\nSimplified ability\/permission checking for editing Sites through the interface, the user must have WRITE permission on the Site object itself. This is consistent with permission checking when editing Sites through Web Services.\nSimplified ability\/permission checking for exporting Sites through the interface, the user must have READ permission on the Site object itself.\nImproved link checking efficiency during content checks, publishing and Broken Link Report generation. Also, updated XML Feed Blocks to use the same HTTP client library as link checking.\nUpgraded image editing library to the latest version, 2024.04.\nImproved stability of scheduling library, Quartz, for MySQL and Oracle.\nAllowed for links to WYSIWYG Editor Configurations and Shared Fields to have leading slashes.\nUpgraded various front-end libraries, including those used for the advanced code editor, date formatting and code formatting (via the advanced code editor).\nThe external link check timeout now has a maximum limit of 10 seconds and the feed block request timeout system preference or 20 seconds.\nPublish Set files, pages and folders will now be sorted alphabetically while viewing and editing. Reading a Publish Set using Web Services will also sort the assets consistently.\nImproved UX of Workflows Report filtering by updating visibility of filter options based on the selected status filter.\nAdded support for SQL Server 2022. Support for SQL Server 2016 is deprecated and will be removed in the next on-premise release on or after 1\/1\/2025.\nUpgraded image editing library to the latest version, 2024.08.\nThe library used for SFTP Transports has been upgraded for improved security and support for newer algorithms.\n","fixed":"\nThe UnpublishAndDelete workflow trigger will now respect the authorizing type\/user trigger parameters for non-publuishable assets, such as blocks. Additionally, the Delete workflow trigger will now allow for using the authorizing type\/user trigger parameters.\nFixed an issue where certain Drafts would display an error Missing message for key \"prompt.asset.linkrewriting.\"\nCreating\/editing an Asset Factory using Web Services will now allow for omitting a folderPlacementPosition (or using an explicit null value), allowing for placement the new asset in the parent folder's last position.\nImproved handling of invalid XML while checking for broken links.\nMoving\/renaming a Folder or Container within Manage Site area will now update search indexes for descendants to prevent stale search information such as paths.\nLink checking external URLs with special characters will no longer result in false positive broken links.\nXML Block content will now undergo content checks.\nThe Siteimprove integration will now respect extensionless linking.\nAddressed an issue in which spell checking would not properly handle empty content.\nFixed summary generation in Publish modals.\nPrevented non-editable image files from causing errors on profile picture upload.\nAsset information passed to Publish Triggers when unpublishing via move, rename and delete will now contain the correct asset identifier and type.\nUnpublishing when deleting an asset will now unpublish from Destinations that use a Database Transport.\nAudits created from unpublishing as part of move, rename and delete operations will now reference the correct asset.\nDeleting a Site will now show a relationship error if a Publish Set is being referenced from another Site.\n","rows":[{"heading":"Upgrade Guide","content":"\nFirst time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version. \n\n"},{"heading":"Requirements & Supported Platforms","content":"\n\n\nServer Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is  recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases  1 \nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nMicrosoft SQL Server\n\n\n2022\n2019\n2017\n2016 (deprecated)\n\n\nSupport for SQL Server 2016 will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 1\/1\/2025.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n 1  Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation.\n\n"}]},{"version":"8.24.3","name":"Cascade CMS 8.24.3","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.24.3.html","date":"2024-05-27","eolDate":"2025-05-27","description":"Cascade CMS version 8.24.3 is a patch release containing upgrades to Tomcat 9.0.86 and our image editing library. It also contains a fix for the Siteimprove integration pre-publish functionality among other improvements\/fixes.","slug":"8.24.3","featureCount":"","improvementCount":"2","fixCount":"11","intro":"","highlights":"","features":"","improvements":"\nUpgraded image editing library to the latest version.\nThis release contains an upgrade to Tomcat 9.0.86\n","fixed":"\nAddressed an issue to improve stability of the Siteimprove integration pre-publish feature.\nAddressed an issue in which paginating outputs\/destinations table when (un)publishing would not include all selected outputs\/destinations.\nDeleting a workflow through Web Services will correctly verify the authenticating user's Delete workflows Site Role ability.\nUpdating an SFTP Transport will no longer inadvertently remove the existing private key.\nMy Sites dashboard widget will correctly show \"more sites\" indicator if user has access to more sites than what is listed.\nSiteimprove integration will no longer cause an error for Oracle customers when previewing a draft of a new page that does not have a name entered.\nAddressed an issue where Oracle customers would see an error when previewing a new page which does not a system name entered and uses an Index Block that includes calling page information.\n","rows":[{"heading":"Upgrade Guide","content":"\nFirst time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n\n"},{"heading":"Requirements & Supported Platforms","content":"Server Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2022\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 10\/1\/2024.\n\n\nMicrosoft SQL Server\n\n\n2019\n2017\n2016\n\n\n \n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 10\/1\/2024.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation."}]},{"version":"8.24.2","name":"Cascade CMS 8.24.2","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.24.2.html","date":"2024-01-30","eolDate":"2025-01-30","description":"Cascade CMS version 8.24.2 is a patch release containing a fix to region assignments in Configuration Sets.","slug":"8.24.2","featureCount":"","improvementCount":"","fixCount":"1","intro":"","highlights":"","features":"","improvements":"","fixed":"\n\nChanging the Template for a Configuration Set's Output will correctly persist region assignments of the same region name, including the \"no block\/format\" option.\n\n\n\n \n","rows":[{"heading":"Upgrade Guide","content":"First time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n"},{"heading":"Requirements & Supported Platforms","content":"Server Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2022\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nMicrosoft SQL Server\n\n\n2019\n2017\n2016\n\n\n \n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation."}]},{"version":"8.24.1","name":"Cascade CMS 8.24.1","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.24.1.html","date":"2024-01-12","eolDate":"2025-01-12","description":"Cascade CMS version 8.24.1 is a patch release containing a fix to Daily Content Report email notifications and editing Workflow Definition operation types through Web Services.","slug":"8.24.1","featureCount":"","improvementCount":"","fixCount":"2","intro":"","highlights":"","features":"","improvements":"","fixed":"\nEditing a Workflow Definition via Web Services and toggling the move operation type will now use the correct value.\nAddressed an issue in which Daily Content Report email notifications were not being sent.\n","rows":[{"heading":"Upgrade Guide","content":"First time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n"},{"heading":"Requirements & Supported Platforms","content":"\n\n\nServer Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2022\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases1\nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nMicrosoft SQL Server\n\n\n2019\n2017\n2016\n\n\n \n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n1 Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation.\n\n"}]},{"version":"8.24","name":"Cascade CMS 8.24","link":"https://www.hannonhill.com/cascadecms/latest/releases/versions/8.24.html","date":"2023-12-05","eolDate":"2024-12-05","description":"Cascade CMS version 8.24 is a feature release containing a new Suggested Unused Assets Report, new Broken Link Report functionality and improvements, the ability to edit WebP image files, improved UX in various areas across the application, an upgrade to the application's scheduling library, an OpenJDK 11.0.21+9 upgrade, among other performance improvements and bug fixes.","slug":"8.24","featureCount":"6","improvementCount":"14","fixCount":"10","intro":"","highlights":"","features":"\nA new Suggested Unused Assets Report helps site managers identify assets that are not being referenced within the system.\nIt is now possible to edit images with the WebP file format. Note: the .webp image file extension may need to be added to the Editable Image Extensions System Preferences under the Content tab in order to take advantage of this feature.\nAllowed URLs can be used to skip checking certain links\/domains within the Broken Link Report, Publish Reports, and on-submit content check for broken links.\nIt is now possible to define Valid Response Codes for external link checking during publishing, on-submit content checks and Broken Link Report generation.\nUsers will now be presented with a warning when attempting to remove or change a File asset's extension, which can result in issues viewing the File within the CMS as well as the live website. This applies to File creation and rename as well as upload through the File chooser.\nSiteimprove integration now has Prepublish capabilities, allowing performing checks on page content rendered inside of Cascade CMS.\n","improvements":"\nImproved memory usage when uploading large files. Also updated file size validation to ensure it occurs at the time the file is uploaded.\nVarious tables across the application will now have docked controls as the user scrolls down.\nUpdated internal libraries and Software Bill of Materials (SBOM) for improved security posture\nA close button was added to the page regions pane for improved UX.\nUpdated content checks interface for improved UX\nUpdated the link checker's user agent to help prevent false positives when remote servers block certain types of user agents.\nImproved performance of using the Velocity Locator Tool to locate assets by their path.\nImproved performance of loading audits through the application interface and Web Services. Note: a maximum of 10,001 results will be returned from a Web Services readAudits operation request.\nViewing a user and group will now list users, groups and roles alphabetically.\nReduced likelihood of system instability by improving the Index Block rendering process and also imposing a 50MB hard max on the Maximum Rendered Size of an Index Block system preference.\nAdded support for OpenJDK 11.0.21+9\nBroken Link Report now contains a summary describing exactly what sort of links it contains based on current filters. Additional tooltips are available with explanation of data points.\nThe application's scheduling library, Quartz, has been upgraded for improved stability, performance and security.\nImproved accessibility of asset More menu links.\n","fixed":"\nImproved reliability of Daily Content Report generation. Additionally, the most viewed pages section will now only include data from verified Google Analytics Connectors.\nAddressed an issue in which Google Analytics summaries no longer displayed trend information (i.e. +\/- changes).\nThe Google Analytics dashboard widget will now load properly if data from the previous time period is not present. Additionally, data within the report will now be displayed in a friendlier format.\nAddressed an issue in which 'okina diacritical marks caused spell checking to cause an error.\nLive links to page within the More dropdown, context menu and within Workflow Email notifications will now respect the Site's Extensions to Strip property and remove the extension where applicable.\nRestoring previous versions of Publish Sets and Destinations will (un)schedule publishing based on that version's scheduled publishing settings.\nBroken Link data points are more consistent across the dashboard widget and the report.\nUsers with only the Publish Writable Home Area Assets Site Role ability will now see the Unpublish action under an asset's More menu.\nThe system will no longer attempt to send email notifications to disabled users.\nScheduled LDAP syncing will no longer continue after disabling LDAP.\n","rows":[{"heading":"Upgrade Guide","content":"First time installation?\nBe sure to import our default database schema prior to installing Cascade CMS for the first time. Then follow the appropriate installation instructions for your environment.\nUpgrade Steps\n\nShut down your currently running Cascade CMS environment.\nBefore you upgrade, we strongly recommend that you back-up your production database as well as set up a test environment and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.\nRead the release notes and upgrade guides for all releases between your version and the latest version.\n"},{"heading":"Requirements & Supported Platforms","content":"Server Requirements (for CMS deployment)\nSummary of system requirements for Cascade CMS.\n\n\n \nRequirement\nNotes\n\n\n\n\nCPU\n\n\n8-core (recommended)\nQuad core (minimum)\n\n\nCascade can be run in virtualized environments like VMware and Hyper-V.\n\n\nMemory\n\n\n8GB RAM (recommended)\n6GB RAM (minimum)\n\n\nIt is recommended to allocate approximately 1\/2 of the server’s total memory to Cascade.\n\n\nHard Drive Space\n\n\n25GB (recommended)\n15GB (minimum)\n\n\n \n\n\n\nSupported Platforms\nSummary of supported platforms for Cascade CMS.\n\n\n \nSupported platform(s)\nSupported version(s)\nNotes\n\n\n\n\nJava platforms\nOpenJDK\n\n\nOpenJDK 11.0.21+9\n\n\n64-bit is  recommended for all platforms.\n\n\nOperating System\nMicrosoft Windows Server\n\n\n2022\n2019\n2016\n2012 \/ 2012 R2\n\n\n \n\n\nmacOS Server\n\n\n10.4 or later\n\n\n \n\n\nLinux\n\n\n64-bit (recommended)\n32-bit\n\n\n \n\n\nDatabases  1 \nMySQL\n\n\n8\n5.7 (deprecated)\n5.6 (deprecated)\n\n\nSupport for MySQL 5.6 and 5.7 will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nMicrosoft SQL Server\n\n\n2019\n2017\n2016\n\n\n \n\n\nOracle\n\n\n19c\n18c (deprecated)\n12c (deprecated)\n\n\nSupport for Oracle 12c and 18c will be removed in the next on-premise release on or after 4\/5\/2024.\n\n\nWeb servers\nApache\n \n \n\n\nMicrosoft IIS\n \n \n\n\nSun Java System Web Server\n \nFormerly Netscape Enterprise Server.\n\n\nZeus Web Server\n \n \n\n\nWeb browsers\nChrome\nLatest Stable\n \n\n\nMicrosoft\nEdge\n \n\n\nMozilla Firefox\nFirefox 115+\n \n\n\nSafari\nSafari 16+\n \n\n\n\n 1  Support is maintained for up to 3 versions from each database vendor. When support for a new database version is added, support for the oldest version is deprecated and will be removed in the first on-premise release 6 months on or after the date of deprecation."}]}]