User tests: Successful: Unsuccessful:
Pull Request for Issue #37061
Check the issue
No bug fix, regression
Status | New | ⇒ | Pending |
Category | ⇒ | JavaScript Repository NPM Change Layout |
Labels |
Added:
NPM Resource Changed
?
|
Category | JavaScript Repository NPM Change Layout | ⇒ | JavaScript Repository NPM Change Layout Front End Plugins |
This PR does solve all for me i.e. automatic lang and fields.
I have tested this item
This PR does solve all for me i.e. automatic lang and fields.
@infograf768 So your issue could be closed? Can you do that?
done
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
|
@brianteeman and @infograf768 would you kindly please re-test?
Status | Ready to Commit | ⇒ | Pending |
Status | Pending | ⇒ | Ready to Commit |
Status | Ready to Commit | ⇒ | Pending |
Revert RTC
Labels |
Added:
Release Blocker
Removed: ? |
@brianteeman @infograf768 Could you test again? Thanks in advance.
I have tested this item
I have tested this item
I have just tested with automatic language detection and with manual language. It works all fine in the editor (backend and frontend).
But in the plugin options the manual language seems not to work for me with this PR applied. The editor elements in the plugin's settings are shown in the current backend language when I have switched off the automatic language detection and chosen a different language as editor language some time before.
@brianteeman Can you confirm that?
P.S.: I mean the parts marked with red in this comment: #37061 (comment) . Without this PR they are in English, with this PR they are in current backend language regardless of the automatic language detection being switched on or off.
Without this PR they are in English, with this PR they are in current backend language regardless of the automatic language detection being switched on or off.
I think this is the expected behaviour. The plugin adapts to the backend language for its own options. The language settings are affecting only the tinMCE (the editor either in the front end or back end).
EDIT unless if that wasn't the previous behaviour so then we have to match what was there
EDIT2: This is expected behaviour as the language for the builder defaults to the current backend language according to the code:
joomla-cms/plugins/editors/tinymce/src/Field/TinymcebuilderField.php
Lines 167 to 183 in cb07dbd
@richard67 that is the expected behaviour
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-03-18 07:54:02 |
Closed_By | ⇒ | bembelimen |
Thx
@dgrammatiko Do I understand right that this PR fixes only a part of the issue? If so, could you mention that at the top of the description by adding something like „(part)“ to the line with the reference to the issue?