I'm working on a multipage experience, and am using folders with multiple pages within.
In the widget description I'm told that the folder should provide a drop-down menu that allow the top level to be clicked without changing the page. But that only seem to work when clicking the arrow next to the heading.
When clicking the text (or anywhere besides the arrow), the home page is shown (as well as the drop down menu).
I vaguely remember being able to work around this by duplicating the page set as "home page", then removing it. But now I can not have an experience that does not have a home page?
This is not the actual app, but I hope that it let you see my point. Whenever clicking the heading - and not the arrow - the homepage is beeing presented.
Solved! Go to Solution.
The specific issue, when clicking on the Folder and then it redirects to the home page incorrectly, has been fixed in the last dev edition release (1.2).
If you are using the AGOL environment, the fix will get synced in the next release.
Thank you David Martinez
While you at it, I would like to propose:
Thanks for bringing these up.
I tried in our development environment and cannot reproduce the behavior you mentioned; then I tried the AGOL environment, still cannot reproduce:
Tried to open your shared app in the builder but it has errors. May I ask - when did this app was originally created? It seems like there are some old codes in this app causing the unexpected behaviors.
Hi Tonghui Ming
Thanks for looking into this.
I just recreated my problem in a new experience (AGOL).
The folder should .
It makes no sense just to have this function on the arrow alone. People are used to have the whole "button" - text and icon - as a header/menu. Not just the small icon/arrow?
Tried too record the issue.
If I want to go from page 2 to page 3 (in Folder 2), I don't want to be sent to homepage when clicking the header "Folder 2".
Or am I using the folder/page setup the wrong way?
I hope that you get what I'm getting at.
Sorry for the delay and thank you for providing the details. I am able to reproduce what you've been seeing.
I logged an issue for it and we will take a look at it soon.