Hello Al

Sorry for the late response. Our team is cut in half due to Covid-19 infections, so our response times are longer than usual. Thank you for your patience!

I'm not sure that I understand what you're trying to do here. Can you please explain in a bit more detail? Why would you need to translate URLs in Amelia? 

Hi again Al

Amelia doesn't have any links nor is it supposed to be used in an iframe. The shortcode for the booking form is placed on a page, and that page provides the link you use for the iframe, so if you need to pass a link, the link is of the page where Amelia's form is.

Weglot translates static strings, if I'm not mistaken, and Amelia has quite a lot of dynamic strings, and I'm not sure that this plugin will be able to translate everything correctly.

Hello again Al

Sorry for the late response. I'll try to explain the approach as best as I can.

Amelia has its translations in ../wp-content/plugins/ameliabooking/languages/ folder. In there, there are currently 27 folders with translations. English, Arabic, French, Turkish, Russian, Chinese (Traditional), and Spanish are already in there, but they are not 100% translated.

When you open Loco Translate, under Plugins find Amelia. You should see this:

When you click on "Edit" below a language, verify that the file and the directory is writable by going into "File Info" tab:

There, you should see if the folder is correct also, so in the example above - if I'm editing French, I can see that the folder is /plugins/ameliabooking/languages/fr_FT/wpamelia-fr_FR.po - so that's good.

When you edit the strings with Loco Translate, they are automatically saved in the correct file, and can be immediately used in the plugin.

Amelia picks up only one language by default (the language you set WordPress to). So, if you set "English (US)" to be the default language of the site, it will be English on all pages. At this point, you need to add languages in Amelia's General Settings:

On the front-end - when you include all these languages with PolyLang, the plugin sets the locale of the front-end to be in a particular language. For example, you have the booking page in English, so Amelia is in English. Then, you translate that page into French with PolyLang, and when you switch to French from the front-end, the locale of that page is no longer English, but French. Since you added French as an additional language in Amelia, it will use the locale of the page fr_FR and translate Amelia into French.

Please note that the locales are different. As you can see in the image above, French can have locales for Belgium, Canada, and France, and they are different. So, since Amelia has French (France) installed, if you add a language in Polylang to be French (Canada), it will not work, because there's no translation for that locale.

Notification templates are not automatically translated, so you have to do that manually. When you land on Amelia/Notifications page, you see templates in English, and if that's the default language of the site (in WordPress' General settings), that's how it's supposed to be. In the top right corner, above the template, you can switch to a different language, so if you're translating to French, change the language first, and then translate into French:

Please note that if you're using Grammarly, Language Tool, or some other grammar checker (browser extension), you won't be able to save translations, so that needs to be disabled. Check out the attached article about this issue:

Disappearing Notification Templates

Dynamic strings (service names, location names, and so on) cannot be translated by multi-lingual plugins, but instead you need to translate them manually. So, when you go to Amelia/Services, and open a service, you'll see the "Translate" button:

When you click on it, it opens a new modal, where you can translate the name of the service into other languages. Again, on the front-end, when the language is changed, the translation is picked up and the service name is translated into that language using the string you've added.

Please let us know if you have any further questions.

Hello again Al

I don't see that you actually translated any of the pages into other languages. For example, the "Book Now" page only had English, so I added French translation:

And, when I take a look at the preview from Elementor of that page, in French - the booking form is in French. You would still need to translate the remainder of the page, though, but Amelia picks up the language correctly:

So, it uses the French locale for existing strings. Custom fields, Category names, the description, and all other dynamic strings need to be translated manually through Amelia. For example, the name of the category:

You haven't translated these, nor have you added pages in these languages. So, the plugin picks up the translated static strings, but names, descriptions, custom fields, etc. need to be translated manually through Amelia, not Polylang, Weglot, Loco Translate, or any other language tool. Those tools are used only for static strings.

Hiding the price in the employee panel is not currently possible, because the entire section with appointment info is one div, and it can't be properly removed without it affecting other segments of the panel. Our developers will work on this in the future, but I can't provide you with an ETA on that.