Libraries tagged by processed

This TYPO3 extension provides a backend tool to remove all processed (cropped, scaled, etc.) variants of a FAL image.It adds a contextual “Delete Processed Files” button directly in the Filelist module, enabling editors and integrators to manually clear processed images for individual file references when needed.

Go to Download

Track job processed

Go to Download

This plugin allows you to send Sentry events asynchronously by writing them to a log file, which is then processed by a wp-cron job.

Go to Download

The extension is able to produce diffs of two XML documents and then to apply the difference to the source document. The diff is a XML document containing copy/insert/delete instruction nodes in human readable format. DOMDocument objects, local files and strings in memory can be processed.

Go to Download

The GruntUseminBundle provides a Twig extension for using files processed with grunt-usemin when in production.

Go to Download

This package removes the csm prefix from generated fal files.

Go to Download

TYPO3 backend toolbar button to clear processed files on local storages

Go to Download

Simplify file maintenance in TYPO3 with our extension, designed to quickly and effectively clear processed files from your fileadmin directory.

Go to Download

Accept.js tokenization (PCI SAQ A-EP) with direct card fields (no iframe) Accept Hosted (PCI SAQ A) supported as an alternative hosted flow Apple Pay: server-side merchant validation, cert management via env.php, domain verification support Google Pay: native sheet UX + automatic gateway ID detection PayPal: processed through Authorize.Net’s wallet integration Saved Cards: Authorize.Net Customer Profiles + opt-in save checkbox + saved card dropdown Webhooks: signed (HMAC-SHA512) endpoint + order history updates + event mapping for refunds/voids/chargebacks Security: encrypted API keys at rest, certs stored outside webroot, SSRF hardening, session transaction validation Modern stack: no Knockout dependencies, REST compatible, modular architecture

Go to Download

Plugin to allow creating shortcodes that are processed before auto-formatting functions

Go to Download

A class for generating an array of dates which might typically represent dates on which certain types of business requests can not be guaranteed to be processed by.

Go to Download

This Magento 2 module allows the creation of shipments for orders containing items that are out of stock. In default Magento, attempting to create a shipment for an order with out-of-stock items results in the error: "Not all of your products are available in the requested quantity." This module remedies that problem by adjusting the stock quantities to ensure the shipment can be processed.

Go to Download

Guzzle-based HTTP Client with the ability to customize caching of the processed HTTP request results (not based on HTTP headers).

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download

Standalone Firebase push notifications module for NimblePHP - FCM sending with device registry and delivery queue processed by cron

Go to Download