Here you can see 3 lines that are not translated as they were added by a hardcoded request.
administrator\components\com_admin\sql\updates\mysql\4.0.0-2018-05-15.sql (similarly for postgresql)
INSERT INTO `#__workflow_transitions` (`id`, `asset_id`, `published`, `ordering`, `workflow_id`, `title`, `description`, `from_stage_id`, `to_stage_id`, `options`, `checked_out_time`, `checked_out`) VALUES
(1, 0, 1, 1, 1, 'Unpublish', '', -1, 1, '{"publishing":"0"}', NULL, 0),
(2, 0, 1, 2, 1, 'Publish', '', -1, 1, '{"publishing":"1"}', NULL, 0),
(3, 0, 1, 3, 1, 'Trash', '', -1, 1, '{"publishing":"-2"}', NULL, 0),
(4, 0, 1, 4, 1, 'Archive', '', -1, 1, '{"publishing":"2"}', NULL, 0),
(5, 0, 1, 5, 1, 'Feature', '', -1, 1, '{"featuring":"1"}', NULL, 0),
(6, 0, 1, 6, 1, 'Unfeature', '', -1, 1, '{"featuring":"0"}', NULL, 0),
(7, 0, 1, 7, 1, 'Publish & Feature', '', -1, 1, '{"publishing":"1","featuring":"1"}', NULL, 0);
Some of the strings have been translated, since there have been translation keys for them for a long time.
If we add the appropriate keys (for example, FEATURE="Избранный"
), then the string is translated. However, we get a problem with Publish & Feature
. File joomla.ini already uses similar keys. We can take them from there (JFEATURE
, JUNFEATURE
, etc).
If we try to edit a transition (even for which there is an actual translation), the English title will pull up in the title.
In addition, if we create an article, then in the status field we will face the fact that the transitions will remain untranslated.
One way or another, this will raise questions from ordinary users. This needs fixing.
Labels |
Added:
No Code Attached Yet
|
//cc @bembelimen
Spam posts deleted.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-09-01 02:47:37 |
Closed_By | ⇒ | bembelimen |
In the same SQL file, a key is set for the title of the stage that works.