Dynamic Selects (Commercial Module)

[kongondo]

Dynamic Selects

Released 27 July 2016

Dynamic Selects is a commercial module that enables the creation of dynamically related/dependent ajax-driven chained dropdown lists (aka cascading selects) for display and storage of multiple types of data. The module can be used both in the front- (display only) and backend (display and storage of data).

Setting up Dynamic Selects is very easy. With minimal effort, site developers can set up simple or complex chained selects. By making a selection in a trigger dropdown, via ajax, values are fetched and dynamically populate options in the dependent select. In turn, making a selection in the now populated select triggers the same action further down in a dependent select. The module only uses/stores ID references to selected options in the selects meaning the most current/up-to-date data will always be displayed in the selects. 

Currently only ProcessWire managed data are supported. If there is enough demand, we may incorporate external data sources (typically JSON). 

The module consists of 4 modules

1. ProcessDynamicSelects
2. MarkupDynamicSelects
3. FieldtypeDynamicSelects
4. InputfieldDynamicSelects

Video Demo: https://youtu.be/wkhx8xQ5ue4

Documentation: http://dynamicselects.kongondo.com/

Shop: https://processwireshop.pw/plugins/dynamic-selects/

Requires: ProcessWire 2.5 or newer and jQuery if using the frontend module (MarkupDynamicSelects)

Features

• Easily create powerful ajax-driven cascading/chained selects/dropdowns
• Unlimited number of select dropdowns per field
• Data-mapping made easy thanks to multiple possible combinations of data relationships, triggers and sources
• Mutlipe data relationships to chose from
• ID-based data referencing ensures your data values always stay fresh
• Remote and local caching to speed up data access and reduce ajax-requests to server
• User-friendly, intuitive and easy to set up

IMPORTANT

Before using this module in the frontend, you will need to thoroughly read the security section in the documentation.
 

[Robin S]

Cool module!

A couple of ideas/dreams for a future update:

1. It would be great to have thumbnails in the select dropdown for image fields.

2. Could there be an option for the last select in the chain to be a select multiple?

[gmclelland]

Nice module.  

Just a suggestion...

Maybe you could add an option to also hide all but the first select input?  When someone selects the first option it could show the next select field as so on?

[kongondo]

9 hours ago, gmclelland said:

Just a suggestion...

Maybe you could add an option to also hide all but the first select input?  When someone selects the first option it could show the next select field as so on?

Thanks for the suggestion. Done!

[gmclelland]

Great job kongondo!

[Torsten Baldes]

Great job!

Is or will it be possible to use this as a frontend module?

Thanks!

[kongondo]

2 hours ago, Torsten Baldes said:

...Is or will it be possible to use this as a frontend module?

 

On 27/07/2016 at 10:21 PM, kongondo said:

..... A MarkupDynamicSelects for use in the frontend is planned if there is enough demand for it.

[Torsten Baldes]

Oh, sorry. 

$demand++

Thanks!

[Basil]

i allso will need the 

$demand++

Thanks!

On 28/7/2016 at 0:21 AM, kongondo said:

..... A MarkupDynamicSelects for use in the frontend is planned if there is enough demand for it.

[cb2004]

On 7/27/2016 at 10:21 PM, kongondo said:

The module consists of a FieldtypeDynamicSelects and InputfieldDynamicSelects. A MarkupDynamicSelects for use in the frontend is planned if there is enough demand for it.

$demand++

[kongondo]

Thanks for the interest guys. I'll have to consider a few potential security issues first then make a decision. No ETA for now...

[kongondo]

Hi all,

I'm going to be away for the next couple of weeks (4-5 weeks possibly) with little if any access to the internet. I will deal with any queries on my return.

Thanks

[Maverick]

$demand++ for use in the frontend

[kongondo]

Am back in play. I am working on the frontend module. 

[hellomoto]

So this field requires more than one input/set of options? A base + a dependent? Is there an option to select from fields? like fields from a selected template?

[kongondo]

Yes, you need at least two selects: a trigger and its dependent select. You can select from fields, but not directly from templates themselves. Rather, select from fields attached to a page. In other words, the following (and more) are currently possible:

1. base/trigger select for #2: display templates
2. dependent select for #1 and also base/trigger select for #3: displays pages using a template selected in #1
3. dependent select for #2: display fields present in (the template of) a page selected in #2

[kongondo]

Quick update guys. Frontend module is ready. I have to update the docs first before releasing it though as with anything frontend, there are security implications if the module is not properly set up. Hence, the need to first prep the docs. Will talk more about how it works later but setting up the selects is quite easy. These are defined in a process module in the backend (think Menu Builder) with caching and validation right out of the box. Hope to release next week.

[kongondo]

Dynamic Selects version 003  (released (27/11/2016))

Happy to announce that the latest release of Dynamic Selects is now available for Download/Purchase.

IMPORTANT

If you will be using this module in the frontend please FIRST READ at least the following topics in the documentation in their entirety.

1. Security
2. Settings
3. Introduction to frontend use
4. Example frontend use
5. Debugging results in the frontend

I have spent a considerable amount of time developing and testing security features to make using MarkupDynamicSelects safe. If you believe you've come across a potential vulnerability, I would appreciate it if you could send me a PM/email about it, thanks.

@note:

Currently, the Excluded Templates + Included Pages combo does not work as expected if you use more than one range of IDs for either. In such cases, please stick to comma-separated values.

Changelog

1. Frontend Dynamic Selects: Added Process- and MarkupDynamicSelects.
2. Expanded included/excluded settings to cover templates and pages.

[kongondo]

Dynamic Selects version 004  (released (30/11/2016))

Glad to announce that the latest release of Dynamic Selects is now available for Download/Purchase.

Changelog

1. Dynamic Selects is now fully compatible with ProcessWire 2.8.x and ProcessWire 3.x. 

[owzim]

Hey @kongondo, does your awesome module also work with ASM selects?

[kongondo]

11 minutes ago, owzim said:

Hey @kongondo, does your awesome module also work with ASM selects?

No; they are just normal selects. Am curious, what's the case for using ASM selects? 

[owzim]

@kongondo, at the end of the select chain one might want to select multiple things, like on regular page selects.

For example a list of employees:

Company > Location > Department > Jane Doe, John Doe and Max Mustermann

[kongondo]

@owzim Ah. I see. For frontend, might be a bit easy to implement (not necessarily with ASM), For backend, a bit trickier since the Fieldtype exclusively stores (int) IDs. It would mean have to rethink the database schema...I'll have a think...

[owzim]

Thanks, I am actually in need of that feature in a current project. So hurry ... jk

edit: As far as I know the page field stores multiple values just as comma separated ids

[kongondo]