EDIT: I've changed the subject line to this opening post in the topic as I'm now less clear about the nature of this issue - as you'll read in my reply.
I think this issue (feature?) is general and not related to the GregCustom theme. Please let me know!
Try this: replicate what I have at https://gregchapman.uk under the "Games" option.
That is a page with links to two sub-pages "Table" and "Board", with the two sub-pages visible on the menu system. Then create further sub-pages on both the "Board" and "Table" pages all set invisible on the menu system.
Now try navigating, using the sub-menu buttons, to the either the "Board" or "Table" pages and from there to one of the further sub-pages. You should find all works well.
However, I just discovered that if you open the "Games" page and follow the links to either "Board" or "Table" and from there to one of the multiple sub-pages you find yourself hitting the 404 page.
That's because when navigating via the sub-menu system the links from the "Board" page are in the correct form:
https://yourdomain/games/board/boardgame.html
but if navigating via the links to "Board" or "Table" from the "Games" page the links to the sub-pages appear in the form:
https://yourdomain/games/boardgame.html
A work around is not to have the links on "Games" as pages, but to include a trailing slash (/) to show them as folders (which I have implemented so the problem doesn't show up on the site any longer).
============
All this seems to me to be related to an issue I have been concerned about for some time:
If you create a sub-page and make it visible Wcms generates a menu item for the new sub-page and this normally relies the theme's CSS code to make it appear on hover. Unfortunately, that doesn't work on touch-screens as hover doesn't work when there isn't an independent pointer separate from your finger.
Additionally, Wcms is deliberately designed to retain a link at the item's parent level on the menu, so you need to create content for that page if the page is to be included in the menu, but there are not sufficient tags in the menu code to build CSS code that allows you to work around the lack of hover capability on a touch screen device.
BUG/FEATURE: Navigation?
-
NorfolkGreg
- Posts: 189
- Joined: Wed Sep 01, 2021 7:50 am
Re: BUG/FEATURE: Navigation?
I have now made a further discovery that, while not perfect, does remove most of my concerns about the "Bug" part of this issue, because perhaps everyone else has always operated like this...
Having added the trailing space to the sub-page link I find that on a touch screen the link performs differently. As before, when you tap on GAMES once the menu is open you go straight to the Games page. As before if you tap and hold on GAMES then the sub-page options TABLE and BOARD to appear, but the menu is overlaid with the context menu that would have appeared when right-clicking on a non-touch-screen.
What's new, or new to me since I added the trailing slash in the code, if I tap and slide, rather than tap and hold, I can open the sub-page options without opening the context menu. It's a little unreliable, as it depends on how long I take to lift my finger after I stop moving my finger as sometimes the context menu will appear, but the tap and slide technique works for me 90% of the time.
I'd still like to see additional tags in the default Wcms sub=page code, but I'm slightly less concerned than I always have been about Wcms sites with multi-level menu structures.
Having added the trailing space to the sub-page link I find that on a touch screen the link performs differently. As before, when you tap on GAMES once the menu is open you go straight to the Games page. As before if you tap and hold on GAMES then the sub-page options TABLE and BOARD to appear, but the menu is overlaid with the context menu that would have appeared when right-clicking on a non-touch-screen.
What's new, or new to me since I added the trailing slash in the code, if I tap and slide, rather than tap and hold, I can open the sub-page options without opening the context menu. It's a little unreliable, as it depends on how long I take to lift my finger after I stop moving my finger as sometimes the context menu will appear, but the tap and slide technique works for me 90% of the time.
I'd still like to see additional tags in the default Wcms sub=page code, but I'm slightly less concerned than I always have been about Wcms sites with multi-level menu structures.