DirectAdmin 1.695

[fln]

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!

 

[LawsHosting]

Totally unrelated, but I find it surprising PHPMyAdmin doesn't get many updates - or should I say, fixes - like it once did.

 

[Ohm J]

@LawsHosting
What do you want from their software ? Read the datetime.

 

[LawsHosting]

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

 

[misthafalls]

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.

 

[jet1972]

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!

 

[fln]

@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.

 

[misthafalls]

@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.

 

[unihostbrasil]

@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.