Libraries tagged by row

RowGroup for DataTables with styling for jQueryUI

Go to Download

RowGroup for DataTables with styling for jQueryUI

Go to Download

A Laravel Nova row field.

Go to Download

Create dynamic HTML tables that can calculate column data, like Excel, and look good doing it, with or without CSS Boostrap.

Go to Download

conrete5 Express Batch Importer

Go to Download

prune your Versions table, keeping many, but the further you go back in time, the less versions you keep. You can also keep versions were a specific field was changed (e.g. Content, Price, or Title)

Go to Download

Package Laravel per la gestione dei filtri di sicurezza perimetrale basati sui modelli Eloquent e sulle competenze utente.

Go to Download

DataTables and all of its extensions.

Go to Download

Attribute-driven transactions and row-level locks for Laravel: retries, backoff, HTTP-aware rollbacks, and FOR UPDATE/SHARE on route model binding.

Go to Download

Editor for DataTables with styling for DataTables

Go to Download

Editor for DataTables with styling for Bootstrap5

Go to Download

Editor for DataTables

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

Finds spatie/laravel-medialibrary media rows without a file and files without a media row, and safely removes them.

Go to Download