Please fill a support ticket. This will allow us to investigate the issue further.Directadmin doesnot works i m unable to login while checking debug logs its showing in correct password but on page it show login successfully but again page refreshs to the same
27491c34f8cd42d011bffa8d59c8f32f99bb1a5a
), with the following Evolution skin changes:I have the same error. Indeed, this update seems like an oopsie.. too much is broken.this 1.642 skin update is a little night mare now i have 2 VPS with this
I even tried with refreshed skin so it is not icon grid related
When i switch back to stable 1.63.9 everything works
rm /usr/local/directadmin/data/users/admin/skin_customizations/evolution/files/config.json
@DanielP, thanks for your post. This is a known issue that can be triggered when upgrading from an older DA version directly to current. It is caused by old Evolution customizations migration failure. We are working on an update to automatically resolve this.
This can be fixed manually by just removing old customizations file:
Code:rm /usr/local/directadmin/data/users/admin/skin_customizations/evolution/files/config.json
But I would recommend waiting for an update.
One of our servers got updated to 1.642 and the evolution skin stopped working on al users giving the following error:
oops!
Privileges needed to load the skin have not been granted for this account or unexpected issue has happened. Please contact your administrator.
I have downgraded the directadmin version and it's working correctly again. Please have a look into this bug.
3cd1f505f05d781bbb4cb5b91e8992dd7d1e5e3d
). Key changes:/usr/local/directadmin/data/skins/evolution/lang
and set language_list
in directadmin.conf
:$ da config-set language_list en:pt_BR --restart
language_list=en:pt_BR
language_list
to a non empty turns Evolution into backwards compatible mode and it uses .po files from /usr/local/directadmin/data/skins/evolution/lang
. When this flag is empty Evolution uses languages that comes built-in. Dealing with JSON files was a temporary workaround until we implemented backwards-compatibility mode.hi everyone, one more update is pushed out (build id3cd1f505f05d781bbb4cb5b91e8992dd7d1e5e3d
). Key changes:
- Fixed Oops! errors when migrating from old customizations. Customizations will be converted to new format and preserved. Reported by @DanielP and @Amplificator and probably by @drukpa
- Fixed table headers as reported by @Erulezz
hi everyone, one more update is pushed out (build id3cd1f505f05d781bbb4cb5b91e8992dd7d1e5e3d
). Key changes:
@paulonichio there is no need to convert translations to JSON and move to custom directory, just keep your translations in .po format in
- Fixed Oops! errors when migrating from old customizations. Customizations will be converted to new format and preserved. Reported by @DanielP and @Amplificator and probably by @drukpa
- Fixed table headers as reported by @Erulezz
/usr/local/directadmin/data/skins/evolution/lang
and setlanguage_list
indirectadmin.conf
:
Code:$ da config-set language_list en:pt_BR --restart language_list=en:pt_BR
Settinglanguage_list
to a non empty turns Evolution into backwards compatible mode and it uses .po files from/usr/local/directadmin/data/skins/evolution/lang
. When this flag is empty Evolution uses languages that comes built-in. Dealing with JSON files was a temporary workaround until we implemented backwards-compatibility mode.
[root@srv2 ~]# /usr/local/directadmin/directadmin c | grep -i language
language=en_GB
language_list=en_GB:en:en_CA
tar cvzf /tmp/customizations.tar.gz -C /usr/local/directadmin/data/users/admin/skin_customizations/evolution .
customizations.tar.gz
on a private message to investigate this issue further. Maybe your issue is not the same we have fixed.Sent.@Amplificator , could you please do:
Code:tar cvzf /tmp/customizations.tar.gz -C /usr/local/directadmin/data/users/admin/skin_customizations/evolution .
And send me thecustomizations.tar.gz
on a private message to investigate this issue further. Maybe your issue is not the same we have fixed.