Libraries tagged by json fields

Laravel package providing a reusable trait for multilingual search in Eloquent JSON fields.

Go to Download

A Laravel-orchid package for translatable models using JSON fields

Go to Download

Validation module (Field, Fieldset, Inner fieldsets, json fieldsets validators and html quote support)

Go to Download

Store your spatie/laravel-translation-loader powered translations in columns instead of in a json field

Go to Download

Additional Data tab for Sulu CMS Categories — generic JSON field with configurable forms

Go to Download

Eloquent model class for translating MySQL flexible JSON fields into native object attributes and vise-versa

Go to Download

Adds the methods: md5AsComputed, jsonFieldStoredAs, manyJsonFieldsStoredAs, concatWsStoredAs.

Go to Download

Automatic translation of json multilingual fields for Laravel.

Go to Download

Simple behavior to use json-like fields on bbdd

Go to Download

kegunaanya untuk memberikan hasil return berupa json, untuk field apa aja yang menyebabkan error saat request, beserta message error dan old value.

Go to Download

Map fields from json files to Easy Property Listings WP plugin meta fields

Go to Download

API Resources & Transformers — PHP 8.4 property hooks, JSON:API, attribute-driven field control, pagination, and OpenAPI schema generation

Go to Download

WP CLI sync for ACF fields from local JSON

Go to Download

Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download

extends of illuminate/database and illuminate/encryption to handle field data stored in json and encrypted. encrypted via $_ENV[CRYPT.KEY]

Go to Download