DirectAdmin v1.642 has been released

Has there been any change in the DirectAdmin translation?
I translated the pt_BR.po file and threw it in the folder

/usr/local/directadmin/data/skins/evolution/lang

Then I generated a Json and threw it in the folder:

/usr/local/directadmin/data/skins/evolution/assets/translations/custom

And the language change does not occur, remaining the incomplete translation of the DirectAdmin translation system.

View attachment 5822

Another problem is that we put the CSS for the subtheme, but in Firefox, the logo doesn't appear. Chrome, Safari and other browsers display normally.

View attachment 5823

Another problem is that by default we use Portuguese (BR) as the default language on the server. Since the last version, when logging into the system in a browser without cache, the English language is loaded by default, and every time we need to go and change it to pt_BR.

Thanks for helping me with these issues. ;)

DirectAdmin logo issue in Firefox using subtheme CSS not showing, can anything be done to fix the issue?
Clear cache not resolve the problem for example.

About the problem in the translation, by inserting "language_list=" apparently fixed the problem.
 
We have released an update (build ID 605562f0eb44bacacd8f34597a903cbe0608d1f0) with the following changes:
  • Fixed an issue where Evolution would show Oops! error message when custom translations were used, thanks @Amplificator
  • Fixed logo on traditional sub-theme compatibility mode to be shown on Firefox, thanks @paulonichio
  • Fixed set_permissions.sh shell script to avoid repetitive DA restarts which could lead to license rate-limit errors
 
We have released an update (build ID 605562f0eb44bacacd8f34597a903cbe0608d1f0) with the following changes:
  • Fixed an issue where Evolution would show Oops! error message when custom translations were used, thanks @Amplificator
  • Fixed logo on traditional sub-theme compatibility mode to be shown on Firefox, thanks @paulonichio
  • Fixed set_permissions.sh shell script to avoid repetitive DA restarts which could lead to license rate-limit errors

Just a heads-up, the issue reported here remains unresolved in this update: https://forum.directadmin.com/threads/directadmin-v1-642-has-been-released.66665/post-350521
 
Resend welcome e-mail doesn't work since the latest update....

1660079903750.png

1660079961567.png

fix_permissions didn't solve anything.
 
We have released an update (build ID 605562f0eb44bacacd8f34597a903cbe0608d1f0) with the following changes:
  • Fixed logo on traditional sub-theme compatibility mode to be shown on Firefox, thanks @paulonichio

Fixed! Thanks! ;)

---------------


I apologize, but I found a new possible bug in the use of translations.

In my directadmin.conf I set the following variables:

Code:
language=pt_BR
language_list=pt_BR:ar:de:es:es_419:fa:fr:hu:ja:en:zh

When opening DirectAdmin, the top of DirectAdmin remains in English, but the rest of the content with the correct translation and written by our company.


img1.png

When clicking on CustomBuild for example, mysteriously the top is translated to pt_BR:

img2.png

When accessing a customer account for example, the top returns to language English:

img3.png

I don't know if I configured something wrong, but on all our servers this behavior is happening with the translation.

Thanks again for the help! :)
 
Resend welcome e-mail doesn't work since the latest update....

View attachment 5833

View attachment 5834

fix_permissions didn't solve anything.
 
Looks like my issue was something different and had to do with rspamd which prevented /usr/sbin/exim to be linked with /usr/sbin/sendmail;

 
There is an issue with sendmail symlink after latest update. DA updated on Sunday:

DA.png

Update changed destination of /usr/sbin/sendmail symlink:

$ ls -la usr/sbin/sendmail
lrwxrwxrwx 1 root root 9 sie 7 06:47 usr/sbin/sendmail -> /etc/exim

Sendmail should point directly to exim (/usr/sbin/sendmail -> exim). This symlink change caused trouble sending emails via PHP mail() and with dovecot rules on severall servers. We've been able to sort it manually but it definitely requires attention and fix to prevent this from happening.
 
In addition to my previos reply - that's all that has been logged in custombuild.log:

2022-08-07 06:47:26 localhost: called: cron
2022-08-07 06:47:32 localhost: DirectAdmin update requested
 
Still facing the OOPS!. Privileges needed to load the skin have not been granted for this account or unexpected issue has happened. Please contact your administrator on the login page for both admin and users on build 605562f0eb44bacacd8f34597a903cbe0608d1f0

Tested out commit 935a1c6033b3d3a2591db2643f0bccdcc19e191e and the issue isn't present.
 
Last edited:
Hmmm, this might be some other issue. The page Oops! just means Evolution encountered a runtime error, which historically could have been caused by wrong permissions (but not anymore, we check permissions after DA upgrade).

Also opening up browser developer tools might show some hints about what error Evolution encountered.

@LeonDynamic it would be great if you could share access to the server with us (via private message) to investigate it further. For Evolution it is just enough to just have credentials and hostname that triggers the error, no need for SSH access.
 
Still facing the OOPS!. Privileges needed to load the skin have not been granted for this account or unexpected issue has happened. Please contact your administrator on the login page for both admin and users on build 605562f0eb44bacacd8f34597a903cbe0608d1f0

Tested out commit 935a1c6033b3d3a2591db2643f0bccdcc19e191e and the issue isn't present.

If you have any skin customizations in folder
Example in users admin /usr/local/directadmin/data/users/admin/skin_customizations

Try to move to skin_customizations.bak or remove it , and restart directadmin
This method work in our server

If still present , try force unpack tar.gz ( tar xzvf directadmin_xxx.tar.gz ) of current version of directadmin after remove skin_customizations
 
Tested out commit 935a1c6033b3d3a2591db2643f0bccdcc19e191e and the issue isn't present.
Just noticed that you have no issues with alpha build. Actually Evolution in current and in alpha is almost identical. Maybe you just accessed Evolution while update was still in progress? Would be great to double check if reverting to current introduces problem again.
 
Just noticed that you have no issues with alpha build. Actually Evolution in current and in alpha is almost identical. Maybe you just accessed Evolution while update was still in progress? Would be great to double check if reverting to current introduces problem again.
The servers have reverted to the current build and the issue is back again. Do you still want to have a look?
 
If you have any skin customizations in folder
Example in users admin /usr/local/directadmin/data/users/admin/skin_customizations

Try to move to skin_customizations.bak or remove it , and restart directadmin
This method work in our server

If still present , try force unpack tar.gz ( tar xzvf directadmin_xxx.tar.gz ) of current version of directadmin after remove skin_customizations
Thanks @IXPLANET, worked a treat.
 
Just noticed that you have no issues with alpha build. Actually Evolution in current and in alpha is almost identical. Maybe you just accessed Evolution while update was still in progress? Would be great to double check if reverting to current introduces problem again.
@fln last i mitigated this issue come if i used version before 1.640 and then jumping out to current 1.642 and this error will present " if " any skin customizations before

It must step by step update before work
1.639 up
1.640 up
1.641 up
1.642
And error will not present
 
Last edited:
Back
Top