Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Could you please increase your WP Memory limit to 256M? 128M is the minimum required by WPML.
Your current values are:
PHP Memory Limit 1024M
WP Memory Limit 40M
Add this code to your wp-config.php to increase WP memory:
define('WP_MEMORY_LIMIT', '256M');
Paste it just before:
/ That's all, stop editing! Happy blogging. /
Now, verify the current settings at WPML > Support > WordPress. Then complete the translation again.
These settings can be limited directly by your hosting provider, so I recommend you contact and ask them to modify them directly.
If you can get even higher values It would be great.
https://wpml.org/home/minimum-requirements/
Note: WPML needs a minimum WP Memory limit of 128M to work only under a minimal environment, which means, with a default theme and no other plugins installed.
If this will still not solve the issue, please let us know.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
Can you please try to run the following SQL command to get those stuck jobs removed from the queue and give you access to the translation queue again?
❌ IMPORTANT: Please backup your database and website before proceeding ❌
UPDATE `wp_icl_translation_status` SET `status` = 10 WHERE `status` = 1;
UPDATE `wp_icl_translation_status` SET `status` = 10 WHERE `status` = 2;
UPDATE `wp_icl_translation_status` SET `status` = 10 WHERE `status` = 9;
After running those commands, please try to send the pages/posts for translation again and check if it is working as expected.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
I'm glad to know that working on the language pairs fixed that issue.
Regarding your previous reply, for some glitch in the system, a (few) translation(s) got stuck and didn't have its status properly updated. The SQL you ran only resets the status of the stuck translation jobs, but it doesn't cause any data loss.
It is pretty rare for it to happen, it is highly likely that you won't face this issue ever again. If it reocurs, we can investigate it, looking for the culprit of the issue. But it should be fixed by now.
Regarding the issue with the untranslated strings, can you please go to WPML -> String Translation, enable the option "Look for strings while pages are rendered" at the bottom of the screen and see if when this option is enabled, the issue still happens?
If the strings are displayed properly with that option enabled, you can go ahead and disable it and try the following steps to try to fix it:
- Make sure you have Woocommerce Multilingual enabled on your website
- Go to WPML > Theme and plugin localization
- Check the "Automatically load the theme's .mo file using 'load_textdomain'" box
- Add the textdomain (probably "woocommerce") of these strings to "Enter textdomain" field then save
- Scroll down and scan the theme and woocommerce plugin
- Go to WPML > Support > Troubleshooting
- Click on "Show custom MO Files Pre-generation dialog box"
- Refresh the page (It should display the MO files dialog box)
- Regenerate the MO Files
If it still doesn't work, you can try to remove one of the strings in WPML -> String Translation, eg.: "Change address", temporarily re-enable the option "Look for strings while pages are rendered" and open that page in the front end where the strings are located. This will cause the string to be reinserted into String Translation. Translate it now and check if it gets the issue fixed.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello,
You mentioned that you're working locally, do you have a staging version that I can access to debug this?
If so, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
If the access to the site is not possible, I'd like your help creating a package of your website and sending it to us.
Please use the plugin Duplicator(hidden link) to create a full copy of your website so we can take a look at it and see what's causing the issues you're experiecing.
If you come across problems while creating it, please feel free to ignore(exclude from the backup) both uploads and cache folders.
I'm also enabling the proper field for your to share this copy, you'll see it on your next response.
Alternatively, you may use any file sharing service that you prefer and share the link in the ticket(your next response is being marked as private, only you and I have access to it).
Please, let me know if you need any additional details.
Thanks!
The topic ‘[Closed] Error loading translation queue – Uncaught DivisionByZeroError’ is closed to new replies.
