Libraries tagged by Ensue

The MHinspeya Hyva Picalike module provides advanced functionality to display similar products on the product detail page. It is designed to enhance user experience by showcasing related products that might interest customers based on their current selection. This module is fully compatible with Hyva themes, ensuring seamless integration and optimized performance.

Go to Download

The MHinspeya Hyva Google Reviews module integrates Google Reviews into your Magento 2 store. This module allows you to display Google Reviews on your product and category pages, enhancing customer trust and engagement. It is fully compatible with Hyva themes, ensuring a seamless and visually appealing integration.

Go to Download

The Laravel Logger project is a robust logging solution tailored for Laravel applications, designed to provide comprehensive monitoring, tracking, and analysis of system activities and events. Developed with the Laravel framework, this logging system offers seamless integration, ensuring smooth operation within Laravel-based projects.

Go to Download

The MessageMedia Signature Key API provides a number of endpoints for managing key used to sign each unique request to ensure security and the requests can't (easily) be spoofed. This is similar to using HMAC in your outbound messaging (rather than HTTP Basic).

Go to Download

A powerful and modular backend core to kickstart your projects with essential functionalities. Includes authentication, role management, database utilities, and more, all designed to save development time and ensure best practices.

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

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

Image Flipper by MageINIC, Image Flipper provides effortless configuration through user-friendly settings, allowing you to choose from a variety of captivating flip effects like horizontal, vertical, and rotational flips. This extension seamlessly integrates with your store's theme, ensuring a cohesive design.

Go to Download

Hyva Image Flipper For by MageINIC, Image Flipper provides effortless configuration through user-friendly settings, allowing you to choose from a variety of captivating flip effects like horizontal, vertical, and rotational flips. This extension seamlessly integrates with your store's theme, ensuring a cohesive design.

Go to Download

Hyva Cookie Notification by MageINIC.Cookie Notification extension is a vital tool for websites utilizing cookies to collect user data. It ensures compliance with privacy regulations while transparently informing users about cookie usage. Customize consent messages, button text, and popup appearance, all while offering flexible event options and auto-hide functionality for experience.

Go to Download

Delete Orders by MageINIC, The Magento 2 Delete Orders extension empowers administrators to efficiently remove unwanted orders, invoices, shipments, and credit memos from the backend, ensuring a streamlined and organized e-commerce operation. Simplify order management, maintain data consistency, and enjoy the flexibility to enable or disable deletion features as needed.

Go to Download

Cookie Notification by MageINIC.Cookie Notification extension is a vital tool for websites utilizing cookies to collect user data. It ensures compliance with privacy regulations while transparently informing users about cookie usage. Customize consent messages, button text, and popup appearance, all while offering flexible event options and auto-hide functionality for experience.

Go to Download

A simple proxy module to ensure your Elastic API keys aren't leaked.

Go to Download

ACL Permissions is a Laravel package that provides a robust and flexible access control system based on ACL (Access Control List). It allows you to define and manage permissions in a granular way for users and groups, ensuring that each resource is accessed only by those with proper authorization.

Go to Download

Email sending package based on PHPMailer, simplifying the process of sending SMTP emails in PHP applications. It offers integration with environment variables using the lithemodules/support-env package, ensuring secure and flexible configuration.

Go to Download