-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
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:
InputfieldSlideToggle
Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
Status
Still very alpha, use with caution!
Features / Field Settings
Size
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.
Screenshots
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?
InputfieldDatetime.zip
Kind Regards
Orkun
-
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
https://modules.processwire.com/modules/process-changelog/
https://github.com/teppokoivula/ProcessChangelog
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:
2019-08-08
2019-06-15
2019-06-02
2019-05-25
If you are interested, you can test the current state of development:
https://github.com/gadgetto/SnipWire
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)
-
By apeisa
Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
***
Latest screencast: http://www.screencas...73-ab3ba1fea30c
Grab the code: https://github.com/teppokoivula/AdminBar
***
I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
***
When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}"); and...
if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }
-
