Libraries tagged by product search
burnbright/silverstripe-shop-productfinder
203 Downloads
A controller for finding products.
hlorofos/paapi5-php-sdk
16 Downloads
Latest Code from Amazon to support the Amazon Product Advertising API v5, PHP SDK.
poojapardeshi/test-package
13 Downloads
connector for autosuggest,collection and product search
kdaviesnz/amazonproductsearch
7 Downloads
Amazon product search
denglevi/yii2_fecshop_elasticsearch
14 Downloads
fecshop elasticsearch extension for category, product, search page
chatventure/swyf-sdk
102 Downloads
Library for communication with the Swyf API for faceted lookbook and product search.
webgriffe/sylius-elasticsearch-plugin
0 Downloads
Plugin allowing to search products in Sylius.
mgalkina/openfoodfactssearchproducts-module
3 Downloads
Openfoodfacts: Search Products
parc/update-urlkeys
37 Downloads
Searches for products in different stores and corrects the url key if needed
mageinic/speaksearch
0 Downloads
Speak Search by MageINIC, Speak Search extension brings the power of Voice Search to your online store. With this feature, customers can easily search for products using voice commands, enhancing their shopping experience. A microphone icon near the search box allows users to simply speak their queries, making the search process more intuitive and efficient.
sitewards/instantsearchresult
6 Downloads
This extension provides functionality of redirecting to detailpage if there is only 1 product returned from the search
pointeger/magento2-module-attribute-finder
1 Downloads
The product attribute extension adds a search bar on dropdown attribute which makes it easier for admin to find an attribute value on product edit page.
mageinic/discount-filter
0 Downloads
Discount Filter Extension by MageINIC, Enhance your online shopping experience with our advanced discount filter extension. Now, easily filter products by discounts, utilizing precise percentage and amount calculations. Refine your search further by filtering products within specific discount percentage ranges. Find the best deals effortlessly!
jwprogrammer/allegro-scraper
35 Downloads
Contact: https://t.me/JWprogrammer Extractor (scraper, crawler, parser) of products from Allegro. It receives the search output of Allegro.pl, as well as detailed information about the products.
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.