What's new

The platform updates continuously — every entry here is live for all firms the day it appears. Larger directions live on the roadmap.

2026-09-10

Times in listings follow the display clock everywhere. A date-and-time column with no formatter chosen printed the value as stored, which is UTC, so the same moment could read two hours earlier on one screen than on another where a formatter had been picked by hand. The platform's display timezone was never the problem — that path simply never asked it. A column with no formatter now falls back to its kind's default, which converts. Nothing to configure. See Views.
A release may hand a person an archive and a program the installer. A browser refuses a freshly signed installer until the signing certificate has earned its reputation, so the download page and the customer's account now offer the release's archive where it has one, while /download, the fixed per-build address and the manifest keep serving the installer — the program verifies a signature over that exact file and an archive would fail it at every customer at once. The archive is picked up from the installer's folder by itself, matched on its name. The size and file name beside the button follow what the button gives; the SHA-256 stays the installer's. The counter belongs to the release, so the tally, the log and the notice mail read the same either way. See Licensing & downloads.
Installations, counted from the program itself. A download was never an installation: the same person downloads twice, an archive is unpacked on three machines, a link checker fetches a build nobody runs. The program's own update check now carries a random id it draws for itself, and the platform turns that into the number that was missing — how many installations exist, how many starts they made, which versions and which languages they actually run. One row per installation per day on the shipped view Installations under Licensing, and the Claudia tool licensing_installations. A program with the update check switched off is counted nowhere, which is the opt-out, and nothing about the count may ever refuse the manifest. See Licensing & downloads.
The download event reaches Tag Manager containers too. The download page reported file_download straight through gtag, which a GTM container never hears — it listens for dataLayer events. Firms on a container lost every download event silently; firms on a plain GA4 tag never noticed, because for them the two paths look the same. It now goes through the one door the integration built for this, like the purchase event. The Google page documents the event, and says plainly why Google will always count fewer downloads than the platform's own log does.

2026-09-09

The ad click id is kept, not just noticed. Where visitors come from now stores the VALUE of an ad platform's click id (gclid, gbraid, wbraid, msclkid, fbclid, ttclid, li_fat_id) next to the parameter that carried it — and reads it whether or not the link was also tagged, which is the normal case, because Google Ads adds gclid on top of your own tags. Until now only the fact of a paid click survived, as source google and medium cpc, so a sale could never be handed back to the ad that produced it and no ad platform could learn which clicks are worth buying. Two columns on the view, available but not shown by default; exporting them is how an offline conversion import is fed, and the server is where that happens — the Google integration keeps advertising consent signals denied on purpose. See Where visitors come from.

2026-09-08

Where visitors come from. Every site remembers the campaign parameters (UTM, click ids) and the referring site of a visit — for the browser session, first touch wins, an internal link never counts — and attaches them to what the visitor sends: an enquiry (and its CRM lead), a form, a registration, an order, a download. A shipped view Where visitors come from under Structure, the Claudia tool seo_sources, and the privacy page names the processing.
A fixed public address for every published build. /download/<file name> serves the file itself — no cookies, no sign-in, counted apart as direct — so a desktop program's update manifest can name the file, and an older manifest still resolves. The licensing home shows the address under each published release.
The processor's customer portal, for the signed-in customer. Where a merchant of record (Paddle) took the money, Orders & invoices in the customer account opens the processor's portal for that customer — a session minted on the server by the sign-in's address, nobody created by the lookup, the shared link as the fallback. Invoices, payment details and cancellations are managed there.
The customer account speaks English in its addresses. /account/, /account/sign-in, /account/register, /account/documents, /account/shipments, /account/downloads, /account/enquiries, /account/support, /account/files, /account/details, /account/settings — the platform's base is English everywhere. The former Slovak addresses (/ucet/…) answer 301 to their new form with the query kept, so verification and password links in mails already sent still land. Payment returns say ?payment=ok|cancelled, an invitation link ?invitation=.
Transport → Billing export without a firm open. The page now explains itself (the toolbar picks the firm) instead of answering 404, like every other transport screen; a firm with the module off is sent to the switch.
A firm's own words for the web's static pages. Meta tags → Static pages: a title and a description per path for the built-in pages (download, privacy, cookies, search, cart, the account), which used to carry the platform's strings on every site. The share card and the canonical address follow.
The language switcher shows flags and names. A dropdown with the Tabler country flags and the languages' own names; a Style setting picks flags, names, both or the bare codes.

