Constants and configuration

Last updated Oct 3, 20263 min read

Constants the plugin defines

Defined in the main plugin file when WordPress loads it. Read them; never redefine them.

Constant	Value
`WPMCF_VERSION`	The plugin version, for example `1.0.0`
`WPMCF_FILE`	Absolute path of the main plugin file
`WPMCF_PATH`	Absolute path of the plugin folder, with a trailing slash
`WPMCF_URL`	URL of the plugin folder, with a trailing slash
`WPMCF_BASENAME`	`mass-custom-fields/mass-custom-fields.php` (the key WordPress uses for the plugin)

php

if ( defined( 'WPMCF_VERSION' ) && version_compare( WPMCF_VERSION, '1.0.0', '>=' ) ) {
    // safe to use the 1.0 API
}

To test whether the plugin has finished booting, use the wpmcf/booted action rather than a constant.

Constants you can set in `wp-config.php`

Add them above the line /* That's all, stop editing! Happy publishing. */.

Constant	Plan	Type	Default	Purpose
`WPMCF_PSEO_GRACE_DAYS`	Pro	int	`14`	Days generated pages keep serving after a paid license expires
`WPMCF_CLIENT_IP_HEADER`	Pro	string	not set	The `$_SERVER` header that carries the real visitor IP behind a proxy or CDN
`WPMCF_AI_OPENAI_KEY`	Pro	string	not set	OpenAI API key, kept out of the database
`WPMCF_AI_ANTHROPIC_KEY`	Pro	string	not set	Anthropic API key
`WPMCF_AI_GEMINI_KEY`	Pro	string	not set	Google Gemini API key
`WPMCF_GUARD_RETHROW`	Free	bool	`false`	Rethrow errors after logging them (development and tests)

`WPMCF_PSEO_GRACE_DAYS`

php

define( 'WPMCF_PSEO_GRACE_DAYS', 30 );

When a paid license (not a trial) expires, generation, sync, AI and editing stop at once, but generated pages keep being served for a grace period, then return 404 unless they were converted to posts. The period is the constant's value in days, or 14 when it is not set. The result is then passed through the wpmcf/licensing/grace_days filter (negative values count as 0). Trials never get a grace period. See Trials, renewals and expiry.

`WPMCF_CLIENT_IP_HEADER`

php

define( 'WPMCF_CLIENT_IP_HEADER', 'HTTP_CF_CONNECTING_IP' );   // Cloudflare
define( 'WPMCF_CLIENT_IP_HEADER', 'HTTP_X_FORWARDED_FOR' );    // many reverse proxies

Front-end forms rate-limit submissions per visitor IP. By default the plugin uses REMOTE_ADDR, because forwarded headers can be forged by the visitor. Behind a proxy or CDN every visitor then shares the proxy's address and one limit. Set this constant to the header your proxy overwrites on every request.

Rule	Detail
Format	Must match `HTTP_` followed by capital letters, digits and underscores (max 60). Anything else is ignored.
Several addresses	In a comma-separated list such as `X-Forwarded-For`, the first address is used.
Validation	The value must be a valid IP; otherwise `REMOTE_ADDR` is used.
Last word	The result passes through the `wpmcf/forms/client_ip` filter.

Only set it when the proxy really replaces that header; otherwise a visitor can choose their own IP and bypass the limit.

`WPMCF_AI_{PROVIDER}_KEY`

php

define( 'WPMCF_AI_OPENAI_KEY', 'sk-...' );
define( 'WPMCF_AI_ANTHROPIC_KEY', 'sk-ant-...' );
define( 'WPMCF_AI_GEMINI_KEY', '...' );

The name is WPMCF_AI_ + the provider ID in capitals + _KEY; a provider added with wpmcf/ai/providers uses the same pattern. A non-empty constant wins over a key saved on the Settings screen and is never written to the database. The screen then reports the key's source as "constant". Keys are never sent to the browser.

`WPMCF_GUARD_RETHROW`

php

define( 'WPMCF_GUARD_RETHROW', true );

The plugin's fault guard catches an error raised in one of its modules, logs it (Settings › Health), tells the admin and lets the page keep rendering. With this constant set, the guard rethrows after logging, so tests and local development show the real error. Do not set it on a live site.

WordPress constants the plugin honors

Constant	Effect
`WP_DEBUG`	Variable engine failures are written to the PHP error log (`[wpmcf] Variable resolution failed — "{{ … }}" — message`); an object reference that names nothing raises a `_doing_it_wrong` notice.
`WP_DEBUG_LOG`	Errors caught by the fault guard are also written to the log as `[wpmcf:module] message in file:line`.
`WP_CLI`	Registers the `wp wpmcf` commands.
`DONOTCACHEPAGE`	Defined by the plugin the first time a front-end page prints a `wp.user_*` variable, so page caches skip the page.

Was this page helpful?

Still stuck? Contact support

Constants and configuration

Constants the plugin defines

Constants you can set in wp-config.php

WPMCF_PSEO_GRACE_DAYS

WPMCF_CLIENT_IP_HEADER

WPMCF_AI_{PROVIDER}_KEY

WPMCF_GUARD_RETHROW