Jump to content

Module: FieldtypeTime & InputfieldTime

Recommended Posts

I've just posted a Fieldtype and Inputfield module combination that support the use of MySQL time fields in ProcessWire. Ryan's Datetime module is great but I needed something that dealt specifically with times for a scheduling system and this is one of the results.



For 24 hour clock format ('HH24MM') you now get a clock-picker pop-up by default...


...but you can inhibit it if you don't want it...


Although the input time format is selectable, as this is stored as a MySQL time field, you currently need to specify values in selectors in full "H:MM:SS" format. So if you wanted to get all events starting on or after 9am you'd do something like this...

$events = $pages->find("template=events, starts>=9:00:00")->sort("starts");

This is definitely a beta module as I've not tested every single input format yet.

Currently does not support negative time-periods or fractions of a second.

FieldtypeTime on Github

FieldtypeTime in the Module Repository 



Version 0.2.0: Adds support for the use of this input field in repeaters and repeater matrix types.

Version 0.1.0: Adds clock picker.

  • Like 22

Share this post

Link to post
Share on other sites

Now added to the module repo and the opening post has been updated. Please report any issues with installation/use here.

Thank you!

Share this post

Link to post
Share on other sites

Thank you for the module.

I'm using it on a site in development as input for publishing times. Discovered no problems so far. All is running smoothly.

Have you considered adding optional JS to the field for user friendly input through a time picker like http://jonthornton.github.io/jquery-timepicker/ ?

  • Like 2

Share this post

Link to post
Share on other sites


Thank you for the feedback - glad this is working for you. For this Inputfield I deliberately wanted to have a way of quickly entering things from the keyboard but I do appreciate that some folks might want a way of adding a JS picker to this. When I'm less busy with my current project I'll look at re-visiting this to add one. If anyone else has additional suggestions for a candidate time-picker, please drop a note below. 

  • Like 1

Share this post

Link to post
Share on other sites


here are some more timepickers that I was looking at when trying to quickly implement one with your field:

https://fgelinas.com/code/timepicker/ : this one is based on jQuery UI

http://jdewit.github.io/bootstrap-timepicker/ : personally, I like this one best, but it relies on Bootstrap and I couldn't get it to work with BS 3 and with other date fields present in the same form

http://weareoutman.github.io/clockpicker/jquery.html : funny picker looks like a clock


  • Like 1

Share this post

Link to post
Share on other sites


I'm starting to play with adding clockpicker (which I find really intuitive) to the inputfield. Here's a screenshot...


...what do you think? Of course, this is only valid for HH24MM format times.

  • Like 12

Share this post

Link to post
Share on other sites

I just pushed a new branch to the github repository that adds the clockpicker popup as seen in the screenshot above. If you want to try it simply use the files from the clockpicker branch. If all goes well with your testing I'll merge this change into the master branch and bump the version.


  • Like 2

Share this post

Link to post
Share on other sites

I've now added clock-picker to the master branch and bumped the version number. Please see the opening post for more details. 

  • Like 3

Share this post

Link to post
Share on other sites

Thanks for the module.

How can I prevent it from populating the field (with 00:00:00) by default?

Share this post

Link to post
Share on other sites

Hi Beluga,

Do you need a configurable value or just a blank as a default?

Blank by default would be the best as it's in line with how Datetime behaves. Configurable is fine by me, though, if you have a usecase for populating by default.

Share this post

Link to post
Share on other sites

I updated my site from 2.5.2 to 2.6.3 with the ProcessUpgrade Module.

When updating InputfieldTime (also through ProcessUpgrade Module) I got a worning that it is not compatible with 2.6. I went ahead anyways to see what will happen.

After upgrade I got 2 Warnings:

ModulesDuplicates: There appear to be multiple copies of module "FieldtypeTime" on the file system. Please edit the module settings to tell ProcessWire which one to use:FieldtypeTime
ModulesDuplicates: There appear to be multiple copies of module "InputfieldTime" on the file system. Please edit the module settings to tell ProcessWire which one to use:InputfieldTime

and a message:

InputfieldTime was updated successfully.

Button: Continue to module settings

In the module settings I got:

There are multiple copies of this module. Select the module file you want to use.
/site/modules/InputfieldTime/InputfieldTime.module (the new one after update)
/site/modules/PW-FieldtypeTime/InputfieldTime.module (the old one)
I chose the new one.
Then I did the same for Fieldtype Time module.
Everything seems to be working fine with 2.6.3
Just wanted to let you know.

Share this post

Link to post
Share on other sites


first of all thanx for the awesome module.

Are there any news about a blank value as Beluga pointed out? I also need a blank value for opening hours.

Best regards

Share this post

Link to post
Share on other sites

@Beluga, @Juergen

Thanks for pressing me on this. I've just been testing this in PhpMyAdmin and there seems to be a problem with trying to set a blank value to MySQL time fields; MySQL itself sees the blank as an invalid time and sets it to '00:00:00'. There is some more detail about this in the MySQL Time type manual page. Here's a quote from the linked manual page...

Illegal TIME values are converted to '00:00:00'. Note that because '00:00:00' is itself a legal TIME value, there is no way to tell, from a value of '00:00:00' stored in a table, whether the original value was specified as '00:00:00' or whether it was illegal.

You could setup your own test table with a TIME field and try it yourself. Please let me know if you find a workable solution and I'll try and work it into the module. At this point in time I'm not sure how to prevent PW from trying to save a blank value into the DB if nothing is entered in the Inputfield.

Share this post

Link to post
Share on other sites


I'm not sure how the duplicate modules got into your filesystem but I've updated the module information to show compatibility with 2.6.

  • Like 1

Share this post

Link to post
Share on other sites

I'm using Netcarver's FieldtypeTime module and I'm trying to sort results by time (in 24hr format hh:mm) but the following doesn't seem to work. My time field is fde_racetime.

foreach ($page->children("fde_date>$todaysDate,sort=fde_date,sort=fde_racetime") as $alldays) {
    foreach ($alldays->fde as $entry) {
      if ($entry->fde_declared == 1) {
        $section_main .= showFDE($alldays, $entry);


Would I need to create a specific sort condition?


Edited by kongondo
Moved: For modules that have support forums, please post such questions in their respective forums

Share this post

Link to post
Share on other sites

Hello Pete,

I'm trying to sort results by time (in 24hr format hh:mm) but the following doesn't seem to work.

Just to clarify; are you getting a non-empty, but incorrectly sorted, result set for that selector?

Share this post

Link to post
Share on other sites

Hi Steve

When i use this field in the profields repeater matrix, the clock picker no longer works.

But outside of the repeater matrix, it works fine.

Within the repeater, we do not get <script type="text/javascript">$('.clockpicker').clockpicker();</script> added. I guess that  is the cause.

Any ideas what could cause that and how we can get it to show up?



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.

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 Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Still very alpha, use with caution!
      Features / Field Settings
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.

      Some examples with checkbox label

      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  

    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      Kind Regards
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      If you are interested, you can test the current state of development:
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)

  • Create New...