2026-09-07

Privacy page names licence activation. A firm that publishes a program to download gets a section on its privacy page and PDF about the activation data (order number, equipment fingerprint, IP address) and the download record; a firm without a published release sees nothing new.
Download notices. A firm may have every download of a release mailed to one address — the build, the time, who and through which door — with the brandable template Licensing: download notice.
Sitemap follows the site's default language. The root tree is the site's own default language; every other site language sits under its prefix — no twin tree of the root.
Record pages render faster. A public record page renders inside one memo and the reference resolver warms itself for the whole record at once — a zone with thousands of postal codes answers in a second instead of many.
Depots stay internal. A transport depot record is for the firm's people only: never a public page, never in the sitemap.
Public download with a counter. The newest published release downloads without an account, every download is counted, the desktop program's update check reads /update.txt (the manifest uploaded beside the installer) and fetches /download; the download page fires an analytics event on the click.

2026-09-06

The product page follows the web view mode. A firm trims what the storefront shows of a variation on Manage display (mode web) without touching the default rows; a mode without its own rule inherits the default row's visibility.
Customer area with tabs. The account page is one frame with tabs — Overview, Orders & invoices, Shipments, Downloads & licences, Enquiries, Support, Files, My details, Account settings — each its own address under /account/; a sidebar on a desk, a scrolling strip on a phone. The Slovak interface strings of the whole area are complete.
My details in the customer account. Name, phone, billing address and a company's identifiers are kept on the customer's own contact from the account page. Registration links the contact to the account at once, a signed-in customer's address typed at the checkout is remembered on their contact, and a contact with only the flat address fields renders it as the billing address on every document.
A variation's bookkeeping stays off the web. SKU, policies, tracking, cost, costing method, VAT rate, ordering weight and a gateway's price id are born with visibility never on the variation display; the back office keeps them, the firm may open a field on Manage display.
Download log. Every download of a release is recorded — who, which build, when — with a tally per release on the Licensing screen, a shipped view Download log, the trail and a Claudia tool.
Pricing page. Two price cards sit centred with the licence card highlighted; five intro tiles fall as three plus two centred; the hidden price label reads for screen readers.
Licensing moved to Commerce in the back-office menu; the Dashboard entry left Content (/backoffice/ is the dashboard). The menu sync follows a moved screen and retires a dropped one.

2026-09-04

Transport phase 2 live. Tariffs with surcharges (express as an add-on), the price calculator and the ride fare estimate blocks, taxi rides with the driver's screen and the customer's portal page, the monthly billing export into invoice drafts, SMS through the firm's own gateway and the day-before notice, reports with a chart and the on-time share, holidays, the driver's offline queue with proof of delivery. Transport is its own back-office group; Fleet keeps the vehicles.
Geo: the Slovak Post register and streets. geo_sync --country SK --supplement adds the postal codes GeoNames lacks and every street of the towns whose code differs by street as the sixth geo level; a municipality only the register knows is founded from it.
Share cards on the built-in pages, profiles in the front page's data, one address for the enquiry page. See Content → Menus and addresses → Meta tags.
The web menu remembers a moved group. A group that moves under another (or back to the top) takes its row along instead of growing a copy.

2026-08-21

