Step 2

Configure production settings

Set locale and policy route in the plugin settings, then confirm the issued package already exposes the correct licensing values in the plugin status area.

Code snippet

Locale: en
Policy URL: /en/cookie-policy
Licensing status: healthy
Settings link shortcode: [cookiezy_settings_link] or [site_cookie_settings_link]
Audit shortcode: [cookiezy_cookie_audit] or [site_cookie_audit]

Multilang

WordPress follows the site locale, with optional locale route mapping

The plugin runtime already uses `determine_locale()` for the active WordPress locale. For multilingual sites, the remaining requirement is to keep the cookie policy URL aligned with the active translated page.

• On a single-language WordPress site, one `Policy URL` setting is enough.
• On WPML or Polylang sites, use the `cookiezy_locale_routes` filter to pass per-locale policy URLs into the runtime config.
• If you do not provide locale routes, the banner text still follows the WordPress locale, but the policy link remains the single URL from plugin settings.

Code snippet

add_filter('cookiezy_locale_routes', function ($routes, $options, $locale) {
  return array(
    'en' => array(
      'policyUrl' => '/en/cookie-policy'
    ),
    'sl' => array(
      'policyUrl' => '/sl/politika-piskotkov'
    )
  );
}, 10, 3);

WordPress adapter: post-purchase rollout

Upload and activate the plugin

Configure production settings

WordPress follows the site locale, with optional locale route mapping

Place shortcodes and validate the install