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

@Macrura Thanks! addBlankOption worked. 

I also managed to get the custom json working by hooking extendAttributes

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

Thanks for clarifying! I was confused by the name of the variable $page.

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

maybe try $page->of(false);

at the top of the code

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

I found out the solution, there was another module to install, Inputfield Selectize Multiple .

thanks again for this module.

  • Like 1

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

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 bernhard
      --- Please use RockFinder3 ---
    • 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 (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...