Jump to content

Recommended Posts

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?

A request to example.php should be caught by Jumplinks if the file or page doesn't exist. My dev installation is doing that. As such, there must be something wrong with your configuration.

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

From the description:

@Mike Rockett

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

Cheers

Jumplinks automatically removes the leading slash. :)

And very glad you like it. Will be updating to 1.5 with a few new features soon.

Share this post


Link to post
Share on other sites

After several git conflicts (hey, I'm learning), 1.5 has been merged into master - I believe it is stable for production.

If you notice any bugs (or other like-minded creatures), please either mention here or submit an issue.

:D

  • Like 1

Share this post


Link to post
Share on other sites

Hey, Mike!

I am not sure if this is related to some other things we talked about before, but anyway... With jumplinks site.com/index.php gerts redirected to site.com. But site.com/index.php/something gets redirected to site.com/index.php.pwpj/something with 301 answer code.

Is there a way to make it throw 404 instead?

Share this post


Link to post
Share on other sites

Hey, Mike!

I am not sure if this is related to some other things we talked about before, but anyway... With jumplinks site.com/index.php gerts redirected to site.com. But site.com/index.php/something gets redirected to site.com/index.php.pwpj/something with 301 answer code.

Is there a way to make it throw 404 instead?

Jumplinks is designed to remove the index.php from URLs. As such, when you request /index.php, you'll be redirected to the root of the site. Additionally, it's designed to work with redirects like /index.php/MyOldPage.html by swapping out index.php for index.php.pwpj so it can check. If it doesn't do this, then developers wanting to strip index.php out of their old URLs would not be possible.

That said, this does appear to be a bug (well, more of an oversight on my part), which I will look into as soon as I get the chance. Requests like the one you've made should remain as-is, so that PW may throw a 404.

Thanks for picking that up! :)

  • Like 1

Share this post


Link to post
Share on other sites

Heads up: Per this post, I'm going to be moving the Jumplinks and SimpleForms repos over to their new home on Github. You'll notice there's also a new repo for Jumplinks' documentation - that's because I'm moving it out of the current wiki and into the new site, which will automatically sync with the repo to ensure all is up to date.

This will all happen within the next few hours, once I've figured out all the nitty-gritty's.

:)

Share this post


Link to post
Share on other sites

Hey, Mike!

I am not sure if this is related to some other things we talked about before, but anyway... With jumplinks site.com/index.php gerts redirected to site.com. But site.com/index.php/something gets redirected to site.com/index.php.pwpj/something with 301 answer code.

Is there a way to make it throw 404 instead?

Hey Ivan,

You are quite right about the previous discussion. Requests to /index.php/something will be seen as requests to the home page by processWire, unfortunately.

As such, the only solution I have for this is to create a new setting in the module's configuration that tells Jumplinks to not redirect /index.php requests to the root and not redirect /index.php/* requests to /index.php.pwpj/*.

Sound good to you?

  • Like 1

Share this post


Link to post
Share on other sites

I have gone ahead and add this to the dev branch. There's a new setting in the configuration called "Disable index.php matching", which you can enable to prevent these redirects.

Please review before I merge with master as 1.5.1. Thanks.

Share this post


Link to post
Share on other sites

It's a really nice documentation site - much appreciated.

  • Like 2

Share this post


Link to post
Share on other sites

It's a really nice documentation site - much appreciated.

I'll second that. Nice work on the new .pw domain :)

  • Like 1

Share this post


Link to post
Share on other sites

It's a really nice documentation site - much appreciated.

I'll second that. Nice work on the new .pw domain :)

Thanks guys. :) Yeah, figured I'd make use of the domain - at $2, it feels like a gift. ;)

  • Like 1

Share this post


Link to post
Share on other sites

