WPML String Translation is attempting to write .mo files with translations

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing an error after setting up the WPML plugin, indicating that the WPML String Translation is unable to write .mo files to the /wp-content/languages folder because it is not writable, even after changing the permissions to 755.
Solution:
In this case the issue was solved by changing the permission of folders /wp-content/language and its existing subfolder to 777.
1. We recommend using File Manager or FTP access to ensure that the /wp-content/languages folder and any subfolders are marked as "Writable".
2. If the issue persists, contact the hosting support to check if there are any server-side limitations regarding file permissions. More about file permissions in WordPress can be found here: WordPress File Permissions Documentation.
3. Create a subfolder named /wp-content/languages/wpml on the server, as WPML uses this for custom .mo files.
4. After creating the subfolder, generate the custom language files via the dialog at the top section of the WPML > Theme & Plugin-Localization page.

If these steps do not resolve the issue or if the solution does not seem relevant, please open a new support ticket with us for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Not WPML issue

This topic contains 1 reply, has 2 voices.

Last updated by Andreas W. 1 year, 7 months ago.

Assisted by: Andreas W..

Author	Posts
November 8, 2023 at 10:55 am #14755311
shahrukhA	Tell us what you are trying to do? Well, I just set up the wpml plugin - uploaded the plugin files directly into the wp-content/plugins folder. and I started getting an error, "WPML String Translation is attempting to write .mo files with translations to folder: /opt/bitnami/wordpress/wp-content/languages This folder appears to be not writable. This is blocking translation for strings from appearing on the site. To resolve this, please contact your hosting company and request that they make that folder writable." I tried to change the permission of the language folder to 755. It still does not work. Can you try helping me and resolving this issue keeping in mind the security of the site - because I can not change the permission of wp-content folder to 755. Is there any documentation that you are following? I tried following the issues that are already resolved but it didn't work. like reseting the wpml plugin etc What is the link to your site? hidden link
November 8, 2023 at 11:22 pm #14761439
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, We do not really have any influence on the server or hosting package and the file permission of more a general WordPress topic, rather than a WPML issue. The file permissions 755 means that the owner has full access (read, write, and execute permissions), and the remaining users have only read and execute rights. Did you try to use the File Manager or FTP access and simply make sure to mark the folder and any existing subfolders as "Writable"? --- If this will still not solve the issue, could you please ask your hosting support if there are any limitations on their side? More about file permission in WordPress: https://developer.wordpress.org/advanced-administration/server/file-permissions/ --- Further, what you could try to do is create the folder /wp-content/languages/wpml on your server. This is the subfolder, that WPML will use for its custom .mo-files. Once the folder is created, please try to create the custom language files, by using the dialog on the top section of the page WPML > Theme & Plugin-Localization. If any further assistance will be needed, please let us know and I will be glad to have a look at the site as admin, if you agree. Best regards Andreas
November 10, 2023 at 5:25 am #14772261
shahrukhA	I did change the permission of language and its existing subfolder to 777 and the error disappeared.