Hello there

Thanks for contacting with us. I have attched two screenshots for top1 and top2 positions.

https://prnt.sc/KbJz2jzL0FOS - top 1

https://prnt.sc/IidcJRiSz8At - top2 Did you place any other thing on top 1 and top 2 positions?

-Regards

no nothing. got the idea when you create categories for the languages and add articles as normal it works better then creating categories and articles in SPPB

Hello Robert

I placed the language switcher module for multilingual site. And it works fine. Can you give me a screenshot of your issue for better understanding.

-Regards

it is local build, i will address it later when the site is on a live server. i can place it on other locations like the menu or other custom positions but it remains invisible on top 1 and top 2. Those locations are programmed in the predefined headers.

Hello Robert

I am waiting for your feedback, then.

-Regards

Hi, it's online now. As you can see it's now placed above the content. It must be in the top row. When I remove the social icons in top 1 in the pre defined header it won't work also.

Can you please take a look? Why the language switcher always gives such a hard time to publish it using SPPB? Due the pre defined header?

Hello Robert

Thanks for sharing the informations. Please allow us some time. We are checking the issue and will get back to you soon.

-Regards

Hello Robert

All pre-defined headers does not allow modules in top1 and top2 positions. In fact, some does not publish modules in the positions. For example: You can check pre-defined header style Top Bar. Here language switcher or any other module can be placed in top1 or top2 positions.

It is not a good idea to use the pre-defined header module positions. Please take a custom header and then place the language switcher wherver you want. Please follow this documentation

Best regards

Yeah, already had the idea it won't work properly in the pre defined headers. maybe an idea to add that option into consideration since it's an important feature in webdesign.

I agree, dear friend. But this will create conflicts if we allow modules there. People can use any modules and not all gonna look good. This is why we have kept the option to create a custom header. I hope you understand our thought behind this. This strict pre-defined headers are for those who does not experiment much.