Hi,

In our translation, we are unable to find the word "topic" that appears when modlog__action_split is used, so we can translate it. I am afraid this word might be hardcoded. Please avise.

Cheers,

Gabe.

This is the "topic" language string.

@Daniel F Can you please provide the exact language key? All language strings containing "topic" are translated here, hence me opening this topic.

The language key 'topic' defaults to "Topic" (with a capitalized "T") and it is translated in our install, so it isn't this key.

mysql> SELECT * FROM core_sys_lang_words WHERE word_key='topic' AND lang_id='2';
+---------+---------+----------+----------+--------------+-------------+----------------------+---------------------+---------+-------------+-------------+------------+----------------+
| word_id | lang_id | word_app | word_key | word_default | word_custom | word_default_version | word_custom_version | word_js | word_export | word_plugin | word_theme | word_is_custom |
+---------+---------+----------+----------+--------------+-------------+----------------------+---------------------+---------+-------------+-------------+------------+----------------+
|   18630 |       2 | forums   | topic    | Topic        | Tópico      | 101016               | 101024              |       0 |           1 |        NULL |       NULL |                |
+---------+---------+----------+----------+--------------+-------------+----------------------+---------------------+---------+-------------+-------------+------------+----------------+
1 row in set (0.00 sec)

Cheers.

Edited December 19, 20213 yr by Gabriel Torres

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

This uses the definite and indefinite article translations. '__defart_topic' and '__indefart_topic'

@Andy Millne Both of these keys are translated here, yet it is shown in English in the context presented in the first post. You should take a look into this, it is a bug.

Thanks for the update, I have reopened the report.

This issue has been resolved in 4.6.10 beta 1. Feel free to give this a try, or await the full release if you prefer