Timeline for Retrofitting languages into English-based Install
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2017 at 8:06 | comment | added | ErikH - CiviCooP | Hi Justin, I have no idea, never dealt with the issue myself. I would indeed re-install. I agree it is a very roundabout way and I look forward to your community contribution to improve it :-) | |
| Feb 2, 2017 at 5:30 | comment | added | Justin | So to move forward I need to...backup my files and DB > deactivate and delete the CiviCRM plugin from WordPress > place CiviCRM files with language files back in the plugin folder on the server > reinstall CiviCRM, choosing the local language during the install? Sorry if I'm being dense, but this just seems like a very roundabout way of getting CiviCRM to recognize that there are new .mo and sql files in the system. | |
| Feb 1, 2017 at 16:50 | comment | added | ErikH - CiviCooP | Exactly :-), or translate the workflow message templates manually. | |
| Feb 1, 2017 at 12:36 | comment | added | Justin | Hi ErikH - sorry for the lack of specificity. I understand that I don't need to make a site multi-lingual, and could use it in a single language, whether that be English or another language. I did install the language files, in both the l10n and sql folders (siteroot/wp-content/uploads/plugins/civicrm/civicrm/l10n and .../civicrm/sql). However, doing so fails to update the system workflow message templates into the new language I've added, which is what I'm after. I assume that this is the precise reason most folks seem to recommend installing the foreign language at the start. | |
| Jan 31, 2017 at 9:48 | history | answered | ErikH - CiviCooP | CC BY-SA 3.0 |