Jump to content


Mike Rockett

Recommended Posts

Well you could place the description right next to the "From" cell content. If it's sufficiently different than the content before it then it should be usable, plus adding text-overflow: ellipsis you can limit the length (plus adding a "title" html tag to see all on hover).


opacity: 0.66;
font-size: 0.92em;
display: inline-block;
font-style: italic;
margin: 0 0 0 1em;
max-width: 200px;
overflow: hidden;
white-space: nowrap;
vertical-align: middle;
text-overflow: ellipsis;

However I would still prefer the full-line descriptions even if the inconsistent look.

A tooltip would be better than nothing but I'm not quite a fond of that.

Link to comment
Share on other sites

2 minutes ago, tpr said:

Darken on hover is a good idea. You could make somehow the descriptions optional too and let the user decide whether he wants the clutter or not :)

When the descriptions are on the bottom, row height becomes inconsistent. On the right, however, the opposite is true, and the clutter is not as bad.

I'm going to play around with this a little. :-)

Link to comment
Share on other sites

Update: Haven't played with it yet - will do so this weekend.

Quick question: I'd like to see very basic analytics of the new module's usage - would anyone be against me installing a basic install/uninstall tracker that communicates with my server? It would literally just send a simple payload containing the domain name and the date on which it was installed or uninstalled. This information would be kept private, but I could potentially put a badge in the documentation to indicate active installs - that's a big maybe though... I would prefer to keep all data 100% private.

Link to comment
Share on other sites

  • 1 month later...

Is it possible to redirect all 404 hits to the homepage? I've just tried ".*" -> "/" and it appends the full url like this:


Tracker: I think most devs wouldn't like this feature but I'm not against it, provided it's OFF by default.

  • Like 1
Link to comment
Share on other sites

9 hours ago, tpr said:

Is it possible to redirect all 404 hits to the homepage? I've just tried ".*" -> "/" and it appends the full url like this:


Tracker: I think most devs wouldn't like this feature but I'm not against it, provided it's OFF by default.

I see - this should definitely be possible (using {all}) and page:1 or a relative/absolute link to your domain root. I will take a look at this when I'm back from work this afternoon.

  • Like 2
Link to comment
Share on other sites

Unfortunately, I'm not able to determine why the httpUrl is being appended to the root URL. I'll need to look into this further, but it has something to do with preg_replace_callback which is at fault here. The method in question is supposed iterate through each source wildcard, applying any replacements to the destination. But as their are no wildcards in the destination, it should be changing anything. When you supply / as your destination, Jumplinks converts this to page:1 so it can get the full URL to that page. As it loops over the source, it's somehow adding that URL twice to the destination.

I need to head out now, but will be back in a bit to investigate.

I do know that Jumplinks 2 is not succeptible to this as it uses a completely different method, powered by FastRoute. I'll try to continue work on that Jumplinks 2 today. (To everyone who's been waiting in anticipation for it, I'm so sorry it's taken so long.)

  • Like 1
Link to comment
Share on other sites

Hi @Mike Rockett, this module is awesome, thanks!

I have this collection thing going on:

example source: project?id=1&foo=bar

So I set it up like this:
source: project?id={id}&foo=bar
dest: projects/{id|projects}


But, when &foo=bar is omitted this does not work:

How to make anything after id optional, I tried brackets, but it does not work.

source: project?id={id}[anything here, but optional]


Link to comment
Share on other sites

@owzim - Thanks. Jumplinks v1 doesn't support explicit optional trailing parts, so you'll need to create a separate jumplink for now if you want to capture foo=bar. However, if it doesn't matter what needs to trail the first parameter, then you can simply use project?id={id}{all} and leave the destination as-is.

v2 will support this. You'll be able to wrap the optional part in square brackets and Jumplinks will add the optional part to the end of the destination if it appears in the source, and it'll also ensure the URL is structured properly. In other words, you'll be able to set it up like this:

Source: project?id={id}[&foo=bar]

Request: project?id=4 --> project/project-name
Request: project?id=4&foo=bar --> project/project-name?foo=bar

If the source is project?id={id}[!&foo=bar], however, then the optional part will not be added to the destination.

I haven't actually worked on the feature yet, so it may change; but this is how I plan on doing it. (Speaking of which, forgot to add this to the roadmap!)

  • Like 1
Link to comment
Share on other sites

Thanks @Mike Rockett, the implicit option with {all} will suffice.

