What’s new in Core dna Platform 2026.11

Container pages

A container page is a node in the page tree. It gives its URL segment to the pages beneath it, but visitors never see it. A page called Consulting under a container with the slug solutions has the address /solutions/consulting, and /solutions itself is not a page.

To add a container, go to Content › Pages, open the add menu on the parent page's row and choose Add Container page. The same menu has Add subpage for an ordinary page. A container has a name, a slug, a parent and a site, but no layout and no content. Its name shows only in the page tree. A container can hold other containers. The root page cannot be a container.

Under Direct URL requests, Direct URL behavior sets what happens when someone opens the container's own address: Return a 404 or Redirect to the nominated page. A redirect goes to the page in Redirect to, with the Redirect type Temporary (302) or Permanent (301), and keeps the query string. The target must be a page on the same site, and it cannot be another container. If the target is later deleted or unpublished, the container returns a 404. The Pages setting Default behavior for new container pages chooses which option the add form selects first.

A container has no address, so the sitemap and the search index leave it out. The pages beneath it stay in both. The frontend pages listing also leaves containers out. Menus have a new element type, Container page. A menu element for a container has an empty URL. In templates, isContainer() is true for a container and false for every other page. On a container, getFullPath() and getUrl() return an empty string. Use isContainer() to show a container as a label instead of a link, for example in a breadcrumb trail. In the API, each page record has a new container field.

Purchase controls

Products and variants have a new Purchase controls tab with six rules. Each field is empty by default, and an empty field sets no rule.

• Minimum quantity: the smallest quantity a customer can buy.
• Maximum quantity: the largest quantity a customer can have in the cart.
• Quantity step: quantities count up from the minimum in these steps. Minimum 2 and step 3 allow 2, 5, 8 and so on.
• Multiple of: only multiples of this number can be bought. 5 allows 5, 10, 15 and so on.
• Overall quantity: the total a customer can buy, counting the orders they have already placed.
• Overall period: how far back the overall quantity counts, in seconds (2592000 is 30 days). Empty or 0 counts every past order.

The rules of a variant apply to that variant only. A variant does not take the rules of its product. Cart lines with the same product code count together. The cart and the checkout check the rules when the quantity changes. When a quantity breaks a rule, the lines stay at the quantity the shopper chose but become unavailable, and a message names the rule, for example "At least 6 of Shiraz is required; the cart has 4". A shopper can always remove a line. While a line breaks a rule, the shopper cannot start the checkout or pay. A guest with no customer record is checked against the cart only.

In templates, getMinQuantity(), getMaxQuantity(), getQuantityStep(), getQuantityMultiple(), getOverallQuantity() and getOverallPeriod() return the rules, for example to set the min and step of a quantity input. In the API, products and variants accept and return the same fields.