Libraries tagged by required

Magento 2 Multiple Wishlists module helps your customers make, share & manage as many wishlists as required making it more convenience for special needs. They can move wishlist items directly to the cart & proceed to checkout. Create unlimited wishlists. Create a new wishlist & use existing wishlist.

Go to Download

The Inspeya Google Reviews module is designed to integrate Google Reviews into your Magento 2 store. This module allows you to display customer reviews from Google directly on your product pages, enhancing credibility and trustworthiness. With full backend manageability, you can easily configure and display reviews, providing a seamless integration that enhances the customer shopping experience. Key features include real-time review updates, customizable display options. Required dependencies include mhinspeya/backend-mod for support configuration.

Go to Download

The MHinspeya Inspeya Filter ShopBy module is a powerful enhancement for Magento 2, designed to improve the catalog navigation experience on the list page. This module provides advanced layer navigation capabilities, allowing users to filter products seamlessly and efficiently. The Inspeya Filter ShopBy module is fully manageable from the Magento backend, giving store administrators complete control over the filter options and their configurations. Key features include advanced layer navigation, backend manageability, SEO-friendly filter options, flexible filter types, and performance optimization. Required dependencies include mhinspeya/backend-mod, mhinspeya/inspeya-filter-base, mhinspeya/inspeya-filter-shop-by-seo, mhinspeya/inspeya-filter-shop-by-page, mhinspeya/inspeya-filter-shop-by-brand, and mhinspeya/inspeya-filter-shop-by-base. For more information, visit https://inspeya.com.

Go to Download

You can create your repository structure with a single command and all required files.

Go to Download

Exiftool is a library for reading, writing and editing meta information. This package is not PHP, but required for the main PHP driver : PHP Exiftool

Go to Download

The MehrAlsNix\ZF\Cache\Storage\Adapter\Couchbase adapter stores cache items over the couchbase protocol. It’s using the required PHP extension couchbase which is based on Libcouchbase.

Go to Download

Rinvex common support helpers, contracts, and traits required by various Rinvex packages. Validator functionality, and basic controller included out-of-the-box.

Go to Download

Rinvex Subscriptions is a flexible plans and subscription management system for Laravel, with the required tools to run your SAAS like services efficiently. It's simple architecture, accompanied by powerful underlying to afford solid platform for your business.

Go to Download

List the installed packages, the required packages and the reasons for installing the packages.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

RedisController is a high performance PHP Redis client which implement some of the latest Redis functionalities. It is completely written in PHP and does not required anything else than PHP 5.4

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

An autoloader that enables standard plugins to be required just like must-use plugins. The autoloaded plugins are included during mu-plugin loading. An asterisk (*) next to the name of the plugin designates the plugins that have been autoloaded.

Go to Download

A Laravel Package Biscotto, will help you enable and disable cookies or scripts that required gdpr compliance.

Go to Download

Rinvex Subscriptions is a flexible plans and subscription management system for Laravel, with the required tools to run your SAAS like services efficiently. It's simple architecture, accompanied by powerful underlying to afford solid platform for your business.

Go to Download