veerap

1) https://polylang.pro/doc/multilingual-custom-post-types-and-taxonomies/

2) I don’t understand the question… Maybe your menu isn’t translated? https://polylang.pro/doc/create-menus/

Just “shortcodes” is pretty broad concept since their functionality could be build in custom theme or plugin and have some queries which requires language detection. First you should figure out where the shortcode comes and then check out if it has support for multilingual use.

Build-In shortcodes in WordPress core doesn’t care what language are you using since they are pretty simple https://codex.www.ads-software.com/Shortcode#Built-In_and_Additional_Shortcodes

https://polylang.pro/polylang-for-woocommerce/

That doesn’t make sense, you should translate the content with Polylang instead trying to fetch it from main language.

No, you cannot do this with Polylang alone.

You could example
1. Modify your body_class to detect active language https://developer.www.ads-software.com/reference/functions/body_class/
2. Then target your font-family change to Japanese body class with CSS

1) Did you actually migrated Polylang to WPML? https://wpml.org/documentation/related-projects/migrate-polylang-wpml/

2) Try to debug your site to see if there’s some errors when Polylang is deactivated https://codex.www.ads-software.com/Debugging_in_WordPress

1. You don’t need to translate media
If you don’t need to translate the title, alternative text and the description, deactivate the Media module in Polylang settings

Go in Languages > Settings > Media module

deactivate the Media

https://polylang.pro/doc/working-with-media/

4. Subdomains name and domains in Polylang: https://polylang.pro/doc/url-modifications/

All your subdomains (or domains) must point to the same directory (where the WordPress index.php is present). Polylang checks if your domains or subdomains are correctly accessible. Otherwise, Polylang returns an error message.

1. https://polylang.pro/doc/define-your-home-page-as-a-static-page/

2. Yes you can use anchor links. They just needs to be more specific like: /en/#about

You can migrate the site if there’s nothing you need to preserve in new server. Example with All-in-One WP Migration

Hmm, that’s strange! Maybe some other plugin is messing up the front page logic? Have you followed the instructions found here: https://www.ads-software.com/support/topic/please-read-before-posting-21/?

Especially these:

* Update WordPress, your theme, Polylang and all other plugins to the latest version.
* Deactivate your other plugins and switch to the default WordPress theme. If the problem persists, open a thread, if not, figure out which plugin is the cause of the problem and open a thread mentioning both plugins.

Quick fix: maybe you can use String Translation for widgets here?
https://polylang.pro/doc/strings-translation/

Sounds that theme uses deprecated function for counting widgets
https://developer.www.ads-software.com/reference/functions/wp_get_sidebars_widgets/

Should this be your front page in primary language: https://www.olvasttegels.be/home/ ?

If so, seems that you don’t have static front page set & your “blog” page is not translated to EN => Set the static front page in Settings -> Reading.

If you are using pretty permalinks, paged pages should be https://www.voltaia.com/page/2

format
(string) (optional) Used for Pagination structure. The default value is ‘?page=%#%’, If using pretty permalinks this would be ‘/page/%#%’, where the ‘%#%’ is replaced by the page number.
Default: ‘?page=%#%’

https://codex.www.ads-software.com/Function_Reference/paginate_links

Check your URL modifications in Language -> Settings https://polylang.pro/doc/url-modifications/