Mike Rockett

Members
  • Content Count

    1,329
  • 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,099 Excellent

About Mike Rockett

  • Rank
    Hero Member
  • Birthday 03/07/1991

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mike Rockett

    @cb2004 – https://jumplinks.rockett.pw/features/smart-wildcards.html – you'll probably want to use {segments} or {all} here.
  2. Mike Rockett

    @DarsVaeda – Thanks for bringing that up. I did indeed plan to move it some time back, but then decided to only do it for v2, which, hasn't been under active development of late. I'll try find some time to sort this out on v1 soon. Sorry for the issues caused here. @gr00__ (sorry, not sure why it's not tagging you) – That would likely be due to PW’s htaccess rules, as the error is coming from Apache. As that's where its coming from, you'd need to create a rule that will strip out those characters. Haven't worked with htaccess for a long time now, so not confident that I can assist accurately…
  3. Mike Rockett

    @panx - looks like there might be an encoding issue with the RewriteCond directive there... Not sure how it would have happened, but my best guess would be to type the directives in manually. Also, the second RewriteCond line in that state won't apply to you. You'd likely need a catch-all of sorts to match the different types. I'm not able to test this as I no longer use Apache, but this could work: RewriteCond %{REQUEST_URI} ^\/index\.php [NC] RewriteCond %{QUERY_STRING} ^(.+)$ [NC] RewriteRule ^ /index_php/%1? [R,L] From there, you'd be able to create a jumplink for index_php/reference={reference:segment}&object={object:num}, which could then be directed to reference/{reference}/object/{object}.
  4. Mike Rockett

    @adrian I'd actually assumed that hidden included unpublished (). Will sort the changes out in the coming days (public holiday here today, back to work tomorrow).
  5. Mike Rockett

    @adrian – I see what you're saying now; thought about it the wrong way around. With that said, surely include=hidden is enough?
  6. Mike Rockett

    @mel47 – Hmm, I migrated the site to my newer dev environment, and the issue’s no longer showing up. That said, the Typography package appears to have been updated considerably, so I think it might be an idea to do an upgrade there...
  7. Mike Rockett

    @mel47 – Sorry for the delayed response here. I noticed this is happening on one of my own sites. Will investigate.
  8. Mike Rockett

    Module moved to GitLab: https://gitlab.com/rockettpw/tools/typographer
  9. Mike Rockett

    Module has been moved to GitLab. https://gitlab.com/rockettpw/tools/parsedown-extra-plugin
  10. Mike Rockett

    I've released 1.5.50, now hosted over at GitLab: https://gitlab.com/rockettpw/seo/jumplinks-one This release fixes an issue where calls to sitemap.xml from my sitemap module were being logged as 404s.
  11. Mike Rockett

    @Nick Belane – I've pushed JL 1.5.50, which should resolve the logging issue. I see there was already a check for the other sitemap module, just never accounted for my own after it was released.
  12. Mike Rockett

    @adrian So if I use include=hidden (I won't use all as it includes too much), I also need to exclude anything under admin, which is cool and it works, but it would mean that if a hidden parent would need to be excluded using the sitemap options. With that said, including hidden and unpublished pages will be configurable as a single config option. Root … Hidden Page (would be included by default if the option is enabled, so it would need to be turned off in options) Child 1 (included) Child 2 (included) … Would this be suitable? PS, I had hell with the File Compiler - not sure if anything there has changed of late, but my traits were just not being read properly. Any changes I made didn't take effect, even after clearing the cache. For now, I'm moving everything into the main module file except for the field builder.
  13. Mike Rockett

    Hi guys, super sorry for the delay here. @adrian – Will have a look at this now. Would likely want it to be configurable as well. @Nick Belane – I recall noticing this as well. My initial thinking was to ignore it as the plan was to drop the 404 tab in Jumplinks and replace it with a dedicated module that works side-by-side with Jumplinks v2. That said, I just don't have the time. Haven't even managed to get around to finishing the new Jumplinks. So for the time being, I'm going to see what I can do to have the sitemap ignored from the logger.
  14. Mike Rockett

    @panx Thanks for the report – please could you have a look in your server logs to see what the error is?
  15. Mike Rockett

    @rareyush My apologies for the late response here. Haven't had a chance to look into it yet. What is the domain of the new site? Is it live at the moment? Thinking I'd need to take a look and see what happens - if you could provide some more info. Thanks!