[Escalated to WPML Developers team] custom field

Hello,

Here is the link to the test site:

hidden link

Please use this one-click login and install the theme and its core plugin.

Leave me a short notification once the components are installed.

In case you find the time to replicate the issue with a simple example it would be highly appreciated. Otherwise please make sure that I still have access to your site so that I have a reference for recreating the issue.

Best regards
Andreas

Hello,

Please take note again that the issue that you experience on your site only occurs if properties are untranslated and the fallback option is used.

Now, on the sandbox if you go to WPML > Settings you will see that all Custom Post Types form WP Residence are locked and by default set to "Translatable - only show translated contents."

This means that the developers of WP Residence are including a pre-defined configuration for their post types and the fact that they are locked, means that you ar not supposed to change those settings, as you could experience unexpected behaviors.

This means the custom post types from WP Residence appear not to support the fallback options so it would not make much sense to keep replicating the issue, as this is already pre-defined by the author in this way.

Best regards
Andreas

Hello,

Yes, indeed.

It is that we can not report an issue with property posts not working on fallback as expected if the author does actually block this setting - which means he is not supporting it yet.

But you could ask WP Residence if they are planning to support this feature in an upcoming version of their theme/plugin.

In case you run into issues with the translations of the properties, please let me know.

Best regards
Andreas

Hello,

You are welcome!

Take note that the WP Residence Theme is using this setting inside the wpml-config.xml file in their theme:

<custom-types>
<custom-type translate="1">estate_agent</custom-type>
<custom-type translate="0">wpestate_invoice</custom-type>
<custom-type translate="0">membership_package</custom-type>
<custom-type translate="1">estate_property</custom-type>
<custom-type translate="1">estate_developer</custom-type>
<custom-type translate="1">estate_agency</custom-type>
</custom-types>

This means they define that those post types should use those specific settings.

Could you please ask them, if they do this on purpose as the post type would not support a fallback option?

Take note, that I will be glad to escalate this issue internally for you, but I think it would save time if you could first clarify with WP Residence if a fallback option should work with WPML for their post types.

Let us know if you need any further assistance.

Best regards
Andreas

Hello,

Nevermind, I was able to organize a license key already - I will keep you updated.

Best regards
Andreas