I haven't dug too deep into all the options, but it would be great if mapping could be done without collections:

source: project?id={someCustomField}

So that someCustomField would be a field of projects/ child pages, like $pages->get('/projects/')->children('someCustomField={value}');

This way one could simply migrate the ids of the old site over.

source: project?id={oldID}



Link to comment
Share on other sites

@owzim - This is what destination selectors are for. In your case:

source: project?id={id}
[[parent=/projects/, oldID={id}]]

Anything inside double-square-brackets is a selector, and returns the full httpUrl of the page. You can also append a query string to the destination for the purposes of analytics, if you wish.

(The syntax is changing in v2 to @[selector].)


  • Like 1
Link to comment
Share on other sites

Have been doing some work on v2, Currently, the new manager looks like this the image below.

Descriptions: I've opted to show the optional descriptions underneath the source, and there will also be an option to not show them if it starts looking too cluttered. Originally, I'd said that they should be shown to the side of the source, but that makes it difficult and tedious to prevent datatables from running of the side of the page. With that said, my recommendation is to only use descriptions where they are really necessary -- like if you need to use the description for the purposes of searching a large data-set and you can't remember the source. At the end of the day, this feature won't be used my many and, for those who don't use it, it won't get in your way.

Parameter Highlighting: You'll also notice that parameters in the jumplink destinations are now highlighted - this makes it easy for those who don't know 100% what's going on (like someone who has taken over a site) to learn quickly (tooltips provided). This feature can be disabled, though I'm not sure if it should be disabled by default. Please vote in reply -- if there's no feedback, I'll leave it enabled by default. Lastly, I don't think it's necessary to highlight source parameters (too flashy), but I do plan to add a slight underline to those for the purposes of tooltips, which will only really be handy for aliases such as segment.

Slug alias: Speaking of aliases, I've added a slug alias, which strictly captures parts of a URI that are slugs; that is, a word, optionally followed by a single hyphen, rinse, repeat. Segment, however, is not strict and allows any amount of consecutive hyphens. In the new documentation, I'll recommend the use of slug.


  • Like 4
Link to comment
Share on other sites

Hi @Mike Rockett, I can't get the CSV import on 1.5.46 to work:






In the cases without trailing delimiters I get:

Notice: Undefined index: source
Notice: Undefined index: destination
ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1

With trailing delimiters, the jumplinks are created but source is empty and destination is a string: page:1.

I made sure, no empty lines are present.

Link to comment
Share on other sites

@tpr - Jumplinks 2 will be able to export all of its data, including config, via JSON or a gzipped archive containing JSON data. It will also be able to import from CSV and JSON files generated by other systems. When importing from JSON, a specific format will be required, but the importer will ask for fieldnames where they don't match the destination fieldnames. So If you provide {{"from": "/Somedir/file.ext", "to": "/awesome/path"}}, it will work correctly without asking questions, but if from or to or any other field does not use those names, then the importer will ask what the names are so it can read those instead.


@All - Initially, I wanted to have the PHP version requirement match that of Processwire, but I would now like to stick to the PW version recommendation, which is currently 5.5+. This allows me to use slightly newer components. However, 5.5 is at end of life, and only 5.6+ is currently supported. In the interests of users with hosting providers who still offer 5.5 as the newest version, Jumplinks will work for you. That said, using a host that provides unsupported software is not recommended. Many providers are moving over to 7.0 and 7.1, so the Jumplinks PHP version requirement become 5.6 when 7.0 active support comes to an end in 10 months. Then I'll follow that format in the future, meaning that 7.0 will be required when 7.1 active support comes to an end in 1 year and 10 months.

It's either that or I run a poll to see what version of PHP folks are using, and then make a decision from there.

For those interested: http://php.net/supported-versions.php

  • Like 3
Link to comment
Share on other sites

Thanks for the update @Mike Rockett. After the update: without trailing delimiters (foo;bar) I get:

ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1

With trailing delimiters (foo;bar;;) I get:

Notice: Undefined index: date_end
ProcessJumplinks: SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '-0001-11-30 00:00:00' for column 'date_start' at row 1

This only happens if I input more than one line. If it's only one line, it works. If it's only one line, both values separated by the delimiter land in the source field, destination stays empty.

Is there a reason, why you rolled your own CSV parser instead of using str_getcsv?

Link to comment
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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.

      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      ProcessWire module directory
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
  • Create New...