Jump to content

Recommended Posts

Hi Guys, 

For some reason I cannot get JumpLinks 404 monitor to work, everything else is working and the CMS notifications show 404's but JumpLinks is not displaying the list of received 404's

Anyone have an idea why this could be? 

I am running PW 2.6.1

Interesting... I just tested on 2.6.17 (one of my local testing installs) and it really isn't logging 404s... Let me have a quick look.

Share this post


Link to post
Share on other sites

I have found the issue. If there are no Jumplinks registered scanAndRedirect simply returns false, which lands up skipping the process of logging the request.

I have now fixed the issue both on master and dev. Will get Module Directory to see the update shortly.

Thanks for the heads-up!

Share this post


Link to post
Share on other sites

@Mike Rockett, 

After updating, I get this error:

Parse error: syntax error, unexpected ''alphanum'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in /modules/ProcessJumplinks/ProcessJumplinks.module on line 92

Share this post


Link to post
Share on other sites

@Mike Rockett, 

After updating, I get this error:

Parse error: syntax error, unexpected ''alphanum'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in /modules/ProcessJumplinks/ProcessJumplinks.module on line 92

Sorry about that - accidential input appeared on that line when attempting a grep. Issue has been resolved - please replace Jumplinks.module with the one from Github.

  • Like 1

Share this post


Link to post
Share on other sites

Have just bumped the dev branch up to 1.3.4, bringing several important updates to be merged with master soon.
 
Firstly, and most importantly: In light of PW 2.7 being around the corner, the minimum PW version requirement is now 2.6.1. This allows the use of 2.6 goodies that were not used before. Mainly, Jumplinks now uses ModuleConfig.
 
Next, the Entity Editor (the name used for the jumplinks editor page) is now working as expected. PageListSelect and PageAutocomplete are now syncing correctly. This is really just a visual gimmick for the purposes of consistency. The editor now looks much cleaner, and easier to use.

post-2289-0-72635100-1444321983_thumb.pn

post-2289-0-99146600-1444321988_thumb.pn
 
Few other changes to note:

  • Table font size has been increased a notch.
  • Destination column now has page title and full path hint for jumplinks that reference existing pages.
  • Table footer has been removed - I don't think this was very informative, and thus not needed.

Please note that I have not tested everything extensively as yet - this will be done soon. As such, don't use this branch on a production site until merged with master.
 
Once merged, I'll bump the version up to 1.5, considering the major changes/departures compared to the current 1.3.x.

  • Like 1

Share this post


Link to post
Share on other sites

Hi there,

Is JumpLinks activated when a page is accessed via $pages->get($url)?

I have some code calling a page using $pages->get() and the "old" url. The get() is returning a null page. The jumplink works if I access the page with the "old" URL in the browser address bar.

Any advice appreciated! :)

Many thanks.

Share this post


Link to post
Share on other sites

Hi there,

Is JumpLinks activated when a page is accessed via $pages->get($url)?

I have some code calling a page using $pages->get() and the "old" url. The get() is returning a null page. The jumplink works if I access the page with the "old" URL in the browser address bar.

Any advice appreciated! :)

Many thanks.

Hi Gazley,

No, it only hooks to ProcessWire's 404 event, which fires only on HTTP requests that do not resolve to a Page.

Were the old URIs from another CMS, or did you move pages around in an existing PW installation?

Edited by Mike Rockett
  • Like 1

Share this post


Link to post
Share on other sites

I am using Jumplinks for one of my clients. We have set up a number of redirects to monitor several campaigns we have in place. For instance, we have links like this:

http://website.com/bioh

that redirect to actual pages in the site:

http://website.com/biohealth/

The original link is being used in Google AdWords. AdWords is adding a Google Click Identifier (gclid) to the url, so when a user clicks on the link, it actually appears like this when they visit the site:

http://website.com/bioh?gclid=CPaHlL3_jckCFdc9gQod4xEB4g

The problem is that the link with the gclid parameter is returning a 404 error. Jumplinks doesn't appear to recognize when a parameter is appended to the url.

Is there a way to prevent this, or perhaps I didn't set something up correctly? Any advice is appreciated. I'm using Jumplinks 1.3.1 with ProcessWire 2.6.1.

Share this post


Link to post
Share on other sites

@lance O. Also make sure you have the template setup to allow URL segments and remove the back slash. Especially if your using landing pages. 

Share this post


Link to post
Share on other sites

It looks like setting up the Source URL with the additional code works. (It doesn't look like we need to add the additional code to the page url.)

Thank you for your quick response! Client is happy and has restored faith in PW and Jumplinks. :-)

  • Like 1

Share this post


Link to post
Share on other sites

@ Lance O. - No problem! I love Jumplinks and have used ProcessWire for tons of client projects! 

Have faith in it!

  • Like 1

Share this post


Link to post
Share on other sites

I am using Jumplinks for one of my clients. We have set up a number of redirects to monitor several campaigns we have in place. For instance, we have links like this:

http://website.com/bioh

