- Joined
- Aug 30, 2021
- Messages
- 1,060
Managed to sort out @webmaster-hub issue together, apparently it was not related to DA upgrade ?.
It's been added to DA file mirrors already. Thank you for the request.@fln Currently phpmyadmin has version 5.2.
Hi @paulonichio would you be willing to share translation file with community? If you would send me the PO file I would import it to our community translation system at https://translate.directadmin.com. If you would create account there you could also update the outdated translations yourself as well.
If you want to use your old translations without sharing you need to create a new file atdata/skins/evolution/assets/translations/custom/pt_BR.json
.
Using DA to convert it from JSON you can achieve it withcurl -k -s "$(da root-auth-url)/CMD_JSON_LANG?json=yes&lang=pt_BR" > /usr/local/directadmin/data/skins/evolution/assets/translations/custom/pt_BR.json
pt_PT.json
contents as pt_BR.json
it would be visible when one selects pt_BR
.Hi @fln thanks but that i not my question.... before in 1.639 (and earlier) we have the pt_PT language correctly working with no problem at all in /usr/local/directadmin/data/skins/evolution/langhi @jmmm, current Evolution skin does not support adding additional languages. Only existing language files can be replaced or updated. For example if you placedpt_PT.json
contents aspt_BR.json
it would be visible when one selectspt_BR
.
Based on the language tag it seems you would like to add Portuguese (Portugal) language file. In our shared translations platform at https://translate.directadmin.com Portuguese (Portugal) is barely translated and therefore not included in the distribution bundle. If you would to share your pt_PT translation PO file, I could import it into online translation system. Then it it would get released with Evo in the next DA release and no language file replacements would be needed..
pt_PT
translations over pt_BR
and change language to pr_BR
:curl -k -s "$(da root-auth-url)/CMD_JSON_LANG?json=yes&lang=pt_PT" > /usr/local/directadmin/data/skins/evolution/assets/translations/custom/pt_BR.json
perl -pi -e 's/language=.*/language=pt_BR/' /usr/local/directadmin/data/users/*/user.conf
pt_PT
available in translate.directadmin.com it would get released with new DA versions and there would be no need to use pt_BR
as a substitute language. Sharing the translation improvement efforts with other community members would help to get new features translated changed translations updated quicker.directadmin.conf
to enable such mode. However I think it only hides the real issue instead of fixing. Could you give me more details why would you like to keep only one instance of dataskq
running?dataskq
instance takes quite some time to execute it truncates the task log so that subsequent concurrent dataskq
calls will have nothing more to do. Strictly serializing all dataskq
calls is trivial to implement but could have a very nasty consequences. For example if you start a backup for a huge account it could take hours to finish, with concurrent dataskq disabled all other actions would be stuck until the large backup or restore job gets finished.max_concurrent_backups
config parameter in the directadmin.conf
file, link to feature description.