Requirements

Versions

WordPress itself checks the WordPress and PHP minimums. On a site below them, the plugin cannot be activated and WordPress tells you why.

Hosting and permissions

• Database user rights. The database user in wp-config.php must be allowed to CREATE, ALTER, DROP and add indexes to tables. Almost every host grants this by default. Shared hosts that block ALTER TABLE will break schema changes.
• REST API. The admin screens are React apps that talk to the WordPress REST API (/wp-json/wpmcf/v1/). Security plugins or server rules that block REST requests for logged-in users make the screens fail to load or save.
• JavaScript. A current browser with JavaScript on. There is no non-JavaScript admin.
• Background jobs. Imports, schema changes and Pro tasks run in batches on Action Scheduler, which is bundled with the plugin. WP-Cron must be able to run (a normal DISABLE_WP_CRON-free setup, or a real cron hitting wp-cron.php).
• Memory. Nothing special for normal use. Large imports run in small batches so they do not need a high memory limit.

Who can use the admin screens

Every Mass Custom Fields screen, including the setup wizard, the dashboard and the Settings screen, requires the manage_options capability. In a default WordPress that is the Administrator role. Editors can fill in field values on the edit screens where a group appears, but cannot open the plugin's own screens.

Compatibility notes

• Multisite is supported; see Multisite.
• Page builders: Elementor, Bricks, Divi 4, Breakdance and Oxygen Classic get dynamic tags; Elementor also gets a Field widget. See Integrations.
• Cache plugins are asked to clear their pages after relevant changes. See Settings.
• Other custom field plugins can run next to Mass Custom Fields. To move over from Advanced Custom Fields, use WPM Fields › Tools › Migrate from ACF.

Troubleshooting