Home›Support›English Support›[Resolved] I need helo with Elementor Search Form - I cant see the translated Property Features ( taxonomies)
[Resolved] I need helo with Elementor Search Form - I cant see the translated Property Features ( taxonomies)
This thread is resolved. Here is a description of the problem and solution.
Problem: You are using the Real Homes theme and have created a search form with Elementor. Although you have translated the Property Features taxonomies using WPML, the translated features are not displaying in the Elementor search form, except for one feature that remains untranslated and in English. Solution: We tested the issue by setting up a new test site with the Real Homes theme and its plugins. After translating a property and its taxonomies, we added the "RH: Search Form 2" widget on a translated page. The form displayed all features correctly in the translated language. It appears that the "RH: Search Form 2" widget does allow using Real Homes Templates, which are set up in the Customizer's search settings. If you use such a template, you might run into unexpected issues. We were sadly not able to replicate and investigate this issue, as we would require a license key for Real Homes for this purpose. We recommend using the widget without any templates, in case you run into unexpected issues.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket.
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.
It seems that you dont understand adn we are staying at the same for days now. I cant dublicate 2000 properties in 3-4 languaages and crete 8000 new posts !!!
I just want to find a way to show the additional features in the elementor search forms ONLY THIS!
JUST EXACTLY ASHAPPENS NOW WITH ALL THE OTHER FIELDS ! Like Locations, Property Types, and more, that although the properties are not translated, they do appear just fine !
Each post and term you create in WordPress has a unique ID. Each translated post or term also has a unique ID and is then connected based on active language settings using WPML's database tables.
In your case the posts (properties) are not translated and use the "fallback" settings:
"Translatable - or fallback to site default language if a translation does not exist".
The problem is that the fallback method from WPML displays the original content if a translation does not exist. There is no post ID in a second language, and therefore, the term count for translated taxonomies is zero.
In your form, you currently have translated features, which are expected to have a count of "0" as no properties exist in a second language.
For example, if you view a German property, then the features neither show up translated, which is expected in your current setup: hidden link
Possible workaround:
Delete the "Feature" translation from WPML > Taxonomy Translation and then set the "Features" in WPML > Settings > Taxonomies Translation to use "Translatable - or fallback to site default language if a translation does not exist".
---
If this does not solve the issue, I would like to offer to take a look at the site as admin.
The private reply form is enabled again.
In case you can't provide access to the site, I can offer a WPML Test Site on which you can install the latest version of the theme and its plugins. We can then try to replicate the issue and try to find a solution.
I cant delte the traslation of the Feauted , does not give me a choice like this. see image .
Something might be worng in general. I tried with Chatgpt, to find how i can tranlsate in bulk autotranslate tags ( and yoast titles and meta of the tags). This is what proposed me to send you: "I am experiencing a critical issue with WPML on my site.
When I try to access the main WPML Settings page at:
/wp-admin/admin.php?page=wpml-settings
I receive the message:
"Sorry, you are not allowed to access this page."
Because of this, the Site Translation Mode section does not appear anywhere in the admin area.
I cannot switch to Translate Everything Automatically, and the bulk translate button for taxonomies (Tags, Property Types, Property Features, etc.) is missing.
I can access other WPML pages such as:
WPML → Taxonomy Translation
WPML → Translation Dashboard
WPML → String Translation
WPML → Languages
But the main Settings page is completely inaccessible.
I already tried the following:
Ran all safe actions in WPML → Support → Troubleshooting:
Clear the cache in WPML
Set language information
Fix element type collation
Repair taxonomy relationships
Confirmed that no WPML add-ons are disabled or missing.
Confirmed that my user role is Administrator.
The problem still persists.
It looks like my administrator user lost the capability required to access the main WPML Settings page, or WPML is redirecting incorrectly to the TM settings page (tm/menu/settings).
Can you please check what capability or configuration is blocking access to:
wpml-settings
and help me restore access so I can enable "Translate Everything Automatically" and bulk translate taxonomies?"
I would like to offer to take a closer look and request temporary access (wp-admin and FTP) to the website to investigate the issue further.
Please also provide me exact details about which user account is affected. It might also be recommendable to provide me access to the account on which I can see the issue.
The required fields are located below the comments section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up your website and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and website credentials will be set to "PUBLIC." DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private reply form looks like this: hidden link
Click "I still need assistance" the next time you reply.
Video: hidden link
Please note that we are required to request this information individually on each ticket. We are not permitted to access any credentials that were not specifically submitted on this ticket using the private response form.
This request refers to the custom widget "RH Search Form 2" of the RealHomes Theme on your homepage.
In your case, you translate the Features in WordPress, but not the listings but you are able to display the original listings in all languages using WPML's fallback setting.
You expect Features to display the correct count per language, but if you go to Easy Real Estate > Features and switch the language to French or German, you will see that the translated Features have a count of "0", as there are no translated listings.
This means that the search form is kind of working as expected and displays what is reflected on the backend, but it is not considering WPML's fallback setting for Listings on the Features taxonomy.
Anyhow, if we go to a translated Features archive, we can see results and the fallback for Properties works as expected: hidden link
This means there seems to be a problem with the rendering logic of the Search Form widget, and this is not something that we have direct influence on.
I can offer to investigate and try to suggest a solution, but it is very likely that Real Homes will need to adapt the widget's code to make it consider the fallback for property features, similar to what it does for Property Types, Locations, or Statuses.
This is why it would usually be advisable to report this issue directly to RealHomes.
I can further offer a WPML test site on which you could install the latest version of the RealHomes theme and its plugins. I will then replicate the issue, try to suggest a solution, and escalate to our compatilbity team.
Would this be possible?
---
Sidenote (unrelated to the reported issue):
ACF Field Groups should always be set to "Not translatable".
Translate field groups should be removed.
Can you plese make it clear what this means? " can further offer a WPML test site on which you could install the latest version of the RealHomes theme and its plugins. I will then replicate the issue, try to suggest a solution, and escalate to our compatilbity team.
It is our internal procedure to first replicate issues from scratch in order to confirm that we are handling a general compatibility issue or bug.
The problem is that "RealHomes" is not one of our partners, so we do not have access to the Real Homes Theme and its plugin, which is why I was asking if you could install the latest version of the theme and its plugin on a test site, which I will provide.
Here is the link to the test site.
One-Click-Login: hidden link
Please leave me a comment once the theme and its plugins are installed.
Due to the huge amount of data and files on your site, taking a local copy is sadly not an options, as it would take too much time.
I have downloaded the theme and plugins from your site instead and I am about to set up a local development site on which I will try to replicate the issue and propose a solution.
I downloaded the theme and its plugins from your site and installed them on a new test site. Here, I created a property including taxonomies and translated it.
I then added the "RH: Search Form 2" on a page and translated the page.
The form shows up as translated entirely, including Features. See screenshot.
It might be that the issue is related to the fact that your Search form Widget is using an Elementor Template.
I will continue with testing and keep you updated.
It seems like the "RH: Search Form 2" widget does not support the Elementor Templates.
The only way to use an Elementor Template was by selecting it as a Search Template inside the Customizer's search settings, which works as expected.
Inside the widget itself, I am not obtaining any option to select a template.
Those templates seem to be only available when using the Demo Imports of the theme, which is only possible when having a paid license for the theme.
Do you maybe have an import for those demo contents for further testing?
---
I am sadly not able to pass you a link to my test site, as it runs on localhost. I am still waiting for our systems team to update Sandboxes to PHP 8.3, which will still require a test phase.
If you have the ability to register the theme on another site, would it maybe be possible for you to install it on a staging site, register it, and import the demo content, so that we could use this staging for testing in the meantime?
I am afraid that this is not the solution, as I need to be able to:
- Revise the code of the theme & plugin
- Finding a workaround for fix for the issue by interacting with the code
It is not recommended to take those steps on a production website.
At the moment, it would be very helpful if you could explain to me where the Search Form Template "Property Search, Property to buy in Greece" is coming from.
Is there any place in the backend where I can edit this template? If so, please send me a link, as I can not find the matching template.
