Jump to content
netcarver

Module: FieldtypeTime & InputfieldTime

Recommended Posts

Selamat Pagi. Khabar baik tuan Steve!

Thanks for the reply!

Look forward to you figuring it out whenever your free next.

Till then...

Cheers!

 

Share this post


Link to post
Share on other sites
2 hours ago, Zahari Majini said:

Khabar baik tuan Steve!

Tuan? Saya? :undecided:  Terimah Kasih, tetapi "Steve" cukup baik. :)

</offtopic>

Share this post


Link to post
Share on other sites

@Zahari Majini Could you let me know...

  1. which time format you are using for your input? (From the details tab of your time field.)
  2. if you have the picker inhibited? (Look on the input tab of your time field.)

timepicker-00.png  timepicker-01.png

 

Thank you!

Share this post


Link to post
Share on other sites

Hi Steve

Time format is Hours (0-24) & minutes (00-59)

Picker is unchecked or not inhibited. Works fine on a regular page. Just not in a repeater matrix.

Terima kasih!

Share this post


Link to post
Share on other sites

@Zahari Majini

It appears to be the same issue as reported here. For now, you can work around it by changing the settings for your repeater matrix to the following...

timepicker-02.png

Not the most satisfactory of results. Note, doesn't work well enough if you simply switch the Ajax option to off as the picker appears on all the fields as soon as you open the owning entry.

  • Like 2

Share this post


Link to post
Share on other sites

Hi Steve!

Thanks so much for all the effort you have put into this!

I will check out the thread you linked to to learn more.

Many thanks again!

 

 

 

Share this post


Link to post
Share on other sites

@Zahari Majini

Could you give the code from the new dev branch a try, please. Just replace the existing files in your installation directory and include the new file: InputfieldTime.trigger.js

Thanks!

Share this post


Link to post
Share on other sites

Hi Steve

Thanks so much again for looking into this. Unfortunately after trying the dev version, i think it's made things worse. At least for me. The clock picker has now stopped working on both a "normal simple" page and within a repeater matrix. Replacing it with the previous main one restored back the clock picker on the "normal" page....

Share this post


Link to post
Share on other sites

@Zahari Majini

Ok, that's unexpected. My local install (3.0.36) has it working in normal contexts as well as repeater-matrix contexts. Did you overwrite the InputfieldTime.module file with the new one?

Any chance you can PM me login details to allow me to try and trace what is happening on your installation?

Regards, Steve

  • Like 1

Share this post


Link to post
Share on other sites

Hi Steve

Actually the site is on local host in MAMP Pro.

I will upload it to a live site over the weekend and pass you the login details so you can have a dig!

But now that you mention it mine is 3.0.38. Hmmm. Will rollback too and see!

 

Cheers!

Share this post


Link to post
Share on other sites

Hi Steve

Have messaged you the details you asked for.

Many thanks mate!

Share this post


Link to post
Share on other sites

I just pushed fixes for the issue identified by @Zahari Majini

Please update to v0.2.0 or later if you want to use this field in repeaters.

  • Like 3

Share this post


Link to post
Share on other sites

Thanks Steve!!

Fabulous module indeed!

^-^

Curious now... what were the jobs or the needs you had that made you make it?

Share this post


Link to post
Share on other sites
On 16.6.2015 at 0:18 AM, netcarver said:

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

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.

Why don't you insert a NULL value for the time if it's left blank? This should work perfectly with MySQL.

Apart from that, thanks a lot for the module, but the blank problem is also essential for me, so I really would appreciate a solution  :-)

Share this post


Link to post
Share on other sites

@FlorianA Sorry for the delay on this. I've been away from the keyboard over the summer holidays and must have missed the notification email from the forum about your post here.

Looking at this now.

Share this post


Link to post
Share on other sites

Hi @netcarver great module! Something I'm not sure how to do or if I missed the option: With date time fields from PW you get the option to format the output based on the language. Is this also possible with your plugin? Seems I can't find the option…

59ddfc4422a4e_ScreenShot2017-10-11at13_10_33.png.58e32b44ab43a38481e5c16dfcb92959.png

Share this post


Link to post
Share on other sites
On 28.9.2017 at 3:53 PM, netcarver said:

I've now merged FlorianA's patch into the allow-blanks branch. Please test and let me know if it works for you.

I am using it too and I have not detected any problems since then.

  • Like 1

Share this post


Link to post
Share on other sites

Hey @netcarver - using this for the first time - very handy, thank you!

Just wondering if the field should be blank by default, rather than 00:00:00 ? I want to check to see if a time has been entered, but the way things are, it doesn't seem possible. I am doing the check against 00:00:00 but of course that is a valid time (fortunately not one that anyone would enter in my case, but in some others in certainly would be).

Thanks.

EDIT: Oops, looks like @FlorianA is already on this :) Anyway, looking forward to seeing that merged!

Share this post


Link to post
Share on other sites

Actually, what do you guys @netcarver @FlorianA @bernhard think about putting 00:00:00 in the placeholder attribute - that way editors know what format to enter, but the value is still blank.

  • Like 2

Share this post


Link to post
Share on other sites

@adrian

Thanks for the feedback - I like the idea. It needs a take account of the chosen time format (that's just one of the ones on offer), but this should be possible. Will see what I can do.

  • Like 3

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 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');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...