DirectAdmin 1.710

[fln]

We are happy to announce the release of DirectAdmin 1.710.

A full release change log is here:

DirectAdmin 1.710​

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!

 

[Ohm J]

this is still working same as before ? without touch/update the customize template to latest support format

server
{
|CUSTOM|
|?SDOCROOT=`DOCROOT`/`SUB`|
#...
#...
#...  
    root "|SDOCROOT|";

 

[fln]

There is no easy answer to this. Yes and no.

The |?SDOCROOT=...| inside the main template file sets the token SDOCROOT value only if this token was not defined before. For subdomains, DA prefers a custom document root by default (to keep the subdomain outside of the main domain docroot). For such subdomains, the |?SDOCROOT=...| inside the main template is dead code (even for older DA releases).

However, for domains that do not have a custom document root set, the previous DA releases would NOT set the SDOCROOT token prior to the template evaluation. This means the initial token was set by the |?SDOCROOT=...| inside the template. With this release DA makes sure that SDOCROOT is always set prior to the template evaluation. This means |?SDOCROOT=...| is now ALWAYS a dead code.

---

If the question is about the token value (not the place which sets the token value), then the answer is yes. It is backwards compatible with no changes because DA sets the SDOCROOT value to the same string that would be set by the template. It just means setting this token value inside the main template is now a dead code. It used to be dead code sometimes, now it is a dead code always.

 

[fln]

Anyway, I would recommend syncing the customized templates to be as close to the original templates as possible. I mean updating the custom templates to match the original templates in places that does not need customizing and keeping only changes that are really the purpose of the customization.

It will make it easier to maintain the customizations in the future. And the custom templates will be more likely to be forwards compatible with new DA releases.

 

[exlhost]

So this update will break the Custom1 value in --> |?DOCROOT=/home/abcderfg/domains/testtestdomainnew.com/public_html/pub/| in http.conf? for a Magento webshop?

 

[fln]

Tokens can still be changed in the CUSTOM sections. The token can not be changed in the main template only (same as before). The way it works have not changed.

Note: The reason we are making these changes is to allow DA to set custom document root for domain as well. So hopefully once we finish with this feature you will no longer need to use CUSTOM sections for non-default main domain document roots.

 

[fln]

A new build is pushed out. It fixes a couple of modal windows not behaving correctly in the UI.

 

[JosKlever]

@fln I'm not sure if it's caused in the latest update or a bit earlier, but when I try to change the limits/quota of a mailbox, the modal doesn't do anything when pressing Save. No error, nothing.