[Extension issue] Wrong page path generated by TreeMenu / Tree View

[christiaan]

WWB is a phantastic web design application and Paplo's support is lightning fast.
Thank you Pablo for your strong efforts to keep WWB always state of the art.


I do WWB design on a complete different level so this issue to both extensions " TreeMenu " and " Tree View " is a little bit tricky to describe - but I do my best. The sample project is linked at the bottom of this post.

This Issue in one sencentce: Both extensions " TreeMenu " and " Tree View " do have an (very special) issue in generating the correct path to a project page.


Ok, let's go in details:
The project has the following structure (which can't be changed, so no work around is possible):




" pageInFolderA " has got one text item and one TreeMenu item (extension " TreeMenu "):




The TreeMenu item has got one entry - link to the page in folder B (internal web page link):







" pageInFolderB " has got one text item and pageInFolderA as *embedded* page (the yellow layer below is for understandability reason only):




Sample Project:
http://www.filedropper.com/treemenu


Now generate " pageInFolderB ".

As an expected result " pageInFolderB " should contain a link to itself,
but the generated path to " pageInFolderB " is missing the " commonFolder " entry
so clicking on the link end up with an error page.

Code: Select all

file:///C:/Users/LENOVO~1/AppData/Local/Temp/preview/folderB/START-HERE_pageInFolderB.html

The reason for this may be that the extensions " TreeMenu " and " Tree View " are using a different page selection than e. g. "embedded page " does:




Sample Project:
http://www.filedropper.com/treemenu

[Pablo]

This is expected behavior.

The master page / embedded page must be in the same folder as the page that is using it.
The reason for this is that all links are relative to the location of embedded page. Because there is only one instance of the menu which is the same for all pages (because that is the purpose of the embedded page in the first place).

Note that applies to all menus/navigation and it is documented in the help.

See also the notes in this tutorial:
https://www.wysiwygwebbuilder.com/embedded_page.html

Alternatively, you can use absolute paths instead of internal links.

[christiaan]

Lightning fast response, thank you Pablo.

But doing the same using a CSS Menu item (instead of a TreeMenu / Tree View item) *does* work.

Sample project *with* CSS Menu:
http://www.filedropper.com/treemenucss


But CSS Menu uses a *different* page selection than TreeMenu / Tree View does:


CSS Menu page selection:





TreeMenu / Tree View page selection:




Sample project *with* CSS Menu:
http://www.filedropper.com/treemenucss

[Pablo]

That is because the CSS menu is built-in so it can do some extra checks. However, even then it may not always work. That is why the note about this is in the documentation.
Extensions are separate applications which do not know where they are placed inside the project.