Contentpass Integration
| 开发者 | contentpass |
|---|---|
| 更新时间 | 2026年7月9日 19:26 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Integration – Configure your Contentpass property (base URL, ID), choose your Consent Management Platform (CMP), and manage staging vs production behaviour.
- CMP support – Built-in hooks for major CMPs (for example Consentmanager, Didomi, CCM19, OneTrust, Usercentrics V2/V3, Sourcepoint). Choose whether the CMP is already on your site or should be loaded by the plugin (Consentmanager via validated snippet paste).
- Blocking Rules – Define patterns to scan for or exclude, with admin UI for script blocking aligned with your consent setup.
- Request Contract – Quick link to the Contentpass publisher contact flow with tracking parameters for support context.
- Staging mode – During onboarding, Contentpass is limited to logged-in editors and administrators (or an authorized URL debug flag). Production for all visitors begins automatically once your property is approved and live in the Contentpass publisher dashboard.
manage_options capability by default (filterable via cp4wp_required_capability).
安装:
- Upload the
contentpass-integrationfolder to the/wp-content/plugins/directory, or install the ZIP from your distribution package. - Activate Contentpass Integration through the Plugins screen in WordPress.
- Open Contentpass in the admin menu and complete Integration (CMP, URLs, IDs).
- If you use script blocking, review Blocking Rules and save your patterns.
- Once your property is approved and live in the Contentpass publisher dashboard, verify consent and Contentpass behaviour on the front end. Staging mode ends automatically when both statuses are active (config refresh may take up to 10 minutes).
屏幕截图:
常见问题:
Do I need a Contentpass publisher account?
Yes. You need Contentpass-side configuration (including property URL / CNAME as required by Contentpass). Use Request Contract in the admin menu if you need to contact Contentpass.
Why does the plugin load now.js from my Contentpass base URL?
now.js is required by the Contentpass platform. It is not optional custom code and not pasted by the publisher. The plugin loads it only from the publisher’s configured Contentpass property base URL (for example https://cp.example.com/now.js) after that URL is validated during setup. This script powers subscription and consent integration together with the official Contentpass stubs from static.contentpass.net. Without now.js, Contentpass cannot function on the site.
What are “Scripts to load after consent”?
This is an optional list of external script URLs only (for example your ad network’s https://…/ads.js). Publishers enter URLs in dedicated fields; the plugin does not accept arbitrary HTML, inline JavaScript, PHP, or CSS. Each value is sanitized (esc_url_raw), must use http:// or https://, and is output only as a programmatic <script src="…" async defer> tag after consent. Legacy free-form “custom code” markup was removed in favour of this structured URL list. This matches the consent workflow: third-party tags blocked before consent may be loaded again after the visitor accepts.
What is staging mode?
While your Contentpass property is not yet approved or not yet live, staging mode is active automatically: Contentpass is shown only to logged-in users with Editor or Administrator roles, or to visitors using an authorized ?cpdebug=staging URL. You cannot turn staging off manually during onboarding. Once Contentpass has approved your property and you have set it to live in the publisher dashboard, staging ends automatically and Contentpass is served to all visitors. Changes from the dashboard may take up to 10 minutes to apply.
Which WordPress and PHP versions are supported?
The plugin header declares WordPress 6.3+ and PHP 7.4+. Newer releases may raise these; check the plugin main file after updates.
Can I change who may access the plugin settings?
Yes. Developers can use the cp4wp_required_capability filter to require a different capability than manage_options.
Does this plugin send data to external services?
Yes, when configured. See the External services section above for each provider, what is transmitted, and links to terms and privacy policies. Only your selected CMP and Contentpass endpoints are used.
更新日志:
- Persist front-end verification on successful admin save (and self-heal when Integration debug shows endpoints reachable).
- Admin debug now shows property_verified_transient, property_verified_persisted, and property_frontend_ready.
- Set cmp_noscreen only when Contentpass is actually ready to load (fixes CM layer hidden while CP is blocked).
- Fix frontend verification cache: saving Integration settings now verifies config.json and now.js so Contentpass scripts can load.
- Fix staging detection: read isApproved and isLive from funnelConfig in config.json (fixes live properties stuck in staging mode).
- Fix CNAME onboarding detection: gate on config.json only; now.js remains required for front-end script loading.
- Add editable Base URL field on the CNAME setup screen for custom CNAME hosts.
- Improve Integration debug output (config vs frontend readiness).
- Fix config availability check on the Integration page (force_fresh cache logic).
- Remove unreachable now.js script tag filter; load now.js async via the safe inline loader.
- Prevent front-end crashes when Base URL is misconfigured (e.g. WordPress site URL instead of Contentpass CNAME).
- Load Contentpass scripts only after config.json and now.js are verified for the configured property.
- Reject saving a Base URL that matches the WordPress site host; add admin tooltip and error notice.
- Load now.js via a safe dynamic loader with console errors on failure instead of blocking the page.
- Add CMP integration mode (already on site vs plugin loads CMP) and Consentmanager semi-automatic snippet paste with validation.
- Load Consentmanager semi-automatic CMP script from Consentmanager CDN instead of a bundled minified loader; clarify Code-ID (data-cmp-cdid) in admin settings.
- Fix post-consent script unlock and watchdog race conditions with OneTrust and dynamic ad scripts.
- Asset cache busting via updated plugin version query string.
- Document third-party/external services in readme (WordPress.org compliance).
- Scope elevated PCRE backtrack limit to script-scan replacements only; restore previous value after use.
- Replace global output-buffer callback with WordPress 6.9 template enhancement filter; legacy buffers are explicitly closed on shutdown.
- Add legacy output-buffer fallback on WP 6.9+ when the core template enhancement buffer is skipped or cancelled.
- Limit DONOTCACHEPAGE to staging/debug requests that actually load Contentpass, not all front-end pages.
- Sanitize Accept-Language header and placeholder language cookie input before validation.
- Escape SVG branding, custom ad code, and placeholder CSS on output (late escaping).
- Harden admin output escaping in script scan and settings screens (esc_attr, wp_kses, sanitized query args).
- Protect ?cpdebug=staging and ?cpdebug=settings with an Integration debug password (?cpdebug_key); limit anonymous cache bypass to staging sites only; sanitize admin preview HTML in JS.
- Current stable release (see plugin header and repository for detailed changes).