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
Or, even better, they should actually be merged to my GitHub username, which is the last one. That possible?

Ok, here you go: http://modules.processwire.com/authors/mikerockett/

I am pretty sure you just have those two modules, correct?

I have deleted the account author except for "mike", just in case it wasn't you.

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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...