Jump to content
Macrura

Selectize.js modules family

Recommended Posts

17 hours ago, Sipho said:

As a tangent question, is it possible to use InputfieldSelectize for non-page inputfields? So for example, using InputfieldSelect I can say:


<?php
$f->addOption("pie","Pie");

But using InputfieldSelectize I can't seem to figure out how to get the value in the itemDataArray. Is there a way to do this?

the way this module works is that the json is attached to each option;

you could use a plain selectize init on your inputfield select, i do that a lot and it works well... using something like a hook in ready or admin custom files...

Share this post


Link to post
Share on other sites

ok great, i'm hoping to test the changes and push the update to the module next week..

  • Like 2

Share this post


Link to post
Share on other sites

Hello @Macrura,

I'm thinking of using Inputfield Selectize as a "visual page selector", picking pages from a page reference field, meaning I need something which works like an AsmSelect but at the same time it can display an imagefield's picture of the selectable pages along with the title. Is that possible? 

  • Like 1

Share this post


Link to post
Share on other sites

yup, doing it all the time.. one of the main use cases for this...

lotta examples earlier in this thread of images being used, here is a slider section where you select the slides to be shown:

Selectize Page Select Slide Example

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the reply!

4 minutes ago, Macrura said:

slider section where you select the slides to be shown

"Coincidentally" it is what I want to do :) I want to create selectable "slides" which can be used on the homepage as slider images a but also on blog post pages as "featured" images, so there should be no need to upload different images for the same "slide/post pairs".

7 minutes ago, Macrura said:

lotta examples earlier in this thread of images being used

Sure, however I only spotted examples with "$page->images" and could not find any examples with "custom selectors" and that is I why I thought I ask first before installing it.

Share this post


Link to post
Share on other sites

here are the settings for the image above:

1) Array of Data

$image = '';
if(count($page->images)) $image = $page->images->first();
$thumb = '';
$dims = '';
if($image !='') {
    $thumb = $image->size(100,100)->url;
    $dims = $image->width . 'x' . $image->height;
}

$data = array(
    'title'       => $page->title,
    'type'        => $page->media_type->title,
    'thumb'       => $thumb,
    'img_dims'    => $dims,
    'edit_src'    => $page->editUrl
);

return $data;

 

2) Render Item Markup

'<div class="item" style="width:100%;">' +
    (item.thumb ? '<div class="image-wrapper" style="float:left;"><img src="' + escape(item.thumb) + '" alt=""></div>' : '') +
    '<div class="info-wrapper" style="float:left; padding:5px;">' +
        '<span style="font-size:14px;font-weight:bold">' + escape(item.title) + '</span><br>' +
        '<span>Type: ' + escape(item.type) + '</span><br>' +
        (item.img_dims ? '<span>Dims: ' + escape(item.img_dims) + 'px</span><br>' : '') +
        '<a class="pw-modal pw-modal-medium" href="' + escape(item.edit_src) +
        '">Edit <span class="ui-icon ui-icon-extlink"></span></a></div>' +
'</div>'

3) Render Option markup

'<div class="item" style="width:100%;">' +
    (item.thumb ? '<div class="image-wrapper" style="float:left;"><img src="' + escape(item.thumb) + '" alt=""></div>' : '') +
    '<div class="info-wrapper" style="float:left; padding:5px;">' +
    '<span style="font-size:14px;font-weight:bold">' + escape(item.title) + '</span><br>' +
        '<span>Type: ' + escape(item.type) + '</span><br></div>' +
'</div>'

 

  • Like 2

Share this post


Link to post
Share on other sites

I have just I realized that in your examples $page must be a reference to the selected page and not the current page being edited. Am I right?

I should install the module instead of asking silly questions :D

Share this post


Link to post
Share on other sites

correct, when you get the array of data to supply to each option, that is being used when the module iterates through the selectable pages and is then used to generate the json attribute that gets added to the select option itself, in the data-data attribute. Selectize.js natively reads that data-data attribute to get the object that it can then parse into the item and option markup that it renders... item always refers to the actual option

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

Just discovered selectize. Sounds quite interesting!

However I have a small problem; title of multilang pages give [object Object]

