PHP 7.4+<\/li>\n<\/ul>\n\nUsage<\/h3>\n\n
Go to LUKDEV Custom Data Tables<\/strong> in the admin menu. You need the manage_options<\/code> capability.<\/p>\n\n\n- Create a structure.<\/strong> Give it a name and, optionally, a slug (the name is used when the slug is empty). Then add fields. A field's key is generated from its label, for example
Hero title<\/code> becomes hero_title<\/code>. Keys must be unique within a structure.<\/li>\n- Add rows.<\/strong> After you save the structure, the rows editor opens. Rows are saved one at a time, can be moved up or down, and can be deleted.<\/li>\n
- Fetch the data<\/strong> from the REST API (see below).<\/li>\n<\/ol>\n\n
Deleting a structure also deletes all its rows.<\/p>\n\n
Field types<\/h3>\n\n
Each type is listed with its settings, the value stored in the database and the value returned by the API.<\/p>\n\n
\ntext<\/code>: no settings. Stored: string. API: string.<\/li>\ntextarea<\/code>: no settings. Stored: string. API: string.<\/li>\nwysiwyg<\/code>: no settings. Stored: HTML (wp_kses_post<\/code>). API: string.<\/li>\nnumber<\/code>: no settings. Stored: numeric string. API: string.<\/li>\nemail<\/code>: no settings. Stored: string. API: string.<\/li>\nurl<\/code>: no settings. Stored: string. API: string.<\/li>\nboolean<\/code>: no settings. Stored: \"1\"<\/code> \/ \"0\"<\/code>. API: true<\/code> \/ false<\/code>.<\/li>\nselect<\/code>: settings: options, default. Stored: option value. API: string.<\/li>\nradio<\/code>: settings: options, default. Stored: option value. API: string.<\/li>\ncheckbox<\/code>: settings: options, defaults. Stored: list of option values. API: array of strings.<\/li>\nimage<\/code>: no settings. Stored: attachment ID. API: image object or null<\/code>.<\/li>\ncolor_picker<\/code>: settings: default, opacity, return format (string<\/code> \/ array<\/code>). Stored: #rrggbb<\/code> or rgba(r,g,b,a)<\/code>. API: string, or { red, green, blue, alpha }<\/code>.<\/li>\ndate_picker<\/code>: settings: display format, return format, first day of week. Stored: Ymd<\/code>. API: date in the return format.<\/li>\npost_object<\/code>: settings: post types, multiple. Stored: post ID or list of IDs. API: post object, null<\/code>, or array of posts.<\/li>\nrelationship<\/code>: settings: post types, filters (search \/ post type \/ taxonomy), max. Stored: list of post IDs. API: array of posts.<\/li>\nlink<\/code>: no settings. Stored: { page, url, title, target }<\/code>. API: { title, url, target }<\/code> or null<\/code>.<\/li>\nrepeater<\/code>: settings: sub-fields. Stored: list of items. API: array of objects.<\/li>\n<\/ul>\n\nNotes:<\/p>\n\n
\n- Options:<\/strong> an option without a value uses its label as the value, and the other way round.<\/li>\n
- Repeaters<\/strong> can't be nested. A repeater added as a sub-field is saved as
text<\/code>.<\/li>\n- Post object and relationship fields<\/strong> accept any public post type (except attachments) when no post types are selected. The API returns published posts only. Drafts and private posts picked in the admin are left out.<\/li>\n
- Link fields<\/strong> point to either a page or a custom URL. The page wins if both are set. The page's title is used when the link text is empty.<\/li>\n
- Date picker fields<\/strong> use PHP date formats. The default for both display and return is
d\/m\/Y<\/code>.<\/li>\n- Changing a field's type or settings keeps saved data where possible.<\/strong> For example, a single post object becomes a list when multiple<\/em> is turned on, and a select value becomes a one-item checkbox list. Fields saved before field types existed are treated as
textarea<\/code>.<\/li>\n<\/ul>\n\nREST API<\/h3>\n\n
Both endpoints are public (no authentication) and read-only.<\/p>\n\n
GET \/wp-json\/ldcdt\/v1\/data<\/code><\/h3>\n\nLists all structures.<\/p>\n\n
[\n {\n \"name\": \"Team\",\n \"slug\": \"team\",\n \"fields\": [\n { \"key\": \"name\", \"label\": \"Name\", \"type\": \"text\" },\n { \"key\": \"photo\", \"label\": \"Photo\", \"type\": \"image\" }\n ],\n \"url\": \"https:\/\/example.com\/wp-json\/ldcdt\/v1\/data\/team\"\n }\n]\n<\/code><\/pre>\n\nGET \/wp-json\/ldcdt\/v1\/data\/{slug}<\/code><\/h3>\n\nReturns one structure with its rows, in the order set in the admin. Each item has an id<\/code> plus one property per field key. Returns 404<\/code> (ldcdt_not_found<\/code>) for an unknown slug.<\/p>\n\n{\n \"name\": \"Team\",\n \"slug\": \"team\",\n \"fields\": [ ... ],\n \"items\": [\n {\n \"id\": 1,\n \"name\": \"Jane Doe\",\n \"photo\": {\n \"id\": 42,\n \"url\": \"https:\/\/example.com\/app\/uploads\/jane.jpg\",\n \"alt\": \"\",\n \"width\": 1200,\n \"height\": 800,\n \"sizes\": {\n \"thumbnail\": { \"url\": \"...\", \"width\": 150, \"height\": 150 }\n }\n }\n }\n ]\n}\n<\/code><\/pre>\n\nShapes of the other object values:<\/p>\n\n
\n- Post<\/strong> (
post_object<\/code>, relationship<\/code>): { id, type, slug, title, url, date }<\/code>, where date<\/code> is an ISO 8601 GMT date.<\/li>\n- Link:<\/strong>
{ title, url, target }<\/code>, where target<\/code> is \"\"<\/code> or \"_blank\"<\/code>.<\/li>\n<\/ul>\n\nProject structure<\/h3>\n\nlukdev-custom-data-tables.php Plugin header, constants, bootstrap\nincludes\/\n install.php Table names, creation and upgrades\n fields.php Field types, sanitization and API formatting\n data.php Reading structures and rows\n rest-api.php REST routes (ldcdt\/v1)\nadmin\/\n admin.php Menu, assets, page router, notices\n handlers.php admin-post.php form handlers, post search AJAX\n partials\/ List, structure builder and rows editor screens\n css\/, js\/ Admin assets\n vendor\/select2\/ Select2 4.1.0 (MIT)<h3>Extending<\/h3>\n<\/code><\/pre>\n\n- To add a field type, register it in ldcdt_field_types()<\/code>. Then handle its settings in ldcdt_sanitize_fields()<\/code>, its value in ldcdt_sanitize_value()<\/code> and ldcdt_format_value()<\/code>, and its inputs in the admin partials and admin\/js\/admin.js<\/code>.\n- Everything uses the ldcdt<\/code> prefix: functions (ldcdt_<\/code>), constants (LDCDT_<\/code>), tables, options, the REST namespace, CSS classes and JS. Sites upgraded from Custom Headless Data (old chd<\/code> \/ chdata<\/code> prefixes) have their tables and option renamed automatically. Admin form actions are ldcdt_save_structure<\/code>, ldcdt_delete_structure<\/code>, ldcdt_save_row<\/code>, ldcdt_delete_row<\/code> and ldcdt_move_row<\/code>. The post search AJAX action is ldcdt_search_posts<\/code>.<\/p>\n\n\n\n- Copy the
lukdev-custom-data-tables<\/code> directory to wp-content\/plugins\/<\/code> (web\/app\/plugins\/<\/code> on Bedrock).<\/li>\n- Activate LUKDEV Custom Data Tables<\/strong> in Plugins<\/em>.<\/li>\n<\/ol>\n\n
On activation the plugin creates two tables. If the plugin is already active and the stored ldcdt_db_version<\/code> option differs from LDCDT_DB_VERSION<\/code>, it creates or updates them on plugins_loaded<\/code>.<\/p>\n\n\n{prefix}ldcdt_structures<\/code>: id<\/code>, name<\/code>, slug<\/code> (unique), fields<\/code> (JSON field definitions), created_at<\/code><\/li>\n{prefix}ldcdt_rows<\/code>: id<\/code>, structure_id<\/code>, data<\/code> (JSON values keyed by field key), sort_order<\/code><\/li>\n<\/ul>\n\n\n\nIs the REST API protected?<\/h3><\/dt>\nNo. Both endpoints are public and read-only, so don't store private data in a structure. Editing data in the admin requires the manage_options<\/code> capability.<\/p><\/dd>\nWhere is the data stored?<\/h3><\/dt>\nIn two custom tables, {prefix}ldcdt_structures<\/code> and {prefix}ldcdt_rows<\/code>, not in post meta or options.<\/p><\/dd>\nCan I nest repeaters?<\/h3><\/dt>\nNo. A repeater added as a sub-field of another repeater is saved as a text<\/code> field.<\/p><\/dd>\nWhy doesn't a post I picked show up in the API?<\/h3><\/dt>\nThe API returns published posts only. Drafts and private posts picked in a post object or relationship field are left out.<\/p><\/dd>\n
What happens to saved data when I change a field's type?<\/h3><\/dt>\nThe plugin keeps the data where possible. For example, a select value becomes a one-item checkbox list, and a single post object becomes a list when multiple<\/em> is turned on.<\/p><\/dd>\n\n<\/dl>\n\n\n0.1.0<\/h3>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Define custom data structures (fields) and manage rows of data exposed through the REST API.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/379263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=379263"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lukdev"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=379263"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=379263"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=379263"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=379263"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=379263"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=379263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}