Skip Navigation

Home › Support › English Support › [Resolved] String Translation is attempting to write .mo files with translations to folder

[Resolved] String Translation is attempting to write .mo files with translations to folder

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.

This topic contains 4 replies, has 2 voices.

Last updated by sipsik 1 year, 10 months ago.

Assisted by: Bobby.

Author Posts
February 10, 2023 at 6:19 pm #13009155

sipsik

I'm getting the error message: WPML String Translation is attempting to write .mo files with translations to folder:
/home/ts1kkel/public_html/wordpress/wp-content/languages

This folder appears to be not writable. This is blocking translation for strings from appearing on the site.

The permissions of the folder are 777 but the error message does not disappear.

Also, as of a few hours ago, there is a white screen of death on the homepage hidden link

I have not made any changes to the website in a couple of days and this error appeared only a few hours ago.

I have tried to deactivate all plugins and reactivate them but the error does not disappear nor does the website come alive again.

screencapture-renditsikkel-ee-wordpress-2023-02-10-20_11_42.png
February 10, 2023 at 8:53 pm #13009777

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hello,

I would need to see the detail of the error. You can see how to enable debug logging here:
https://wpml.org/documentation/support/debugging-wpml/

Go in your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:
define('WP_DEBUG', true);

Edit your wp-config.php file and add these lines, just before it says 'stop editing here':

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . 'https://cdn.wpml.org/error_log.txt');

This will create an error_log.txt file in your site's root directory. Please send me its contents.
February 11, 2023 at 5:20 am #13011183

sipsik

Hello,

Here is the content of the error log created today.

Deprecated: Return type of SkyVerge\WooCommerce\PluginFramework\v5_5_0\SV_WC_DateTime::getTimestamp() should either be compatible with DateTime::getTimestamp(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-content/plugins/jilt-for-woocommerce/lib/skyverge/woocommerce/compatibility/class-sv-wc-datetime.php on line 85

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: Return type of ElementorPro\Core\Database\Model_Base::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-content/plugins/elementor-pro/core/database/model-base.php on line 135

Deprecated: Return type of ElementorPro\Core\Utils\Collection::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ts1kkel/public_html/wordpress/wp-content/plugins/elementor-pro/core/utils/collection.php on line 75

Deprecated: Hook elementor/widgets/widgets_registered is deprecated since version 3.5.0! Use elementor/widgets/register instead. in /home/ts1kkel/public_html/wordpress/wp-includes/functions.php on line 5758

Deprecated: Function Elementor\Widgets_Manager::register_widget_type is deprecated since version 3.5.0! Use register instead. in /home/ts1kkel/public_html/wordpress/wp-includes/functions.php on line 5383

Deprecated: Automatic conversion of false to array is deprecated in /home/ts1kkel/public_html/wordpress/wp-content/plugins/woocommerce-direct-checkout/includes/view/frontend/general.php on line 29

Deprecated: Automatic conversion of false to array is deprecated in /home/ts1kkel/public_html/wordpress/wp-content/plugins/woocommerce-direct-checkout/includes/view/frontend/general.php on line 29

Here is the content of the error log that was created a few days ago.

[05-Feb-2023 06:38:53 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 227
[05-Feb-2023 06:38:53 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[05-Feb-2023 06:38:54 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 227
[05-Feb-2023 06:38:54 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[05-Feb-2023 06:38:58 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 1
[05-Feb-2023 06:38:58 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[05-Feb-2023 06:40:21 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 81920 bytes) in /home/ts1kkel/public_html/wordpress/wp-includes/option.php on line 672
[06-Feb-2023 06:38:49 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 81920 bytes) in /home/ts1kkel/public_html/wordpress/wp-includes/option.php on line 672
[07-Feb-2023 06:38:47 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 81920 bytes) in /home/ts1kkel/public_html/wordpress/wp-includes/option.php on line 672
[08-Feb-2023 06:38:53 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 81920 bytes) in /home/ts1kkel/public_html/wordpress/wp-includes/option.php on line 672
[09-Feb-2023 06:38:12 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 227
[09-Feb-2023 06:38:12 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[09-Feb-2023 06:38:12 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 227
[09-Feb-2023 06:38:12 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[09-Feb-2023 06:38:16 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /home/ts1kkel/public_html/wordpress/wp-content/plugins/sitepress-multilingual-cms/inc/utilities/wpml-languages.class.php on line 1
[09-Feb-2023 06:38:16 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[09-Feb-2023 06:39:25 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/rmccue/requests/library/Requests/IRI.php on line 1060
[09-Feb-2023 06:39:25 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/php-cli-tools/lib/cli/Colors.php on line 1
[10-Feb-2023 06:38:30 UTC] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 81920 bytes) in /home/ts1kkel/public_html/wordpress/wp-includes/option.php on line 672
February 13, 2023 at 7:09 pm #13024027

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Thank you!

I am not seeing any errors related to WPML other than the following:
PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes)

however, your site's memory should be plenty as it's at 500M. Did you upgrade the memory after this error?

I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)

**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **

I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.

NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.

Thank you,
Bobby
February 14, 2023 at 8:10 am #13027067

sipsik

My issue is resolved now. Thank you!

The issue was on the server side. They updated their system which caused PHP problems.

Thank you for your assistance!