WebsiteBaker Community Forum

WebsiteBaker Support (2.12.x) => General Help & Support => Topic started by: johnbroeckaert on December 22, 2019, 01:45:15 PM

Title: multi languages and base pages
Post by: johnbroeckaert on December 22, 2019, 01:45:15 PM
Hey,
I have a client who wants a website in three different languages (FR-DE-EN). No problem, but a number of pages in all languages should only be displayed in English. On these pages you can click through to the next page of this subject.

I thought it was smart to solve with SectionPicker. That goes well until the next page is clicked through. At that time the menu changes to the language in which the original pages are. I would like to keep it in the language in which the visitor views the website.

Someone a smart solution?
John
Title: Re: multi languages and base pages
Post by: dbs on December 22, 2019, 04:25:07 PM
Hi John, a test with droplets sectionpicker and nextpage results in a expected way.
In every language the droplet nextpage leads you to the real next page of this language.

In DE page a wysiwyg and inside of this the droplet nextpage.
In EN page the sectiopnpicker droplet calls the de wysiwyg section.Is this what you mean?
Title: Re: multi languages and base pages
Post by: johnbroeckaert on December 22, 2019, 06:42:30 PM
Hi DBS,
I try to explain:

In The EN pages i have a WYSIWYG page with descriptions of a product. There is an other page with additional information in EN and this page is not visable in the menu. A "normal" button takes you there.

In the DE page I use the module (not a droplet) SECTIONPICKER to get the EN page in the DE language. So far it works fine. The button on this page takes you to the page with additional info but the main menu is changing at that point to EN instaet DE.

Hope its clear now?
John
Title: Re: multi languages and base pages
Post by: dbs on December 22, 2019, 11:02:26 PM
Ok, understand.
WB does what it should, linking to a english page.

If a popup is an option i have a solution.
In the DE or EN page you click the button and its open a popup with additional Infos as inline html from the EN page.
Tested with colorbox.
Title: Re: multi languages and base pages
Post by: crnogorac081 on December 23, 2019, 08:33:03 AM
Hello,

Maybe to put for additional pages to seccond menu and not in main menu. So you can display only main menu via show_menu2() function.
Title: Re: multi languages and base pages
Post by: johnbroeckaert on December 23, 2019, 10:54:34 AM
@ crnogorac081


Quote
Maybe to put for additional pages to seccond menu and not in main menu. So you can display only main menu via show_menu2() function.
At this moment the second page setting are to menu "NONE". So that is not a solution

@dbs
Code: [Select]
Tested with colorbox.I wil go and test this one. See how it is like..
Keep you informed

John
Title: Re: multi languages and base pages
Post by: CodeALot on December 29, 2019, 10:17:17 PM
Hi DBS,
I try to explain:

In The EN pages i have a WYSIWYG page with descriptions of a product. There is an other page with additional information in EN and this page is not visable in the menu. A "normal" button takes you there.

In the DE page I use the module (not a droplet) SECTIONPICKER to get the EN page in the DE language. So far it works fine. The button on this page takes you to the page with additional info but the main menu is changing at that point to EN instaet DE.

Hope its clear now?
John

John,
 
In a situation like this I would not create a second page with more information.
I would make one English page, with all the information on it, part of information in a hidden DIV that will become visible when the visitor clicks a "read more" or similar link.
 

Then you can pull the information into the other languages using the SectionPicker without having trouble with links to secondary pages.
Title: Re: multi languages and base pages
Post by: dbs on December 29, 2019, 11:53:51 PM
This is what i mean with inline html via colorbox.
Title: Re: multi languages and base pages
Post by: johnbroeckaert on December 30, 2019, 11:35:58 AM
@dbs
The solution with colorbox is working. Could be an option.

@codealot
A hidden div on the orihinal page.... That sounds great too. Advantage is of course that there isn't a pop_up window from colobox. Perhaps the child to tab module is an other solution witch i could consider......

Let you all know
John