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 teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if anyone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put, I've been using MSN (...) for a number of years, and it's been great – but there have been some smallish issues with it, particularly with the markup generation part, and it's also doing some things in a way that just doesn't work for me – the xtemplates thing being one of these. In many ways it's less about features, and more about style.
      In MarkupMenu I've tried to correct these little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and PHP 7.1+, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) on my todo list.
      One smallish and rather specific difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site has a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to omit that 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...