Module Selectize.js modules family

[Macrura]

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

[Sipho]

@Macrura Thanks! addBlankOption worked. 

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

[Macrura]

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

[szabesz]

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? 

[Macrura]

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:

[szabesz]

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.

[Macrura]

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>'

 

[szabesz]

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 

[Macrura]

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

[szabesz]

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

[mel47]

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

[Macrura]

maybe try $page->of(false);

at the top of the code

[mel47]

12 minutes ago, Macrura said:

maybe try $page->of(false);

at the top of the code

Unfortunately, nope.

[Macrura]

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); 

[szabesz]

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!

[Macrura]

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.

[adrianromega]

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.

[adrianromega]

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

thanks again for this module.

[Robin S]

Hi @Macrura

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

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.

[Macrura]

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

[Robin S]

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.

[Macrura]

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.

[adrian]

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.

[Robin S]

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?

[adrian]

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