Pods plugin issue. Custom post-type relationships and files are showing the translation.
Solution:
The Pods plugin is not officially compatible with WPML. We have a few reported compatibilities issues. In this specific case, the user shared the way he was able to solve this issue. Please read it here.
Problem: The client is experiencing an issue with the Houzez theme where the property counter on the search results page is not working correctly. The counter is including properties from all languages, not just the current language, leading to incorrect counts displayed in the autocomplete search results.
Solution: We have identified a problem in the Houzez theme code and are providing a hotfix. We also recommend contacting the theme author to ensure the fix is included in the next theme update. Here are the steps to apply the hotfix:
If you want to start over with translating your website, you can remove the secondary languages and existing translations from your site and then do a WPML reset.
This removes all WPML-related data and tables from the database.
The Layout section created with Avada can't be translated
Solution:
To translate the Avada layout section you need to make sure first that the layout is created for all languages, so please try the following steps:
1- Go to Avada > Layouts
2- Switch the language to "All languages" from the admin bar
3- Create the layout in all languages
4- Create the layout section in all languages
5- When translating the content of the layout that was created with the Avada builder, make sure not to use the translation editor. So just switch to the secondary language and create the translation content.
Problem: The client wanted one page to display in a right-to-left (RTL) format and another page to display in a left-to-right (LTR) format.
Solution: We explained that text direction is controlled by CSS, and it is the theme's CSS files that determine whether a page is displayed RTL or LTR. We reviewed the client's site and confirmed that the pages were displaying in the correct directions. We also asked the client to verify the source code of the RTL page, which correctly included
dir="rtl" lang="he-IL"
, indicating that the RTL direction was set up correctly.
If you're experiencing similar issues with text direction on your multilingual site, we recommend checking your theme's CSS files for the correct text direction settings. Additionally, you can verify the source code of your pages to ensure that the
dir
attribute is set correctly for RTL or LTR languages.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
Problem: The client is trying to translate the Shipping Methods into other languages but cannot find the strings in WPML String Translation. Solution: We recommend clicking on the blue button to scan for strings that are not yet registered for translation. Once the scan is complete, search for the strings again. If found, select the strings and add them to String Translation following the steps outlined in our documentation: Finding strings that don’t appear on the String Translation page.
If this solution does not seem relevant to your issue, please open a new support ticket in our support forum.
Problem: The client encountered a 'Critical error' on their website while a page was open in the browser. The error was related to the WPML plugin and was caused by a missing auto-increment on a primary key in one of the database tables. Solution: We recommend checking the ICL tables manually to ensure that they all have at least one primary key and that they are set to auto-increment. This also applies to the
wp_options
,
wp_post
, and
wp_postmeta
tables, which should all have a primary key with auto-increment. If you're experiencing this issue, please verify these database table configurations.
Problem:
How can I change the default language of existing products, from English to Ukrainian?
Solution:
- Backup database
- Go to the edit screen of the product (original language)
- Change the language using the Language switcher at the top admin bar to Ukrainian
- On the right sidebar, select "none" at "This is a translation of" and save
- Now, on the right sidebar, "This is a translation of" select back original language page.
- Popup will appear asking you if you wish to change the default language of the product.
- Confirm by selecting checkbox and Assing.
Solution:
Please contact your hosting provider and ask them to whitelist the following:
- wpml.org
- cdn.wpml.org
- api.wpml.org
If you still have issues:
Make sure that the PHP cURL extension is currently configured and updated on your server. In doubt, contact your hosting service so they can update the cURL extension to the latest version and they will also need to allow SSLV3.
Problem:
I am trying to:
Add a translation to a post/page.
1. Write the post title and content for a new post.
2. Click Save Draft or Publish.
3. Add a translation to that post.
4. Click the plus icon on language.
5. WordPress opens the translation page
6. Write the title and content.
7. Press Save Draft or Publish.
I expected to see:
Draft saved or post published.
Instead, I got:
Updating failed. You are probably offline.
- - -
I added a screenshot with the console log. It seems that WPML can't connect with the REST API and it fails. GET shows the REST url, but it's missing a slash.
Problem:
I just purchased WPML and I get the following error only when the 'WPML String Translation' plugin is activated.
Warning: ftp_fget() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
When I deactivate the 'WPML String Translation' plugin the error goes away.
This error will occur on the published website and also when I edit a webpage within WordPress. Any ideas what is causing this? I literally just installed WPML and I'm using the Avada WordPress theme which is said to be 100% compatible.
**EDIT**
I resolved the first error by increasing the Memory Limit to 256M. I am still getting the second error:
Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /wp-admin/includes/class-wp-filesystem-ftpext.php on line 560
Solution:
I found the solution to the issue. The owner of the core wordpress files was set to my personal user. I changed this permission to be apache and everything seems to be working.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