Actually giving this index.php thing a bit of extra thought. Sites that used such routing were simply not configured to use htaccess, which is default in PW anyway. Surely all index.php/* requests should be stripped of index.php? Right now, the module only redirects index.php with or without the trailing slash. Whereas, if I tell it to strip the index.php out of all requests, such as /index.php/hello -> /hello, then a 404 would be thrown if the resulting destination isn't found.

To me, this makes more sense...

Feedback?

Edit: Also consider the fact that when you request index.php/hello, PW shows the home page... So no automatic 404 there anyway.

Share this post


Link to post
Share on other sites

As I understood you are proposing:

  1. First redirect urls like /index.php/hello to /hello,
  2. Then either let PW manage the routing (if /hallo exists, then just show it)...
  3. ...or rewdirect it with Jumplinks.

So in the module we will have to check option to strip out index.php and then create redirects like /hello -> /new-hallo. Am I getting you right?

Share this post


Link to post
Share on other sites

As I understood you are proposing:

  1. First redirect urls like /index.php/hello to /hello,
  2. Then either let PW manage the routing (if /hallo exists, then just show it)...
  3. ...or rewdirect it with Jumplinks.

So in the module we will have to check option to strip out index.php and then create redirects like /hello -> /new-hallo. Am I getting you right?

Well, I don't actually think there should be an option for it - should just happen automatically, because requesting index.php/hello does not throw a 404 by default. So yes, if you were to request index.php/hello, Jumplinks would redirect it to /hello, which would then be redirected to /new-hello if a jumplink was registered for it.

Share this post


Link to post
Share on other sites

Has anyone using Jumplinks experienced any issues with timestamps when using MySQL 5.7? I use MariaDB, and presently don't have access to MySQL 5.7, and so cannot test. As I understand it, strict mode is enabled by default in 5.7, and strict mode does not allow for zero-based timestamps.

This issue came up in Laravel recently, and the solution was to use the previously disallowed NULL timestamps.

On my end, with MariaDB 10.1.9, all appears to be working quite fine. For those running MySQL 5.7, please do let me know if you encounter any issues. If you do, we'll have to work on a schema update to figure out the best way to target all platforms.

Edit: I see that 5.7.8 reverts changes to be compatible with 5.6 (strict mode on). As 5.7.9 is a general availability release, I don't really see this being a problem. For those that do experience issues, the best bet is to allow zero dates or turn strict mode off (whichever comes first - not entirely sure on how the config there would work).

Share this post


Link to post
Share on other sites

Well, I don't actually think there should be an option for it - should just happen automatically, because requesting index.php/hello does not throw a 404 by default. So yes, if you were to request index.php/hello, Jumplinks would redirect it to /hello, which would then be redirected to /new-hello if a jumplink was registered for it.

Going to go ahead and implement this - I don't see any problems with it. If any come up, we can look at those when they do.

Share this post


Link to post
Share on other sites

Git is starting to irritate me. Something changed when they release Github Desktop, which replaced the old Github for Windows. Before, I could simply merge the dev branch with master, and everything would sync up perfectly. Now, when I do it with Desktop, it creates a new commit called "Merge remote-tracking branch 'refs/remotes/origin/dev'", which means that the dev branch will always be one commit behind master. I made the mistake of merging master back to dev, and it's gone and added another commit, leaving master one commit behind dev.

What on earth? Any way I can undo this mess? Delete dev and re-branch?

Share this post


Link to post
Share on other sites

Merges do (or at least should) always create an commit, but if there's nothing to merge (just new additions) the master branch can be fast-forwarded to the dev branch state without an commit. But most git apps I've used by now do fast-forward automatically if possible.

Share this post


Link to post
Share on other sites

Merges do (or at least should) always create an commit, but if there's nothing to merge (just new additions) the master branch can be fast-forwarded to the dev branch state without an commit. But most git apps I've used by now do fast-forward automatically if possible.

Thought I'd seen that term somewhere. Thing is, Github Desktop no longer fast-forwards, it creates a new commit. I do prefer the fast-forward method, and believe was actually doing it with Git GUI.

I take it there's no way I can revert this?

(Btw: I see that a fast-forward cannot be achieved if master has diverged from dev in a separate commit. However, that doesn't seem to be the case for me. It was an issue at one point, but then I had everything synced up so there was no divergence.)

(And forgive me; I'm not a git guru, so some things obviously baffle me... Getting to the point, however, where I just want to delete the repo and push a fresh one without history.)

Share this post


Link to post
Share on other sites

Hi, I just installed the latest version 1.5.1 on PW devns 3.0.3 (fresh install) and I got this warning

Failed to init module: ProcessJumplinks - SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'last_hit'

Share this post


Link to post
Share on other sites

Hi, I just installed the latest version 1.5.1 on PW devns 3.0.3 (fresh install) and I got this warning

Failed to init module: ProcessJumplinks - SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'last_hit'

Strange... I've just tried the same, and got no errors or warnings. Let me check the schema quickly.

Update: Schema appears to be correct. It first installs the tables, and then performs schema updates to those tables. last_hit is only added once. So, unable to reproduce here.

Share this post


Link to post
Share on other sites

Just a note to everyone, Jumplinks doesn't appear to be compatible with 3.0.3. I had it working on 3.0.1 and 3.0.2, but did not test with 3.0.3.

In the meantime, I'm dropping the PW3 compatibility tag until I am 100% certain everything works.

Scratch that. It is actually working. It was an error that appeared only once, and then disappeared. I believe it has something to do with namespacing or file compilation. Can't be sure as yet.

So support for current devns is there, just prepare yourself for the odd warning or error here and there (though, I don't think there will be many).

Edited by Mike Rockett
  • Like 1

Share this post


Link to post
Share on other sites

Yes I confirm, I uninstalled the module and reinstalled again and the error gone, sorry for that.

  • Like 1

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 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...