DirectAdmin 1.695

fln

Administrator
Staff member
Joined
Aug 30, 2021
Messages
1,308
We are happy to announce the release of DirectAdmin 1.695.

A full release change log is here:

DirectAdmin 1.695


The update should be automatically available for all installations subscribed to the current release channel.

We appreciate all the feedback on forums and issues reported in the ticketing system.

Thanks!
 
Totally unrelated, but I find it surprising PHPMyAdmin doesn't get many updates - or should I say, fixes - like it once did.
 
@LawsHosting
What do you want from their software ? Read the datetime.
1771425597965.png
 
What do you want from their software ? Read the datetime.
Was just making an observation, that's all.... I remember from years ago that we had a few updates a month due to CVEs.

Maybe all the old coders moved to Microslop. /s
 
Can this be marked as a breaking change: "Web server configuration templates always use public_html directory update"

Because we had a client that only used private_html so we needed to add custom templates for this situation.
 
Can this be marked as a breaking change: "Web server configuration templates always use public_html directory update"

Because we had a client that only used private_html so we needed to add custom templates for this situation.

The same! Broke multiple sites!
 
@misthafalls, @jet1972, to help with the migration away from the private_html directories, please check the Maintenance tasks page (Evolution skin). There is a helper script Ensure all domains private document roots link to public (released in DA 1.649). Usage of private_html directories are deprecated for almost three years now.

Unfortunately we can not force a migration on everyone because it can lead to data loss if private_html and public_html directories contain different data. We do this kind of breaking change instead. This gives the server administrators for resolve the problem without data loss.
 
Last edited:
@fln I have no qualms to remove the feature, however in some cases people have been using DA for such a long time that legacy will creep up, especially considering not everyone started with the same provider and will have migrated etc. over the years. This means when DA changes something on a server we do not have full knowledge over (because migration or unmanaged cases) and something breaks it is our support that needs to deal with it. So in that case we would like to clearly know about a potential breaking issue even if it has been deprecated for a long time. This also quite standard practice in most other changelogs (e.g. PHP) that on a feature removal even if deprecated gets clearly stated.

About the link you supplied to DA 1.649 while the text says it is getting removed in possible future it wasn't clearly marked in the title or tag as being deprecated. While something like the "DEPRECATED: User or mail can get their dovecot quotas with directadmin suid mode" in version 1.55 did get clearly marked in the title as being DEPRECATED.

So please do better in regards to being more consistent in your changelogs in this, because that will help us and in the end you for answering our in this case "silly" questions.
 
@fln Critical problem: User information/limits cannot be edited. Control over cgroup limits (Resource Limits) is broken (user or package management areas). The "Memory high" field does not accept any value and displays "Invalid size format used."

And when changing the language at the top of the page, the Resource Limit fields are not updated until the page is reloaded.
 
@unihostbrasil, we are unable to reproduce the problem. Could you please open a support ticket.
We have already identified the problem. In "modify reseller" (as admin) (/evo/admin/users/resellers/{reseller}/view/modify), the resource limit input validations are not being performed.

If a non-integer number is used, the value is accepted, for example:
Memory High = "3.7G"

However, in "modify user" (as reseller) (/evo/reseller/users/{user}/view/modify), this non-integer value causes a problem in the validation script, and no value, even an integer, is accepted, making any changes to the user impossible.

The translation problem is easily reproducible. Open the user modification page and change the language. Everything will be translated, except for the resource limit labels. These labels will only be translated when the page is reloaded.

Does this still require creating a ticket?
 
  • Like
Reactions: fln
We see that the filemanager_disable_features=65536 feature doesnt work anymore to disable the Trash Can. File still getting moved to the trash can.
Testing other described numbers also doesnt work so it seems the filemanager_disable_features feature might be broken in current file manager
 
We see that the filemanager_disable_features=65536 feature doesnt work anymore to disable the Trash Can. File still getting moved to the trash can.
Testing other described numbers also doesnt work so it seems the filemanager_disable_features feature might be broken in current file manager
It should be working only for Enhanced skin, but not for Evolution one.
 
@unihostbrasil, thanks for detailed reproduce steps. It seems the decimal resource amount validation problem is not something introduced in this version (it is also present in stable). We will fix it in the next DA release like a normal bug (not a hot-fix).

Translations for the resource options comes from the backend (it is not part of the Evolution but instead part of the directadmin service). That is why it requires a full page reload. To change how it works (move translations out of backend into the Evolution) we need to redesign the resource control management API. This will happen eventually but not in the next release.

@Ohm J, the time should be in seconds. This a bug in the UI. Thanks! Time is in minutes. The default value might be misleading because 86400 seconds would be 24 hours, but is is actually in minutes and default value is 60 days.
 
Last edited:
It should be working only for Enhanced skin, but not for Evolution one.
Yes, so why is it broken now? The disable Trash Can feature used to work with Evolution skin. It works fine when you use DirectAdmin 1.962 for example with the Evolution skin. Hope it can be fixed. We already have our own snapshots/backups and the trash can causes sudden disk space usage for customers.
 
Sorry, I was too quick to jump to conclusions 🤦‍♂️. My previous statement is wrong.
@Ohm J, the time should be in seconds. This a bug in the UI. Thanks!
The time is actually in minutes. UI shows it correctly. The default value is quite misleading 86400 seconds would be 24 hours (1day). But it is actually 86400 minutes, which is 60 days.
 
Ah sad, it's the emergency bug, I just update some setting in today to match with my custom "block_ip.sh".

I don't know how the interface save the default value, maybe default value is just remove the config from "directadmin.conf".


Previously, the fields are accept as "seconds", I just notice today why I config some option like "3600 miniute" by myself or miss something in the past.... I can't remember.

So the "seconds" option should be here for backwards comparative.
 
Back
Top