[#12641] - Use the new native title metadata in installed languages view
- Fixed in Code Base
- 4 Nov 2016
- Medium
- Build: staging
- # 12641
- Diff
- andrepereiradasilva:installed
- Success continuous-integration/drone the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success JTracker/HumanTestResults Human Test Results: 2 Successful 0 Failed. Details
User tests: Successful: Unsuccessful:
Summary of Changes
Use the new native name metadata in installed languages view
Testing Instructions
- Use latest staging
- Apply patch
- Go to Extensions >Languages > Installed
- Check there is a new column (Native Title) with the info
- Test site and admin languages.
The code was also optimized to use the new JLanguageHelper::getInstalledLanguages method.
Documentation Changes Required
None.
@infograf768 please check this.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Administration Components |
yes we can, will add a - then
done
Sorry i am confused
The Native Language column is complete in the content language view and incomplete in the installed language view
@brianteeman the native name for a language is a new metadata value for the site/admin language, when the language packs translate that metadata value it will apeear here.
The content languages use other method since, IIRC, they fallback to the name, and if installed using install they even fallback to a language var in installation ini. See https://github.com/joomla/joomla-cms/blob/staging/installation/language/en-GB/en-GB.ini#L187
This was made to preserve B/C.
In the future this nativeName metadata should be the native title used for all views: Installed languages, Content Languages and Installation.
I have tested this item
Does what you say it will do althuough kind of hard to test if no language supports this yet
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12641.
Does what you say it will do althuough kind of hard to test if no language supports this yet
They will in 3.7.0. See for instance https://crowdin.com/translate/joomla-cms/532/engb-pt
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12641.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12641.
| Labels |
Added:
?
|
||
@andrepereiradasilva
Note: I remarked that updating a language pack via Extensions=>Install=>Upload Package File does not create a Content Language.
If a pure install (i.e. NOT updating), the Content language is created.
You may want to look into this
@infograf768 not related to this PR will check that in another PR if needed
@andrepereiradasilva just noticed that in a pure install (i.e. NOT updating), the Content languages other than en-GB - English are not more created with postgresql , some other PR's maybe have create these issues
| Milestone |
Added: |
||
rdeutz
- | Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-11-04 09:08:04 |
| Closed_By | ⇒ | rdeutz |
@andrepereiradasilva just noticed that in a pure install (i.e. NOT updating), the Content languages other than en-GB - English are not more created with postgresql , some other PR's maybe have create these issues
Seems to be database related. Can you open a new issue @alikon ?
not sure i like the "unknown" as it would look bad on older packs.
may be just leave it empty ?