Letterhead PDFs & the legal floor. Any page type can offer a PDF download (top-right mark) rendered into the firm's letterhead — the invoicing identity fills the head, the site the foot. The privacy (GDPR) and cookies pages download as PDFs built from the very same translated text they display. A selling site's legal set — terms, refund policy with a refund-request form, footer links — seeds per firm, shaped by Paddle's seller checklist.
Invoicing identity & the payment QR. Each firm writes its own supplier box — name, address, IČO/DIČ, the register note — printed on every document issued from then on; documents asking for money carry a PAY by square QR for one-scan payment, and a paid invoice drops the payment box entirely. See invoicing identity.
Wire transfers close themselves. Ordering with bank transfer mails a pro-forma invoice with IBAN and variable symbol; the firm's Fio account is polled and the incoming payment matched automatically — the invoice (already paid) and any licence keys follow without a hand touching them. Unmatched money waits in a review queue. See wire transfers & Fio bank.
Selling a downloadable program. Releases, tiers as variations, signed licence keys the program verifies offline, downloads and licences in the customer account. See licensing & downloads.
Human check on the auth doors. A firm can require Cloudflare's Turnstile (the no-puzzle CAPTCHA) on customer sign-in, registration and password doors — its own keys, verified server-side, secret never shown again. See safety.
Login shield at the edge. One switch on the Safety screen caps the customer sign-in doors at the edge — a brute-force is refused before the server hears of it. See safety.
One sign-in door. Customers and staff sign in at the same place; each lands in their own world — customers in their account area, staff in the back office.
Organizations can be deleted. An operator removes a firm whole — inventory first, then one atomic step; audit evidence survives unlinked, user accounts and other firms are untouched. See deployment.
Customer sign-in completed. Forgotten passwords get a reset link, lost verification mails can be re-sent, and a customer of one firm can become a customer of another with the same account — one registration step, no support ticket. The request doors never reveal whether an account exists. See the customer portal.
Meta patterns per firm. The meta-tag default patterns (titles, descriptions, social cards) now belong to each firm separately — the screen edits the open firm's patterns and says so, and no firm's wording can appear on another firm's pages. Every firm started with its own copy of the previous shared set, so nothing changed until edited. See menus & addresses.
Four more frontend behaviors. A banner can glide with real parallax, the bricks style packs a true masonry wall in reading order, number fields gain an animated counter that always keeps the true value in the page, and grid/gallery/bricks tiles can tilt under the pointer. All clicked together, all with graceful fallbacks, all respecting reduced-motion readers. See the showcase and frontend behaviors.

2026-08-20

Frontend behaviors. Galleries open a touch-friendly lightbox with swipe and zoom, carousels loop and autoplay, a fade effect turns any carousel into a slideshow — all clicked together in listing styles, never coded. Image fields join in with their own gallery and carousel formatters. See the showcase and the frontend behaviors page.
Image cropping. The file manager crops a picture in place — aspect presets, rotation, and every link and share keeps working because the file stays the same file.

2026-08-19

Card payments. The web shop takes cards through Stripe or Paddle — each firm with its own keys and its own sandbox switch, webhooks as the source of truth, refunds from the order page.
Shipping carriers. DPD, UPS and Packeta as configurable carriers; a product can narrow which carriers may deliver it, and checkout offers only what every line allows.
Commerce reorganized. All shop settings live under Commerce → Settings, with each payment provider and carrier on its own page carrying its own documentation.
API hub. A firm declares a resource once and gets three doors: a REST route, an OpenAPI description per reader, and assistant tools — all through one gate with hashed keys, scopes and rate limits.
Edge protection. A firm connects its Cloudflare token under Backoffice → Safety and manages Under-Attack mode and country rules from the same screen — live state, no stored mirror.

2026-08-17

A shell for every site. The sidebar navigation became one shared shell: per-block sticky pinning, a collapsed dropdown on phones, and documentation trees and menus rendering the same way everywhere.
Branding per firm. Every firm has its own logo, colors and corner radius; the design scale is inherited, the identity never is.

2026-08-13

One file tree. Every stored file — uploads, mail attachments, frozen PDFs, editor images — lives in one per-firm tree with Public and Private branches, quotas and share links.