DirectAdmin 1.711

[fln]

We are happy to announce the release of DirectAdmin 1.711.

A full release change log is here:

DirectAdmin 1.711​

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!

 

[zEitEr]

Hello,

You're probably too aggressive in forcing a 'private_html' removal. There are old servers, which still use public_html and private_html with different content. I understand you need to evolve. But still... just my point

 

[nsc]

Hello,

You're probably too aggressive in forcing a 'private_html' removal. There are old servers, which still use public_html and private_html with different content. I understand you need to evolve. But still... just my point

Why do you think someone is deleting private_html? The changelog says they'll simply stop creating that directory for new users going forward.

In fact, they haven't used private_html in their templates for over half a year already:

Version 1.695 | DirectAdmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

 

[zEitEr]

Why do you think someone is deleting private_html?

I don't. Who told you that? No `private_html` can be used since 1.710. I will need to replace a DOCROOT with a CUSTOM TOKEN, if I want to still use `private_html`

- https://docs.directadmin.com/changelog/version-1.710.html-all-web-server-templates-use-docroot-token

The web server configuration templates are updated. Key changes:

• The DOCROOT token will be used for both domains and subdomains. Previous releases used the SDOCROOT token for subdomain document root.
• Templates will no longer set or change the document root tokens inside the template. The main DOCROOT token will be set by the main DirectAdmin service before the template is evaluated.
• The tokens REALDOCROOT and PUB_DOCROOT are completely removed. They were defined inside the templates but not used.
• The token SDOCROOT will still be available. The value of this token will be the same as the main DOCROOT token.

Special care should be taken if the token DOCROOT is being changed in the CUSTOM[N] sections. It is still possible to change the document root by changing this token value. However, since subdomains are now using the token DOCROOT instead of SDOCROOT, a customised main document root can leak into the subdomain configuration.

 

[nsc]

I don't. Who told you that? No `private_html` can be used since 1.710. I will need to replace a DOCROOT with a CUSTOM TOKEN, if I want to still use `private_html`

- https://docs.directadmin.com/changelog/version-1.710.html-all-web-server-templates-use-docroot-token

The web server configuration templates are updated. Key changes:

• The DOCROOT token will be used for both domains and subdomains. Previous releases used the SDOCROOT token for subdomain document root.
• Templates will no longer set or change the document root tokens inside the template. The main DOCROOT token will be set by the main DirectAdmin service before the template is evaluated.
• The tokens REALDOCROOT and PUB_DOCROOT are completely removed. They were defined inside the templates but not used.
• The token SDOCROOT will still be available. The value of this token will be the same as the main DOCROOT token.

Special care should be taken if the token DOCROOT is being changed in the CUSTOM[N] sections. It is still possible to change the document root by changing this token value. However, since subdomains are now using the token DOCROOT instead of SDOCROOT, a customised main document root can leak into the subdomain configuration.

Ah, you mean the ability to use separate public_html and private_html directories as a concept?

You can still customize your templates to accommodate that - if it's the HTTPS part, use one docroot; if HTTP, use a different one. Basically, the same way you'd customize any main domain's docroot.

Throughout the period when websites started loading only from public_html, we did come across different websites being used between HTTP and HTTPS for some users, but in every case it was accidental - either an old, unused version, or a duplicate copy of the site where the user simply didn't know where to upload their files. Across our entire server fleet, we've had zero cases where this was actually needed.
So far, I haven't heard a valid reason why this separation would actually be needed. With .dev domains, browsers do not even let you access the websites over http:// due to preloaded hsts rules.

 

[zEitEr]

In fact, they haven't used private_html in their templates for over half a year already:

It would be probably more user-friendly if you give an option to support legacy private_html within DOCROOT token. You might add additional code in DirectAdmin which will check if private_html folder exists, and set DOCROOT to use private_html instead of public_html.