Mike Rockett

Members
  • Content count

    1,306
  • Joined

  • Last visited

  • Days Won

    8

Mike Rockett last won the day on October 22 2017

Mike Rockett had the most liked content!

Community Reputation

1,079 Excellent

About Mike Rockett

  • Rank
    Hero Member
  • Birthday 03/07/1991

Profile Information

  • Gender
    Male
  1. Thanks @Robin S, I'll give that a try.
  2. @rash You're quite right. I did think about it earlier, but not 100% sure how to go about it... Would be awesome if we could do something like find('extends=FieldtypeImage').
  3. I've bumped to 0.4.0 RC3 on the repo.
  4. @rash Great, I figured it might be that. I'll push the change and bump as soon as I can.
  5. @rash, the module checks to see if any image fields are available to your installation. To be more precise, the check is specific to FieldtypeImage, which might be where the problem is coming in... I'm not sure if there are other Image modules that extend FieldtypeImage out there (and if so, if you're using one). On my side though, a fresh install of PW with the latest MarkupSitemap and an image field added in results in the config showing the applicable selector:
  6. Hi @rash -- did you add the image field in via the module's config? This is basically a way to globally add specific image fields in one swoop, and then the exclusion options are available at page-level to override.
  7. No problem, and thanks. I'm going to stick with my original solution as I need it to only be set once... This also gives a level of customisation, which I like. 🙂
  8. @ngrmm - if you're wanting to redirect /old-dir/* to /new/*, then you can use the following: Source: old-dir/{all} Destination: new/{all} {all} is a smart wildcard (https://rockett.pw/jumplinks/smart-wildcards) that equates to {all:all}, which matches anything and everything, until another wildcard or marker. So, /old-dir/child-a/ will be redirected to /new/child-a/. If you need the path after /new/ to be omitted, then just use new/ as the destination, and then /old-dir/child-a/ will redirect to /new/.
  9. In all honesty, I think that Jumplinks is better suited to site migrations. Black holes should either be covered by a specifically-built module, or by htaccess/vhost config...
  10. Thanks Macrura I actually see that I'm going to need to bump PHP Typography to 6.x first, which means I'll land up bumping the module version to 0.5 for a little testing. Looks like there's been a cleanup and some new features added, as well as a bunch of hyphenation languages. Will open an issue for that shortly.
  11. The original roadmap has been closed, in favour of a project board. As already mentioned, I'll be resuming work on Jumplinks in the next few weeks. (Super sorry it's taken so long...)
  12. I'd like to get some general feedback from people using the module. If you have a minute, please share your experiences or issues (even those that are self-resolved, if any). If it's looking stable enough, I'd like to bump to stable v1. If there are issues, please also feel free to let me know. Thanks!
  13. I'd like to get some general feedback from people using the module. If you have a minute, please share your experiences or issues (even those that are self-resolved, if any). If it's looking stable enough, I'd like to bump to stable v1. If there are issues, please also feel free to let me know. Thanks!
  14. I see that another request has come in for resolvable pages to redirect. I can see this adding a little bit of overhead (FastRoute or no), so if I do implement it, it'll probably need to go behind a configuration option that's turned off by default... Haven't devved in PW for a while now, but I'm sure there's a nifty way to get it working (I hook-change based on the config should be good enough). That aside, I'm looking to continue work on this in about two to three weeks. I'll need to bring it over from my old dev environment on Windows/WSL to my MacBook, which has made development a breeze.
  15. Jumplinks doesn't allow that, I'm afraid. It hooks onto the 404 event, so it will only respond to requests that don't resolve. You would need to call $session->redirect() in your template to do a redirect from an existing, published page. If you don't mind my asking, why do you need published pages that redirect to others?