Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2026-02-12 14:54
📄 .gitignore _site dist	11 B	2026-02-12 14:54
📄 README.md Select2 Documentation ===================== [This repository][select2-docs-source] holds the latest documentation for [Select2][select2]. What is this? ------------- The documentation is automatically extracted from the `docs` directory at the [Select2 source repository][select2-source]. This is done periodically by the maintainers of Select2. How can I fix an issue in these docs? ------------------------------------- If you are reading this from the source repository, within the `docs` directory, then you're already in the right place. You can fork the source repository, commit your changes, and then make a pull request and it will be reviewed. If you are reading this from the [documentation repository][select2-docs-source], you are in the wrong place. Pull requests made directly to the documentation repository will be ignored and eventually closed, so don't do that. How can I build these docs manually? ------------------------------------ In the [main Select2 repository][select2-source], you can build the documentation by executing ```bash grunt docs ``` Which will start up the documentation on port 4000. You will need [Jekyll][jekyll] installed to build the documentation. [jekyll]: http://jekyllrb.com/ [select2]: https://select2.github.io [select2-docs-source]: https://github.com/select2/select2.github.io [select2-source]: https://github.com/select2/select2	1.36 KB	2026-02-12 14:54
📁 _includes	-	2026-02-12 14:54
📁 _layouts	-	2026-02-12 14:54
📁 _sass	-	2026-02-12 14:54
📄 announcements-4.0.html --- layout: default title: Select2 4.0.0 Released slug: announcements-4.0 --- <section id="pre-release" class="jumbotron"> <div class="container"> <h1>Announcing Select2 4.0.0</h1> </div> </section> <div class="container s2-docs-container"> <div class="row"> <div class="col-md-9" role="main"> <section id="release"> <h1 class="page-header">Select2 4.0.0</h1> <p class="lead"> The 4.0 release of Select2 is the result of three years of working on the code base and watching where it needs to go. At the core, it is a full rewrite that addresses many of the extensibility and usability problems that could not be addressed in previous versions. </p> <p> This release contains many breaking changes, but easy-upgrade paths have been created as well as helper modules that will allow for backwards compatibility to be maintained with past versions of Select2. Upgrading <em>will</em> require you to read the release notes carefully, but the migration path should be relatively straightforward. You can view a list of the most common changes that you will need to make <a href="https://github.com/select2/select2/releases">in the release notes</a>. </p> <p> Below is an in-depth review of what is new in Select2, as well as some of the major changes that have been made. </p> </section> <section id="new"> <h2>New features</h2> <p> The notable features of this new release include: </p> <ul> <li> A more flexible plugin framework that allows you to override Select2 to behave exactly how you want it to. </li> <li> Consistency with standard <code><select></code> elements for all data adapters, removing the need for hidden <code><input></code> elements. </li> <li> A new build system that uses AMD to keep everything organized. </li> <li> Less specific selectors allowing for Select2 to be styled to fit the rest of your application. </li> </ul> </section> <section id="plugins"> <h2>Plugin system</h2> <p> Select2 now provides interfaces that allow for it to be easily extended, allowing for anyone to create a plugin that changes the way Select2 works. This is the result of Select2 being broken into four distinct sections, each of which can be extended and used together to create your unique Select2. </p> <p> The adapters implement a consistent interface that is documented in the <a href="options.html#adapters">options section for adapters</a>, allowing you to customize Select2 to do exactly what you are looking for. Select2 is designed such that you can mix and match plugins, with most of the core options being built as decorators that wrap the standard adapters. </p> </section> <section id="amd-builds"> <h2>AMD-based build system</h2> <p> Select2 now uses an <a href="https://en.wikipedia.org/wiki/Asynchronous_module_definition">AMD-based build system</a>, allowing for builds that only require the parts of Select2 that you need. While a custom build system has not yet been created, Select2 is open source and will gladly accept a pull request for one. </p> <p> Select2 includes the minimal <a href="https://github.com/jrburke/almond">almond</a> AMD loader, but a custom <code>select2.amd.js</code> build is available if you already use an AMD loader. The code base (available in the <code>src</code> directory) also uses AMD, allowing you to include Select2 in your own build system and generate your own builds alongside your existing infrastructure. </p> <p> The AMD methods used by Select2 are available as <code>jQuery.fn.select2.amd.define()/require()</code>, allowing you to use the included almond loader. These methods are primarily used by the translations, but they are the recommended way to access custom modules that Select2 provides. </p> </section> <section id="migrating"> <h1>Migrating from Select2 3.5</h1> <p> There are a few breaking changes that migrators should be aware of when they are coming from older versions of Select2. </p> <p> If you use the full build of Select2 (<code>select2.full.js</code>), you will be automatically notified of the major breaking changes, and compatibility modules will be used in some cases to ensure that your code still behaves how you were expecting. </p> <h2 id="hidden-input">No more hidden input tags</h2> <p> In past versions of Select2, an <code><input type="hidden" /></code> tag was recommended if you wanted to do anything advanced with Select2, such as work with remote data sources or allow users to add their own tags. This had the unfortunate side-effect of servers not receiving the data from Select2 as an array, like a standard <code><select></code> element does, but instead sending a string containing the comma-separated strings. The code base ended up being littered with special cases for the hidden input, and libraries using Select2 had to work around the differences it caused. </p> <p> In Select2 4.0, the <code><select></code> element supports all core options, and support for the old <code><input type="hidden" /></code> has been deprecated. This means that if you previously declared an AJAX field with some pre-selected options that looked like… </p> <pre class="prettyprint linenums"> <input type="hidden" name="select-boxes" value="1,2,4,6" /> </pre> <p> It will need to be recreated as a <code><select></code> element with some <code><option></code> tags that have <code>value</code> attributes that match the old value. </p> <pre class="prettyprint linenums"> <select name="select-boxes" multiple="multiple"> <option value="1" selected="selected">Select2</option> <option value="2" selected="selected">Chosen</option> <option value="4" selected="selected">selectize.js</option> <option value="6" selected="selected">typeahead.js</option> </select> </pre> <p> The options that you create should have <code>selected="selected"</code> set so Select2 and the browser knows that they should be selected. The <code>value</code> attribute of the option should also be set to the value that will be returned from the server for the result, so Select2 can highlight it as selected in the dropdown. The text within the option should also reflect the value that should be displayed by default for the option. </p> <h2 id="new-matcher">Advanced matching of searches</h2> <p> In past versions of Select2, when matching search terms to individual options, which limited the control that you had when displaying results, especially in cases where there was nested data. The <code>matcher</code> function was only given the individual option, even if it was a nested options, without any context. </p> <p> With the new matcher function, only the root-level options are matched and matchers are expected to limit the results of any children options that they contain. This allows developers to customize how options within groups can be displayed, and modify how the results are returned. </p> <p> A function has been created that allows old-style matcher functions to be converted to the new style. You can retrieve the function from the <code>select2/compat/matcher</code> module, which should just wrap the old matcher function. </p> <p> So if your old code used a matcher that only displayed options if they started with the term that was entered, it would look something like… </p> <pre class="prettyprint linenums"> function matchStart (term, text) { if (text.toUpperCase().indexOf(term.toUpperCase()) == 0) { return true; } return false; } $("select").select2({ matcher: matchStart }) </pre> <p> Then in Select2 4.0, you would need to wrap the <code>matchStart</code> method (or the name of the matcher you created) with a <code>oldMatcher</code> method that we have created. </p> <pre class="prettyprint linenums"> function matchStart (term, text) { if (text.toUpperCase().indexOf(term.toUpperCase()) == 0) { return true; } return false; } $.fn.select2.amd.require(['select2/compat/matcher'], function (oldMatcher) { $("select").select2({ matcher: oldMatcher(matchStart) }) }); </pre> <p> This will work for any matchers that only took in the search term and the text of the option as parameters. If your matcher relied on the third parameter containing the jQuery element representing the original <code><option></code> tag, then you may need to slightly change your matcher to expect the full JavaScript data object being passed in instead. You can still retrieve the jQuery element from the data object using the <code>data.element</code> property. </p> <h2 id="flexible-placeholders">More flexible placeholders</h2> <p> In the most recent versions of Select2, placeholders could only be applied to the first (typically the default) option in a <code><select></code> if it was blank. The <code>placeholderOption</code> option was added to Select2 to allow users using the <code>select</code> tag to select a different option, typically an automatically generated option with a different value. </p> <p> The <code>placeholder</code> option can now take an object as well as just a string. This replaces the need for the old <code>placeholderOption</code>, as now the <code>id</code> of the object can be set to the <code>value</code> attribute of the <code><option></code> tag. </p> <p> For a select that looks like the following, where the first option (with a value of <code>-1</code>) is the placeholder option… </p> <pre class="prettyprint linenums"> <select> <option value="-1" selected="selected">Select an option</option> <option value="1">Something else</option> </select> </pre> <p> You would have previously had to get the placeholder option through the <code>placeholderOption</code>, but now you can do it through the <code>placeholder</code> option by setting an <code>id</code>. </p> <pre class="prettyprint linenums"> $("select").select2({ placeholder: { id: "-1", placeholder: "Select an option" } }) </pre> <p> And Select2 will automatically display the placeholder when the value of the select is <code>-1</code>, which it will be by default. This does not break the old functionality of Select2 where the placeholder option was blank by default. </p> <h2 id="value-ordering">Display reflects the actual order of the values</h2> <p> In past versions of Select2, choices were displayed in the order that they were selected. In cases where Select2 was used on a <code><select></code> element, the order that the server received the selections did not always match the order that the choices were displayed, resulting in confusion in situations where the order is important. </p> <p> Select2 will now order selected choices in the same order that will be sent to the server. </p> <h2 id="changed-options">Changed method and option names</h2> <p> When designing the future option set for Select2 4.0, special care was taken to ensure that the most commonly used options were brought over. For the most part, the commonly used options of Select2 can still be referenced under their previous names, but there were some changes which have been noted. </p> <h3 id="removed-initselection"> Removed the requirement of <code>initSelection</code> </h3> <p> In the past, whenever you wanted to use a custom data adapter, such as AJAX or tagging, you needed to help Select2 out in determining the initial values that were selected. This was typically done through the <code>initSelection</code> option, which took the underlying data of the input and converted it into data objects that Select2 could use. </p> <p> This is now handled by <a href="options.html#dataAdapter">the data adapter</a> in the <code>current</code> method, which allows Select2 to convert the currently selected values into data objects that can be displayed. The default implementation converts the text and value of <code>option</code> elements into data objects, and is probably suitable for most cases. An example of the old <code>initSelection</code> option is included below, which converts the value of the selected options into a data object with both the <code>id</code> and <code>text</code> matching the selected value. </p> <pre class="prettyprint linenums"> initSelection : function (element, callback) { var data = []; $(element.val()).each(function () { data.push({id: this, text: this}); }); callback(data); } </pre> <p> When using the new <code>current</code> method of the custom data adapter, <strong>this method is called any time Select2 needs a list</strong> of the currently selected options. This is different from the old <code>initSelection</code> in that it was only called once, so it could suffer from being relatively slow to process the data (such as from a remote data source). </p> <pre class="prettyprint linenums"> $.fn.select2.amd.require([ 'select2/data/array', 'select2/utils' ], function (ArrayData, Utils) { function CustomData ($element, options) { CustomData.__super__.constructor.call(this, $element, options); } Utils.Extend(CustomData, ArrayData); CustomData.prototype.current = function (callback) { var data = []; var currentVal = this.$element.val(); if (!this.$element.prop('multiple')) { currentVal = [currentVal]; } for (var v = 0; v < currentVal.length; v++) { data.push({ id: currentVal[v], text: currentVal[v] }); } callback(data); }; $("#select").select2({ dataAdapter: CustomData }); } </pre> <p> The new <code>current</code> method of the data adapter works in a similar way to the old <code>initSelection</code> method, with three notable differences. The first, and most important, is that <strong>it is called whenever the current selections are needed</strong> to ensure that Select2 is always displaying the most accurate and up to date data. No matter what type of element Select2 is attached to, whether it supports a single or multiple selections, the data passed to the callback <strong>must be an array, even if it contains one selection</strong>. The last is that there is only one parameter, the callback to be executed with the latest data, and the current element that Select2 is attached to is available on the class itself as <code>this.$element</code>. </p> <p> If you only need to load in the initial options once, and otherwise will be letting Select2 handle the state of the selections, you don't need to use a custom data adapter. You can just create the <code><option></code> tags on your own, and Select2 will pick up the changes. </p> <pre class="prettyprint linenums"> var $element = $('select').select2(); // the select element you are working with var $request = $.ajax({ url: '/my/remote/source' // wherever your data is actually coming from }); $request.then(function (data) { // This assumes that the data comes back as an array of data objects // The idea is that you are using the same callback as the old `initSelection` for (var d = 0; d < data.length; d++) { var item = data[d]; // Create the DOM option that is pre-selected by default var option = new Option(item.text, item.id, true, true); // Append it to the select $element.append(option); } // Update the selected options that are displayed $element.trigger('change'); }); </pre> <h3 id="query-to-data-adapter"> Custom data adapters instead of <code>query</code> </h3> <p> <a href="http://select2.github.io/select2/#data">In the past</a>, any time you wanted to hook Select2 up to a different data source you would be required to implement custom <code>query</code> and <code>initSelection</code> methods. This allowed Select2 to determine the initial selection and the list of results to display, and it would handle everything else internally, which was fine more most people. </p> <p> The custom <code>query</code> and <code>initSelection</code> methods have been replaced by <a href="options.html#dataAdapter">custom data adapters</a> that handle how Select2 stores and retrieves the data that will be displayed to the user. An example of the old <code>query</code> option is provided below, which is <a href="http://select2.github.io/select2/#data">the same as the old example</a>, and it generates results that contain the search term repeated a certain number of times. </p> <pre class="prettyprint linenums"> query: function (query) { var data = {results: []}, i, j, s; for (i = 1; i < 5; i++) { s = ""; for (j = 0; j < i; j++) {s = s + query.term;} data.results.push({id: query.term + i, text: s}); } query.callback(data); } </pre> <p> This has been replaced by custom data adapters which define a similarly named <code>query</code> method. The comparable data adapter is provided below as an example. </p> <pre class="prettyprint linenums"> $.fn.select2.amd.require([ 'select2/data/array', 'select2/utils' ], function (ArrayData, Utils) { function CustomData ($element, options) { CustomData.__super__.constructor.call(this, $element, options); } Utils.Extend(CustomData, ArrayData); CustomData.prototype.query = function (params, callback) { var data = { results: [] }; for (var i = 1; i < 5; i++) { var s = ""; for (var j = 0; j < i; j++) { s = s + params.term; } data.results.push({ id: params.term + i, text: s }); } callback(data); }; $("#select").select2({ dataAdapter: CustomData }); } </pre> <p> The new <code>query</code> method of the data adapter is very similar to the old <code>query</code> option that was passed into Select2 when initializing it. The old <code>query</code> argument is mostly the same as the new <code>params</code> that are passed in to query on, and the callback that should be used to return the results is now passed in as the second parameter. </p> <h3 id="changed-templating">Renamed templating options</h3> <p> Select2 previously provided multiple options for formatting the results list and selected options, commonly referred to as "formatters", using the <code>formatSelection</code> and <code>formatResult</code> options. As the "formatters" were also used for things such as localization, <a href="#changed-translations">which has also changed</a>, they have been renamed to <code>templateSelection</code> and <code>templateResult</code> and their signatures have changed as well. </p> <p> You should refer to the updated <a href="options.html#templating">documentation on templates</a> when migrating from previous versions of Select2. </p> <h3 id="changed-id"> The <code>id</code> and <code>text</code> properties are strictly enforced </h3> <p> When working with array and AJAX data in the past, Select2 allowed a custom <code>id</code> function or attribute to be set in various places, ranging from the initialization of Select2 to when the remote data was being returned. This allowed Select2 to better integrate with existing data sources that did not necessarily use the <code>id</code> attribute to indicate the unique identifier for an object. </p> <p> Select2 no longer supports a custom <code>id</code> or <code>text</code> to be used, but provides integration points for converting incorrect data to the expected format. </p> <h4> When working with array data </h4> <p> Select2 previously supported defining array data as an object that matched the signature of an AJAX response. A <code>text</code> property could be specified that would map the given property to the <code>text</code> property on the individual objects. You can now do this when initializing Select2 by using the following jQuery code to map the old <code>text</code> and <code>id</code> properties to the new ones. </p> <pre class="prettyprint linenums"> var data = $.map([ { pk: 1, word: 'one' }, { pk: 2, word: 'two' } ], function (obj) { obj.id = obj.id \|\| obj.pk; obj.text = obj.text \|\| obj.word; return obj; }); </pre> <p> This will result in an array of data objects that have the <code>id</code> properties that match the existing <code>pk</code> properties and <code>text</code> properties that match the existing <code>word</code> properties. </p> <h4> When working with remote data </h4> <p> The same code that was given above can be used in the <code>processResults</code> method of an AJAX call to map properties there as well. </p> <h3 id="changed-translations">Renamed translation options</h3> <p> In previous versions of Select2, the default messages provided to users could be localized to fit the language of the website that it was being used on. Select2 only comes with the English language by default, but provides <a href="options.html#language">community-contributed translations</a> for many common languages. Many of the formatters have been moved to the <code>language</code> option and the signatures of the formatters have been changed to handle future additions. </p> <h3 id="changed-data"> Declaring options using <code>data-</code> attributes </h3> <p> In the past, Select2 has only supported declaring a subset of options using <code>data-</code> attributes. Select2 now supports declaring all options using the attributes, using <a href="options.html#data-attributes">the format specified in the documentation</a>. </p> <p> You could previously declare the URL that was used for AJAX requests using the <code>data-ajax-url</code> attribute. While Select2 still allows for this, the new attribute that should be used is the <code>data-ajax--url</code> attribute. Support for the old attribute will be removed in Select2 4.1. </p> <p> Although it was not documented, a list of possible tags could also be provided using the <code>data-select2-tags</code> attribute and passing in a JSON-formatted array of objects for tags. As the method for specifying tags has changed in 4.0, you should now provide the array of objects using the <code>data-data</code> attribute, which maps to <a href="options.html#data">the array data</a> option. You should also enable tags by setting <code>data-tags="true"</code> on the object, to maintain the ability for users to create their own options as well. </p> <p> If you previously declared the list of tags as… </p> <pre class="prettyprint linenums"> <select data-select2-tags='[{"id": "1", "text": "One"}, {"id": "2", "text": "Two"}]'></select> </pre> <p> …then you should now declare it as… </p> <pre class="prettyprint linenums"> <select data-data='[{"id": "1", "text": "One"}, {"id": "2", "text": "Two"}]' data-tags="true"></select> </pre> <h2 id="removed-methods">Deprecated and removed methods</h2> <p> As Select2 now uses a <code><select></code> element for all data sources, a few methods that were available by calling <code>.select2()</code> are no longer required. </p> <h3>.select2("val")</h3> <p> The <code>"val"</code> method has been deprecated and will be removed in Select2 4.1. The deprecated method no longer includes the <code>triggerChange</code> parameter. </p> <p> You should directly call <code>.val</code> on the underlying <code><select></code> element instead. If you needed the second parameter (<code>triggerChange</code>), you should also call <code>.trigger("change")</code> on the element. </p> <pre class="prettyprint linenums"> $("select").val("1").trigger("change"); // instead of $("select").select2("val", "1"); </pre> <h3>.select2("enable")</h3> <p> Select2 will respect the <code>disabled</code> property of the underlying select element. In order to enable or disable Select2, you should call <code>.prop('disabled', true/false)</code> on the <code><select></code> element. Support for the old methods will be completely removed in Select2 4.1. </p> <pre class="prettyprint linenums"> $("select").prop("disabled", true); // instead of $("select").enable(false); </pre> </section> </div> <div class="col-md-3" role="complementary"> {% include nav/announcements-4.0.html %} </div> </div> </div> <script type="text/javascript"> prettyPrint(); </script>	27.53 KB	2026-02-12 14:54
📄 community.html --- layout: default title: Community - Select2 slug: community --- <section class="jumbotron"> <div class="container"> <h1> Community </h1> <p class="lead"> Select2 has an active community that enjoys helping each other out. </p> </div> </section> <div class="container"> <section id="support"> <div class="page-header"> <h1>Getting support</h1> </div> <p> Having trouble getting Select2 working on your website? Is it not working together with another plugin, even though you think it should? Select2 has a few communities that you can go to for help getting it all working together. </p> <ol> <li> Try sending a message to the <a href="https://groups.google.com/d/forum/select2"> Select2 discussion group </a> or searching the archives. </li> <li> Ask in the <code>#select2</code> channel on <code>chat.freenode.net</code> or use the <a href="https://webchat.freenode.net/?channels=select2"> web irc client. </a> </li> <li> Raise a question on <a href="http://stackoverflow.com/">Stack Overflow</a>, make sure to include the <a href="http://stackoverflow.com/questions/tagged/jquery-select2?sort=votes"> "jquery-select2" </a> tag. </li> </ol> </section> <section id="reporting-bugs"> <div class="page-header"> <h1>Reporting bugs</h1> </div> <p> Found a problem with Select2? Feel free to open a ticket on the Select2 repository on GitHub, but you should keep a few things in mind: </p> <ol> <li> Use the <a href="https://github.com/select2/select2/search?q=&type=Issues"> GitHub issue search </a> to check if your issue has already been reported. </li> <li> Try to isolate your problem as much as possible, so we can easily test if the issue has been fixed. </li> <li> Once you are sure the issue is with Select2, and not a third party library, <a href="https://github.com/select2/select2/issues/new"> submit a ticket </a> to the repository. </li> </ol> <p> You can find more information on reporting bugs in the <a href="https://github.com/select2/select2/blob/master/CONTRIBUTING.md#reporting-bugs-with-select2"> contributing guide, </a> including tips on what information to include. </p> </section> <section id="requesting-features"> <div class="page-header"> <h1>Requesting new features</h1> </div> <p> New feature requests are usually requested by the <a href="https://github.com/select2/select2/issues"> Select2 community on GitHub, </a> and are often fulfilled by <a href="#contributing"> fellow contributors. </a> </p> <ol> <li> Use the <a href="https://github.com/select2/select2/search?q=&type=Issues"> GitHub issue search </a> to check if your feature has already been requested. </li> <li> Check if it hasn't already been implemented as a <a href=""> third party plugin. </a> </li> <li> Please make sure you are only requesting a single feature, and not a collection of smaller features. </li> </ol> <p> You can find more information on requesting new features in the <a href="https://github.com/select2/select2/blob/master/CONTRIBUTING.md#requesting-features-in-select2"> contributing guide. </a> </p> </section> <section id="contributing"> <div class="page-header"> <h1>Getting involved</h1> </div> <p> You can find more information on getting involved with Select2 in the <a href="https://github.com/select2/select2/blob/master/CONTRIBUTING.md#triaging-issues-and-pull-requests"> contributing guide. </a> </p> </section> </div>	4.05 KB	2026-02-12 14:54
📁 css	-	2026-02-12 14:54
📁 dist	-	2026-02-12 14:54
📄 examples.html --- layout: default title: Examples - Select2 slug: examples --- <script type="text/javascript" src="vendor/js/placeholders.jquery.min.js"></script> <script type="text/javascript" src="dist/js/i18n/es.js"></script> <style type="text/css"> .img-flag { height: 15px; width: 18px; } </style> <section class="jumbotron"> <div class="container"> <h1> Examples </h1> </div> </section> <div class="container s2-docs-container"> <div class="row"> <div class="col-md-9" role="main"> {% include examples/basics.html %} {% include examples/placeholders.html %} {% include examples/data.html %} {% include examples/disabled-mode.html %} {% include examples/disabled-results.html %} {% include examples/multiple-max.html %} {% include examples/hide-search.html %} {% include examples/programmatic-control.html %} {% include examples/tags.html %} {% include examples/tokenizer.html %} {% include examples/matcher.html %} {% include examples/localization-rtl-diacritics.html %} {% include examples/themes-templating-responsive-design.html %} </div> <div class="col-md-3" role="complementary"> {% include nav/examples.html %} </div> </div> </div> {% include js-source-states.html %} <script type="text/javascript"> var $states = $(".js-source-states"); var statesOptions = $states.html(); $states.remove(); $(".js-states").append(statesOptions); $("[data-fill-from]").each(function () { var $this = $(this); var codeContainer = $this.data("fill-from"); var $container = $(codeContainer); var code = $.trim($container.html()); $this.text(code); $this.addClass("prettyprint linenums"); }); prettyPrint(); $.fn.select2.amd.require([ "select2/core", "select2/utils", "select2/compat/matcher" ], function (Select2, Utils, oldMatcher) { var $basicSingle = $(".js-example-basic-single"); var $basicMultiple = $(".js-example-basic-multiple"); var $limitMultiple = $(".js-example-basic-multiple-limit"); var $dataArray = $(".js-example-data-array"); var $dataArraySelected = $(".js-example-data-array-selected"); var data = [ { id: 0, text: 'enhancement' }, { id: 1, text: 'bug' }, { id: 2, text: 'duplicate' }, { id: 3, text: 'invalid' }, { id: 4, text: 'wontfix' } ]; var $ajax = $(".js-example-data-ajax"); var $disabledResults = $(".js-example-disabled-results"); var $tags = $(".js-example-tags"); var $matcherStart = $('.js-example-matcher-start'); var $diacritics = $(".js-example-diacritics"); var $language = $(".js-example-language"); $.fn.select2.defaults.set("width", "100%"); $basicSingle.select2(); $basicMultiple.select2(); $limitMultiple.select2({ maximumSelectionLength: 2 }); function formatState (state) { if (!state.id) { return state.text; } var $state = $( '<span>' + '<img src="vendor/images/flags/' + state.element.value.toLowerCase() + '.png" class="img-flag" /> ' + state.text + '</span>' ); return $state; }; $(".js-example-templating").select2({ templateResult: formatState, templateSelection: formatState }); $dataArray.select2({ data: data }); $dataArraySelected.select2({ data: data }); function formatRepo (repo) { if (repo.loading) return repo.text; var markup = "<div class='select2-result-repository clearfix'>" + "<div class='select2-result-repository__avatar'><img src='" + repo.owner.avatar_url + "' /></div>" + "<div class='select2-result-repository__meta'>" + "<div class='select2-result-repository__title'>" + repo.full_name + "</div>"; if (repo.description) { markup += "<div class='select2-result-repository__description'>" + repo.description + "</div>"; } markup += "<div class='select2-result-repository__statistics'>" + "<div class='select2-result-repository__forks'><i class='fa fa-flash'></i> " + repo.forks_count + " Forks</div>" + "<div class='select2-result-repository__stargazers'><i class='fa fa-star'></i> " + repo.stargazers_count + " Stars</div>" + "<div class='select2-result-repository__watchers'><i class='fa fa-eye'></i> " + repo.watchers_count + " Watchers</div>" + "</div>" + "</div></div>"; return markup; } function formatRepoSelection (repo) { return repo.full_name \|\| repo.text; } $ajax.select2({ ajax: { url: "https://api.github.com/search/repositories", dataType: 'json', delay: 250, data: function (params) { return { q: params.term, // search term page: params.page }; }, processResults: function (data, params) { // parse the results into the format expected by Select2 // since we are using custom formatting functions we do not need to // alter the remote JSON data, except to indicate that infinite // scrolling can be used params.page = params.page \|\| 1; return { results: data.items, pagination: { more: (params.page * 30) < data.total_count } }; }, cache: true }, escapeMarkup: function (markup) { return markup; }, minimumInputLength: 1, templateResult: formatRepo, templateSelection: formatRepoSelection }); $(".js-example-disabled").select2(); $(".js-example-disabled-multi").select2(); $(".js-example-responsive").select2(); $disabledResults.select2(); $(".js-example-programmatic").select2(); $(".js-example-programmatic-multi").select2(); $eventSelect.select2(); $tags.select2({ tags: ['red', 'blue', 'green'] }); $(".js-example-tokenizer").select2({ tags: true, tokenSeparators: [',', ' '] }); function matchStart (term, text) { if (text.toUpperCase().indexOf(term.toUpperCase()) == 0) { return true; } return false; } $matcherStart.select2({ matcher: oldMatcher(matchStart) }); $(".js-example-basic-hide-search").select2({ minimumResultsForSearch: Infinity }); $diacritics.select2(); $language.select2({ language: "es" }); $(".js-example-theme-single").select2({ theme: "classic" }); $(".js-example-theme-multiple").select2({ theme: "classic" }); $(".js-example-rtl").select2(); }); </script>	6.57 KB	2026-02-12 14:54
📁 images	-	2026-02-12 14:54
📄 index.html --- layout: home title: Select2 - The jQuery replacement for select boxes slug: home --- <main class="jumbotron" role="main"> <div class="container text-center"> <h1>Select2</h1> <p class="lead"> The jQuery replacement for select boxes </p> <p> <a href="https://github.com/select2/select2/releases" class="btn btn-outline-inverse btn-lg"> Download Select2 </a> </p> <p class="version"> Currently v4.0.1</a> </p> </div> </main> {% include notice-previous.html %} <div class="container"> <section id="lead" class="lead"> Select2 gives you a customizable select box with support for searching, tagging, remote data sets, infinite scrolling, and many other highly used options. </section> <hr class="half-rule"> <div class="s2-docs-featurette"> <div class="row"> <div class="col-sm-4"> <i class="fa fa-language"></i> <h4>In your language</h4> <p> Select2 comes with support for <a href="examples.html#rtl">RTL environments</a>, <a href="examples.html#diacritics">searching with diacritics</a> and <a href="examples.html#language">over 40 languages</a> built-in. </p> </div> <div class="col-sm-4"> <i class="fa fa-database"></i> <h4>Remote data support</h4> <p> <a href="examples.html#data-ajax">Using AJAX</a> you can efficiently search large lists of items. </p> </div> <div class="col-sm-4"> <i class="fa fa-paint-brush"></i> <h4>Fits in with your theme</h4> <p> Fully skinnable, CSS built with Sass and an <a href="https://github.com/fk/select2-bootstrap-theme">optional theme for Bootstrap 3</a>. </p> </div> </div> <div class="row"> <div class="col-sm-4"> <i class="fa fa-plug"></i> <h4>Fully extensible</h4> <p> The <a href="announcements-4.0.html#plugin-system">plugin system</a> allows you to easily customize Select2 to work exactly how you want it to. </p> </div> <div class="col-sm-4"> <i class="fa fa-tag"></i> <h4>Dynamic item creation</h4> <p> Allow users to type in a new option and <a href="examples.html#tags">add it on the fly</a>. </p> </div> <div class="col-sm-4"> <i class="fa fa-html5"></i> <h4>Full browser support</h4> <p>Support for both modern and legacy browsers is built-in, even including Internet Explorer 8.</p> </div> </div> </div> <hr class="half-rule"> <section id="getting-started"> <h2> Getting started with Select2 </h2> <p> In order to use Select2, you must include the JavaScript and CSS file on your website. You can get these files built for you from many different locations. </p> <h3> Using Select2 from a CDN </h3> <p> Select2 is hosted on both the <a href="https://cdnjs.com/libraries/select2">cdnjs</a> and <a href="http://www.jsdelivr.com/#!select2">jsDelivr</a> CDNs, allowing you to quickly include Select2 on your website. </p> <ol> <li> <p> Include the following lines of code in the <code><head></code> section of your HTML. </p> <pre class="code prettyprint"> <link href="//cdnjs.cloudflare.com/ajax/libs/select2/4.0.1/css/select2.min.css" rel="stylesheet" /> <script src="//cdnjs.cloudflare.com/ajax/libs/select2/4.0.1/js/select2.min.js"></script> </pre> <div class="alert alert-info"> <i class="fa fa-info-circle"></i> Immediately following a new release, it takes some time for CDNs to catch up and get the new versions live on the CDN. </div> </li> <li> <p> Initialize Select2 on the <code><select></code> element that you want to make awesome. </p> <pre class="code prettyprint"> <script type="text/javascript"> $('select').select2(); </script> </pre> </li> <li> Check out the <a href="examples.html">examples page</a> to start using the additional features of Select2. </li> </ol> <h3> Downloading the code locally </h3> <p> In some situations, you can't use Select2 from a CDN and you must include the files through your own static file servers. </p> <ol> <li> <p> <a href="https://github.com/select2/select2/tags"> Download the code </a> from GitHub and copy the <code>dist</code> directory to your project. </p> </li> <li> <p> Include the following lines of code in the <code><head></code> section of your HTML. </p> <pre class="code prettyprint"> <link href="path/to/select2.min.css" rel="stylesheet" /> <script src="path/to/select2.min.js"></script> </pre> </li> <li> Check out the <a href="examples.html">examples page</a> to start using the additional features of Select2. </li> </ol> </section> <section id="builds"> <h2> The different Select2 builds </h2> <p> Select2 provides multiple builds that are tailored to different environments where it is going to be used. If you think you need to use Select2 in a nonstandard environment, like when you are using AMD, you should read over the list below. </p> <table class="table table-bordered table-striped"> <thead> <tr> <th>Build name</th> <th>When you should use it</th> </tr> </thead> <tbody> <tr id="builds-standard"> <td> Standard (<code>select2.js</code> / <code>select2.min.js</code>) </td> <td> This is the build that most people should be using for Select2. It includes the most commonly used features. </td> </tr> <tr id="builds-full"> <td> Full (<code>select2.full.js</code> / <code>select2.full.min.js</code>) </td> <td> You should only use this build if you need the additional features from Select2, like the <a href="options.html#compatibility">compatibility modules</a> or recommended includes like <a href="https://github.com/jquery/jquery-mousewheel">jquery.mousewheel</a> </td> </tr> </tbody> </table> </section> </div>	6.57 KB	2026-02-12 14:54
📄 options-old.html --- layout: default title: Options - Select2 slug: options --- <section class="jumbotron"> <div class="container"> <h1> Options </h1> </div> </section> <div class="container s2-docs-container"> <div class="row"> <div class="col-md-9" role="main"> {% include options-old/core-options.html %} {% include options-old/dropdown.html %} {% include options-old/events.html %} {% include options-old/adapters.html %} {% include options-old/setting-default-options.html %} {% include options-old/backwards-compatibility.html %} </div> <div class="col-md-3" role="complementary"> {% include nav/options-old.html %} </div> </div> </div> <script type="text/javascript"> prettyPrint(); </script>	772 B	2026-02-12 14:54
📄 options.html --- layout: default title: Options - Select2 slug: options --- <section class="jumbotron"> <div class="container"> <h1> Options </h1> <p class="lead"> Select2 supports a wide variety of options that allow you to customize it to your needs. </p> </div> </section> <div class="container s2-docs-container"> <div class="row"> <div class="col-md-9" role="main"> {% include options/introduction.html %} {% include options/core.html %} {% include options/data.html %} {% include options/selections.html %} {% include options/dropdown.html %} {% include options/events.html %} {% include options/compatibility.html %} </div> <div class="col-md-3" role="complementary"> {% include nav/options.html %} </div> </div> </div> <script type="text/javascript"> prettyPrint(); </script>	876 B	2026-02-12 14:54
📁 vendor	-	2026-02-12 14:54

Terminal