codestylist

Yes.

This feature is not missing. You get it with the Pro version.

@zoszko I can not reproduce the issue. I checked it with Edge, FF and Chrome on Windows. Best is tro try it yourselfe using a private browser to make sure you do not have any cookie issue.

This documentation is what you need: https://polylang.wordpress.com/documentation/documentation-for-developers/functions-reference/

Use pll_register_string()

Thank you once more @jonathanstegall for your time and reply.
The hint aobut the JavaScript error was the push to the right solutiuon. I checked the console and there was a JavaScript error with jQuery. So, I deactivated the plugin which occures the error and – magic – the “Add another field mapping” buttons works. And, I could map the fields I needed. Great!
Once more, sorry I have bothered you and thank you for your knowledge.

@katoakira00 You can buy the Pro version. This version creates the media in WordPress in all languages during upload automatically. It saves a lot time, if you have a lot of immages to upload.

Thany you, @jonathanstegall, for your quick reply. I really appriciate this.
Maybe I do not understand how to add fields to the mapping. I understood I have to select a Default Record Type first. If this is not necessary my question is, how do I map fields.
Clicking on the Button Add another field mapping results in nothing. Means, clicking does not start any action.
Maybe I’m totally wrong. Is there a video or documentation where the mapping is described?
At the moment I feel lost and I hope to get your advice to understand how the system works.
Thanks a lot for your effort.

@motopress This is not allowed with the GPDR regulations. It says, a user has to actively confirm a privacy policy. A pre-confirmation by pre-selecting the checkbox is not allowed.
If I would add just a text which refers to the send button it would be the same then pre-selecting the checkbox. A user can always say he/she didn’t read the text.
This is why we need a checkbox.

Great, @dimned . Hope, it will not take too long because, as I described, the contact form is not useable as it is (in Europe), if the site owner will follow the GDPR regulations.

The first issue you have so solve is, your shortcode is not executed. And this is still not Polylang related. Bring it up and running and afterwards you can check the Polylang function further.

No.

First of all, if you hired a WordPress developer and he/she can not help you, you should claim back your money.
To solve this problem you need to know where the strings come from and how they are added to your website. Based on this result you (or somebody else) can fix this.
The way how a text is displayed can be different. So, the solution is also different.

This is not an Polylang related issue. add_shortcode() is a WordPress feature.

Then you should contact the add-on author. As I wrote, Polylang is not compatible with WooCommerce so, you have to ask the developer who added this feature.

Polylang is not compatible with WooCommerce. You need an add-on.