Libraries tagged by Overridden

Circuit breaker pattern for PHP with multiple storage adapters, event system, and manual override.

Go to Download

A default Easy Email template configured to override all emails sent from the site.

Go to Download

Easy Email templates that replicate and override the content of emails sent by Drupal core with HTML-formatted versions.

Go to Download

A professional, framework-agnostic modular architecture for Laravel 11+. Features zero-config autoloading, 29+ Artisan command overrides, and seamless Vite integration.

Go to Download

Go to Download

Overrides Laravel and WordPress translation helpers so a single __() serves both catalogues

Go to Download

Override your seo markup on the fly

Go to Download

TYPO3 Language File Editor for XLIFF & Overrides - TYPO3 backend module for managing XLIFF language files with translation-state overview, per-language and per-constant editing (edit/add/rename/delete), metadata maintenance, and global key/value search across extensions. Includes extension and override modes with locallangXMLOverride integration, role-based language permissions, and migration support for legacy override files.

Go to Download

Configuration access helper and environment manager

Go to Download

Fast, Efficient permission system for controlling access to your website resources

Go to Download

A module so Magento saves orders from multiple sources in one table, overrides the default order list in customer backend.

Go to Download

Provides a configuration override for SMTP credentials for use with Pantheon Hosting.

Go to Download

Provides rulesets for phpmd, phpcs and eslint that overrides some Magento sniffs and provides some new ones as well

Go to Download

An override of FosUserBundle to provide authentication on Open Orchestra

Go to Download

Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.

Go to Download