View Categories

Requirements

Before using PolyFields, make sure your site meets the following requirements.

Software requirements

Dependencies

Advanced Custom Fields Pro is required because options pages are part of ACF Pro features.

Polylang Pro replaces the free Polylang plugin, so only one of them should be active at a time. With Polylang Pro, this plugin can also use Pro ACF field strategies and DeepL machine translation when configured.

Missing dependencies

If any required dependency is missing, the plugin shows an admin notice and does not initialize its services. Resolve the notice before expecting multilingual options behavior.

WordPress multisite

PolyFields works on WordPress multisite the same way it does on a single site: all plugin data is stored in each subsite’s own wp_options table. Translation maps, per-language stores (pfao__*), import and migration state, autoload snapshots, and license data are never shared across sites.

Each subsite that needs multilingual ACF options must have its own working stack:

  • PolyFields active on that subsite (network activation is supported and enables the plugin on every site in the network)
  • Polylang or Polylang Pro configured with languages for that subsite
  • Advanced Custom Fields Pro with the options pages you want to translate on that subsite

Options values, first-use import or migration, and field propagation all run in the context of the current site. Run those workflows separately on each subsite that needs them. From WP-CLI, target a subsite with the --url flag, for example wp polyfields import-options --url=https://example.com/subsite/.

Licensing is also per subsite. Activate your license under Languages → Settings → License keys on each site that should use the plugin. Each activation is tied to that site’s URL.

The plugin does not provide network-wide options pages or centralized multilingual storage. If subsites need different languages, field groups, or option values, configure and manage them independently on each site.