Developers page

The introduction gives the date of the last check: “A newer version usually works; it is tested for the next release.” The table has three columns:

• Software: WordPress, PHP, then plugins and themes.
• Tested: the version tested and its date, with a label that says how. For WordPress and PHP, the version tested and the minimum.
• On this site: the version installed on your site, or Not installed.

WordPress, PHP and the plugins and themes installed on your site are in the table. The others are folded under Other plugins and themes tested, with their number. Type a name under Find a plugin or theme: a folded section that holds it opens.

The list grows with each version of Cookie Rocks. The table in your administration is the reference for the version you run.

The 675 tools whose cookies Cookie Rocks knows in your pages, with their logos, in one folded section per category: Necessary, Preferences, Statistics, Marketing, each with its number. Type a name under Find a service to find a tool. The column What it does gives the purpose of each one. The scan of the Cookies screen then says, for each tool found on your site, whether it loads before the visitor’s choice.

This section appears with Cookie Rocks Pro only: the Audit adds no banner. Add your CSS where your site already keeps its own:

• Appearance, Customize, Additional CSS (classic themes);
• Appearance, Editor, Styles, Additional CSS (block themes);
• the custom CSS field of your theme or page builder;
• the stylesheet of your child theme.

Start with the variables: one line changes the whole banner. Use the selector .cr-root[data-theme] so that your values apply in the light and dark themes. The screen shows this example, with a Copy button:

/* Square corners and a lighter shadow, in light and dark themes */
.cr-root[data-theme] {
	--cr-radius: 6px;
	--cr-shadow: 0 8px 24px rgba(0, 0, 0, .12);
}

/* Buttons in capital letters */
.cr-root .cr-btn {
	text-transform: uppercase;
	letter-spacing: .04em;
}

Variables

--cr-gap sets the distance between the floating box and the screen edges: 20 px by default. The Distance from the screen edges setting of the Appearance screen goes from 0 to 40 px. At 0, the box sits in the corner, and its corners on the screen side are square. The bar at the bottom of the page does not change. On a phone, the distance is 8 px at most.

Classes

.cr-policy__credit is the thin frame of the credit at the bottom of the cookie policy, when Credit is ticked on the Consent screen. Its style is written in the element itself, so that it fits every theme.

Video and map placeholders are drawn inside their own frame: they follow the accent colour, not your CSS. While the details panel is open, the html element has the class cr-locked.

These five sections appear with Cookie Rocks Pro only. They give a short summary, with code to copy:

• Hold a script until consent: known cookies are held automatically. For another script, change its type and add the category, for example <script type="text/plain" src="…">, or <iframe> for a frame. After consent, held scripts download together and run in page order. A script that takes more than 3 seconds to arrive stops holding back the next ones: code that calls a tool right after its script should wait for that tool to be ready. See JavaScript API and events.
• Let a script load at once: add the attribute data-cr-ignore to a script or a stylesheet, and Cookie Rocks leaves it alone, before any choice, even when it belongs to a known service. Use it only for code that sets no cookie and sends no personal data, or that the law lets load without consent. It does not apply to iframes.
• “Manage cookies” link: the [cookie_rocks_link] shortcode, a menu link to #cr-preferences, or any element with the attribute data-cr-open. For the United States, [cookie_rocks_link type="do-not-sell"] writes “Do Not Sell or Share My Personal Information”, in the language of the page. For your own wording: [cookie_rocks_link text="…"]. See Shortcodes.
• Accounts managed outside WordPress: with the GPC signal honoured, a refusal follows the visitor’s account. WordPress accounts (WooCommerce, memberships) need nothing. If your customers sign in with another system, call do_action( 'cookie_rocks_account', $customer_id ); on each page they see while signed in, before anything is printed (on init, for example). Only a fingerprint of the ID is kept.
• JavaScript: CookieRocks.open(), CookieRocks.hasConsent(), CookieRocks.onConsent(), the cookie-rocks:change event, and the Google Tag Manager events cr_consent_ready and cr_consent_update, with the variable cr_consent. See JavaScript API and events.
• PHP filters: cookie_rocks_texts, cookie_rocks_categories, cookie_rocks_services, cookie_rocks_config, cookie_rocks_gcm_map. See PHP filters, actions and REST API, which lists every hook.