Description
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.
Field types (35)
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.
Features
- Field group builder with drag-and-drop ordering and per-field settings
- Location rules: post type, post ID, status, page template, category, taxonomy, user role, options page and block, combined with AND / OR
- Conditional logic: show or hide a field based on other fields
- Repeater and flexible content, including nested ones
- Clone fields to reuse a group inside another
- Options pages, user profile fields and term fields
- Custom Gutenberg blocks driven by your field groups (
cfstudio_register_block()) - JSON export and import, plus optional local JSON files in the uploads folder
- REST API: values on posts, users and terms, and
/cfstudio/v1/options - Template functions (
cfstudio_get_field(),cfstudio_have_rows(),cfstudio_the_row(),cfstudio_get_sub_field()) and the[cfstudio]shortcode - Optional per-language options for Polylang and WPML sites
- Google Map field works with typed coordinates, and adds a searchable map when you add a Google Maps API key
Fieldloom Pro (optional add-on)
Fieldloom works fully without Pro. Pro is a separate paid add-on, sold by the plugin author, for sites that need more:
- ACF Importer: bring ACF field groups into Fieldloom, with every conversion gap listed
- Advanced Validation: length, pattern, range and unique-value rules
- AEO & Schema: JSON-LD schema, a Quick answer and FAQ box, and an optional llms.txt
- Team & Structure: role permissions per field group, revisions and a post type manager
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/
External services
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.
Google Maps JavaScript API and Places API (editor map)
- What it is used for: showing a searchable, draggable map when someone edits a Google Map field in the WordPress admin.
- When it is used: only if a site administrator has saved a Google Maps API key under Field Groups > Tools, and only on admin screens that show a Google Map field.
- What is sent: the editor’s browser loads Google’s script from
maps.googleapis.comand 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.
Google Maps embed (front end)
- What it is used for: displaying a map when a Google Map field is printed with the
[cfstudio]shortcode. - When it is used: only on pages where such a shortcode outputs a Google Map field.
- What is sent: the visitor’s browser loads an iframe from
www.google.com/mapsand sends the saved latitude, longitude and zoom level, plus the visitor’s IP address and user agent. No API key is sent.
Both services are provided by Google: Google Maps Platform Terms of Service, Google Maps/Google Earth Additional Terms of Service, Google Privacy Policy.
Installation
- Upload the plugin to
/wp-content/plugins/fieldloom/, or install it from the Plugins screen. - Activate it through the Plugins screen.
- Go to Field Groups > Add New, add fields and choose where they should appear.
- In your theme, print values with
cfstudio_get_field( 'field_name' )or the[cfstudio field="field_name"]shortcode.
FAQ
-
How do I show a field on the front end?
-
Use
cfstudio_get_field( 'name' )in a template, or[cfstudio field="name"]in content. For options pages use[cfstudio field="name" post_id="option"]; for userspost_id="user_1"; for termspost_id="term_5". -
How do I add a custom block?
-
Register it with
cfstudio_register_block()in your theme or a small plugin, then create a field group whose location rule is “Block is equal to” your block. -
Does the Google Map field need an API key?
-
No. Without a key you type the address, latitude and longitude. With a Google Maps API key (Field Groups > Tools) the editor shows a searchable, draggable map.
-
Is it multisite compatible?
-
Multisite has not been tested.
-
Where is my data stored?
-
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.
-
Where are local JSON files saved?
-
Local JSON is off by default. When you turn it on under Field Groups > Tools, field groups are saved as JSON files in
wp-content/uploads/fieldloom/json/. The plugin does not write to theme or plugin folders. -
Is there a Pro version?
-
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/
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Fieldloom Custom Fields” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Fieldloom Custom Fields” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.14.0
- The plugin is now called Fieldloom Custom Fields (text domain
fieldloom). - The shortcode is now
[cfstudio]. Existing[cfs]shortcodes in post content are updated automatically. - The REST field on posts, users and terms is now
cfstudio. - Local JSON is now a setting under Tools and saves files in the uploads folder (
uploads/fieldloom/json). It no longer writes to the theme folder. Use thecfstudio/json_load_pathsfilter to sync from an extra read-only folder. - Script handles, JavaScript globals and admin page slugs now use the
cfstudioprefix. - Documented the use of Google Maps.
0.13.1
- Fix: block names saved in field-group location rules are now migrated too.
0.13.0
- Internal rename of the code prefix from cfs to cfstudio (functions, hooks, options, post type, REST namespace
cfstudio/v1, block namespacecfstudio/). Existing data is migrated automatically on first load. - Theme developers: template functions are now cfstudio_get_field(), cfstudio_have_rows(), cfstudio_the_row(), etc.
0.12.4
- Fix: fields inside custom blocks (repeater rows, media pickers, relationship) now work when the block editor runs in an iframe.
0.12.3
- Design: checkboxes and radios use the plugin accent colour inside plugin screens.
0.12.0 – 0.12.2
- Custom Gutenberg blocks, Google Map field, per-language options, refreshed admin design.
0.11.0
- JSON import/export and local JSON sync, REST API, extra location rules, clone field, user and term fields.