/** display fine
$data = array(
    'title' => $page->name,
    'ville' => $page->ville,
    'region' => $page->region->name
);

/***error: printing [object Object]
$data = array(
    'title' => $page->title,
    'ville' => $page->ville,
    'region' => $page->region->title
);

Thanks

Share this post


Link to post
Share on other sites
12 minutes ago, Macrura said:

maybe try $page->of(false);

at the top of the code

Unfortunately, nope.

Share this post


Link to post
Share on other sites

you’ll have to use the language api to get the value you want to show there;

You may also be able to try

$page->region->getFormatted('title')

but the language api should give you what you need to get that value/data if formatted doesn't work..., e.g.

$dutch = $languages->get('dutch'); // get the language we want
$body = $page->title->getLanguageValue($dutch); 

Share this post


Link to post
Share on other sites

Hi @Macrura

Finally I had the time to actually install the module and make changes to the website in order to use it as the "selector" of the slides. It works well, I'm just wondering why the "type" bit gave me "Undefined property" notice when using your example above. Since I do not really think displaying type is useful – if it is always "image" just as the user expects it to be... - I just simply replaced with another property of the slide page and that is the "url" where the slide is linked to.

All in all, I think this module is really great! Thanks a lot!

Share this post


Link to post
Share on other sites

right, sorry, my example was pulling from a 'media' template where you have these different media types, like image, video, audio. So you wouldn't need that in your application.

  • Like 1

Share this post


Link to post
Share on other sites

Nice module, just tried it and I do not know how to make it work for multiple page selection...

In a field page config, in Input Field Type. Inputfield Selectize appears only for Single page selection...

I am using the latest processwire 3.

Thank you.

Share this post


Link to post
Share on other sites

Hi @Macrura

I'm not able to install SelectizeImageTags in PW 3.0.83.

2017-11-16_232751.png.1716a230f33a89418c6a8ba70cc4cbec.png

Edit: I can install it if I download and manually copy the directory to /site/modules/

This came up a while back...

...were you able to get to the bottom of what was causing it?

Also, if I am able to install the module is it still working given the changes to image tagging in the core? I remember you discussing this with Ryan when the core changes were made and just wondering where things stand.

  • Like 1

Share this post


Link to post
Share on other sites

Ok sorry about this – i just change the leading zero integer to a string so we'll see if that fixes the download install...

2 hours ago, Robin S said:

Also, if I am able to install the module is it still working given the changes to image tagging in the core? I remember you discussing this with Ryan when the core changes were made and just wondering where things stand.

I regularly use this module instead of the core image tagging, so that i can have those benefits i listed somewhere, in short, key/value pairs for tags and template context for different tags on a field..

  • Like 1

Share this post


Link to post
Share on other sites
7 hours ago, Macrura said:

i just change the leading zero integer to a string so we'll see if that fixes the download install

Did you push this yet? Not seeing any new commit in the repo. I think there might be some other issue with the module regarding the modules directory, because the directory is showing v0.0.3 but SelectizeImageTags.info.php is v0.0.7. Maybe the getModuleInfo() in the main module file is still being read despite being commented out?

7 hours ago, Macrura said:

I regularly use this module instead of the core image tagging, so that i can have those benefits i listed somewhere

Absolutely - the key/value tags is a big benefit and was about to recommend it to someone because of this when I struck the install issue. I just thought there was some discussion about the module being impacted by the core changes, but I might be misremembering or those things are now resolved.

Share this post


Link to post
Share on other sites

sorry must have not gone through, just pushed it now. I'm guessing the mods dir is having the same leading zero problem, possibly running php 7 since v 003, when leading zeros used to work... hoping this does fix that.

Share this post


Link to post
Share on other sites
20 minutes ago, Macrura said:

sorry must have not gone through, just pushed it now. I'm guessing the mods dir is having the same leading zero problem, possibly running php 7 since v 003, when leading zeros used to work... hoping this does fix that.

It's always been an issue to some degree:

 

I have actually moved all my modules to string version numbers so that I can do 1.2.13 etc. I am trying to be more diligent with using numbers that are somewhat semantic at least.

  • Like 2

Share this post


Link to post
Share on other sites
3 minutes ago, adrian said:

I have actually moved all my modules to string version numbers so that I can do 1.2.13

Does that cause a problem though if you are doing a numerical comparison on the version? For example, in the "requires" item of getModuleInfo() or in the upgrade() method?

Share this post


Link to post
Share on other sites
6 minutes ago, Robin S said:

Does that cause a problem though if you are doing a numerical comparison on the version? For example, in the "requires" item of getModuleInfo() or in the upgrade() method?

I haven't seen any issues and it should be fine, because it uses PHP's version_compare() which support comparison of integer and string version numbers

https://github.com/processwire/processwire/blob/57b297fd1d828961b20ef29782012f75957d6886/wire/core/Modules.php#L4023

http://php.net/manual/en/function.version-compare.php

  • Like 1

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.

Guest
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
      Features
      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:
      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)
       




×
×
  • Create New...