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 Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...