Version 1.695
Released: 2026-02-??
Improve File Manager keyboard navigation evolution update
The File Manager components (Main toolbar and breadcrumbs) have been improved for better accessibility. Users can now more easily navigate these elements using keyboard shortcuts, with enhanced tab navigation and improved focus indicators to show which element is currently selected.
Use DirectAdmin User-Agent for HTTP requests update
HTTP requests made by DirectAdmin daemon now report User-Agent: DirectAdmin/1.695 (with correct DirectAdmin version).
Fix git deploy crash fix
Git feature deploy action used to crash abruptly. This is now fixed.
Plugin Manger script permissions fix
If any of the scripts located inside plugin's scripts folder do not have execute permissions, they'll be added as necessary.
Removed custom menu names evolution removal
Custom menu entry names can no longer be configured within "Customize Evolution Skin" page. Any previously set custom names will revert to defaults.
Drop sleep parameter from taskq action=rewrite removal
Optional sleep parameter is no longer supported for dataskq action=rewrite actions. For compatibility sleep parameter is now ignored as if it did not exist.
Removed config.json maintenance task removal
The migration task titled "Migrate legacy Evolution customizations to new format" was dropped.
Cluster: cluster_domainowners: allow master to create subdomain under same User fix
If the hosting master has check_subdomain_owner=1 and the dns slave has check_subdomain_owner_in_cluster_domainowners=1, if User fred has fred.com, the bug was that this User account would not be able to create a new domain called sub.fred.com. This fix uses the existing returned hostname and User values from the slave, such that the master can validate if the current User is allowed to create the current hostname. It would have previuosly returned the incorrect Domain exists on 1.2.3.4 when trying to create a subdomain as a full domain, where the full domain itself exists in the slave's cluster_domainowners file. As before, the slave still returns that the value already exists, because of check_subdomain_owner_in_cluster_domainowners=1 with status exists=3, which refers to the subdomain match for a higher-level domain name, including the hostname and username, during the Cluster's CMD_API_DNS_ADMIN?action=exists&domain=fred.com&check_for_parent_domain=true check. (The fix is in the code on the master side)
Rspamd: mime_whitelist was using 'from' instead of 'from_mime' fix
The per-user rspamd config uses 2 sections for each whitelist and blacklists. One uses the "from" format matches the smtp sender and the "from_mime" matches the mime sender. The whitelist section was using "from" instead of "from_mime".