User tests: Successful: Unsuccessful:
Adding missing string in case a content language can't be created when installing a language during J installation
Saw this when testing #25258 (comment) on a clean install.
Issue will normally be solved by #27854 but better be safe in case a Content Language can't be created at J installation time.
Status | New | ⇒ | Pending |
Category | ⇒ | Installation Language & Strings |
@infograf768 Forget my previous question. Got it. Am just testing.
I have tested this item
On a clean current 4.0-dev branch as long as PR #27854 hasn't been merged yet, make a new installation.
At the end of installation, customize installation and install e.g. Persian language.
Result: Notice alert shown.
Without PR notice not translated but showing the language string constant.
With this PR: OK, correct message is shown.
This new string is just a precaution. There are many possible reasons why a content language could not be created.
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-09 17:00:05 |
Closed_By | ⇒ | wilsonge | |
Labels |
Added:
?
?
|
Thanks!
@infograf768 I haven't seen that warning, not translated and not untranslated, and this PR here seems to deal with new installation. Shall we do real test or do code review only? Please provide instructions.