[Resolved] a few issues

Hi

1. Translation of About Us
You needed to introduce a small change (extra blank space) into the body of the post in order for it to show up in the Trnaslation Editor (TE)
I did this for you and you can now see that it appears in the TE. Any small change is accepted...I introduced an extra "blank" at the end of a sentence for example.

However, the content-boxes are pagebuilder elements that are custom and not currently recognised by the Translation Editor.

I tried to add them using the WPML -> Trasnlation Management -> Custom XML Configuration tabl according to this documentation:
https://wpml.org/documentation/support/wpml-integration-with-page-builders-that-use-shortcodes/

However it did not work. I also noticed that you are using quite an old copy of Visual Composer, so you might try upgrading it to the most recent version.

In any case, if the shortocde for content-blocks is not supported, then you can translate the page manually following this documentation:
https://wpml.org/documentation/translating-your-contents/page-builders/translating-content-created-with-page-builders-using-manual-translation/

2. The footer menu
It is strange that you are not seeing the translation options for the menu. I think this is a compatilbity issue with one of your plugins or theme. I have seen this behaviour before with the Swift Framework.

Please open another ticket for this issue so we can look more closely at it.

3. To translate Widgets and Plugins you will be needing String Translation module
Have you read this documentation?
https://wpml.org/documentation/getting-started-guide/theme-localization/

Specifically for Widgets, if you have problems, you can always try the 3rd party plugin:
WPML WIdgets
Here is also some documetnation about widgets specficially:
https://wpml.org/documentation/getting-started-guide/translating-widgets/

4. Location URL
If you try changing your URL format from "Language by parameter" to " A different directory per language" in WPMl -> Languages ->Language URL Format

Does it make a difference in the behaviour?

IMportant: be sure to resave your permalinks after changing the URL format by going to Settings-> Permalinks and selecting the "Save changes" button (you don´t have to actually make any changes).

Thanks.

Hello

1. Content Boxes
You can translate these content boxes if you switch to the native wordpress editor and translate them within the translated page/Visual Composer builder. (see image).

Othewise, if you are asking how to delete the Content Boxes, you need only switch to the Visual Composer editor in your editor view and delete them (see image). You would need to do the same to the translation though....so why not just translate them manually?

2. Menu Dot
You are not "missing" the menu dot, it is being placed to the left of the menu items instead of to the "right".

If you compare with the appearance in the English footer menu, you will see that the logic is to list the first menu item, and then each following menu item is started with a dot (ie.dot to the Left). This gives the effect of placing dots between menu items.

In your RTL styling, this dot placement is not having the same effect. It does follow same logic, however. It prints the first menu item, and then prints each subsequent item with a dot placed to the "Left" (instead of the right) The effect is that the 3 dots are there, but not placed correctly to give same effect.

You need to approach your theme author/support for this styling issue.

3. URL
You are using the wrong URL format.
You wrote the hebrew link as :
hidden link

When it should be
hidden link

3. I am confused about your question.
To clarify the way things are working, I have inlucded temporarily a Language Switcher to the footer of your theme. You can remove it if you wish after reading my response.

If you visit the English: hidden link
and hover over the Hebrew language flag, you will see that the translated link is having the language directory added to the permalink base.

This is following the rules that you set for the URL Format in WPML-> Languages

The image you posted is the Hebrew translation of the taxonomy term "HaCarmel Market".
This is a taxonomy label. It does not really have it´s own link apart from the slug associated with it.

The permalink base will use URL format you configured (e.g. with the /he/ added) and append it to the taxonomy term slug. This full URL will open the archive page for any listings that are tagged with this taxonomy term.

I hope by explaining how things work, I might have answered the question you posed which I could not really understand.