Kaleta 2.7.0

Kaleta 2.7 is about moving existing sites over without losing anything: a report that checks every old address before the domain is switched, old form entries in Enquiries, SEO plugin data and custom post types from WordPress, and the builder features business sites made with page builders rely on.

Check the move before going live

Administration → Import and export → Check the move before going live. Enter the address of the old site. Kaleta finds its pages the same way as the website import, then looks up every old address on this site.

It reports:

• Missing addresses – nothing at the address and no redirect, so visitors would get a 404.
• Pages that are not published yet – imported pages stay hidden until you publish them.
• Redirect chains – an address redirected more than once.
• What got lost – a search engine description, a form, or most of the images of the old page.

The report ends with the checks of the whole site: mail, off-site backups, company details, indexing and the cookie bar. Nothing is changed – the check only reads. Claude runs the same report with the new migration_report tool.

Moving a site with Claude

• The migrate_site prompt describes the whole move. Claude reads the old site – through its own connection, for example Breakdance or WordPress – and rebuilds it here as drafts: the look, the pages, the header, the footer, forms and pop-ups. It keeps every old address working and ends with the migration report. Nothing is published until you say so.
• Old form entries: import_enquiries brings old form submissions into Enquiries, so no enquiry is lost in the move. An entry imported once is skipped the next time. Entries older than the retention period of enquiries are deleted with the next clean-up.

WordPress import

• SEO plugin data: titles, descriptions and noindex from SmartCrawl, Yoast SEO and Rank Math come over. Plugin variables such as %%sitename%% are filled in. A title that is only the plugin's default pattern is skipped – Kaleta builds the same one itself.
• Custom post types and custom fields (CPT UI, ACF, Secure Custom Fields) become collections:
  • each post type is one collection, each field a collection field;
  • field types are guessed from the values: text, number, date, link, image or formatted text;
  • the collection takes the old address prefix, so /reference/kitchen/ keeps its address;
  • images of the fields download in the image step;
  • repeaters, galleries and relationships are left out, and the preview names them.

Builder

• Header on scroll: a header can sit transparent over the first section and turn solid, get smaller, or both, as the visitor scrolls. Its text can be light or dark while it is transparent. CSS only; visitors who prefer less motion get the solid header.
• Menus: an icon next to a menu item; in the mega menu, groups become columns with headings, and items can have a short description.
• Display conditions: show an element only in some language versions, or only when the page address has a parameter, e.g. ?utm_campaign=spring. A page with a parameter condition is never cached.
• Copy and paste between Kaleta sites: copied elements carry their shared classes and components. Paste in the builder of another site, or use More actions → Paste from another Kaleta site. Images of the other site keep loading from it (https) until you replace them; the builder says how many.
• Motion: reveal from the left, from the right or from a blur; motion while scrolling (parallax, a slight rotation, growing into view); and ready-made hover effects (lift with a shadow, grow, nudge, fade). All CSS, and off for visitors who prefer less motion.

Updating

Update from Settings → Backups and updates. It works from every earlier release. There is no database change in this release.