{"id":403938,"date":"2026-11-14T10:32:47","date_gmt":"2026-11-14T10:32:47","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/custom-fields-studio\/"},"modified":"2026-11-15T08:12:37","modified_gmt":"2026-11-15T08:12:37","slug":"fieldloom","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/fieldloom\/","author":23604616,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.14.0","stable_tag":"0.14.0","tested":"7.1.4","requires":"6.0","requires_php":"8.0","requires_plugins":null,"header_name":"Fieldloom Custom Fields","header_author":"Sapatarshi Samanta","header_description":"Add custom fields to posts, pages, users, terms, options pages and Gutenberg blocks. Repeater, flexible content, clone, conditional logic, JSON import\/export and a REST API.","last_updated":"2026-11-15 08:12:37","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/Sapta2022\/custom-fields-studio","header_author_uri":"https:\/\/github.com\/Sapta2022","rating":0,"author_block_rating":0,"active_installs":0,"downloads":95,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.14.0":{"tag":"0.14.0","author":"sapta2022","date":"2026-11-15 08:12:37","revision":3802891}},"upgrade_notice":{"0.14.0":"<p>Renamed to Fieldloom Custom Fields. The shortcode is now [cfstudio] and local JSON files move to the uploads folder; turn local JSON on again under Tools.<\/p>","0.13.1":"<p>Fixes custom blocks losing their field group after the 0.13.0 prefix rename.<\/p>","0.13.0":"<p>Template functions were renamed from cfs_* to cfstudio_*. Update your theme code after upgrading; saved data is migrated automatically.<\/p>","0.12.4":"<p>Fixes repeater and media fields inside custom blocks on current WordPress versions.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3802746,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3802746,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3802746,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3802746,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3802746,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.14.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[4121,2010,2238,22028,2244],"plugin_category":[],"plugin_contributors":[292705],"plugin_business_model":[],"class_list":["post-403938","plugin","type-plugin","status-publish","hentry","plugin_tags-blocks","plugin_tags-custom-fields","plugin_tags-flexible-content","plugin_tags-options-page","plugin_tags-repeater","plugin_contributors-sapta2022","plugin_committers-sapta2022"],"banners":{"banner":"https:\/\/ps.w.org\/fieldloom\/assets\/banner-772x250.png?rev=3802746","banner_2x":"https:\/\/ps.w.org\/fieldloom\/assets\/banner-1544x500.png?rev=3802746","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/fieldloom\/assets\/icon.svg?rev=3802746","icon":"https:\/\/ps.w.org\/fieldloom\/assets\/icon.svg?rev=3802746","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Fieldloom lets you build field groups in the WordPress admin and show them wherever you need them: on posts and pages, on user profiles, on taxonomy terms, on options pages and inside your own Gutenberg blocks.<\/p>\n\n<p><strong>Field types (35)<\/strong><\/p>\n\n<p>Text, textarea, WYSIWYG, number, range, email, URL, password, select, checkbox, radio, button group, true\/false, image, file, gallery, date, time, date-time, colour, link, oEmbed, Google Map, post object, page link, user, relationship, taxonomy, message, tab, accordion, group, clone, repeater and flexible content.<\/p>\n\n<p><strong>Features<\/strong><\/p>\n\n<ul>\n<li>Field group builder with drag-and-drop ordering and per-field settings<\/li>\n<li>Location rules: post type, post ID, status, page template, category, taxonomy, user role, options page and block, combined with AND \/ OR<\/li>\n<li>Conditional logic: show or hide a field based on other fields<\/li>\n<li>Repeater and flexible content, including nested ones<\/li>\n<li>Clone fields to reuse a group inside another<\/li>\n<li>Options pages, user profile fields and term fields<\/li>\n<li>Custom Gutenberg blocks driven by your field groups (<code>cfstudio_register_block()<\/code>)<\/li>\n<li>JSON export and import, plus optional local JSON files in the uploads folder<\/li>\n<li>REST API: values on posts, users and terms, and <code>\/cfstudio\/v1\/options<\/code><\/li>\n<li>Template functions (<code>cfstudio_get_field()<\/code>, <code>cfstudio_have_rows()<\/code>, <code>cfstudio_the_row()<\/code>, <code>cfstudio_get_sub_field()<\/code>) and the <code>[cfstudio]<\/code> shortcode<\/li>\n<li>Optional per-language options for Polylang and WPML sites<\/li>\n<li>Google Map field works with typed coordinates, and adds a searchable map when you add a Google Maps API key<\/li>\n<\/ul>\n\n<p><strong>Fieldloom Pro (optional add-on)<\/strong><\/p>\n\n<p>Fieldloom works fully without Pro. Pro is a separate paid add-on, sold by the plugin author, for sites that need more:<\/p>\n\n<ul>\n<li>ACF Importer: bring ACF field groups into Fieldloom, with every conversion gap listed<\/li>\n<li>Advanced Validation: length, pattern, range and unique-value rules<\/li>\n<li>AEO &amp; Schema: JSON-LD schema, a Quick answer and FAQ box, and an optional llms.txt<\/li>\n<li>Team &amp; Structure: role permissions per field group, revisions and a post type manager<\/li>\n<\/ul>\n\n<p>Pro is sold as one bundle for $15 a year per site, with updates and support included; single packages are coming soon. See the details and pricing at https:\/\/sapatarshi.in\/fieldloom-pro\/<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin can connect to Google Maps. It is only used by the Google Map field type; if you do not use that field, no external service is contacted.<\/p>\n\n<p><strong>Google Maps JavaScript API and Places API (editor map)<\/strong><\/p>\n\n<ul>\n<li>What it is used for: showing a searchable, draggable map when someone edits a Google Map field in the WordPress admin.<\/li>\n<li>When it is used: only if a site administrator has saved a Google Maps API key under Field Groups &gt; Tools, and only on admin screens that show a Google Map field.<\/li>\n<li>What is sent: the editor's browser loads Google's script from <code>maps.googleapis.com<\/code> and sends your API key, the browser's IP address and user agent, the map area being viewed, and any address text typed into the map's search box.<\/li>\n<\/ul>\n\n<p><strong>Google Maps embed (front end)<\/strong><\/p>\n\n<ul>\n<li>What it is used for: displaying a map when a Google Map field is printed with the <code>[cfstudio]<\/code> shortcode.<\/li>\n<li>When it is used: only on pages where such a shortcode outputs a Google Map field.<\/li>\n<li>What is sent: the visitor's browser loads an iframe from <code>www.google.com\/maps<\/code> and sends the saved latitude, longitude and zoom level, plus the visitor's IP address and user agent. No API key is sent.<\/li>\n<\/ul>\n\n<p>Both services are provided by Google: <a href=\"https:\/\/cloud.google.com\/maps-platform\/terms\">Google Maps Platform Terms of Service<\/a>, <a href=\"https:\/\/maps.google.com\/help\/terms_maps\/\">Google Maps\/Google Earth Additional Terms of Service<\/a>, <a href=\"https:\/\/policies.google.com\/privacy\">Google Privacy Policy<\/a>.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin to <code>\/wp-content\/plugins\/fieldloom\/<\/code>, or install it from the Plugins screen.<\/li>\n<li>Activate it through the Plugins screen.<\/li>\n<li>Go to <strong>Field Groups &gt; Add New<\/strong>, add fields and choose where they should appear.<\/li>\n<li>In your theme, print values with <code>cfstudio_get_field( 'field_name' )<\/code> or the <code>[cfstudio field=\"field_name\"]<\/code> shortcode.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"how%20do%20i%20show%20a%20field%20on%20the%20front%20end%3F\"><h3>How do I show a field on the front end?<\/h3><\/dt>\n<dd><p>Use <code>cfstudio_get_field( 'name' )<\/code> in a template, or <code>[cfstudio field=\"name\"]<\/code> in content. For options pages use <code>[cfstudio field=\"name\" post_id=\"option\"]<\/code>; for users <code>post_id=\"user_1\"<\/code>; for terms <code>post_id=\"term_5\"<\/code>.<\/p><\/dd>\n<dt id=\"how%20do%20i%20add%20a%20custom%20block%3F\"><h3>How do I add a custom block?<\/h3><\/dt>\n<dd><p>Register it with <code>cfstudio_register_block()<\/code> in your theme or a small plugin, then create a field group whose location rule is \"Block is equal to\" your block.<\/p><\/dd>\n<dt id=\"does%20the%20google%20map%20field%20need%20an%20api%20key%3F\"><h3>Does the Google Map field need an API key?<\/h3><\/dt>\n<dd><p>No. Without a key you type the address, latitude and longitude. With a Google Maps API key (Field Groups &gt; Tools) the editor shows a searchable, draggable map.<\/p><\/dd>\n<dt id=\"is%20it%20multisite%20compatible%3F\"><h3>Is it multisite compatible?<\/h3><\/dt>\n<dd><p>Multisite has not been tested.<\/p><\/dd>\n<dt id=\"where%20is%20my%20data%20stored%3F\"><h3>Where is my data stored?<\/h3><\/dt>\n<dd><p>Values are saved as post, user, term or option meta in your own database. The only external service is Google Maps, used by the optional Google Map field; see the External services section.<\/p><\/dd>\n<dt id=\"where%20are%20local%20json%20files%20saved%3F\"><h3>Where are local JSON files saved?<\/h3><\/dt>\n<dd><p>Local JSON is off by default. When you turn it on under Field Groups &gt; Tools, field groups are saved as JSON files in <code>wp-content\/uploads\/fieldloom\/json\/<\/code>. The plugin does not write to theme or plugin folders.<\/p><\/dd>\n<dt id=\"is%20there%20a%20pro%20version%3F\"><h3>Is there a Pro version?<\/h3><\/dt>\n<dd><p>Yes. Fieldloom Pro is an optional add-on with an ACF importer, advanced validation, AEO and schema markup, and team permissions. Everything in this plugin stays free. Details: https:\/\/sapatarshi.in\/fieldloom-pro\/<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>0.14.0<\/h4>\n\n<ul>\n<li>The plugin is now called Fieldloom Custom Fields (text domain <code>fieldloom<\/code>).<\/li>\n<li>The shortcode is now <code>[cfstudio]<\/code>. Existing <code>[cfs]<\/code> shortcodes in post content are updated automatically.<\/li>\n<li>The REST field on posts, users and terms is now <code>cfstudio<\/code>.<\/li>\n<li>Local JSON is now a setting under Tools and saves files in the uploads folder (<code>uploads\/fieldloom\/json<\/code>). It no longer writes to the theme folder. Use the <code>cfstudio\/json_load_paths<\/code> filter to sync from an extra read-only folder.<\/li>\n<li>Script handles, JavaScript globals and admin page slugs now use the <code>cfstudio<\/code> prefix.<\/li>\n<li>Documented the use of Google Maps.<\/li>\n<\/ul>\n\n<h4>0.13.1<\/h4>\n\n<ul>\n<li>Fix: block names saved in field-group location rules are now migrated too.<\/li>\n<\/ul>\n\n<h4>0.13.0<\/h4>\n\n<ul>\n<li>Internal rename of the code prefix from cfs to cfstudio (functions, hooks, options, post type, REST namespace <code>cfstudio\/v1<\/code>, block namespace <code>cfstudio\/<\/code>). Existing data is migrated automatically on first load.<\/li>\n<li>Theme developers: template functions are now cfstudio_get_field(), cfstudio_have_rows(), cfstudio_the_row(), etc.<\/li>\n<\/ul>\n\n<h4>0.12.4<\/h4>\n\n<ul>\n<li>Fix: fields inside custom blocks (repeater rows, media pickers, relationship) now work when the block editor runs in an iframe.<\/li>\n<\/ul>\n\n<h4>0.12.3<\/h4>\n\n<ul>\n<li>Design: checkboxes and radios use the plugin accent colour inside plugin screens.<\/li>\n<\/ul>\n\n<h4>0.12.0 \u2013 0.12.2<\/h4>\n\n<ul>\n<li>Custom Gutenberg blocks, Google Map field, per-language options, refreshed admin design.<\/li>\n<\/ul>\n\n<h4>0.11.0<\/h4>\n\n<ul>\n<li>JSON import\/export and local JSON sync, REST API, extra location rules, clone field, user and term fields.<\/li>\n<\/ul>","raw_excerpt":"Custom fields for posts, pages, users, terms, options pages and Gutenberg blocks, with repeater, flexible content, clone and conditional logic.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/403938","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=403938"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/sapta2022"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=403938"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=403938"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=403938"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=403938"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=403938"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=403938"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}