Skip to content

gosite 0.68.0

Choose a tag to compare

@charly-palencia charly-palencia released this 13 Nov 12:42
· 4 commits to main since this release
55d7d30

Includes 0.66.0 and 0.67.0, which were not published as releases.

0.68.0

Analytics: Meta Pixel and store events

  • Added: Meta Pixel (meta-pixel, { "pixelId": "..." }, 15 to 20 digits),
    in the marketing category. Nothing from Meta loads, and no _fbp/_fbc
    cookie is written, before marketing consent; withdrawing it clears them. No
    <noscript> image. Offered on thin sites only: a legacy CMS does not list it.
  • Added: store events. With Commerce, the product page, add to cart,
    checkout and confirmation send ViewContent, AddToCart,
    InitiateCheckout and Purchase (value, currency, variant ids, item count,
    order id) through analytics.track(), so every enabled provider gets them
    under its own consent. Purchase goes once per order in a browser session,
    with the order id as Meta's eventID.
  • Changed: no replay after a late accept. An event raised before the
    visitor answered the banner is dropped, also when they accept later on the
    same page. Before, page-code analytics.track() calls were replayed. This
    applies to every provider.
  • Changed: the GTM key in the README is containerId, as the code always
    had it, and an extra config key is kept and named on the Analytics screen,
    as the code did.
  • Upgrade (thin sites): gosite generate (adds the gosite.layout marker
    to cockpit/config.core.php), rebuild the CMS image, and update the core
    module (go get github.com/Avanxo-Technology/gosite-cli/core@v0.68.0).
    A theme that replaces the product, checkout or confirmation page must keep
    the new data-analytics-event block.

0.67.0

Replica: protected content and comparison between instances

  • Added: protected content per instance. The Replica screen has a
    Protected content card with one switch per content model. A protected
    model refuses every replication write (entries and definitions), whoever
    sends it; local editing and reading are not affected. Nothing is protected by
    default. Each change is in the activity log.
  • Added: a push skips protected models and continues. The destination's
    manifest lists them; they are counted as protected, not as errors. A pull
    does not write into a model protected on the local instance.
  • Added: replica:diff and the Compare view. Read-only, per entry: only
    here, changed here, changed there, only there, same. Sameness is a hash of
    the content, so a re-save without changes is same.
  • Added: push a selection. replica:push <target> <model> --ids=a,b, or
    tick entries in the Compare view.
  • Changed: identical entries are skipped as same, in the dry run and in
    the real run, so a run reports what its dry run planned. Against a 1.0.0
    destination the real run still rewrites them.
  • Fixed: singletons pair by model. Each instance creates its own singleton
    (for example analyticsConsent), so the two sides had different ids: a push
    left two documents on the destination and the site read either one. A push
    or pull now replaces the destination's singleton, and the next push merges a
    duplicate left by 1.0.0.
  • Fixed: a push to a plain Cockpit no longer fails on an empty singleton.
    Its 404 stopped the whole run.
  • Upgrade: Replica goes to 1.1.0 and is baked into the CMS image, so rebuild
    the CMS of each site that uses it. Upgrade the destination before the source:
    a 1.0.0 source that pushes to a protected model fails that run with a
    "protected" message and writes nothing for the model; a 1.0.0 destination has
    no protection, and every push says so.

0.66.0

Mailer: send an order's e-mails to the address the buyer chose

  • Added: the recipient "The order's receipt address" (order_receipt).
    It sends to the addresses in the order's metadata.receipt_email (one or
    more, separated by commas; invalid ones are dropped), and to the order's
    e-mail when the key is missing or holds none. A checkout can ask the buyer
    where the purchase details go without changing the order's e-mail.
    A migration adds the value to mailer_rule.recipient.
  • See gosite docs medusa-mailer.