mwestrik

Hi Michael,

yes, you have to let wpml search for strings.then, eventually, they will show up in the string translation.

For the label values (which is nothing more then on/off) Estatik told me that it only works with Loco translation. But it would be weird to have to install another translation plugin just for those labels. they already can be translated with wpml though, but in a very unconventional way: add them in one language, save, and then change the language, add them there too, and do that for all languages. They will NOT show up in the translation editors.

I have already asked both wpml and estatik for a solution, if you find one, i’d be happy to hear it!

Update, both WPML and Estatik have declared that the label translation does not work with the WPML trandlation editor, which makes Estatik NOT compatible with WPML.

well, it doesn’t work flawlessly. Fort instance, it takes some effort to get custom field labels translated, they do not automatically appear in string translation, as the field values do.

More importantly, the labels (featured, new, sold etc) can be translated through the taxonomy translation, but the values are NOT translated. I’ve tried translate and copy, and they simply dom’t work. WMP itself is looking into it now, and so far they can’t get it to work either.

Maybe estatik support has a solution?

even with the new version it still doesnt work. it seems to work well when you just fill in one value: min or max, but when you enter a min and a max value, it doesnt work well.

i put in mix: 1000000 and max 2500000, and all properties below 1000000 were shown as well.

Easiest way is to use a child theme and put the changed template files in that child theme.

Just create a folder “estatik” in your child theme and add the files there, in the same folder structure as in the estatik/templates folder.

so to change the pdf style, in the estatik folder of your child theme, you will have to add the property/pdf folders.

Hi,

Thanks for the reply.

I just found out Woo had AGAIN created new pages, which breaks the entire site in all extra languages, as those newly created pages have no translations.

A quick fix would be very welcome!

That is a rather shortsided conclusion. But often seen with developers: everything that goes wrong when interacting with other people’s plugins, themes etc is always the others’ fault…

I suspect the problem to be woocommerce, as wpml of course is not able to create Woocommerce pages. Woo is.

Another reason for that: the problem didn’t happen due to a wpml update, it happened after updating woocommerce.

Therefore the issue is far from resolved, as long as you don’t know the reason it happened, it might happen again with every new update.

I do expect it has something to do with the addition of that new draft page that is created by woocommerce, about the return policy.

I found out it happens to all websites that use wpml translations as well. Stores with just one language, or with (for instance) translatepress are not affected.

Yes, the affected websites were active stores (for some years) with all pages properly set and working well.

do i need to substitute my_output_value with the actual field name? And if so, i assume it is the database field name?

you can do that with any form plugin or even the elementor pro form.

You will have to copy the content-singe.php to your (child)theme.
Then create the form, and then add the shortcode in the content-single.php, almost at the bottom, between the

<?php endif; ?>

and the

<?php do_action( ‘es_property_after_tabs’, $es_property ); ?>

lines.

Use it like this:

<?php echo do_shortcode(‘[YOUR SHORTCODE]’); ?>

It was enabled before installing your plugin. I even had a “default” cover photo for any profile that doesn’t have a custom one. That has disappeared as well.

sent you credentials

btw, can we activate province as well, because that would be great? simply adding “province” doesnt do the job…

ah I see. it doesnt work when there’s another search form somewhere on the page with “country” enabled, but indeed it does work when there is no “country” field on the page.

So that leaves the writing of the states, at least in some local cities in this area, but possibly in other spanish regions as well.

Hi,

Thank you.

I am aware that the “city” field works without country and state, but the “state” field should also work without country. That does not work at the moment.
That is no problem as long as I have a few cities in this state, but as soon as the list of towns and states grows, that filter really is necessary.

There are some more villages nearby that have valencian (Alacant) spellings:
El Verger, Benidoleig, La Nucia for instance.