Contentpass Integration
| 开发者 | contentpass |
|---|---|
| 更新时间 | 2026年10月29日 16:13 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1.2 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Contentpass is a privacy-focused monthly subscription for readers. With one registration, Contentpass users visit participating websites ad-free and without being tracked.
For you as a publisher, that means revenue from visitors who reject advertising consent. Contentpass pays out at ad market rates, so you earn the same from these visitors as you do from advertising.
This plugin adds Contentpass to your WordPress site. You set everything up in the WordPress admin, without editing your theme.
What your readers get
- A fair choice. Your consent layer offers two options: agree to personalized advertising, or subscribe to Contentpass and visit ad-free and without being tracked.
- One subscription for many websites. A single registration covers every participating website.
- Revenue when visitors reject consent. Contentpass pays out at ad market rates for visits from Contentpass users.
- Less work for your team. Contentpass handles payment processing and customer service for its users.
- Reporting without profiles. You receive aggregated page-view counts from Contentpass users, not personal profiles.
- Consent in one place. The plugin connects Contentpass with Consentmanager and holds back third-party scripts and embeds until visitors consent.
- A safe start. Try Contentpass with your own editors first. It goes live for all visitors once your property is approved.
- WordPress 6.3 or later and PHP 7.4 or later.
- A Contentpass publisher account with a Property ID.
- Consentmanager as your consent management platform (CMP). Consentmanager is the only supported CMP.
- Integration: Enter your Property ID. The plugin loads your property configuration from Contentpass, including the host that Contentpass loads from.
- Consentmanager: The plugin can load Consentmanager for you from the script tag you copy in Consentmanager. If Consentmanager already runs on your site (through your theme, a tag manager, or another plugin), the plugin works alongside it.
- Blocking Rules: Block scripts and iframes by URL until visitors consent, and set exceptions that always load. Blocked content shows a placeholder with your own text, styling, and privacy link. A rule can also hand its content to Consentmanager Dynamic Content Blocking, using the vendor ID from Consentmanager. Rules can be exported and imported as JSON or CSV.
- Scripts after consent: Load external scripts, such as ad tags, only after visitors give full consent.
- Staging mode: Until your property is approved and live, the Contentpass consent layer appears only to logged-in Editors and Administrators, or to anyone who opens a page with
?cpdebug=staging. Consentmanager and script blocking run for every visitor. Staging ends on its own once the property is approved and live in the publisher dashboard (this can take up to 10 minutes). - Access control: The admin screens require the
manage_optionscapability. Developers can change it with thecp4wp_required_capabilityfilter.
安装:
- 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: enter your Property ID first, then configure Consentmanager.
- 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 a Contentpass property and its Property ID and the domain setup completed in the publisher dashboard. 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 Contentpass host listed as hostname in your property config.json (for example https://cp.example.com/now.js). 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?
Staging limits the Contentpass consent layer only. While the property is not approved or not live, the consent layer is shown to logged-in Editors and Administrators, or to anyone using ?cpdebug=staging. Consentmanager and script blocking still run for every visitor. You cannot turn staging off manually during onboarding. Once the property is approved and live, the consent layer is shown to everyone. Dashboard changes 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. The plugin only talks to Contentpass and Consentmanager.
更新日志:
1.4.7
- Accept-all (including a stored Accept-all cookie) lifts every blocking rule and stops the watchdog. Deny, no choice, and partial consent keep blocking.
- WordPress.org listing has a new description and a sharper large banner.
- When a blocking rule matches several scripts from one vendor, each embed now shows one placeholder. One click loads all of them in order.
- A valid Contentpass subscription removes the Contentpass consent layer only. Embeds and vendor scripts stay blocked until the visitor accepts each placeholder.
- Dynamic Blocking iframes send their own width and height to Consentmanager as the preview size, so the preview box is drawn for embeds of 300px or larger.
- Integration settings open directly. A missing Property ID no longer blocks the rest of the screen.
- Plugin description now says the plugin supports Consentmanager only.
- WordPress.org listing now describes Consentmanager only. The description and FAQ no longer mention other CMPs.
- Script blocking and the Consentmanager loader run for every visitor. Staging and
?cpdebug=stagingonly control the Contentpass wall. - Without the Contentpass wall, Dynamic Blocking scripts use Consentmanager
cmplazyload, so each vendor is unlocked by Consentmanager. Placeholders unlock on accept-all (consentapproved). - With the Contentpass wall, scripts stay in document order and load after
onFullConsentor a content preview Accept. - Consentmanager is the only CMP. Didomi, CCM19, OneTrust, Usercentrics, and Sourcepoint integrations are removed.
- Keep the CMP consent screen when config.json reports a live or public property whose Contentpass domain is not ready (
isDomainReadyfalse). The CNAME does not resolve yet, so the stub cannot render the wall and must not suppress the CMP screen. - Treat config snapshots that never included
isDomainReadyas ready, so older properties do not lose Contentpass.
- Skip the plugin's Contentpass stub, now.js and cmp_noscreen when the CMP renders the Contentpass wall itself (config.json
cmpRendersWall) — avoids a second cp('create') racing the CMP's own integration. - Only set cmp_noscreen when the Contentpass layer actually loads (previously the CM screen could be suppressed without any consent UI taking its place).
- "CMP already integrated" now arms the Contentpass gate for Consentmanager, so CM/TCF consent no longer unlocks blocked embeds behind an open Contentpass wall.
- "CMP already integrated" now unlocks Contentpass placeholders for visitors with a valid subscription (parity with the plugin-loaded CMP path).
- Load property config.json from the Contentpass static CDN (
https://static.contentpass.net/properties/{id}/config.json). - Replace the CNAME/DNS onboarding step with a Property ID field; Base URL is taken from config
hostname. - Property ID on Integration is prefilled from step 1 and remains editable.
- Property ID autosave now loads config.json and continues to the Integration form automatically once the property is found; step 1 shows a Continue button instead of Check again / CNAME skip.
- Show Integration status notices from config.json (
isDomainReady,isVerified) with a link to the publisher dashboard. - config.json verification cache is keyed by Property ID only; no fallback Base URL derived from the site domain.
- Hide the Save Changes button while step 1 is shown; remove CMP integration mode hint texts.
- Update admin wording (onboarding checklist, site-host error, config debug messages) for the Property ID flow.
- Tested up to WordPress 7.1.2.
- Contentpass gate: CM preview Accept no longer opens UnlockAll / MarkConsentGranted (placeholders stay behind the wall until onFullConsent).
- onFullConsent always unlocks CP placeholders even if Dynamic Blocking scripts already finished loading.
- Watchdog prepares late-injected Dynamic Blocking scripts instead of letting executable src tags run before consent.
- Activate Dynamic Blocking scripts on CM vendorconsent (official event when a content preview is accepted) — click-class matching was missing Accepts.
- Fallback: trusted clicks on controls inside CM wraps; clearer one-line Dynamic Blocking diagnostics.
- After CM content Accept: clear data-cmp-preview-mode / set data-cmp-haspreview=0 and strip overlays (mode=1 was keeping Accept visible forever).
- Broader Accept-button detection + treat post-boot cmplazyloaded as Accept if the click handler missed CM's control.
- Dynamic Blocking wraps use data-cmp-preview-mode="1" so CM always shows the content Accept UI (even if the vendor cookie already exists). Without this, prior vendor consent hid the preview while dependency scripts stayed inert → empty box.
- Add Dynamic Blocking state diagnostics in the console (wraps / preview buttons / pending scripts).
- Stop hiding CM Dynamic Blocking wraps during Contentpass auth (CSS hide prevented CM content previews → empty box after login).
- Do not treat placeholder unlock / watchdog-off as full consent (removes spurious UnlockAll ignored logs).
- Keep Dynamic Blocking generic: remove MapPress/Leaflet-specific waits, remounts, and text matching.
- Subscription/login no longer auto-activates CM Dynamic Blocking — only onFullConsent or explicit CM preview Accept does.
- Do not unlock Dynamic Blocking on CM/TCF consent while the Contentpass wall is open (cmp_noscreen was loading MapPress behind the wall).
- Unlock only after Contentpass onFullConsent, valid subscription, or an explicit CM content-preview Accept.
- Stop self-unblocking: no auto-click on CM Accept; only activate after real user Accept, Accept All, or valid Contentpass subscription.
- Hide CM content previews briefly while Contentpass authenticate runs (avoids flash then auto-unlock for subscribers).
- Fix fatal parse error on activation (unescaped quote in watchdog JS string).
- Remove leftover Consentmanager content-preview cards after subscription/full unlock (auto-Accept + DOM cleanup) so MapPress is not shown under a second CM banner.
- Stop repeated UnlockAll spam once Dynamic Blocking scripts are active.
- Unlock Dynamic Blocking when Contentpass reports a valid subscription (subscribers often never fire onFullConsent).
- Add [CP4WP] debug logs for UnlockAll / script activation / reveal / remount; avoid revealing wrappers before dependency scripts load.
- Fix content/preview accept: observe CM wrapper accept state, remount MapPress embeds after script load, and tighten preview-button detection.
- Harden CM content/preview accept (inline): activate dependency scripts immediately on preview button click, mark wrappers cmplazyloaded, and trigger resize after load.
- Load Dynamic Blocking dependency scripts in strict order without CM cmplazyload (prevents Leaflet/MapPress race: L is not defined).
- Wait for Leaflet before loading MapPress bridge/main scripts after consent.
- Activate Consentmanager Dynamic Blocking scripts on Accept All / full consent (not only CP placeholders).
- On preview accept, load remaining vendor scripts in order and reveal CM-wrapped content.
- Fix CM Dynamic Blocking accept: do not let the watchdog re-block scripts CM just activated after preview click.
- Avoid nesting cmplazyload wrappers inside an existing CM wrapper; activate remaining vendor scripts in order if CM leaves them inert.
- Dynamic Blocking: wrap custom elements whose tag name matches the rule (e.g. mappress → mappress-map) so Consentmanager can show a content preview.
- Do not auto-add data-cmp-preview on scripts; preview is only set when configured (or for iframes/wrapped content as needed).
- Add Consentmanager Dynamic Content Blocking per block rule (checkbox + CMP vendor ID + optional preview size).
- When Dynamic Blocking is enabled, matched scripts/iframes are prepared for Consentmanager (
cmplazyload,data-cmp-src,data-cmp-vendor) instead of Contentpass placeholders. - Watchdog prepares dynamically inserted matching tags the same way; Contentpass unlock skips CM-managed elements.
- Temporarily hide the CMP dropdown in the admin UI; existing CMP selections (e.g. Sourcepoint) are preserved.
- Unconfigured sites default to Consentmanager in the UI only.
- Docs/readme list Consentmanager as the offered CMP; other CMP external-service sections are commented out for now.
- Sanitize Base URL and Property ID more strictly; clarify Base URL must match the dashboard CNAME.
- Remove debug password; open ?cpdebug=staging and ?cpdebug=settings without a key.
- Make CNAME skip permanent; speed up Property ID autosave debounce.
- Add Doc/Dashboard buttons on Blocking Rules; remove the top Save button.
- Show the Integration debug password in plain text so it can be shared without resetting.
- Default new installs to “CMP already integrated”; existing sites keep their current mode.
- Auto-save when the CMP dropdown or integration mode radios change.
- Rename post-consent field to “Script” and allow a single URL only.
- On the CNAME setup screen, auto-save the Property ID after typing stops (1s) or on Enter, with a toast confirmation.
- 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).