Skip to content

Releases

v0.1.6

Choose a tag to compare

@simon-mundy simon-mundy released this 05 Nov 01:14
804163b

Changed

  • Accepts contenir/contenir-extension-api 0.9 as well as 0.8, so the CMS can host 0.9. 0.9 only adds a service a host
    may lend, so nothing in the add-on changes.

v0.1.5

Choose a tag to compare

@simon-mundy simon-mundy released this 04 Nov 10:47
22ff88b

Changed

  • Accepts contenir/contenir-extension-api 0.8 as well as 0.7, so the CMS can host 0.8. 0.8's changes are
    additions for add-ons, and only hosts must implement the new methods.

v0.1.4

Choose a tag to compare

@simon-mundy simon-mundy released this 21 Oct 13:11
f5e1187

Changed

  • Accepts contenir/contenir-extension-api 0.7 as well as 0.6, so the CMS can host 0.7. 0.7's changes are
    additions for add-ons, and only hosts must implement the new methods.

v0.1.3

Choose a tag to compare

@simon-mundy simon-mundy released this 21 Oct 01:47
3d98471

Changed

  • Requires the API and the library by their new names: contenir/contenir-extension-api ^0.6.1 and
    contenir/contenir-tracking ^0.2. They replace contenir/extension-api and contenir/tracking, so a site never
    installs both. 0.6.1 is the API's first release under its new name.

v0.1.2

Choose a tag to compare

@simon-mundy simon-mundy released this 21 Oct 00:07
a081961

Added

  • The "Tracking and consent" check passes once the site enables the Consent add-on, whose banner holds the tags back
    (TRK-1). The enabled add-ons are read from the site's config/autoload/extensions.*.php (EnabledAddOns).

Changed

  • Requires contenir/tracking ^0.1 from Packagist, where it required 0.1.x-dev through a vcs repository entry.
    A project at stable stability can now install the add-on.
  • Allows contenir/extension-api 0.3, 0.4 and 0.5, whose changes (module templates, menus, handler privileges,
    tabs on described screens and template fragments) are additions the add-on doesn't use, so the CMS can install it
    beside a module.
  • Allows contenir/extension-api 0.6, whose changes (services add-ons provide, and their context in settings
    operations) are additions the add-on doesn't use, so the CMS can install it beside the Cloudflare add-on.

v0.1.1

Choose a tag to compare

@simon-mundy simon-mundy released this 20 Oct 12:04
eaead00

Changed

  • Requires contenir/tracking ^0.1 from Packagist, where it required 0.1.x-dev through a vcs repository entry.
    A project at stable stability can now install the add-on.
  • Allows contenir/extension-api 0.3, 0.4 and 0.5, whose changes (module templates, menus, handler privileges,
    tabs on described screens and template fragments) are additions the add-on doesn't use, so the CMS can install it
    beside a module.

v0.1.0

Choose a tag to compare

@simon-mundy simon-mundy released this 20 Oct 09:54
03e5cc1

Added

  • The Tracking settings section (Site Settings > SEO > Tracking Codes): the Google tag ID, Tag Manager container,
    Meta pixel ID and LinkedIn Insight partner ID under the keys the CMS's Tracking plugin and today's sites use;
    wait for consent, the regions that wait, ad signals and URL passthrough; and "Track on this environment", kept in
    local settings and off by default.
  • Field types that check each ID and the region list as they are saved (tracking:google-tag,
    tracking:tag-manager, tracking:meta-pixel, tracking:linkedin-insight, tracking:regions).
  • The tags as scripts for public pages (Script\TrackingScripts), each with its consent category.
  • Two checks: "Tracking outside production", with fixes to stop tracking a copy or to track production again, and
    "Tracking and consent", which warns while the tags run before visitors consent.
  • The reference documentation for building, testing and releasing an add-on, in the README.