Libraries tagged by repeat

Flexible Content & Repeater Fields for Laravel Nova.

Go to Download

Flexible Content & Repeater Fields for Laravel Nova.

Go to Download

Blocks Content & Repeater Fields for Laravel Nova.

Go to Download

A Laravel package for creating secure codes, providing unique and random n-digit codes for any use.

Go to Download

TYPO3 Form Enhancer, Spam Protection & Submission Overview/Export Module - Enhances TYPO3 EXT:form with repeatable containers, linked checkboxes, custom field identifiers, PDF form filling, submission storage with backend/CLI CSV export, a backend submission module with translation-aware grouping and restore support, upload rename and cleanup workflows, form translation handling, and spam protection through sg_captcha, honeypot and link-spam checks.

Go to Download

WP_Field v4 HTML fields library for WordPress with fluent API, 52 field types, legacy compatibility, React/Vanilla integrations, conditional logic, and storage strategies.

Go to Download

Laravel form components with repeatable groups that actually work — searchable selects, a chainable type-aware JS API, full old()/validation/CSRF integration, and a zero-CSS-framework theme. Zero JS dependencies.

Go to Download

A Symfony2 bundle providing helpers to ease usage of common patterns.

Go to Download

This Craft plugin will generate an array of dates between a start and end date based on frequency.

Go to Download

A modern Laravel Nova field for managing a sortable list of scalar values (tags, emails, steps…) stored as JSON.

Go to Download

An efficient tree structure for finding duplicate number values (ex. phone numbers) in fixed-length strings

Go to Download

This framework plugin makes adding post types with taxonomies and meta to WordPress very simple, yet flexible.

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

Are you often tired to repeat static choices like gender or civility in your apps ?

Go to Download

Repeater widget for yii2 tabular

Go to Download