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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • 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-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 ----
       
×
×
  • Create New...