Page 2 of 3
Re: WonderCMS 3.5.0 released
Posted: Tue Mar 25, 2025 9:14 pm
by NorfolkGreg
Is yours a fresh install or an upgrade?
Have you done anything other than login into your site?
Re: WonderCMS 3.5.0 released
Posted: Wed Mar 26, 2025 3:54 pm
by NorfolkGreg
NorfolkGreg wrote: Tue Mar 25, 2025 9:14 pm
Is yours a fresh install or an upgrade?
Have you done anything other than login into your site?
A further thought...
I believe that some hosting services get suspicious about the "Phone Home" feature in Wcms that checks whether there are updates available and my block, or at least delay, the call to
https://wondercms.com
It's possible that you have run into this. Hopefully if you try again later you will find the themes and plugin have become available.
Re: WonderCMS 3.5.0 released
Posted: Wed Mar 26, 2025 4:14 pm
by wiz
viewtopic.php?t=3995
Similar issue was resolved here.
Also Greg, will check the menus when I have some spare time.
Re: WonderCMS 3.5.0 released
Posted: Thu Mar 27, 2025 8:08 am
by Nightwanderer
Two different servers. Different locations, different PHP versions, different certificates and certification authorities. Clean installation. The result is the same. Maybe because
https://raw.githubusercontent.com/Wonde ... files/main gives Invalid request?
Re: WonderCMS 3.5.0 released
Posted: Thu Mar 27, 2025 9:28 am
by wiz
https://raw.githubusercontent.com/Wonde ... -list.json
If you check the full paths instead of /main, you will see the files are fetched/displayed.
I cannot reproduce the issue also on different hosts and older PHP version along with a new one.
It does seem like you might have an issue with either a missing certificate or an invalid one (seeing you have them, I’m not sure why they don’t work for you).
1. Do you have cURL enabled?
2. Did you possibly check out:
https://stackoverflow.com/questions/298 ... 6#48488736 ?
3. Any errors in the logs?
Re: WonderCMS 3.5.0 released
Posted: Thu Mar 27, 2025 4:11 pm
by Nightwanderer
Yes. It was all about the curl certificate. Thanks for the answers.
Re: WonderCMS 3.5.0 released
Posted: Thu Mar 27, 2025 9:27 pm
by wiz
Most welcome, enjoy WonderCMS:)
Re: WonderCMS 3.5.0 released
Posted: Sun Mar 30, 2025 4:33 pm
by wiz
NorfolkGreg wrote: Sat Mar 22, 2025 11:03 am
I've just looked again at the standard navigation code generated for
https://gregchapman.uk The list item I am concerned about is this:
Code: Select all
<li class="nav-item subpage-nav">
<a class="nav-link" href="https://gregchapman.uk/games/">Games</a>
<ul class="subPageDropdown">
<li class="nav-item ">
<a class="nav-link" href="https://gregchapman.uk/games/board/">Board</a>
</li>
<li class="nav-item ">
<a class="nav-link" href="https://gregchapman.uk/games/table/">Table</a>
</li>
</ul>
</li>
It's just Line 2 that I'm looking to change to:
Code: Select all
<button class="nav-link">Games</button>
I can then use a CSS first-child selector to style the second (now <button>) line to appear like other menu items and open the child drop-down list <ul class="subPageDropdown"> on hover (on a desktop) or tap (on a phone).
I see your suggested code includes a reference to "top level" but I would want any list item of class "subpage-nav" to replace a link with button code, so sub-pages could cascade almost indefinitely.
Does that make sense?
Hi Greg, if you want for example:
Code: Select all
<a class="nav-link" href="https://gregchapman.uk/games/">Games</a>
to be replaced with a button, wouldn't the Games then not be a link anymore?
1. If you see the following example, this time no JS is used. However button will still lead to the correct URL.
2. Replace your default theme.php with the new one:
Code: Select all
<?php
// Define the helper function outside of the listener to avoid redeclaration
function hasVisibleSubpages($item) {
foreach ($item->subpages as $subpage) {
if ($subpage->visibility === 'show') {
return true;
}
}
return false;
}
global $Wcms;
$Wcms->addListener('renderPageNavMenuItem', function ($args) use ($Wcms) {
// Ensure we have the required arguments
list($output, $item, $parentSlug, $visibleSubpage) = array_pad($args, 4, null);
// Check if this item has visible subpages
$hasVisibleSubpages = hasVisibleSubpages($item);
// If the item has subpages, create a button for the parent item (still a link)
$navTag = $hasVisibleSubpages
? '<a class="nav-link" href="' . $Wcms->url($parentSlug) . '"><button class="nav-link-button">' . $item->name . '</button></a>'
: '<a class="nav-link" href="' . $Wcms->url($parentSlug) . '">' . $item->name . '</a>';
// Create the main list item
$output = '<li class="nav-item ' . ($Wcms->currentPage === $item->slug ? 'active ' : '') . ($hasVisibleSubpages ? 'subpage-nav' : '') . '">'
. $navTag;
// Render subpages only if there are visible ones
if ($hasVisibleSubpages) {
$output .= '<ul class="subPageDropdown">';
foreach ($item->subpages as $subpage) {
if ($subpage->visibility === 'hide') {
continue;
}
// If the subpage has its own visible subpages, treat it as a button
$subpageHasVisibleSubpages = hasVisibleSubpages($subpage);
// If the subpage has visible subpages, make it a button
$subpageSlug = $parentSlug . '/' . $subpage->slug;
$subpageTag = $subpageHasVisibleSubpages
? '<a class="nav-link" href="' . $Wcms->url($subpageSlug) . '"><button class="nav-link-button">' . $subpage->name . '</button></a>'
: '<a class="nav-link" href="' . $Wcms->url($subpageSlug) . '">' . $subpage->name . '</a>';
$output .= '<li class="nav-item ' . ($subpageHasVisibleSubpages ? 'subpage-nav' : '') . '">'
. $subpageTag
. '</li>';
// If the subpage has its own visible subpages, render them
if ($subpageHasVisibleSubpages) {
$output .= '<ul class="subPageDropdown">';
foreach ($subpage->subpages as $subsubpage) {
if ($subsubpage->visibility === 'hide') {
continue;
}
$subsubpageSlug = $subpageSlug . '/' . $subsubpage->slug;
$output .= '<li class="nav-item">'
. '<a class="nav-link" href="' . $Wcms->url($subsubpageSlug) . '">' . $subsubpage->name . '</a>'
. '</li>';
}
$output .= '</ul>';
}
}
$output .= '</ul>';
}
$output .= '</li>';
return [$output];
});
?>
<!DOCTYPE html>
<html lang="<?= $Wcms->getSiteLanguage() ?>">
<head>
<!-- Encoding, browser compatibility, viewport -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<!-- Search Engine Optimization (SEO) -->
<meta name="title" content="<?= $Wcms->get('config', 'siteTitle') ?> - <?= $Wcms->page('title') ?>" >
<meta name="description" content="<?= $Wcms->page('description') ?>">
<meta name="keywords" content="<?= $Wcms->page('keywords') ?>">
<meta property="og:url" content="<?= $this->url() ?>" >
<meta property="og:type" content="website" >
<meta property="og:site_name" content="<?= $Wcms->get('config', 'siteTitle') ?>" >
<link href="https://fonts.googleapis.com/css?family=Boogaloo|McLaren" rel="stylesheet">
<meta property="og:title" content="<?= $Wcms->page('title') ?>" >
<!-- Website and page title -->
<title>
<?= $Wcms->get('config', 'siteTitle') ?> - <?= $Wcms->page('title') ?>
</title>
<!-- Admin CSS -->
<?= $Wcms->css() ?>
<!-- Theme CSS -->
<link rel="stylesheet" rel="preload" as="style" href="<?= $Wcms->asset('css/style.css') ?>">
</head>
<body>
<div id="wrapper">
<!-- Admin settings panel and alerts -->
<?= $Wcms->settings() ?>
<?= $Wcms->alerts() ?>
<header>
<h1>
<em><?= $Wcms->get('config', 'siteTitle') ?></em><br>
<?= $Wcms->page('title') ?>
</h1>
<h2><?= $Wcms->page('description') ?></h2>
</header>
<section id="topMenu">
<div class="inner">
<!-- Hamburger icon -->
<input id="menuControl" type="checkbox">
<label for="menuControl"></label>
<nav>
<ul class="menu">
<!-- Menu -->
<?= $Wcms->menu() ?>
</ul>
</nav>
</div>
</section>
<section class="main">
<?= $Wcms->page('content') ?>
</section>
<footer>
<?= $Wcms->footer() ?>
</footer>
</div>
<!-- Admin JavaScript. More JS libraries can be added below -->
<?= $Wcms->js() ?>
<script>
function check() {
document.getElementById("menuControl").checked = true;
}
</script>
</body>
</html>
3. Add CSS for styling the button (bottom of your style.css - this still might need some tweaks according to your liking)
Code: Select all
/* Style buttons in the menu to match navigation items */
nav .nav-item button {
background-color: transparent;
border: none;
cursor: pointer;
font-weight: bold;
color: var(--menutext);
font-size: 1em;
padding: 0;
}
5. With this solution, all pages with subpage-nav are buttons and look like this. And no JS is used
- Screenshot 2025-03-30 at 18.22.52.png (24.64 KiB) Viewed 728001 times
Re: WonderCMS 3.5.0 released
Posted: Sun Mar 30, 2025 10:20 pm
by NorfolkGreg
wiz wrote: Sun Mar 30, 2025 4:33 pm
Hi Greg, if you want for example:
Code: Select all
<a class="nav-link" href="https://gregchapman.uk/games/">Games</a>
to be replaced with a button, wouldn't the Games then not be a link anymore?
That's right and that's what's needed if you want a drop down menu to work on a touch screen device.
I'm prepared to be told I'm missing something but this is what I find (with my limited HTML and CSS coding knowledge.)
With the default code a tap on GAMES menu option opens the Games page. The dropdown never opens so there is no opportunity to pick one of the sub-pages. Tap and Hold over GAMES and and the dropdown does appear but it's hidden under the context menu which overlays it. You then need to tap somewhere off the context menu to clear it before being able to pick a sub-page.
You're right, changing GAMES to a button, will lose it as a link. Instead it becomes a heading that, with the appropriate CSS, will open the dropdown and allow you to select the sub-pages.
Yes, it is possible, with rather more complicated HTML and appropriate CSS, to create a menu that would allow you to tap on GAMES that would both open the dropdown and activate a link on the GAMES option. However, I thought that would add a lot more complication to the code needed in the function that would be more difficult to document and explain in the Wcms docs. (BTW: I like how you've moved it away from the GitHub interface that I think many potential users find too technical to use.)
I'll play with the code you suggest over the next few days and see how I get on, but I hope the above better indicates what I was thinking.
Re: WonderCMS 3.5.0 released
Posted: Mon Mar 31, 2025 7:42 am
by wiz
NorfolkGreg wrote: Sun Mar 30, 2025 10:20 pm
wiz wrote: Sun Mar 30, 2025 4:33 pm
Hi Greg, if you want for example:
Code: Select all
<a class="nav-link" href="https://gregchapman.uk/games/">Games</a>
to be replaced with a button, wouldn't the Games then not be a link anymore?
That's right and that's what's needed if you want a drop down menu to work on a touch screen device.
I'm prepared to be told I'm missing something but this is what I find (with my limited HTML and CSS coding knowledge.)
With the default code a tap on GAMES menu option opens the Games page. The dropdown never opens so there is no opportunity to pick one of the sub-pages. Tap and Hold over GAMES and and the dropdown does appear but it's hidden under the context menu which overlays it. You then need to tap somewhere off the context menu to clear it before being able to pick a sub-page.
You're right, changing GAMES to a button, will lose it as a link. Instead it becomes a heading that, with the appropriate CSS, will open the dropdown and allow you to select the sub-pages.
Yes, it is possible, with rather more complicated HTML and appropriate CSS, to create a menu that would allow you to tap on GAMES that would both open the dropdown and activate a link on the GAMES option. However, I thought that would add a lot more complication to the code needed in the function that would be more difficult to document and explain in the Wcms docs. (BTW: I like how you've moved it away from the GitHub interface that I think many potential users find too technical to use.)
I'll play with the code you suggest over the next few days and see how I get on, but I hope the above better indicates what I was thinking.
With the current solution I posted, this works as expected. On mobile dropdown is opened, if the user clicks it again, it opens the parent page.
Example:
1. When user clicks drop down (in my case "How to"), it opens the drop down on mobile without opening "How to" page.
2. If user clicks on same "How to" while the drop down is opened again, it opens "How to", since the drop down is already expanded.
Here's a video of how it works:
https://streamable.com/mri67r (expires in 2 days)