Mike Rockett

I'm no longer maintaining any of my modules. If someone wants to take them over, let me know. It's been a long time since I first asked, but nobody has reached out.

@Peter Knight — if someone could fully take it over (along with any other modules that matter), that'd be the most ideal scenario. Imo, forking may as well be a new project… Larger PRs are a no-go I'm afraid, unless someone is willing to fully test them, in which case they may as well take a leap and become maintainer 🙃.

Thanks for raising this, however I'm not maintaining Jumplinks anymore. It has been up for grabs for a while now, and nobody has expressed an interest in taking it over. I would consider the module archived at this point. I am open to a merge request to resolve any lingering issues, but am not prepared to spend development time on the module.

@adrian – I've released 1.5.64 which adds the safety net around CLI usage (as a general rule) and request_uri. Please let me know if that solves it.

Guessing this should do the trick…?

@adrian The only thing I can think of is an upgrade to PHP 8.1, as that's the only thing that can cause it. I guess I'd need to find a way to have the module not do anything when being executed via the CLI...

Hi @adrian – very odd as $_SERVER['REQUEST_URI'] should never be null. Perhaps something is unsetting it? Imo, Jumplinks should actually be throwing a hard exception in this case.

Thanks – completely forgot about the info.json file. Bumping to 1.5.63 to remedy it.

@DV-JF Thanks for reporting. 1.5.62 released with fixes. Please test and let me know if all's good.

Version 2 of this module has been published. It now has support for Composer (via composer-installers). PW >= 3.0 and PHP >= 7.4 is now required. Dependencies updated. Please let me know if you bump into any issues.

Thanks @gornycreative I'll see if I can get a new version published this weekend.

Hi all, I've released 0.9.0, which brings the minimum PHP version to 7.4, adds support for PHP 8, and adds support for Composer 2. Also released 0.9.1 which handles @gebeer's suggestion (thanks!). Note, however, that I've published these versions on a hunch that they will be ok – I do not have a PW setup for testing. If something is broken, let me know and I'll fix it.

Hi guys, I'm afraid I don't have the time to maintain this module, and would prefer if someone took it over, along with Jumplinks. The simple reality is that I don't do website development anymore and, by extension, don't use PW anymore, and so I feel it best that these modules be handed over to someone who is active with PW and would be happy to take them over. If you'd like to do so, please drop me a DM and we can take it from there.

Hey @adrian — surely it should be working as it's a recursive method-call that uses canBeIncluded to determine whether or not the template has access? I looked very briefly and that's the way I'm seeing it. On another note: wow, I have not looked at my modules in a looong time ?

@patman Not sure how that's possible. The module simply hooks onto PWs page not found event to display the sitemap at that path. Not sure if something has changed in PW itself that might cause this to happen, or perhaps another module is somehow conflicting. Is anyone else experiencing this?