that redirect to actual pages in the site:

http://website.com/biohealth/

The original link is being used in Google AdWords. AdWords is adding a Google Click Identifier (gclid) to the url, so when a user clicks on the link, it actually appears like this when they visit the site:

http://website.com/bioh?gclid=CPaHlL3_jckCFdc9gQod4xEB4g

The problem is that the link with the gclid parameter is returning a 404 error. Jumplinks doesn't appear to recognize when a parameter is appended to the url.

Is there a way to prevent this, or perhaps I didn't set something up correctly? Any advice is appreciated. I'm using Jumplinks 1.3.1 with ProcessWire 2.6.1.

Just as a follow-up on this:

In a private discussion with Jeff last month, I noted that this scenario will be accomodated in the next version. However, if there are more Jumplinks users bumping into this issue, then I would want to make it part of 1.5.

In the discussion, I mentioned there would either be a checkbox in the entity editor that allows you to make query strings optional, or that we could use square parenthises to mark them as optional, like this: bioh[?gclid={token:any}].

After a little thought on the matter, I think it may be better to use the checkbox approach for query strings. However, I think the behaviour should be somewhat different in that it would let you choose to "ignore the query string in source" and, if that is selected, "append original query string to destination".

Thoughts?

In light of the square parenthises idea, I also have plans to make parameters optional, like so: {?title}

  • Like 1

Share this post


Link to post
Share on other sites

Hi Mike, 

I think the checkbox would be a great addition.

This would make it easier for a newbie to Jumplinks be able to just dive in and get things done.  

I am for this update!

  • Like 2

Share this post


Link to post
Share on other sites

@Mike

Thanks for jumplinks. You did a great job. I like it.

I have some small remarks/ questions

  • Why isn't it listet in PW Modules?
  • Why doesn't it have its own support board in PW Forum. ProcessRedirect is another Module. I think its better to have one support board for each module, even if they are related.
  • I would like to have an option to clear the 'HITS'.
EDIT

Just found it in the directory and even the support board: https://processwire.com/talk/topic/8697-jumplinks/

It isn't listet if I select modules by Modulauthor mikerockett

mikerockett or mike-rockett (better to merge)

I strongly recommend to unravel Support Board for ProcessJumplinks and ProcessRedirect. Maybe this post could be moved to Jumplinks Support Board too. (Hello Pete?)

Hi kixe,

Hehe, glad you found it. :)

I would like to have an option to clear the 'HITS'.

> I will be adding that option to v1.5.

It isn't listet if I select modules by Modulauthor mikerockett

mikerockett or mike-rockett (better to merge)

> Thanks for picking that up - not sure why that happened. Hoping an admin can pop in and assist with that...

:)

Share this post


Link to post
Share on other sites
Thanks for picking that up - not sure why that happened. Hoping an admin can pop in and assist with that...

Hey Mike - looks like you have a lot of aliases in the modules directory. Are all these you? What do you want them all merged to?

post-985-0-08929700-1448565052_thumb.png

Share this post


Link to post
Share on other sites

Hey Mike - looks like you have a lot of aliases in the modules directory. Are all these you? What do you want them all merged to?

attachicon.gifScreen Shot 2015-11-27 at 5.09.24 AM.png

Hey Adrian - yes, please. I guess they should all be merged into the third one, which equates to the named version of my profile display name. Or, even better, they should actually be merged to my GitHub username, which is the last one. That possible?

Thanks.

(Oh, and I'm not sure about the first one - I may have tried to change my display name to just mike at one point, but didn't think it would affect the modules directory...)

Share this post


Link to post
Share on other sites

Dev branch bumped to 1.3.5 with an important fix. compileDestinationUrl was not returning the correct data, which resulted in relative redirects. This issue has now been resolved, and the behaviour is the same as the current stable.

Looking to push to 1.5 soon for stable release - please test... Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Dev branch updated to 1.3.6 adding support for clearing jumplink hits on an individual basis by means of a new checkbox in the jumplink editor.

post-2289-0-34577200-1449582200_thumb.pn

Note that this only clears the counter. The date of the last hit will always be stored.

Everything is looking good at this point. Hoping to push to 1.5 stable in about a week or so - please let me know if you've noticed any issues before I do that.

Thanks.

Share this post


Link to post
Share on other sites

I am trying to implement Jumplinks on a new site but not sure what is happening, the 404 template is not even being fired. I dont think this is a bug with Jumplinks or ProcessWire to be honest, but wondering if any light could be shed on this.

If I go to /example.php, I get a page which just says 'File not found.' and nothing else. If I go to /example then the 404 template is fired. I have setup Jumplinks to try and change /example.php to go to /new-example but it is not kicking in.

Server configuration do you think?

Share this post


Link to post
Share on other sites

How did you add the rule for redirecting example.php, with the leading slash?

From the description:

Enter a URI that's relative to the root of this installation, without the leading slash.

@Mike Rockett

Just used this module for the first time, it's great!! Thanks for your work :)

Cheers

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...