Jump to content
netcarver

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.

FieldtypeTime_001.png

FieldtypeTime_002.png

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

2015-02-12-02.png

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

2015-02-13-01.png

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 

 

Releases

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

I have sneaked around this feature many times with dirty solutions. Thanks for making this Steve.

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

@gebeer

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

@netcarver

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

http://amsul.ca/pickadate.js/

  • Like 1

Share this post


Link to post
Share on other sites

@gebeer

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

post-465-0-56632800-1423751672_thumb.png

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

Thanks!

  • 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?

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

@netcarver,

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

@geeber

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?

http://modules.processwire.com/modules/inputfield-time/

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?

Cheers

 

Share this post


Link to post
Share on other sites

@Zahari Majini

Apa khabar, Zahari? I guess that the JS and/or the CSS file from InputfieldTime isn't getting loaded in that context, I don't know why yet.

Steve

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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...