FuzzyBot: Updating to match new version of source page

2026-04-21T19:41:03Z

Updating to match new version of source page

← Older revision		Revision as of 21:41, 21 April 2026
Line 41:		Line 41:
	# Check the ID (if it's the 1st : ID is 1) and use it for next instruction		# Check the ID (if it's the 1st : ID is 1) and use it for next instruction
	# Create the related translation : <code>INSERT INTO lime_message (id, language, translation) VALUES ('1', 'fr', 'Valider'); </code>		# Create the related translation : <code>INSERT INTO lime_message (id, language, translation) VALUES ('1', 'fr', 'Valider'); </code>

			==Please Note==
			The <code>category</code> field in <code>lime_source_message</code> must be an empty string (`''`), not <code>NULL</code>. If the category does not match exactly, <code>gT()</code> will not find the source message, and your translation will not be applied. This is especially important when adding translations for theme-specific strings.

FuzzyBot: Updating to match new version of source page

2024-05-23T08:22:16Z

Updating to match new version of source page

New page

<languages />
=Introduction=

Since LimeSurvey 5.4.0 you can have your own translation for all strings in all included languages with direct access to your database.

This system can be used if an existing translation is not compatible with your business needs.

It should be reserved for specific cases, since text modifications in the heart of LimeSurvey will again require a modification of your database.

Furthermore, you can use this method for translating Survey Theme specific strings.

=How database translations works=

For database translations, LimeSurvey uses a method inspired by [https://www.yiiframework.com/doc/api/1.1/CDbMessageSource CDbMessageSource] from the Yii framework.

# find the string in SourceMessage table lime_source_message->message, get the id : lime_source_message->id
# if exists, find the related translation in Message table lime_message->translation for current language lime_message->language with current id lime_message->id

LimeSurvey creates the array with translations from po file (see [[Translating LimeSurvey]] for information how to update this file), and afterwards merges it with all translations from the database.

Then the translations from the database are always returned if they exist.

=Sample for “Submit” button in English and French=

You want to show _Validate_ and not _Submit_ for the submit button in all of your surveys (with a specific theme). If you just update the theme and replace gT('Submit') by gT('Validate') : it always shows _Validate_ in all languages.

==For all surveys with all themes==

# Create the source message <code>INSERT INTO lime_source_message (id, category, message) VALUES (NULL, NULL, 'Submit');</code>
# Check the ID (if it's the 1st : ID is 1) and use it for next instruction
# Create the related translation : <code>INSERT INTO lime_message (id, language, translation) VALUES ('1', 'en', 'Validate'), ('1', 'fr', 'Valider'); </code>

==Using your own theme (recommended solution)==

This method uses a solution with your own template, it updates the default string for all other languages as well.

# In [[Theme editor]] select the Navigation part
# Search for <code>{{ gT("Submit") }}</code> (in navigator.twig)
# Replace by <code>{{ gT("Validate") }}</code>
# Create the source message <code>INSERT INTO lime_source_message (id, category, message) VALUES (NULL, NULL, 'Validate');</code>
# Check the ID (if it's the 1st : ID is 1) and use it for next instruction
# Create the related translation : <code>INSERT INTO lime_message (id, language, translation) VALUES ('1', 'fr', 'Valider'); </code>

Custom translation/en - Revision history

FuzzyBot: Updating to match new version of source page

FuzzyBot: Updating to match new version of source page