Description
Massbase Custom Fields stores field values in real database tables, one table per field group and one column per field, instead of thousands of rows in wp_postmeta. Queries stay fast, values are typed (numbers are numbers, dates are dates), and you can index the columns you filter by.
Field groups
- 30+ field types: text, text area, number, range, email, URL, password, color, select, radio buttons, checkboxes, button group, true / false, date, date and time, time, link, WYSIWYG editor, oEmbed, image, file, icon, map (OpenStreetMap or Google Maps), group, repeater, relationship, post object, page link, taxonomy, user, accordion and tab.
- Attach groups to posts, pages and custom post types, users, terms, comments and widgets with location rules.
- Per-field SQL control: column type, length, charset, collation, unique and regular indexes, and generated values (UUID, hash, timestamp, …).
- Validation rules and conditional logic on the edit screen.
- Safe schema changes: renames keep data, risky type changes keep a backup column, removed fields never drop data.
- Schema health: see drift between the definition and the table, import orphan columns, clean up orphan tables.
Post types and taxonomies
Create and edit custom post types and taxonomies without code: labels, visibility, menus, URLs and rewrites, archives, REST API, capabilities and supported features.
Options pages
Create settings screens (top level or under Settings, Appearance, Tools, …) and show any field group on them. Read the values with wpmcf_get_option_field( 'group', 'field' ), the [wpmcf_field context="options"] shortcode, blocks and page builders.
Import, export and migration
- Export and import field groups, post types, taxonomies and options pages as JSON, with a preview before anything is saved.
- Local JSON: create a
wpmcf-jsonfolder in your theme and every definition is saved there too, ready for version control; changes from another site show up under Tools › Local JSON. - Migrate from Advanced Custom Fields: field groups, options pages, post types, taxonomies and the saved values of posts, terms, users, comments and options are copied in the background. ACF data is never changed.
- ACF compatibility: after a migration, theme code that calls
get_field(),the_field(),have_rows(),update_field()or the[acf]shortcode keeps working on the migrated fields once ACF is deactivated. Tools › ACF lists where your code still calls ACF, with the replacement code. - Page caches of WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Optimizer, Breeze and WP Engine are cleared after options, Global Data and field group changes (can be turned off in Settings).
- WP-CLI:
wp wpmcf export,wp wpmcf import,wp wpmcf json sync,wp wpmcf acf migrate.
Global Data
Site-wide values (phone number, address, opening hours, …) you can print anywhere.
Variables
A small, safe template language: {{ glb.phone }}, {{ fg.product.price | number(2) }}, {{ wp.post_title | upper }}. Use it in field values, placeholders and Global Data. Only whitelisted functions and filters run; no PHP is ever evaluated. Expressions in post and user field values run only when the post’s author (or that user) may post unfiltered HTML, never in comment fields, and password fields and password Global Data never appear in their output.
Output
[wpmcf_field group="product" field="price"]and[wpmcf_global key="phone"]shortcodes.wpmcf_get_field(),wpmcf_the_field(),wpmcf_has_field()andwpmcf_format_field()(the display text) for themes.- A public PHP API for site builders and themes: read field groups, fields, post types, taxonomies and options pages, and create or update them from an export document (
wpmcf_get_field_groups(),wpmcf_save_definitions(), …). - Number format for number and range fields: decimal places and a thousands separator in the site language; the field’s prefix and suffix (for example a currency sign) are shown with it everywhere.
- REST API and WPGraphQL: per field group, values appear under
wpmcfin the REST API of its post types (editable by users who can edit the post) and, with the WPGraphQL plugin, as a read-onlywpmcf{Group}field. - Blocks: a “Massbase Field” block (text, link or image, works in query loops), a “Massbase” Block Bindings source for paragraphs, headings, buttons and images (values of the post, its author, the term of a term template or archive, or an options page) and a “Massbase Global Data” Block Bindings source.
- Page builders: dynamic tags for Elementor Pro, Bricks, Divi 4, Breakdance and Oxygen Classic; with Elementor (free is enough) a “Field” widget,
{{ }}variables in any widget’s text and links, and display conditions set up in Pro keep working.
Pro
Massbase Custom Fields Pro is a separate plugin, sold at wpmass.com. Everything described above is part of this free plugin and works without it. Pro adds:
- Advanced fields: gallery, flexible content and clone.
- Admin columns: filters, quick and bulk edit and CSV export of lists.
- Data tables: standalone database tables you can fill by CSV import, a scheduled Google Sheets link or front-end forms, browse and edit in the admin, export as CSV and show on your site with a shortcode or block.
- WooCommerce order fields: field groups on the order edit screen (HPOS and classic order storage), shown for all orders or by order status, readable in templates and emails with
wpmcf_get_order_field(). - Front-end forms: create and edit posts, edit the profile, register users, file uploads, spam protection without a CAPTCHA. Submissions of Contact Form 7, Gravity Forms, WPForms and Fluent Forms can be saved into a data table.
- Page builder widgets: repeater, gallery, post grid and form widgets and display conditions for Elementor, styled with the builder’s own design controls.
- Programmatic SEO: generate thousands of pages from your own data (CSV upload, Google Sheets link, or your posts, terms and WooCommerce products), with a quick start, SEO plugin and sitemap integration, and conversion of generated pages into regular posts.
- AI content for generated pages with your own API key (OpenAI, Anthropic or Google Gemini).
External services
The plugin connects to outside services only for Map fields, oEmbed fields and, if you opt in, Freemius (usage data).
Map fields: nothing is contacted until a Map field is shown, and nothing is sent by your server: the visitor’s or editor’s browser makes these requests, so the service also receives that browser’s IP address and user agent.
oEmbed providers (oEmbed fields)
When an oEmbed field with a URL is shown, your server asks the provider of that URL for its embed code through WordPress’s built-in oEmbed support. Only the providers WordPress itself lists (for example YouTube, Vimeo, Spotify) are asked; a URL of any other site is shown as a plain link and that site is never contacted. Sent: the URL the editor entered. The plugin caches the embed code for a day, and filters it before it is printed. While an editor types the URL, the edit screen shows a preview through WordPress’s own oEmbed proxy, asking the same providers only, and loads the provider’s thumbnail image in the editor’s browser. Each provider’s own terms and privacy policy apply, for example YouTube Terms and Vimeo Terms.
OpenStreetMap tiles (default map provider)
Map images for Map fields on edit screens and on your site are loaded from tile.openstreetmap.org, operated by the OpenStreetMap Foundation. Sent: the tile coordinates of the visible map area (which reveal the location being viewed) and the page address as referrer. Tile usage policy, Terms of use, Privacy policy.
Nominatim address search (default map provider)
When an editor types an address into a Map field and presses Search or Enter, the search text is sent to nominatim.openstreetmap.org to find matching places. No request is made while typing, and at most one per second. Usage policy, Privacy policy.
Google Maps (only when selected in Settings › Maps with an API key)
The Google Maps JavaScript API is loaded from maps.googleapis.com with your API key to show maps and, on edit screens, to look up searched addresses (the search text is sent on Search or Enter). Google receives the map area viewed, the search text and the API key. OpenStreetMap is not contacted in this mode. Google Maps Platform Terms of Service, Google Privacy Policy.
Freemius (opt-in usage data)
Massbase Custom Fields uses the Freemius SDK. After activation you are asked whether to share basic usage data; nothing is sent unless you opt in. If you opt in, your server sends api.freemius.com the site URL, WordPress, PHP and plugin versions, the site language, the admin’s name and email address, and the plugin’s activation, deactivation and uninstall events. The buy and trial links of the Pro page open the Freemius checkout of the separate Pro plugin; nothing is sent until you open one. What Freemius receives and how it is used, with links to the Freemius Terms of Service and Privacy Policy: Massbase Custom Fields privacy notice.
Source code and libraries
The complete, human-readable source code of every compiled file ships inside this plugin. Nothing is downloaded from elsewhere to build it.
- Compiled JavaScript and CSS:
assets/js/build/(minified by@wordpress/scripts, which uses webpack). - Their sources:
assets/js/in TypeScript and React (.ts,.tsx) and CSS. - Build configuration:
package.json,package-lock.json,webpack.config.js,tsconfig.json,tailwind.config.js,postcss.config.js.
Each compiled file and its source (every entry point is listed in webpack.config.js; a .asset.php file next to a script only lists its WordPress dependencies):
assets/js/build/dashboard.jsfromassets/js/dashboard/index.tsxassets/js/build/field-groups.jsfromassets/js/field-groups/index.tsxassets/js/build/global-data.jsfromassets/js/global-data/index.tsxassets/js/build/options-pages.jsfromassets/js/options-pages/index.tsxassets/js/build/post-type.jsfromassets/js/post-type/index.tsxassets/js/build/taxonomies.jsfromassets/js/taxonomies/index.tsxassets/js/build/tools.jsfromassets/js/tools/index.tsxassets/js/build/plans.jsfromassets/js/plans/index.tsxassets/js/build/settings.jsfromassets/js/settings/index.tsxassets/js/build/setup.jsfromassets/js/setup/index.tsxassets/js/build/blocks.jsfromassets/js/blocks/index.tsassets/js/build/edit-screen.jsfromassets/js/edit-screen/index.tsassets/js/build/field-types.jsandfield-types.cssfromassets/js/field-types/index.tsassets/js/build/map-field.jsandmap-field.cssfromassets/js/map/field.tsassets/js/build/map-view.jsandmap-view.cssfromassets/js/map/view.tsassets/js/build/map-block.jsfromassets/js/blocks/map/view.tsassets/js/build/map-provider.jsfromassets/js/map/provider.ts(loaded on demand)assets/js/build/map-leaflet.jsandmap-leaflet.cssfromassets/js/map/leafletMap.ts(loaded on demand)assets/js/build/481.jsandassets/js/build/images/from the Leaflet 1.9.4 npm package (node_modules/leaflet, source: https://github.com/Leaflet/Leaflet)assets/js/build/admin-style.cssandadmin-style.jsfromassets/js/admin-style.ts, which importsassets/css/tailwind-src.css(Tailwind CSS)-
-rtl.cssfiles are right-to-left copies of the CSS next to them, made by the same build.assets/css/tokens.css and
assets/css/field-group-meta-present.cssare not compiled.
To build the files yourself, use Node.js 20 or later in the plugin folder:
npm cinpm run build
The result is written to assets/js/build/. npm run start rebuilds on every change while you develop.
Bundled libraries:
- Action Scheduler 4.2 (GPLv3) for background jobs.
- Leaflet 1.9.4 (BSD-2-Clause) for OpenStreetMap maps, bundled into the map script; no CDN is used.
- The Freemius WordPress SDK 2.13 (GPLv3) for opt-in usage data.
ACF function names (note for reviewers)
src/Portability/Acf/Compat/functions.php declares functions with Advanced Custom Fields' own names so that theme code written for ACF keeps working after a migration. They are declared only on sites that ran the ACF migration, only while neither ACF nor Secure Custom Fields is loaded, only at the end of `after_setup_theme`, after the theme had its chance to load a bundled ACF (never while a plugin is being activated), each one only if no function of that name exists, and the site owner can turn them off in Tools. The `[acf]` shortcode is added under the same conditions and only if no `acf` shortcode exists. No `ACF` class is declared. The full list: `get_field`, `get_fields`, `the_field`, `get_field_object`, `update_field`, `delete_field`, `have_rows`, `the_row`, `get_row`, `get_row_index`, `get_row_layout`, `reset_rows`, `add_row`, `update_row`, `delete_row`, `get_sub_field`, `the_sub_field`, `get_sub_field_object`, `update_sub_field`, `acf_add_local_field_group`, `acf_add_local_field`, `acf_add_options_page`, `acf_add_options_sub_page`, `acf_register_block_type` and `acf_update_setting`.
Screenshots









Blocks
This plugin provides 4 blocks.
- Massbase Field Filters A filter form for a Query Loop: visitors narrow the posts by field values. Works without JavaScript.
- Massbase Map Shows the address of a map field and loads the interactive map only when a visitor asks for it.
- Massbase Field Shows a custom field of the current post, a query loop post, a repeater row, the term, the author or an options page.
- Massbase Repeater Repeats its blocks for each row of a repeater or flexible content field.
Installation
- Upload the plugin folder to
/wp-content/plugins/, or install it from the Plugins screen. - Activate it. The tables it needs are created on activation.
- The setup wizard opens: pick a goal and a starter, or skip it and open Massbase › Field Groups.
FAQ
-
Where are field values stored?
-
In one table per field group, named
{prefix}wpmcf_fg_{group key}, linked to the post, user, term or comment by ID. Nothing is written to post meta. -
Which databases are supported?
-
MySQL 8.0 or newer and MariaDB 10.6 or newer.
-
What happens to my data when I deactivate or delete the plugin?
-
Deactivating keeps everything. Deleting the plugin keeps your data too, unless you turn on Settings › Delete all plugin data on uninstall. Posts and pages you created always stay.
-
Can I switch from Advanced Custom Fields?
-
Yes. Massbase › Tools › Migrate from ACF copies field groups, options pages, post types, taxonomies and the saved values of posts, terms, users, comments and options in the background. A report shows what will be copied first, and ACF data is never changed, so you can compare both before you deactivate ACF.
-
Do I have to rewrite my theme after migrating from ACF?
-
No. Once ACF is deactivated, the plugin provides ACF’s template functions for the migrated field groups:
get_field(),the_field(),get_fields(),get_field_object(), the row loop (have_rows(),the_row(),get_sub_field(),the_sub_field()and the other row functions),update_field(),delete_field(), the[acf]shortcode and options page reads with'option'. Values come back in the return formats set in ACF. Tools › Migrate from ACF › ACF compatibility lists each place in your theme or plugins that still calls an ACF function, with thewpmcf_*call that replaces it, so you can move over gradually; the same screen has a switch to turn the compatibility functions off. Fields the migration could not copy (they are listed in the report before you start) are not covered. -
Can I move other post meta into field groups?
-
Field groups answer and accept post meta by field name (on by default, per group):
get_post_meta(),update_post_meta(),add_post_meta()anddelete_post_meta()with a field’s key read and write its column, so importers and other plugins fill your fields. Values already stored in post meta are not moved automatically; save each post again or write them withwpmcf_update_field(). -
How do I query posts by field value?
-
Pass
wpmcf_querytoWP_Query(or usewpmcf_query_posts()), for example'wpmcf_query' => [['field' => 'listing.price', 'compare' => '<=', 'value' => 500]], and order with'orderby' => ['wpmcf:listing.price' => 'ASC']. The columns are real, indexable database columns, so these queries stay fast on large sites. -
Does it work on multisite?
-
Yes. Every site has its own tables and settings. Deleting a site from the network also removes its plugin tables.
-
Does it work with page builders and SEO plugins?
-
Yes. Elementor, Bricks, Divi 4, Breakdance and Oxygen Classic get dynamic tags, Elementor also gets a Field widget (more widgets in Pro), and field values print through shortcodes and the PHP API in any builder that renders shortcodes. Programmatic SEO (Pro) integrates with Yoast SEO, Rank Math, All in One SEO, the core sitemap and Elementor.
-
Does it collect personal data?
-
Values you store in fields stay in your database. Values of user fields are included in WordPress’s personal data export and erasure tools (Tools › Export / Erase Personal Data), and a suggested text for your privacy policy is added under Settings › Privacy.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Massbase Custom Fields” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Massbase 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
1.1.0
- Changed: the plugin is now called Massbase Custom Fields; the admin menu, blocks and page builder groups say “Massbase”.
- Changed: requires WordPress 6.9 or later (the bundled Action Scheduler 4.2 needs it). License is GPLv3 or later.
- New: public PHP API for definitions:
wpmcf_get_field_groups(),wpmcf_get_field_group(),wpmcf_get_field_object(),wpmcf_get_post_types(),wpmcf_get_taxonomies(),wpmcf_get_options_pages(),wpmcf_get_global_definitions(),wpmcf_export_definitions(),wpmcf_save_definitions()andwpmcf_set_definition_active(). - New:
wpmcf_format_field()returns a field’s display text (choice labels, formatted dates and numbers, titles, prefix and suffix). - New: number format setting for number and range fields (decimal places, thousands separator).
- New: the “Massbase” binding reads the post author, the current term or an options page (
object), picks an image size (size), can give the stored value (raw) and reads the current row inside a repeater block. - New: “Massbase Global Data” Block Bindings source (
wpmcf/global). - New:
wpmcf_preview_values()andwpmcf_clear_preview_values()show proposed field values for one request without saving them (sanitized like a save; password fields never). - New:
wpmcf/values/savedaction after field values are saved on an edit screen or throughwpmcf_update_field(). - New: blocks Repeater, Map (the map loads only after a click), Field Filters (a filter form for a Query Loop, no JavaScript) and Gallery (Pro, core lightbox).
- New: Query Loop field filters, field sorting, a “Related (field)” variation and visitor filters.
- New: the Massbase Field block reads the post author, the current term or an options page and the current repeater row.
- Fixed:
wpmcf_queryrefuses conditions on password fields. - Changed: blocks, bindings and page builder tags show the field’s display prefix and suffix; related posts in plain text are separated by commas.
1.0.0
- First release.
- ACF compatibility layer: ACF’s template functions and the
[acf]shortcode keep working on migrated field groups after ACF is deactivated, with a list of the calls left to replace. - Repeater and flexible content rows ask before removing a row in an accessible dialog. Pro: flexible content rows can be duplicated and dragged, and show a number and summary; share images and image columns can be picked from the media library. Google Maps use Google’s current markers when a Map ID is set, and sites on Google Maps no longer download the OpenStreetMap library.
- Fields on menu items: field groups located on a menu or menu item show in each item’s settings on Appearance › Menus, also for items just added, and are read with
wpmcf_get_field(). - Safer data:
wpmcf_update_field()returns false and keeps the stored value when a value is invalid; an options page form whose security check expired says so instead of saving; WordPress exports leave password fields out and imports link relationships, images and terms to the imported content; post types with their own capabilities stay editable by administrators. - Template variables understand negative numbers and chained conditions (
a ? b : c ? d : e,a == b == c). Changed: a block with stray words after a complete expression ({{ 1 2 }}) now renders empty instead of its first part; word counts include numbers and words in every script; trim, split and reverse work on characters in any language, andltrim/rtrimwith'0'trim zeros.
