<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Jumoo Blog</title>
  <subtitle>Jumoo is a digital services company specialising in helping people build evidence based, customer focused, digital services.</subtitle>
  <link href="https://blog.jumoo.co.uk/feed.xml" rel="self" type="application/atom+xml"/>
  <link href="https://blog.jumoo.co.uk/" rel="alternate" type="text/html"/>
  <id>https://blog.jumoo.co.uk/</id>
  <updated>2026-11-13T15:10:05Z</updated>
  <author>
    <name>Jumoo</name>
  </author>
  <icon>https://blog.jumoo.co.uk/images/og-default.png</icon>
  <entry>
    <title>v19 Release Candidates</title>
    <link href="https://blog.jumoo.co.uk/2026/v19-release-candidates/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/v19-release-candidates/</id>
    <published>2026-11-13T15:10:05Z</published>
    <updated>2026-11-13T15:10:05Z</updated>
    <category term="uSync"/>
    <category term="translations"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;We&#39;ve released v19.0.0-rc1 of our packages, ready for the Umbraco v19 release candidate.&lt;/p&gt;
&lt;p&gt;These are release candidates, so you&#39;ll need to include prereleases to see them in your package manager.&lt;/p&gt;
&lt;h2&gt;What&#39;s out&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/KevinJump/uSync/releases/tag/v19.0.0-rc1&quot;&gt;uSync&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nuget.org/packages/uSync.Complete/19.0.0-rc1&quot;&gt;uSync.Complete&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/uSync.Forms/releases/tag/v19.0.0-rc1&quot;&gt;uSync.Forms&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/uSync.Umbraco.Commerce/releases/tag/v19.0.0-rc1&quot;&gt;uSync.Umbraco.Commerce&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nuget.org/packages/Jumoo.TranslationManager/19.0.0-rc1&quot;&gt;Translation Manager&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/Our.Umbraco.MaintenanceMode/releases/tag/v19.0.0-rc1&quot;&gt;Maintenance Mode&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can see the latest versions of all our packages on &lt;a href=&quot;https://releases.jumoo.co.uk/&quot;&gt;releases.jumoo.co.uk&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The rest of our packages will follow before the full v19 release.&lt;/p&gt;
&lt;p&gt;If you&#39;re trying out the Umbraco v19 RC, give these a go and let us know on GitHub if anything breaks.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>uSync.Complete 17.7 - Side by side</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-complete-17-7-side-by-side/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-complete-17-7-side-by-side/</id>
    <published>2026-11-10T10:40:50Z</published>
    <updated>2026-11-10T10:40:50Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;uSync.Complete 17.7 (Umbraco 17) and 18.4 (Umbraco 18) are out. The headline is a new &lt;strong&gt;Side by side&lt;/strong&gt; view in the change details dialog. It shows you what an item will look like once it&#39;s synced, laid out the way you&#39;d see it in the backoffice, before anything changes.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.7.0
&lt;/pre&gt;
&lt;h2&gt;Inspired by Moriyama&lt;/h2&gt;
&lt;p&gt;This one isn&#39;t all our idea, and we want to say so up front.&lt;/p&gt;
&lt;p&gt;The Side by side view is heavily influenced by Moriyama&#39;s &lt;a href=&quot;https://github.com/Moriyama-Umbraco/umbraco-pr-preview&quot;&gt;umbraco-pr-preview&lt;/a&gt;. It&#39;s an Azure DevOps extension that adds an Umbraco tab to pull requests. It takes the changed uSync (and Umbraco Deploy) files in a PR and renders them with the real backoffice property editors, so a reviewer sees a document type change the way it&#39;ll look in Umbraco.&lt;/p&gt;
&lt;p&gt;When we saw it, the reaction was more or less &amp;quot;oh, that&#39;s how it should look&amp;quot;, and it&#39;s shaped a lot of what&#39;s in this release. So thank you to the team at Moriyama for building it and putting it out in the open. If you review uSync changes in Azure DevOps, go and have a look at it.&lt;/p&gt;
&lt;h2&gt;Side by side&lt;/h2&gt;
&lt;p&gt;Open the details of any change in a Publisher report, and you now get the item twice. On the left is the incoming version, the one you&#39;re about to send. On the right is the current one, on the site it&#39;s going to. Each side is labelled with the site&#39;s name, so you can tell which is which at a glance.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/side-by-side-push.png&quot; alt=&quot;The Side by side tab for a push of the Home page, with the new title, subtitle and main image on the left and the live site&#39;s values on the right&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Every value is shown in its real property editor. Text boxes are text boxes, the media picker shows the image, block lists look like block lists. Values that differ are marked green on the incoming side and red on the current one. A dot on a tab tells you there are changes on it, and the dialog opens on the first tab that has some.&lt;/p&gt;
&lt;p&gt;There&#39;s an &lt;strong&gt;Only show changes&lt;/strong&gt; toggle for when a page has forty properties and you only care about three of them. Content that varies by language gets a language switch.&lt;/p&gt;
&lt;p&gt;The editors are there to look at, not to use. Nothing you click in the preview changes either site.&lt;/p&gt;
&lt;h2&gt;Document types and data types&lt;/h2&gt;
&lt;p&gt;It isn&#39;t just content. Document, media and member types are laid out like the document type editor, with their compositions merged in, and every property rendered by its own editor. Added, removed and changed tabs, groups and properties are highlighted.&lt;/p&gt;
&lt;p&gt;Here&#39;s a TimeMachine rollback of a document type, where someone added two properties that the rollback is going to take away again:&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/side-by-side-rollback-doctype.png&quot; alt=&quot;A TimeMachine rollback of the Article Controls document type, showing the Reading time and Topics properties marked as removed&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Data types show a preview of the editor, plus their configuration with the changed settings picked out.&lt;/p&gt;
&lt;p&gt;If a new property uses a data type that only exists in what&#39;s being synced, the preview builds that data type from the sync too, so the property still shows up in its real editor. The same goes for new compositions. Nothing gets created on the site to do this.&lt;/p&gt;
&lt;h2&gt;Where you&#39;ll see it&lt;/h2&gt;
&lt;p&gt;The preview is built from whatever is being synced, not from the site&#39;s uSync folders. So you see what&#39;s actually going to happen:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Publisher pushes and pulls.&lt;/strong&gt; A push is previewed on the target server, because that&#39;s where the sync pack is. A pull is previewed on your site.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Exporter imports.&lt;/strong&gt; The preview comes from the sync pack you uploaded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Snapshots.&lt;/strong&gt; The preview comes from the snapshot.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Restore points.&lt;/strong&gt; The preview comes from the restore point.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;TimeMachine rollbacks.&lt;/strong&gt; You see the item as it will be after the rollback.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Previewing a push needs 17.7 / 18.4 on the target as well. If the target is on an older version, you get the Details tab as before. The background, result and approval reports keep the Details view for now.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;The other tabs&lt;/h2&gt;
&lt;p&gt;The dialog&#39;s tabs are now &lt;strong&gt;Side by side&lt;/strong&gt;, &lt;strong&gt;Web page&lt;/strong&gt; and &lt;strong&gt;Details&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Web page&lt;/strong&gt; is the side by side view of the rendered pages that&#39;s been in Publisher &lt;a href=&quot;https://blog.jumoo.co.uk/2021/uSync-8-9/&quot;&gt;since 8.9&lt;/a&gt;. It shows the incoming page next to the live one, and it now tells you when the item doesn&#39;t exist on the other site yet.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/side-by-side-webpage.png&quot; alt=&quot;The Web page tab showing the Home page on this site, with the new image and title, next to the page on the live site&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Details&lt;/strong&gt; is the property-by-property diff you already know.&lt;/p&gt;
&lt;h2&gt;In uSync too&lt;/h2&gt;
&lt;p&gt;The preview itself lives in uSync, and has done since uSync 17.6 / 18.3. If you use free uSync, you get the Side by side view on your import reports, previewing what&#39;s in your uSync folders against the site.&lt;/p&gt;
&lt;p&gt;uSync.Complete builds on that to preview from sync packs, snapshots, restore points, rollbacks and remote servers.&lt;/p&gt;
&lt;h2&gt;Getting it&lt;/h2&gt;
&lt;p&gt;Side by side is in uSync.Complete 17.7 for Umbraco 17 and 18.4 for Umbraco 18. 18.4 needs uSync 18.3.1 or later.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.7.0
&lt;/pre&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 18.4.0
&lt;/pre&gt;
&lt;p&gt;There&#39;s plenty more in this release, including a temporary licence option for keys from older versions, a new default &amp;quot;Content &amp;amp; Media&amp;quot; server template, and a notification for code that needs to know when a push has finished. The &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v17.7.0&quot;&gt;v17.7.0&lt;/a&gt; and &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v18.4.0&quot;&gt;v18.4.0&lt;/a&gt; release notes have the full list.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Translation Manager - The Glossary</title>
    <link href="https://blog.jumoo.co.uk/2026/translation-manager-the-glossary/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/translation-manager-the-glossary/</id>
    <published>2026-10-27T22:00:16Z</published>
    <updated>2026-10-27T22:00:16Z</updated>
    <category term="Umbraco"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;Since 17.9, Translation Manager has had a Glossary: one list of the terms you need translated a particular way, or not translated at all, that the machine and AI connectors read every time they translate.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager
&lt;/pre&gt;
&lt;h2&gt;The problem&lt;/h2&gt;
&lt;p&gt;Machine translation is good. It&#39;s also confident, and it doesn&#39;t know anything about your organisation.&lt;/p&gt;
&lt;p&gt;Your product names get translated. Your brand gets translated. The term your industry has agreed on in German gets swapped for a perfectly reasonable word that nobody in your industry uses. And because a lot of this happens in the background now, you often don&#39;t notice until a translator (or worse, a customer) points it out.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://blog.jumoo.co.uk/2026/translation-manager-feature-roundup/&quot;&gt;Translation Memory&lt;/a&gt; helps a bit here: once you&#39;ve fixed a phrase, the fixed version gets reused. But memory works on whole phrases, after the fact. What you actually want is to tell the translator up front: this word, always this way.&lt;/p&gt;
&lt;p&gt;That&#39;s what a glossary is.&lt;/p&gt;
&lt;h2&gt;Where it lives&lt;/h2&gt;
&lt;p&gt;The Glossary sits in the &lt;strong&gt;Translations&lt;/strong&gt; section, below the job lists, next to Translation Memory. The Translations dashboard shows how many terms you have.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/glossary-list.png&quot; alt=&quot;The Glossary in the Translations section, showing English terms with their German values, three marked Do not translate and one still missing&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Seeing it needs the new &lt;strong&gt;View glossary&lt;/strong&gt; permission. On upgrade only Administrators get it, so you&#39;ll need to add it to any other groups that should have it (and if you were logged in during the upgrade, log out and back in to see it).&lt;/p&gt;
&lt;h2&gt;Terms&lt;/h2&gt;
&lt;p&gt;A term is a bit of source text in a source language, with a value for each language you translate into. For each language you can either give the translation it must use, or switch on &lt;strong&gt;Do not translate&lt;/strong&gt;, and the term is left exactly as written.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/glossary-term.png&quot; alt=&quot;Editing the term workflow: a note explaining which meaning it covers, and its German and French values&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Terms can be case sensitive (off by default), which matters when &amp;quot;IT&amp;quot; the department and &amp;quot;it&amp;quot; the word need to be treated differently. There&#39;s also a notes field for your own benefit. Notes are never sent to the translation service.&lt;/p&gt;
&lt;p&gt;The list has a &lt;strong&gt;Missing only&lt;/strong&gt; filter, so when you add a new language you can work through the terms that don&#39;t have a value for it yet.&lt;/p&gt;
&lt;h2&gt;Import and export&lt;/h2&gt;
&lt;p&gt;Nobody wants to type in 400 terms, and quite often the list already exists somewhere: a spreadsheet the marketing team keeps, or a term base your translation agency has built up over the years.&lt;/p&gt;
&lt;p&gt;So you can import and export in two formats:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CSV.&lt;/strong&gt; One language pair per file, with the culture codes in the header row (&lt;code&gt;en-US,fr-FR&lt;/code&gt;). An optional third column, &lt;code&gt;doNotTranslate&lt;/code&gt;, set to &lt;code&gt;true&lt;/code&gt; marks a term that should be left alone. The export opens properly in Excel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;TBX.&lt;/strong&gt; The standard term base exchange format that translation tools and agencies use. A TBX file can carry every language at once.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/glossary-import.png&quot; alt=&quot;The Import Glossary dialog, importing an English to German CSV file&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Importing replaces the values for the target language rather than merging with them, and the import tells you so before it starts. If the file can&#39;t be read, nothing changes.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Which connectors use it&lt;/h2&gt;
&lt;p&gt;This is the important bit, because a glossary only helps if the thing doing the translating reads it.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;DeepL&lt;/strong&gt; (connector 17.3.0 and above). Translation Manager uploads your glossary to DeepL as a real DeepL glossary, one per language pair, and DeepL uses it during the translation. It only uploads again when the terms have changed. This is marked as a prototype in the connector for now, and it only works for the language pairs DeepL supports glossaries for.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AI connector&lt;/strong&gt; (17.6.0 and above). The terms for the language pair go into the prompt, with do not translate terms marked so the model copies them as they are. It works with all the AI providers the connector supports (OpenAI, Azure OpenAI, Claude, Gemini, GitHub Models and Ollama).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The built-in Google and Microsoft connectors don&#39;t use it yet, and neither does XLIFF (the human translators on the other end of an XLIFF file will have their own term base). The Glossary page tells you which of your active connectors support it, so you&#39;re not left wondering.&lt;/p&gt;
&lt;h2&gt;Turning it on&lt;/h2&gt;
&lt;p&gt;The Glossary is off by default. It switches on when a connector that supports it has its glossary option ticked (&lt;strong&gt;Use Translation Manager Glossary&lt;/strong&gt; for DeepL, &lt;strong&gt;Use Glossary&lt;/strong&gt; for the AI connector), or you can turn it on for the whole site in appsettings:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;Translation&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;GlossaryEnabled&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;For developers: there are notifications when terms are saved, deleted or imported (&lt;code&gt;GlossaryUpdatedNotification&lt;/code&gt; is the one to watch), and base classes if you want your own connector to use the glossary.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Getting it&lt;/h2&gt;
&lt;p&gt;The Glossary is in Translation Manager 17.9 and above for Umbraco 17, and 18.3 and above for Umbraco 18.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager
&lt;/pre&gt;
&lt;p&gt;The &lt;a href=&quot;https://docs.jumoo.co.uk/&quot;&gt;user guide&lt;/a&gt; has the detail, including the CSV and TBX formats, and the &lt;a href=&quot;https://github.com/Jumoo/Jumoo.TranslationManager.Issues/releases&quot;&gt;changelog&lt;/a&gt; has the version by version breakdown.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>uSync.Complete 17.6 - The Sync Queue</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-complete-17-6-the-sync-queue/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-complete-17-6-the-sync-queue/</id>
    <published>2026-10-27T21:59:14Z</published>
    <updated>2026-10-27T21:59:14Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;uSync.Complete 17.6 (Umbraco 17) and 18.3 (Umbraco 18) are out, and along with the approvals we talked about in &lt;a href=&quot;https://blog.jumoo.co.uk/2026/usync-complete-17-6-rc/&quot;&gt;the release candidate post&lt;/a&gt;, they bring a new way to push things with Publisher: the Sync Queue.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.6.0
&lt;/pre&gt;
&lt;h2&gt;The problem&lt;/h2&gt;
&lt;p&gt;Publisher has always been good at pushing one thing. You find the page, you push it, it goes.&lt;/p&gt;
&lt;p&gt;Real changes don&#39;t usually look like that. An editor spends a week working on a new section, tweaks a couple of existing pages to link to it, uploads some images, and maybe someone adds a data type along the way. When it&#39;s ready, all of that needs to go to live, and the only way to do it was to remember every item and push them one at a time (or push a parent with its children and take everything else under it too).&lt;/p&gt;
&lt;h2&gt;Turning it on&lt;/h2&gt;
&lt;p&gt;The queue is switched on per server. Tick &lt;strong&gt;Allow queuing&lt;/strong&gt; on the server&#39;s Permissions view in the Publisher settings, and users can add items to their queue and push them to that server from the Sync Queue dashboard.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/sync-queue-settings.png&quot; alt=&quot;The Allow queuing toggle on a server&#39;s Permissions view, under the user groups who can push to it&quot; /&gt;&lt;/p&gt;
&lt;p&gt;It&#39;s off by default. If no server allows queuing, nobody sees any of this.&lt;/p&gt;
&lt;h2&gt;Adding to the queue&lt;/h2&gt;
&lt;p&gt;Once a server allows it, &lt;strong&gt;Add to queue&lt;/strong&gt; shows up in the actions menu for content and media, and for settings items too (document types, data types, templates and the rest). It&#39;s also in the content editor&#39;s push menu, and on the content and media browser dashboards.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/sync-queue-add.png&quot; alt=&quot;Add to queue in the actions menu for a content node, below Push to server and Pull from server&quot; /&gt;&lt;/p&gt;
&lt;p&gt;You only see it if you&#39;re allowed to push to a server that has queuing turned on.&lt;/p&gt;
&lt;h2&gt;The Sync Queue dashboard&lt;/h2&gt;
&lt;p&gt;Everything you&#39;ve queued lands on the new &lt;strong&gt;Sync Queue&lt;/strong&gt; dashboard in the Content section. The queue is yours, other people have their own, and it&#39;s kept in the database so it&#39;s still there tomorrow.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/sync-queue-dashboard.png&quot; alt=&quot;The Sync Queue dashboard with content, media, a document type and a data type queued, and Include children turned on for the Welcome page&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Each item has its own &lt;strong&gt;Include children&lt;/strong&gt; toggle, so you can send a whole section in one row and just the page itself in the next. Pick the items you want, press &lt;strong&gt;Push selected&lt;/strong&gt;, choose the server, and you&#39;re into the normal push dialog, with the usual report of what&#39;s going to change before anything does.&lt;/p&gt;
&lt;p&gt;The queue isn&#39;t tied to a server. You choose where it&#39;s going when you push, from the servers that allow queuing.&lt;/p&gt;
&lt;h2&gt;What happens when you push&lt;/h2&gt;
&lt;p&gt;Items leave the queue when their push goes through. If the push fails, or you cancel it, everything stays where it was, so you can fix the problem and try again without rebuilding your list.&lt;/p&gt;
&lt;p&gt;A few other things worth knowing:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Deleted items&lt;/strong&gt; are marked as deleted on the dashboard. You can&#39;t push them, only remove them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Moved items&lt;/strong&gt; are fine. The queue keeps track of the item, not where it was.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The same item can only be queued once&lt;/strong&gt;, and a queue holds up to 500 items.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If queuing is turned off&lt;/strong&gt; on every server, you can still see and empty your queue, you just can&#39;t push from it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Queues and approvals&lt;/h2&gt;
&lt;p&gt;If the server you push to &lt;a href=&quot;https://blog.jumoo.co.uk/2026/usync-complete-17-6-rc/&quot;&gt;needs approval&lt;/a&gt;, the queue works with it. The push stops at the report as usual, and your batch becomes one request for an approver to look at, rather than a request for every page.&lt;/p&gt;
&lt;p&gt;One rough edge: items that went off for approval stay in your queue, even once the request is approved. For now you&#39;ll need to remove them yourself after the push has gone through (&lt;strong&gt;Remove selected&lt;/strong&gt; does it in one go).&lt;/p&gt;
&lt;p&gt;That&#39;s the combination we think a lot of teams will end up using: editors collect a week&#39;s changes in their queue, and send them to live as one request that someone signs off.&lt;/p&gt;
&lt;h2&gt;Getting it&lt;/h2&gt;
&lt;p&gt;The Sync Queue is in uSync.Complete 17.6 for Umbraco 17 and 18.3 for Umbraco 18.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.6.0
&lt;/pre&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 18.3.0
&lt;/pre&gt;
&lt;p&gt;There&#39;s a good set of fixes in this release too. The &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v17.6.0&quot;&gt;v17.6.0 release notes&lt;/a&gt; have the full list.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>BackChats back</title>
    <link href="https://blog.jumoo.co.uk/2026/backchats-back/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/backchats-back/</id>
    <published>2026-10-15T08:23:37Z</published>
    <updated>2026-10-15T08:23:37Z</updated>
    <category term="Umbraco"/>
    <content type="html">&lt;iframe style=&quot;width: 100%; aspect-ratio: 16 / 9; border: 0;&quot; src=&quot;https://www.youtube-nocookie.com/embed/6M6samPEMpM&quot; title=&quot;Backstreet Boys - Everybody (Backstreet&#39;s Back)&quot; allow=&quot;accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture&quot; allowfullscreen=&quot;&quot;&gt;&lt;/iframe&gt;
&lt;p&gt;&lt;em&gt;&lt;small&gt;// sorry marc&lt;/small&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://powertoys.jumoo.co.uk/&quot;&gt;Power Toys for Umbraco&lt;/a&gt; 17.2 is out, and it brings BackChat with it: chat, tasks and review reminders for the Umbraco backoffice, plus a new Keyboard Shortcuts power toy. Each one is a power toy, so you turn on the bits you want from the Power Toys dashboard.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Umbraco.Community.PowerToys
&lt;/pre&gt;
&lt;h2&gt;Chat&lt;/h2&gt;
&lt;p&gt;BackChat started life at the &lt;a href=&quot;https://gibe.digital/blog/umbraco-spark-2025-from-a-developer-perspective&quot;&gt;Package Jam at Umbraco Spark 2025&lt;/a&gt;, but we never got round to actually publishing it. It&#39;s a better fit inside Power Toys anyway, so that&#39;s where it&#39;s ended up.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/backchat-chat.jpg&quot; alt=&quot;The BackChat panel open beside the About page, with a conversation between two editors and lines showing when the page was saved and published&quot; /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Chat from the header.&lt;/strong&gt; The panel opens beside the page, so you can keep moving around the site while it&#39;s open.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;This page.&lt;/strong&gt; Talk about the page you&#39;re on, and the chat follows you as you move between pages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Everyone, people and groups.&lt;/strong&gt; A chat for everyone, plus direct and user group conversations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;@mentions.&lt;/strong&gt; Mention a person or a group, and they get a notification.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Messages that need reading.&lt;/strong&gt; Ask people to confirm they&#39;ve read something, and see who has.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What happened.&lt;/strong&gt; Saves and publishes show up in the page&#39;s chat.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Tasks&lt;/h2&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/backchat-tasks.jpg&quot; alt=&quot;The Tasks panel showing the tasks assigned to you and the to-do list for the About page, with assignees and due dates&quot; /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Per page and global.&lt;/strong&gt; A to-do list for each page, and one for the whole site.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Assigned to you.&lt;/strong&gt; Everything on your plate in one list, with a badge on the header icon.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who and when.&lt;/strong&gt; Give tasks someone to do them and a due date.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Live.&lt;/strong&gt; Everyone&#39;s panel updates as soon as a task changes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Reminders&lt;/h2&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/backchat-reviews.jpg&quot; alt=&quot;The Tasks panel showing two pages due for review, and the Review box for the Contact page, which is overdue&quot; /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Review dates.&lt;/strong&gt; Give a page a date to be reviewed by, or set a rule per content type (&amp;quot;every 6 months&amp;quot;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Due for review.&lt;/strong&gt; See the pages you look after that have fallen due.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mark as reviewed.&lt;/strong&gt; Add a note, and the page gets its next date from the rule.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reminders.&lt;/strong&gt; The page&#39;s last editor gets a nudge when it falls due.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Reminders are part of Tasks, and you switch them on in the Tasks settings.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Keyboard shortcuts&lt;/h2&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/powertoys-keyboard-shortcuts.jpg&quot; alt=&quot;The Keyboard Shortcuts panel beside the About page, listing save and save and publish, then the keys that work everywhere, in search and in the rich text editor&quot; /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Press ?&lt;/strong&gt; Or use the header button, and a panel lists the shortcuts that work on the screen you&#39;re on.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read live.&lt;/strong&gt; The list comes from Umbraco itself, so it changes as you move around the site.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Your own shortcuts.&lt;/strong&gt; Add shortcuts to jump to a section or URL, open search or a panel, or run an action on the item you have open.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sections out of the box.&lt;/strong&gt; Alt+1 to Alt+9 go to the sections in the order the header shows them.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Have a look at &lt;a href=&quot;https://powertoys.jumoo.co.uk/&quot;&gt;the docs&lt;/a&gt; for all the details, and the &lt;a href=&quot;https://github.com/Jumoo/umbraco.community.powertoys/releases/tag/v17.2.0&quot;&gt;release notes on GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Umbraco.Community.PowerToys
&lt;/pre&gt;
</content>
  </entry>
  <entry>
    <title>uSync.Complete 17.6 RC - Approvals</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-complete-17-6-rc/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-complete-17-6-rc/</id>
    <published>2026-10-12T17:00:00Z</published>
    <updated>2026-10-12T17:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;The release candidate for uSync.Complete 17.6 is out. The big addition is approvals for Publisher: a server can now require someone to approve a push or pull before anything changes on it.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.6.0-rc1
&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;It&#39;s a prerelease, so you&#39;ll need to include prereleases to see it in your package manager.&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;Approvals&lt;/h1&gt;
&lt;p&gt;Approvals are set per server. Turn on &lt;strong&gt;Require approval&lt;/strong&gt; on the server&#39;s Permissions view in the Publisher settings, and pick the user groups that can approve. Admins can always approve. Requests expire after 7 days unless someone decides them, and you can change that (0 means they never expire).&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/approval-settings.png&quot; alt=&quot;The Approval settings on a server&#39;s Permissions view: Require approval, the approver groups and the expiry&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Only content pushes and pulls wait for approval. Settings pushes and pulls carry on as normal.&lt;/p&gt;
&lt;h2&gt;Asking for approval&lt;/h2&gt;
&lt;p&gt;Nothing changes for your editors until the report. They push or pull as usual, uSync works out what will change, and then, instead of going ahead, they get a &lt;strong&gt;Request approval&lt;/strong&gt; button and a box for a note to the approver.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/approval-request.png&quot; alt=&quot;The push dialog at the report, with a note for the approver and the Request approval button&quot; /&gt;&lt;/p&gt;
&lt;p&gt;The push stops there. Nothing has been changed on the other server.&lt;/p&gt;
&lt;h2&gt;The Approvals dashboard&lt;/h2&gt;
&lt;p&gt;Requests land on a new Approvals dashboard in the Content section. Approvers see the requests waiting for them, and everyone sees the requests they&#39;ve made and the history.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/approval-dashboard.png&quot; alt=&quot;The Approvals dashboard listing a request waiting for approval&quot; /&gt;&lt;/p&gt;
&lt;p&gt;The dashboard only appears once a server needs approval (or you already have requests to look back at), so sites that don&#39;t use approvals never see it.&lt;/p&gt;
&lt;h2&gt;Approving&lt;/h2&gt;
&lt;p&gt;Opening a request shows the report the editor saw when they asked, along with their note. Approve it and the push or pull carries on, decline it and it&#39;s cancelled and cleaned up on both servers. Nobody can approve their own request, unless they&#39;re an admin.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/approval-review.png&quot; alt=&quot;Reviewing a request: the editor&#39;s note, the change report and the Approve and Decline buttons&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Time passes between asking and approving, and the other server might have changed in the meantime. So when a request is approved, uSync sends it again and re-checks the target before applying anything, and tells you if the result is different from what was approved.&lt;/p&gt;
&lt;h2&gt;Emails&lt;/h2&gt;
&lt;p&gt;If your site has SMTP set up, approvers get an email when a request needs them, and the person who asked gets one when it&#39;s approved, declined, expires or fails.&lt;/p&gt;
&lt;p&gt;Each email comes from a template you can replace: put a file with the same name in &lt;code&gt;~/uSync/emails/&lt;/code&gt; (for example &lt;code&gt;approval-requested.html&lt;/code&gt;) and it&#39;s used instead. If email isn&#39;t how you want to tell people, there are notifications (&lt;code&gt;PublisherApprovalRequestedNotification&lt;/code&gt; and friends) you can handle and send wherever you like.&lt;/p&gt;
&lt;h1&gt;Also in this release&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Start a sync in one call.&lt;/strong&gt; &lt;code&gt;POST Publisher/Start&lt;/code&gt; runs a push, pull or settings sync in the background, and &lt;code&gt;POST Exporter/Start&lt;/code&gt; does the same for an export, with &lt;code&gt;GET Exporter/Download/{id}&lt;/code&gt; to collect it. Handy if you&#39;re driving uSync from a script or a pipeline.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Push and pull buttons.&lt;/strong&gt; They now only show for user groups whose default permissions allow a push or pull.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Progress.&lt;/strong&gt; The progress bar moves during a push or pull again, and the first step says what it&#39;s doing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fixes.&lt;/strong&gt; The push dialog works in Safari 26.4, import failures show in the result, the TimeMachine timeline refreshes when you come back to it, and a handful of smaller things.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Try it&lt;/h1&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.6.0-rc1
&lt;/pre&gt;
&lt;p&gt;The full list of changes is in the &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v17.6.0-rc1&quot;&gt;v17.6.0-rc1 release notes&lt;/a&gt;. If you try approvals, we&#39;d love to hear how they fit the way your team works before the full release.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Introducing uSync.AI</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-ai/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-ai/</id>
    <published>2026-10-08T17:00:00Z</published>
    <updated>2026-10-08T17:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;Today we have released the first version of uSync.AI, a free add-on that brings uSync to
&lt;a href=&quot;https://docs.umbraco.com/ai-in-umbraco&quot;&gt;Umbraco.AI&lt;/a&gt; on Umbraco 17.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.AI
&lt;/pre&gt;
&lt;p&gt;It does two things. It syncs your Umbraco.AI setup between environments the same way uSync
syncs everything else, and it gives Umbraco.AI agents tools that can run uSync.&lt;/p&gt;
&lt;h2&gt;The problem&lt;/h2&gt;
&lt;p&gt;Umbraco.AI keeps a lot of setup in the database. Connections, profiles, contexts, guardrails,
prompts and agents all live there, and getting an agent working how you want takes a fair bit
of trial and error.&lt;/p&gt;
&lt;p&gt;Then you have to do it all again on staging, and again on live. By hand. And hope you clicked
the same things in the same order.&lt;/p&gt;
&lt;p&gt;That&#39;s exactly the job uSync was built for, so now it does it.&lt;/p&gt;
&lt;h1&gt;Syncing your AI setup&lt;/h1&gt;
&lt;p&gt;Install uSync.AI and the Umbraco.AI items get written to disk when you save them, in their own
folders in the uSync folder (&lt;code&gt;AI-Connections&lt;/code&gt;, &lt;code&gt;AI-Profiles&lt;/code&gt;, &lt;code&gt;AI-Prompts&lt;/code&gt;, &lt;code&gt;AI-Agents&lt;/code&gt; and so
on). They go into source control with the rest of your uSync files, and they import on the
next server like everything else.&lt;/p&gt;
&lt;p&gt;There is a new &lt;strong&gt;AI&lt;/strong&gt; group on the uSync dashboard, so you can report, import and export just
the AI items if you want to.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/usync-ai-dashboard.png&quot; alt=&quot;The uSync dashboard with the new AI group, showing a report across connections, guardrails, contexts, profiles, settings, prompts and agents&quot; /&gt;&lt;/p&gt;
&lt;p&gt;What&#39;s covered:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Settings.&lt;/strong&gt; Connections, profiles, contexts, guardrails and the Umbraco.AI settings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prompts.&lt;/strong&gt; Everything on a prompt, including its instructions, scope rules and the
profile, contexts and guardrails it uses.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agents.&lt;/strong&gt; The agent&#39;s instructions, contexts, profile, guardrails, allowed tools and tool
scopes, and the per-user-group tool permissions.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Items keep the same Id on every server, and they import in order (connections first, agents
last) so everything an agent needs is in place before the agent arrives. If something an item
points at isn&#39;t on the target yet, the item still imports, without that link, and you get a
warning. The next import puts the link back once the missing item is there.&lt;/p&gt;
&lt;h2&gt;What about API keys?&lt;/h2&gt;
&lt;p&gt;The obvious worry with putting AI connections in files is API keys ending up in git. By
default they don&#39;t.&lt;/p&gt;
&lt;p&gt;uSync.AI leaves out any setting the provider marks as sensitive, and any value that is already
encrypted. If you use a configuration reference (&lt;code&gt;$Umbraco:AI:Secrets:OpenAIApiKey&lt;/code&gt; and the
like) that is synced, because it&#39;s only the name of where the key lives, not the key.&lt;/p&gt;
&lt;p&gt;When a connection arrives on a server that already has a key, the existing key is kept. If the
server doesn&#39;t have one yet, the connection gets a placeholder and a warning, and you enter
the real key there once.&lt;/p&gt;
&lt;p&gt;You can tighten or loosen this in &lt;code&gt;appsettings.json&lt;/code&gt; if you need to:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;AI&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
      &lt;span class=&quot;token property&quot;&gt;&quot;Connections&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;IgnoreEncrypted&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;IgnoreSecretValues&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;IgnoreSensitive&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;false&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;IgnoreSettings&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;]&lt;/span&gt;
      &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;Turning &lt;code&gt;IgnoreSecretValues&lt;/code&gt; off writes API keys to disk in plain text. We&#39;d leave it on.&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;Letting agents run uSync&lt;/h1&gt;
&lt;p&gt;The other half is the other way round. uSync.AI.Tools adds uSync tools to Umbraco.AI, so an
agent can list the handlers, run a report, export, or import.&lt;/p&gt;
&lt;p&gt;So an editor (well, more likely a developer) can ask an agent &amp;quot;what would an import change?&amp;quot;
and get the uSync report back as an answer.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/usync-ai-tool-scopes.png&quot; alt=&quot;An agent&#39;s tool permissions in Umbraco.AI, with the uSync and uSync.Complete tool scopes listed&quot; /&gt;&lt;/p&gt;
&lt;p&gt;We were quite careful with this bit, because an agent deciding to run an import is a bigger
deal than a person pressing the button.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Nothing is on by default.&lt;/strong&gt; An agent only gets the uSync tools if you give it them, or
their scope, in the agent&#39;s settings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;It&#39;s checked against the user.&lt;/strong&gt; Each tool checks the backoffice user the agent is acting
for. They need access to uSync, and imports need an administrator by default (you can relax
that with &lt;code&gt;RequireAdminForImport&lt;/code&gt;). The agent&#39;s settings can&#39;t override this.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;You approve the big ones.&lt;/strong&gt; Export and import ask the user to approve each call, and the
prompt says what&#39;s going to run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No signed-in user, no tools.&lt;/strong&gt; An agent run from a schedule or automation can&#39;t use them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One at a time.&lt;/strong&gt; Only one uSync operation runs at once. A second one is refused, not
queued.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;uSync.Complete&lt;/h1&gt;
&lt;p&gt;If you use uSync.Complete, install &lt;code&gt;uSync.Complete.AI&lt;/code&gt; instead. You get everything above, plus
two more things.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete.AI
&lt;/pre&gt;
&lt;h2&gt;Push and pull&lt;/h2&gt;
&lt;p&gt;Connections, guardrails, contexts, profiles, prompts and agents get &lt;strong&gt;Push to server…&lt;/strong&gt; and
&lt;strong&gt;Pull from server…&lt;/strong&gt; in their actions menu, for users with the publisher&#39;s push or pull
permission.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/usync-ai-push-pull.png&quot; alt=&quot;The actions menu on an Umbraco.AI agent, with Push to server and Pull from server options&quot; /&gt;&lt;/p&gt;
&lt;p&gt;An item takes what it needs with it. Push an agent and its profile, that profile&#39;s connection,
and any contexts and guardrails they use all go too, whatever the publisher&#39;s &amp;quot;include
dependencies&amp;quot; setting says. (You can turn that off with &lt;code&gt;AlwaysIncludeDependencies&lt;/code&gt; if you&#39;d
rather follow the publisher.) API keys never travel, same as with files.&lt;/p&gt;
&lt;h2&gt;Publisher tools for agents&lt;/h2&gt;
&lt;p&gt;There are also agent tools for the publisher: list the servers you can push to or pull from,
push a content or media item to another server, pull one in, and take a restore point.&lt;/p&gt;
&lt;p&gt;They work one item at a time (optionally with its children, media and the settings it depends
on). They never send the whole tree. The same rules apply as above: the tools are off until
you give them to an agent, they check the user&#39;s uSync.Complete permissions, and the ones that
change something ask for approval first, naming the server and the item.&lt;/p&gt;
&lt;h1&gt;The packages&lt;/h1&gt;
&lt;p&gt;uSync.AI is split up so you can install just the bits you use:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.&lt;/strong&gt; Installs the four packages below. Most sites want this one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.Sync.&lt;/strong&gt; Connections, profiles, contexts, guardrails and settings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.Prompt.&lt;/strong&gt; Prompts (needs Umbraco.AI.Prompt).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.Agent.&lt;/strong&gt; Agents (needs Umbraco.AI.Agent).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.Tools.&lt;/strong&gt; The uSync agent tools.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.Complete.AI.&lt;/strong&gt; Installs &lt;code&gt;uSync.AI&lt;/code&gt; and &lt;code&gt;uSync.AI.Complete&lt;/code&gt;. For uSync.Complete users.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;uSync.AI.Complete.&lt;/strong&gt; Push, pull and the publisher agent tools.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;uSync.AI needs Umbraco 17.5+, Umbraco.AI 17.5.2+ and uSync 17.4.3+. The Complete packages
also need uSync.Complete 17.5.0+ (and a licence for it).&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Get it&lt;/h2&gt;
&lt;p&gt;uSync.AI is free and open source (MPL-2.0). It&#39;s on NuGet now.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.AI
&lt;/pre&gt;
&lt;p&gt;The code, the readmes for each package, and the issue tracker are all on
&lt;a href=&quot;https://github.com/Jumoo/uSync.AI&quot;&gt;GitHub&lt;/a&gt;, and you can see the
&lt;a href=&quot;https://releases.jumoo.co.uk/package.html?name=uSync.AI&quot;&gt;release notes&lt;/a&gt; on our releases site.
If you want to follow along, nightly builds go to &lt;a href=&quot;https://nightly.jumoo.uk/&quot;&gt;nightly.jumoo.uk&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We honestly don&#39;t know yet how people are going to use agents with uSync, so if you try it,
we&#39;d love to hear how you get on.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>AI Connector 17.7</title>
    <link href="https://blog.jumoo.co.uk/2026/ai-connector-17-7/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/ai-connector-17-7/</id>
    <published>2026-10-02T13:01:57Z</published>
    <updated>2026-10-02T13:01:57Z</updated>
    <category term="Umbraco"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;We have just released v17.7 of the AI connector for Translation Manager. Most of the work in
this one is under the hood, and it makes translations faster and a bit cheaper.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.AI
&lt;/pre&gt;
&lt;h2&gt;Fewer requests&lt;/h2&gt;
&lt;p&gt;In 17.7 the connector batches things up better. It gathers everything on a page together and
sends it to the AI in as few requests as it can. In our tests that reduced the number of
requests by around 70%, and cut the time spent waiting on the AI by more than half.&lt;/p&gt;
&lt;h2&gt;Lower costs&lt;/h2&gt;
&lt;p&gt;Fewer requests means we send the prompt far fewer times, and in our tests the input tokens
for a job dropped by around 40%.&lt;/p&gt;
&lt;p&gt;The overall saving is smaller than that, because most AI providers charge a lot more for the
tokens they send back than the ones you send them, and the translated text itself doesn&#39;t
get any shorter. Across our test runs we have seen around &lt;strong&gt;an 8% reduction in token costs&lt;/strong&gt;.&lt;/p&gt;
&lt;h2&gt;More reliable&lt;/h2&gt;
&lt;p&gt;A few things that will hopefully go unnoticed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Fewer retries.&lt;/strong&gt; When an AI provider is busy, the connector now makes far fewer retry
requests before it gets an answer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Longer timeouts.&lt;/strong&gt; Large translations can take a while, so each request now gets up to
five minutes to finish.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Better splitting of long content.&lt;/strong&gt; Very long text is split at the end of a sentence, and
HTML keeps all of its tags when it is split up.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Complete translations only.&lt;/strong&gt; If the AI stops part way through a translation, the
connector reports it as an error, so you only ever get whole translations.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you translate really big pages and the defaults are too short for you, the timeouts can be
changed in &lt;code&gt;appsettings.json&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;Translations&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;AI&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
      &lt;span class=&quot;token property&quot;&gt;&quot;AttemptTimeout&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;00:05:00&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
      &lt;span class=&quot;token property&quot;&gt;&quot;TotalTimeout&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;00:20:00&quot;&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2&gt;Get it&lt;/h2&gt;
&lt;p&gt;The update is available on NuGet now.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.AI
&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;The AI connector is included in the main Jumoo.TranslationManager package. You can install
this version on its own now, and it will be included in the next Jumoo.TranslationManager
release (v17.9.3).&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You can see the full list of changes in the
&lt;a href=&quot;https://releases.jumoo.co.uk/package.html?name=Jumoo.TranslationManager.AI#v17.7.0&quot;&gt;release notes&lt;/a&gt;,
and there&#39;s more on setting up the connector in &lt;a href=&quot;https://docs.jumoo.co.uk/&quot;&gt;the docs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>uSync.Complete 17.5 / 18.2</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-complete-17-5/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-complete-17-5/</id>
    <published>2026-09-30T14:00:00Z</published>
    <updated>2026-09-30T14:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;uSync.Complete 17.5 (Umbraco 17) and 18.2 (Umbraco 18) are out. They have the same features, and it&#39;s a big release. Publisher supports load-balanced servers, the Publisher browser and server list have had a lot of attention, and there&#39;s now a TimeMachine, so you can travel back in time!&lt;/p&gt;
&lt;p&gt;For Umbraco 17:&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.5.0
&lt;/pre&gt;
&lt;p&gt;For Umbraco 18:&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 18.2.0
&lt;/pre&gt;
&lt;h1&gt;Load balancing&lt;/h1&gt;
&lt;p&gt;17.5 / 18.2 adds support for running Publisher against load-balanced servers, including a load-balanced backoffice.&lt;/p&gt;
&lt;p&gt;A push or pull is a series of requests, and each one builds on files the last one left on the server. So the whole series needs to reach the same server.&lt;/p&gt;
&lt;h2&gt;Server affinity&lt;/h2&gt;
&lt;p&gt;Most load balancers already have a way to pin a session to one server. They set a cookie (ARR affinity on Azure App Service, Application Gateway&#39;s own cookie, and so on) and route any request carrying it back to the same server.&lt;/p&gt;
&lt;p&gt;Publisher now plays along. When a target server sets a cookie on its first response, Publisher remembers it and sends it back on every later request in the same push or pull. The whole operation stays on the server that answered first.&lt;/p&gt;
&lt;p&gt;It&#39;s on by default, and you don&#39;t need to tell it the cookie&#39;s name. Against a single server that doesn&#39;t set cookies it does nothing at all.&lt;/p&gt;
&lt;p&gt;If the requests do end up on different servers, Publisher logs a warning naming both servers and the step. To stop the push or pull at that point, turn on &lt;code&gt;AffinityFailFast&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;Publisher&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;Settings&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
      &lt;span class=&quot;token property&quot;&gt;&quot;AffinityFailFast&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2&gt;A shared working folder&lt;/h2&gt;
&lt;p&gt;By default each server keeps its working files on its own disk. If your servers can see shared storage (a UNC share, a mounted volume, Azure Files), you can point uSync&#39;s working folder at it and every server sees the same files:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;WorkingFolder&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;Path&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;&#92;&#92;&#92;&#92;shared-server&#92;&#92;usyncwork&quot;&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It&#39;s read at startup, so it needs a restart to change.&lt;/p&gt;
&lt;h2&gt;Also in this area&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Temp folder cleanup on every server.&lt;/strong&gt; The cleanup job now runs on each server in a load-balanced site.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Quicker answers from unreachable servers.&lt;/strong&gt; The server-to-server connection gives up straight away on a server it can&#39;t reach, and the server settings page tells you when that connection isn&#39;t available.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Packs sent in parts.&lt;/strong&gt; Pushes and pulls now move their packs between servers in parts, with progress for each one, so large syncs stay well inside request timeouts. &lt;code&gt;PackChunkSize&lt;/code&gt; and &lt;code&gt;PackChunkMaxBytes&lt;/code&gt; set the size of each part, and the defaults suit most sites.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Servers compare notes.&lt;/strong&gt; Servers now tell each other what they support, so a push or pull can adapt to the version at the other end.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There is a full write-up on the &lt;a href=&quot;https://docs.jumoo.co.uk/usync/complete/troubleshooting/load-balancing&quot;&gt;load balancing docs page&lt;/a&gt;.&lt;/p&gt;
&lt;h1&gt;uSync.TimeMachine 🔥🛁⏰&lt;/h1&gt;
&lt;p&gt;Something changed on the site, and nobody is quite sure who did it, when, or what it looked like before. uSync can tell you what&#39;s different between your site and the uSync folder, but it can&#39;t tell you the history.&lt;/p&gt;
&lt;p&gt;TimeMachine is new in 17.5 / 18.2, and it records what happens to your site as a timeline. &amp;quot;Kevin updated Home.&amp;quot; &amp;quot;Kevin imported 59 changes.&amp;quot; Each event lists the items it touched, with a property-level diff of what changed.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/timemachine-timeline.png&quot; alt=&quot;The TimeMachine timeline, showing a day&#39;s events grouped by user and source&quot; /&gt;&lt;/p&gt;
&lt;p&gt;It groups things sensibly. A save in the backoffice is one event. A &amp;quot;save and publish&amp;quot; is one event, not two. A whole uSync import is one event, however many items it touched.&lt;/p&gt;
&lt;h2&gt;Rolling back&lt;/h2&gt;
&lt;p&gt;Pick an event, tick the changes you want to undo, and roll them back. TimeMachine shows you uSync&#39;s report of what will change before it does anything.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/timemachine-rollback.png&quot; alt=&quot;A TimeMachine event opened in the side panel, showing the title change on the Welcome page and the Roll back button&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Under the hood, a rollback imports the &amp;quot;before&amp;quot; version of each item through uSync. If the change was a create, the rollback deletes the item again. A rollback is recorded as an event of its own, so you can roll that back too if you change your mind.&lt;/p&gt;
&lt;p&gt;It covers the same things uSync does: content (including publish, unpublish, move and the recycle bin), media, blueprints, doctypes, data types, languages, templates, dictionary items, relation types, domains and webhooks.&lt;/p&gt;
&lt;h2&gt;Turning it on&lt;/h2&gt;
&lt;p&gt;TimeMachine is &lt;strong&gt;off by default&lt;/strong&gt;. Recording serializes every item on every save, and we didn&#39;t want anyone upgrading and finding their saves slower without having asked for it. Switch it on in appsettings:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;TimeMachine&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;Enabled&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;RetentionDays&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token number&quot;&gt;30&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It picks up the change without a restart. History older than &lt;code&gt;RetentionDays&lt;/code&gt; is cleaned up automatically, because on a busy site those tables grow quickly.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;A couple of honest caveats. Rolling back a media delete won&#39;t bring the file back if Umbraco has already removed it, because uSync&#39;s media XML doesn&#39;t carry the file. And blueprint updates can&#39;t be rolled back, because Umbraco doesn&#39;t raise the notification we&#39;d need. TimeMachine tells you that rather than failing quietly.&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;The Publisher browser&lt;/h1&gt;
&lt;p&gt;The content and media browsers in Publisher have some new tools for finding your way around, especially on bigger sites.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;List view.&lt;/strong&gt; There is now a list view alongside the grid.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync status on every item.&lt;/strong&gt; Each item shows whether it&#39;s in sync, out of sync or missing on the other server, so you can see what needs moving before you move it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Paging, sorting and search.&lt;/strong&gt; Large folders are paged. You can sort by name, type or last update, and search the current folder by name. Refreshing the page keeps your place.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/publisher-browser-list.png&quot; alt=&quot;The Publisher content browser in list view, showing the sync status of each item&quot; /&gt;&lt;/p&gt;
&lt;h1&gt;Knowing which server you&#39;re on&lt;/h1&gt;
&lt;p&gt;If you have a dev, staging and live site open in three tabs, it&#39;s far too easy to do something on the wrong one. We already coloured the navbar with the server&#39;s colour. Now there is a server identifier in the backoffice header too, with the server&#39;s name, icon and colour. Click it to see the servers you can push to or pull from, whether each one is up, and a link to the same page on that server.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/server-identifier.png&quot; alt=&quot;The server identifier in the backoffice header, showing the current server&#39;s name and colour&quot; /&gt;&lt;/p&gt;
&lt;p&gt;New servers get a random colour from the palette and the identifier turned on, with navbar colouring off (you can turn it back on in the server&#39;s settings). A site that isn&#39;t in its own server list shows as &amp;quot;Local&amp;quot;. Existing servers keep whatever you had.&lt;/p&gt;
&lt;p&gt;You can also now sort your servers. &amp;quot;Sort servers&amp;quot; on the Publisher node in the uSync tree sets the order they appear in, both in the tree and wherever you pick a server to push to or pull from.&lt;/p&gt;
&lt;h1&gt;Other bits&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Restore points and snapshots on big sites.&lt;/strong&gt; Creating a restore point or snapshot on a large site could hang when the site was hosted out of process in IIS, because IIS gave up on the one long request. Content and media now export in pages across several requests.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Exporter downloads.&lt;/strong&gt; Exporter built the whole download in memory, and a pack that included media could be as big as the site. It now zips to disk and streams the file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Server json is back.&lt;/strong&gt; The small &amp;quot;Server json&amp;quot; button in the footer of the Publisher dashboard, from the v13 version, is back. It shows your server setup as json, which you can save as &lt;code&gt;usync-servers.json&lt;/code&gt; in the root of a new site to seed its servers on install.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Missing labels.&lt;/strong&gt; Snapshot labels were showing as raw keys, and so were a handful of item types in Publisher (domains, relation types, webhooks, users and user groups). Both are fixed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Smaller fixes.&lt;/strong&gt; The Publisher browser and Compare dialog show the right status for every item in a folder, saving a server no longer loses a re-sort done while its settings were open, the unsaved-changes dialog has clearer choices, and the backoffice text has had a spelling and grammar pass.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Latest uSync.&lt;/strong&gt; Complete now builds on the latest uSync release for each version.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Getting it&lt;/h1&gt;
&lt;p&gt;uSync.Complete 17.5 and 18.2 are on NuGet now.&lt;/p&gt;
&lt;p&gt;For Umbraco 17:&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 17.5.0
&lt;/pre&gt;
&lt;p&gt;For Umbraco 18:&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 18.2.0
&lt;/pre&gt;
&lt;p&gt;The full list of changes is in the release notes for &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v17.5.0&quot;&gt;v17.5.0&lt;/a&gt; and &lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v18.2.0&quot;&gt;v18.2.0&lt;/a&gt;, and the &lt;a href=&quot;https://docs.jumoo.co.uk/&quot;&gt;docs&lt;/a&gt; have the details on the new settings.&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>uSync and Translation Manager in Automate</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-and-translation-manager-in-automate/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-and-translation-manager-in-automate/</id>
    <published>2026-08-18T14:00:00Z</published>
    <updated>2026-08-18T14:00:00Z</updated>
    <category term="Umbraco"/>
    <category term="uSync"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;We have released the first public builds of two new packages, &lt;code&gt;uSync.Automate&lt;/code&gt; and
&lt;code&gt;Jumoo.TranslationManager.Automate&lt;/code&gt;, which put uSync and Translation Manager inside
&lt;a href=&quot;https://umbraco.com/products/add-ons/automate/&quot;&gt;Umbraco.Automate&lt;/a&gt; as actions and triggers you
can drop into a workflow.&lt;/p&gt;
&lt;p&gt;Both are pre-release (uSync.Automate is at beta1, Translation Manager&#39;s is at rc1), and we
would really like people to try them and tell us what breaks.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Automate --prerelease
&lt;/pre&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.Automate --prerelease
&lt;/pre&gt;
&lt;p&gt;Automate is Umbraco&#39;s workflow product: triggers, conditions and actions wired together in the
backoffice. It ships with a core set of building blocks.&lt;/p&gt;
&lt;p&gt;We did have a small package ready for Translation Manager at the release of Umbraco.Automate,
but now we have revisited that and written a uSync.Automate package, so you can hook into the
events and actions for both of these packages.&lt;/p&gt;
&lt;h1&gt;uSync.Automate&lt;/h1&gt;
&lt;p&gt;This is actually three packages, because they do quite different things and not everyone wants
all of them.&lt;/p&gt;
&lt;h2&gt;uSync.Automate&lt;/h2&gt;
&lt;p&gt;Handlers and serializers so uSync exports Automate&#39;s own settings (&lt;code&gt;Workspace&lt;/code&gt;, &lt;code&gt;WorkspaceGroup&lt;/code&gt;
and &lt;code&gt;Automation&lt;/code&gt;) to disk as XML, alongside your document types and data types.&lt;/p&gt;
&lt;p&gt;So the automations themselves become part of the thing you deploy. You build a workflow on your
dev site, uSync exports it, it goes through source control, and it arrives on staging and live
the same way everything else does.&lt;/p&gt;
&lt;p&gt;Connections are deliberately &lt;em&gt;not&lt;/em&gt; synced. Each environment owns its own connections. Your dev
Slack webhook is not your live Slack webhook, and syncing credentials between environments is a
bad idea however convenient it looks. Automations and workspaces reference connections by alias,
and report it when the alias is missing on the target server rather than silently importing a
broken workflow.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/usync-export-automate.png&quot; alt=&quot;uSync reporting on the Automate group, listing the Automate Workspaces, Automate Groups and Automations handlers.&quot; /&gt;&lt;/p&gt;
&lt;h2&gt;uSync.Automate.Actions&lt;/h2&gt;
&lt;p&gt;The other direction: uSync operations you can run &lt;em&gt;from&lt;/em&gt; a workflow.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/automate-usync-actions.png&quot; alt=&quot;The Automate action picker filtered to uSync, showing the five uSync actions and the five uSync.Complete ones.&quot; /&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Export, Import and Report.&lt;/strong&gt; The three uSync run actions, with the settings you would expect:
handler group, set, handler aliases, force, clean, target folders. Report changes nothing, so
it is the safe one to schedule.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Export Item and Import Item.&lt;/strong&gt; Single item versions, taking a key and a handler alias. These
are the ones you bind to a trigger, so you can export just the thing that changed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Triggers for each run.&lt;/strong&gt; &lt;code&gt;Starting&lt;/code&gt; and &lt;code&gt;Completed&lt;/code&gt; for import, export and report. The
completed triggers hand you a summary you can filter on: only fire when there were changes,
or only when there were errors.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Item-level triggers.&lt;/strong&gt; Fire per item imported or exported. These are off by default and
capped, because a full-site import can raise thousands of them and flood Automate&#39;s trigger
outbox. If you want per-item work, the better pattern is a &lt;code&gt;Completed&lt;/code&gt; trigger and a &lt;code&gt;forEach&lt;/code&gt;
over its changes; the config is under &lt;code&gt;uSync:Automate:Actions:ItemTriggers&lt;/code&gt; if you want them on
anyway.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Every setting a uSync run takes is on the action, with the fiddly ones tucked into Advanced.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/usync-report-action-settings.png&quot; alt=&quot;The uSync: Report action&#39;s settings, showing Group, and under Advanced, Set, Handler Aliases, Folders and Max Change Details.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Some things that you might want to do with uSync actions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Report on a schedule, and post to Slack or Teams only when the report finds changes. A quiet
&amp;quot;your dev and live settings have drifted&amp;quot; alarm.&lt;/li&gt;
&lt;li&gt;Export on a timer so the uSync folder on a server is always current, without anyone
remembering to press the button.&lt;/li&gt;
&lt;li&gt;Import as the last step of something else, like a deployment webhook or a content freeze
ending.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;uSync.Automate.Actions.Complete&lt;/h2&gt;
&lt;p&gt;The same idea for uSync.Complete&#39;s publisher. Push and pull content, media and settings items to
and from another server, take a restore point, and a trigger that fires when &lt;em&gt;this&lt;/em&gt; site finishes
receiving a push or pull from somewhere else.&lt;/p&gt;
&lt;p&gt;The push and pull actions carry the options the publisher UI gives you: include children,
include media, include ancestors, include dependencies, and take a restore point on the target
before applying anything.&lt;/p&gt;
&lt;p&gt;So some things you might do:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When a document type is saved on the settings server, push it to staging. No one has to
remember.&lt;/li&gt;
&lt;li&gt;Take a restore point before every scheduled import, so there is always a way back.&lt;/li&gt;
&lt;li&gt;When staging finishes receiving a push, run a uSync report and mail the result to whoever
cares.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;The bit that will bite you&lt;/h2&gt;
&lt;p&gt;Automations that run uSync raise uSync events, which can fire triggers, which can run
automations. It is very easy to build a loop without meaning to.&lt;/p&gt;
&lt;p&gt;Every trigger in these packages has an &lt;strong&gt;origin&lt;/strong&gt; setting in its advanced group, controlling what
happens when the uSync run was itself performed by an automation: ignore it, treat it like any
other, or only fire for it. The item-level triggers default to skipping automation-driven runs
entirely, on the grounds that per-item events are almost always the tail end of a machine-driven
cascade rather than something a human did.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;uSync.Automate needs Umbraco v17, uSync 17.3 and Umbraco.Automate 17.2 or later. The Complete
actions need uSync.Complete as well, and are a separate package so you are not forced into that
dependency.&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;Jumoo.TranslationManager.Automate&lt;/h1&gt;
&lt;p&gt;Translation Manager has had auto translate on save for a while, and there is already a
&lt;a href=&quot;https://github.com/Jumoo/Jumoo.TranslationManager.AutoTranslate&quot;&gt;Jumoo.TranslationManager.AutoTranslate&lt;/a&gt;
package that can trigger translations from content saves or publishes, but it is a fixed
behaviour. It does one thing, the way it is coded to work. This package breaks it into parts you
can rearrange.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Actions:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Translate Content.&lt;/strong&gt; Creates translation nodes for a content item and submits a job per
target culture. Point it at a content key (usually &lt;code&gt;${trigger.contentKey}&lt;/code&gt;), and optionally
restrict it to particular cultures, particular translation sets, or a particular connector.
Blank means everything that applies, which is usually what you want.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Check Translation Job.&lt;/strong&gt; Asks the connector where a job has got to.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Approve Translation Job.&lt;/strong&gt; Approves a job, writing the translation back into Umbraco, and
optionally publishes it. You can approve the whole job or name individual nodes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/tm-automate-actions.png&quot; alt=&quot;The Automate action picker showing the Translation Manager group: Approve Translation Job, Check Translation Job and Translate Content.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Triggers:&lt;/strong&gt; Job Submitted, Translation Received, Job Approved and Translation Published. Each
one is filterable by set, by target culture, and by connector.&lt;/p&gt;
&lt;p&gt;The obvious one to build first is the one auto translate already does:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Content Published&lt;/strong&gt; → &lt;strong&gt;Translate Content&lt;/strong&gt; → &lt;strong&gt;Check Translation Job&lt;/strong&gt; → &lt;strong&gt;Approve Translation Job&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Except now every step is yours to change. Which is the point.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/tm-automate-workflow.png&quot; alt=&quot;A Content Published trigger wired straight into the Translate Content action in the Automate workflow editor.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Where the rearranging actually earns its keep:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Machine translation with no waiting.&lt;/strong&gt; Machine connectors return more or less instantly, so
Translate Content has an approve-when-returned option that approves and optionally publishes in
the same run. Publish in English, and French and German appear.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Human translation, with a nudge.&lt;/strong&gt; Submit the job on publish, then hang a Slack or Teams
message off the &lt;strong&gt;Translation Received&lt;/strong&gt; trigger so someone knows there is something to review.
Approval stays a human decision.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Different rules for different parts of the tree.&lt;/strong&gt; Automate has conditions, so news can go to
machine translation and get published automatically while the legal section goes to a human and
waits. That was never expressible before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Translate on a schedule rather than on publish&lt;/strong&gt;, if your translation budget is billed per
job and you would rather batch them up.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Loops, again&lt;/h2&gt;
&lt;p&gt;Approving a translation publishes content. Publishing content is what started the automation. You
can see where this goes.&lt;/p&gt;
&lt;p&gt;There is loop protection built in: the actions know which content they just wrote, jobs are
idempotent within a run, and the triggers have the same origin setting the uSync ones do. Force
(create translation nodes even where Translation Manager sees no change) is off by default and
deliberately awkward to turn on, because it is the setting that defeats most of the above.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Needs Umbraco v17, Translation Manager 17.4 or later, and Umbraco.Automate 17.2 or later. Both
packages are v17 and .NET 10 only for now.&lt;/em&gt;&lt;/p&gt;
&lt;h1&gt;Tell us what&#39;s wrong with them&lt;/h1&gt;
&lt;p&gt;These are beta and release candidate builds. They have unit tests and they work on our sites, but
&amp;quot;works on our sites&amp;quot; is a low bar for a workflow product where everyone builds something
different.&lt;/p&gt;
&lt;p&gt;The action and trigger aliases are the part we most want to settle before a stable release,
because they get baked into saved automation JSON and we cannot rename them afterwards. If the
naming looks wrong to you, now is the time to say so.&lt;/p&gt;
&lt;p&gt;So if something doesn&#39;t fire, fires twice, or the settings don&#39;t offer you the thing you actually
needed, please tell us:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/uSync.Automate/issues&quot;&gt;github.com/Jumoo/uSync.Automate/issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/Jumoo.TranslationManager.Automate/issues&quot;&gt;github.com/Jumoo/Jumoo.TranslationManager.Automate/issues&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Both repos are MPL-2.0, so you can also go and read exactly what the actions do.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Automate --prerelease
&lt;/pre&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.Automate --prerelease
&lt;/pre&gt;
&lt;hr /&gt;
&lt;p class=&quot;ai-note&quot;&gt;&lt;em&gt;✳︎ Portions of this post were generated by Claude AI.&lt;/em&gt;&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Translation Manager Feature Roundup</title>
    <link href="https://blog.jumoo.co.uk/2026/translation-manager-feature-roundup/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/translation-manager-feature-roundup/</id>
    <published>2026-08-17T11:00:00Z</published>
    <updated>2026-08-17T11:00:00Z</updated>
    <category term="Umbraco"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;It has been a busy year for Translation Manager. We started 2026 on Umbraco v17, we are now
on v18, and we have shipped 31 releases across v13, v17 and v18 so far this year, so a lot of
new things have quietly landed.&lt;/p&gt;
&lt;p&gt;Some of it has had a blog post, a lot of it hasn&#39;t, so this is a bit of a catch up on
what has been added since the start of the year.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager
&lt;/pre&gt;
&lt;h1&gt;Features of note&lt;/h1&gt;
&lt;h2&gt;Translating the Library&lt;/h2&gt;
&lt;p&gt;Umbraco v18 introduced the Library, a place to keep reusable element content that isn&#39;t
tied to a page in the content tree. Which is great, right up until you realise all that
content also needs translating.&lt;/p&gt;
&lt;p&gt;So with our v18 release, Translation Manager can now translate Library elements as well as
documents.&lt;/p&gt;
&lt;p&gt;It works pretty much exactly the way content translation does. You create a translation set,
only now you get a choice of what kind of set you are creating, a content set or a library set.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/new-set-element-dialog.png&quot; alt=&quot;Choosing between a content set and a library set.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Point it at a folder in the Library, pick your languages, and off you go.&lt;/p&gt;
&lt;p&gt;Everything you already know still applies:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Auto translate on save, so elements go off to be translated as soon as an editor saves them.&lt;/li&gt;
&lt;li&gt;&amp;quot;Send to translate&amp;quot; and &amp;quot;Quick translate&amp;quot; from the element editor itself.&lt;/li&gt;
&lt;li&gt;Right click a Library folder and send everything underneath it in one go.&lt;/li&gt;
&lt;li&gt;The same job, approve and publish workflow you use for content.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Under the hood, library translations use the culture variant model, so the translations live
as variants on the same element rather than as a copy somewhere else in the tree. That keeps
the Library tidy, and means your blocks and reusable bits just pick up the right language
when they get rendered.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Library translation needs Umbraco v18 and Translation Manager v18.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Translation Memory grew up&lt;/h2&gt;
&lt;p&gt;Translation Memory has been in Translation Manager for a while now. It stores the phrase
pairs that come back from machine and AI translators, so the next time it sees the same bit
of text it doesn&#39;t need to send it off again. Faster translations, smaller bills.&lt;/p&gt;
&lt;p&gt;The problem was you couldn&#39;t really see any of it. You got a count per connector, and a
&amp;quot;delete everything&amp;quot; button, and that was your lot. If a translator had got a phrase slightly
wrong, that wrong phrase was going to keep coming back forever and there was very little you
could do about it.&lt;/p&gt;
&lt;p&gt;That&#39;s all changed. Translation Memory now has a proper management screen in settings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Browse and search&lt;/strong&gt; everything stored for a connector, paged, so you can actually find
the phrase you are looking for.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Edit entries&lt;/strong&gt; in place. Found a translation you don&#39;t like? Fix it, and every future
translation uses your version.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Delete single entries&lt;/strong&gt;, rather than nuking the whole lot.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Approved only filter&lt;/strong&gt;, so you can look at just the memory that has come from content
somebody has actually signed off.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Copy memory between connectors&lt;/strong&gt;. Trying out a new AI provider, or moving from one
machine translator to another? You can bring your existing memory with you instead of
starting from scratch.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/translation-memory-edit.png&quot; alt=&quot;Browsing and editing the translation memory stored for a connector.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;We also added batch memory support, so connectors that translate in batches (rather than
phrase by phrase) can use memory too, and memory results are now passed back to the connector
and shown in the UI, so you can see which bits of a translation came from memory and which
were freshly translated.&lt;/p&gt;
&lt;h1&gt;And the rest&lt;/h1&gt;
&lt;p&gt;Plenty of smaller things landed too. Here they are in no particular order.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Translate in place.&lt;/strong&gt; Translate a node&#39;s content into another language without setting up
a translation set at all, overwriting it where it sits. Handy for one off jobs and for
invariant doctypes. It&#39;s off by default, turn it on in settings if you want it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Approve and publish are now separate permissions.&lt;/strong&gt; Previously anyone who could approve a
translation could also push it live. Now you can give a translator approve rights and keep
publishing with your editors. &lt;em&gt;(Worth a read of the release notes on this one if you have
custom user groups, the mutating endpoints now check permissions properly too.)&lt;/em&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rich text editing of HTML values.&lt;/strong&gt; Translation values that hold HTML now get a proper
Tiptap rich text editor instead of a textarea full of raw markup. Much nicer if you ever
need to tweak a translation by hand.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lock connector on a set.&lt;/strong&gt; A set&#39;s connector used to be the only option. Now it&#39;s just
the default, and users can pick something else, unless you tick &amp;quot;Lock connector&amp;quot; to keep
the old behaviour. Existing sets stay locked, so nothing changes until you decide it should.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;One click translate setup.&lt;/strong&gt; A much shorter route from &amp;quot;I have just installed this&amp;quot; to
&amp;quot;I have translated something&amp;quot;, along with a simplified job creation dialog and a cleaner
quick translate view.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Batch connectors.&lt;/strong&gt; A new &lt;code&gt;MachineBatchBase&lt;/code&gt; class for connector authors, for translation
services that work asynchronously in batches rather than answering straight away. DeepL,
Microsoft, OpenAI and Claude all support batch now (the last two via the AI connector).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Per request throttling.&lt;/strong&gt; Connectors can now throttle how fast they hammer an external
API, which keeps the rate limits happy on big jobs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Background processing rebuilt.&lt;/strong&gt; The background queue now runs on Umbraco&#39;s recurring
background job framework. That fixed a whole family of &amp;quot;No AmbientContext was found&amp;quot; errors
on big jobs, and background items now run as the user who queued them, so permission checks
behave. Not glamorous, but if you translate thousands of nodes at a time you will notice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;More languages in the backoffice.&lt;/strong&gt; Translation Manager itself now speaks Danish, Dutch,
Spanish, French and German as well as English. Which felt like something a translation
package really ought to do.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Reworked settings page.&lt;/strong&gt; Two column layout, clearer copy, and &amp;quot;Translate on save&amp;quot; is now
called &amp;quot;Pending Translations&amp;quot;, which is what everyone was calling it anyway.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Nicer node and job views.&lt;/strong&gt; Real tab display names, properties grouped the way they are in
the content editor, nested tab handling, proper browser titles, better progress bars, and an
&amp;quot;Add all&amp;quot; button when you have a lot of languages to pick from.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Block editor improvements.&lt;/strong&gt; Support for single blocks, nested blocks coming through
properly, legacy rich text values folded into the translation flow, and a decent pile of
fixes to how blocks merge back after translation.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h1&gt;Getting it&lt;/h1&gt;
&lt;p&gt;All of this is in the current v18 release, and most of the non Library bits shipped in the
v17 line too.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager
&lt;/pre&gt;
&lt;p&gt;&lt;a href=&quot;https://docs.jumoo.co.uk/&quot;&gt;Our documentation&lt;/a&gt; has the detail on all of the above, and the
&lt;a href=&quot;https://github.com/Jumoo/Jumoo.TranslationManager.Issues/releases&quot;&gt;changelog&lt;/a&gt; has the
version by version breakdown if you want to know exactly when something appeared.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>uSync 18.1 - a faster import</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-18-1-a-faster-import/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-18-1-a-faster-import/</id>
    <published>2026-08-12T14:00:00Z</published>
    <updated>2026-08-12T14:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;uSync 18.1 is out, and it is mostly about speed.&lt;/p&gt;
&lt;p&gt;If you have a site with a few hundred items in your uSync folder, you have probably never
thought about how long an import takes. If you have a site with tens of thousands, you almost
certainly have.&lt;/p&gt;
&lt;h2&gt;Why is a &amp;quot;no changes&amp;quot; import slow?&lt;/h2&gt;
&lt;p&gt;The thing that surprises people is that an import where &lt;strong&gt;nothing has changed&lt;/strong&gt; costs almost as
much as a full export.&lt;/p&gt;
&lt;p&gt;That is because of how uSync decides whether something has changed. For every item in the uSync
folder, it:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;looks the item up in Umbraco (a database hit),&lt;/li&gt;
&lt;li&gt;serializes the whole thing to XML,&lt;/li&gt;
&lt;li&gt;hashes both sides,&lt;/li&gt;
&lt;li&gt;compares the hashes.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If the hashes match, uSync says &amp;quot;no change&amp;quot; and moves on — having done all of that work to find
out it had nothing to do. Reading the files off disk isn&#39;t the bottleneck; that has been
parallelised for a while. It is the per-item work afterwards, and on a big site that per-item
work &lt;em&gt;is&lt;/em&gt; the run time.&lt;/p&gt;
&lt;h2&gt;The import state cache&lt;/h2&gt;
&lt;p&gt;New in 18.1 is an opt-in setting that fixes this:&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
  &lt;span class=&quot;token property&quot;&gt;&quot;Settings&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;CacheImportState&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;
  &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;With it on, uSync remembers the hash of each file it has &lt;strong&gt;confirmed&lt;/strong&gt; matches what is in
Umbraco. Next time round, if the file on disk still hashes to the same value, uSync skips
straight to &amp;quot;no change&amp;quot; — no database lookup, no re-serialize. Import cost goes from &lt;em&gt;check
everything&lt;/em&gt; to &lt;em&gt;check the things that have actually changed&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;On a large site the difference is not subtle.&lt;/p&gt;
&lt;h3&gt;Two things you should know before turning it on&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;The first run is no faster.&lt;/strong&gt; uSync only ever records an item in two situations: the full,
expensive check ran and came back as &amp;quot;no change&amp;quot;, or uSync has just exported the item (in which
case the file was written from the database and the two sides match by definition). So the
first run after enabling it is exactly as slow as it was before — the win arrives on the second
run. An export warms the cache too, so an export-then-report cycle is already warm.&lt;/p&gt;
&lt;p&gt;We deliberately do &lt;strong&gt;not&lt;/strong&gt; record an item after a successful import. It is tempting to assume
that because we just wrote the item, the two sides now agree — but they don&#39;t always. Some items
don&#39;t round-trip exactly, which is what uSync&#39;s &lt;em&gt;&amp;quot;XML is different — but properties may not have
changed&amp;quot;&lt;/em&gt; message has always been telling you. Recording those would silence a real difference
for good, so we don&#39;t. Those items get checked again next time. Slower, but honest.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;It is off by default, and that is deliberate.&lt;/strong&gt; The cache is invalidated by Umbraco&#39;s
notifications — an item saved, deleted, moved or published is forgotten immediately, and
changing a doctype, datatype, template, language or folder throws the &lt;em&gt;whole&lt;/em&gt; cache away
(because those get baked into other items&#39; XML — rename a doctype and every item using it
serializes differently, without those items ever being touched). What it cannot see is a change
made by something that raises no notification at all: raw SQL, a row-level database restore.
That is the residual risk, and it is why we haven&#39;t turned it on for you.&lt;/p&gt;
&lt;p&gt;A &lt;strong&gt;force import&lt;/strong&gt; always ignores the cache entirely, so there is always a way to get a
guaranteed full check.&lt;/p&gt;
&lt;h3&gt;Where it lives&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;{LocalTempPath}/uSync/cache/&lt;/code&gt; — the site&#39;s temp folder, deliberately &lt;strong&gt;not&lt;/strong&gt; the uSync folder.
The cache describes &lt;em&gt;this site&#39;s database&lt;/em&gt;, not the source of truth, so it must never travel
between environments, get committed, or turn up in a diff.&lt;/p&gt;
&lt;p&gt;It is thrown away whenever we can&#39;t prove it still applies: a different database, a new uSync
version, or a change to any handler setting that affects what gets written out. If your host
recycles the temp folder (Azure App Service will, and each instance in a scale-out has its own),
the worst that happens is a slow first run.&lt;/p&gt;
&lt;p&gt;If you are thinking about turning this on, please read
&lt;a href=&quot;https://github.com/KevinJump/uSync/blob/v18/main/docs/perf/state-cache.md&quot;&gt;the full write-up in the repo&lt;/a&gt;
first — in particular the limitations section, and the note for anyone who has written a custom
serializer that pulls data in from another item.&lt;/p&gt;
&lt;h2&gt;The rest of the performance work&lt;/h2&gt;
&lt;p&gt;The cache is the headline, but it is not the only thing in 18.1.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Three O(n²) lookups are gone from the import path.&lt;/strong&gt; The duplicate-key check when merging
folders, the &amp;quot;keys to keep&amp;quot; check when cleaning up deleted items, and — the big one — the second
pass import for content and media, which used to scan the whole action list, building two
interpolated strings per comparison, for every single item. On a site with 10,000 two-pass items
that was tens of millions of string allocations for no reason. The action list is now indexed
once.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Content was being exported twice on every save-and-publish.&lt;/strong&gt; Umbraco 18.1 raises the &lt;em&gt;saved&lt;/em&gt;
notification for a save-and-publish as well as the &lt;em&gt;published&lt;/em&gt; one
(&lt;a href=&quot;https://github.com/umbraco/Umbraco-CMS/issues/23523&quot;&gt;umbraco/Umbraco-CMS#23523&lt;/a&gt;), and uSync
listens to both — so one editor action serialized and wrote the item twice. Un-publishing a
culture could manage three. All the notifications for a single operation now share a record of
what has been exported, so each item is written once.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;JSON handling moved to the Jumoo.Json package.&lt;/strong&gt; uSync&#39;s &lt;code&gt;JsonTextExtensions&lt;/code&gt; was a copy of
that library and had drifted behind it, so uSync now calls the real thing and picks up the
correctness and allocation work that has gone into it — including a genuine bug where property
values containing a quote, backslash or control character weren&#39;t being converted to JSON at
all. &lt;code&gt;uSync.Core.Extensions.JsonTextExtensions&lt;/code&gt; is still there and still behaves the same, but
every method on it is now obsolete and forwards on.&lt;/p&gt;
&lt;h2&gt;Thanks to Henrik&lt;/h2&gt;
&lt;p&gt;Not all of this was us. Two of the changes in 18.1 came in from &lt;strong&gt;Henrik at
&lt;a href=&quot;https://impact.dk/&quot;&gt;Impact&lt;/a&gt;&lt;/strong&gt;&lt;!-- TODO: check with Kevin — &quot;Impact&quot; is inferred from the commit
email domain (hg@impact.dk), and I don&#39;t have Henrik&#39;s GitHub handle or surname to link to.
Drop the agency mention or add the handle as appropriate. --&gt;, who went through
uSync&#39;s hot paths and sent us a pair of very welcome pull requests:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/KevinJump/uSync/pull/997&quot;&gt;#997&lt;/a&gt; — avoiding a pile of unneeded dictionary
operations. The classic &amp;quot;check if the key exists, then go and get it&amp;quot; pattern, done once per
item, in code that runs for every item.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/KevinJump/uSync/pull/998&quot;&gt;#998&lt;/a&gt; — marking uSync&#39;s &lt;code&gt;internal&lt;/code&gt; and &lt;code&gt;private&lt;/code&gt;
classes as &lt;code&gt;sealed&lt;/code&gt;, so the JIT can devirtualize calls to them instead of going through a
virtual dispatch every time, plus a move to .NET&#39;s newer &lt;code&gt;Lock&lt;/code&gt; type.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Neither of them changes what uSync does at all. They are the kind of change that is easy to
overlook when you are busy building features and are looking at the same code you have looked at
for years — and exactly the kind of thing a fresh pair of eyes spots straight away.&lt;/p&gt;
&lt;p&gt;They landed on v17 first and are ported forward into 18.1. Thank you Henrik, genuinely.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;One small note for anyone extending uSync: &lt;code&gt;SyncHandlerRoot.SyncChangeInfo&lt;/code&gt; is now &lt;code&gt;sealed&lt;/code&gt; as
part of #998. It is still &lt;code&gt;protected&lt;/code&gt;, so you can construct and return one from an
&lt;code&gt;IsItemCurrentAsync&lt;/code&gt; override exactly as before — you just can&#39;t derive from it any more.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr /&gt;
&lt;p&gt;Full details of everything in this release are in
&lt;a href=&quot;https://github.com/KevinJump/uSync/blob/v18/main/CHANGELOG.md&quot;&gt;the changelog&lt;/a&gt;.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync
&lt;/pre&gt;
</content>
  </entry>
  <entry>
    <title>uSync v18 and the Library</title>
    <link href="https://blog.jumoo.co.uk/2026/usync-v18-and-the-library/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/usync-v18-and-the-library/</id>
    <published>2026-06-25T10:30:00Z</published>
    <updated>2026-06-25T10:30:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;Umbraco v18 is out, and so is &lt;a href=&quot;https://github.com/KevinJump/uSync/releases/tag/v18.0.0&quot;&gt;uSync v18&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Most of the time a new major version of uSync is a fairly quiet affair — we move to the new
Umbraco dependencies, deal with whatever has been deprecated, run everything through the tests
and ship it. This one is different, because v18 of Umbraco brings &lt;strong&gt;Elements&lt;/strong&gt; and the Library,
and that is a whole new kind of thing for uSync to sync.&lt;/p&gt;
&lt;h2&gt;Elements and the Library&lt;/h2&gt;
&lt;p&gt;Elements are Umbraco&#39;s reusable content items — content that isn&#39;t a page, doesn&#39;t live in the
content tree, and can be used in lots of places. They live in the Library, they can be published
and unpublished, and they can be organised into folders.&lt;/p&gt;
&lt;p&gt;From uSync&#39;s point of view they are interesting because they sit somewhere between the things we
already sync. They behave a lot like content — they are publishable, they can be moved and
trashed — but they are organised like a settings item, in containers.&lt;/p&gt;
&lt;p&gt;So v18 of uSync has a new &lt;strong&gt;Library&lt;/strong&gt; handler that treats them properly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Elements are exported and imported like content, including their published/unpublished state.&lt;/li&gt;
&lt;li&gt;Trashed elements are handled — an element in the recycle bin doesn&#39;t come back as a live one
on the other side.&lt;/li&gt;
&lt;li&gt;Element folders (containers) are exported and imported alongside the items in them.&lt;/li&gt;
&lt;li&gt;They appear in uSync&#39;s tree in settings, so you can browse the exported files as usual.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;They sync as part of the &lt;strong&gt;Content&lt;/strong&gt; group, and they run &lt;em&gt;before&lt;/em&gt; media and content. That
ordering matters: if a page uses an element, the element needs to exist by the time the page
arrives.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/v18-usync-folder-structure.png&quot; alt=&quot;The uSync folder on disk, with the new Element folder sitting alongside Content, ContentTypes and the rest.&quot; /&gt;&lt;/p&gt;
&lt;h2&gt;Container folders now export on their own&lt;/h2&gt;
&lt;p&gt;There is one related fix that shipped shortly after, in &lt;strong&gt;18.0.2&lt;/strong&gt;, that is worth calling out
because it caught us out too.&lt;/p&gt;
&lt;p&gt;Elements live in folders, and until now those folders were only written during a &lt;em&gt;full&lt;/em&gt; export.
If you exported a single item — which is what happens on a dependency based push from
uSync.Publisher, for example — uSync resolved the item and wrote its file, but never looked at
the folder it lived in. The item arrived at the other end, the folder it should have been in
did not.&lt;/p&gt;
&lt;p&gt;So we have added a new &lt;code&gt;ISyncContainerHandler&lt;/code&gt; interface. A handler whose items live in
containers can now implement it and be asked to export a single container, rather than only
producing them as a side effect of exporting everything. The Library handler implements it, so
single-item exports now bring their folders with them.&lt;/p&gt;
&lt;p&gt;If you have written your own handler for items that live in folders, this is the interface you
want:&lt;/p&gt;
&lt;pre class=&quot;language-cs&quot;&gt;&lt;code class=&quot;language-cs&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;interface&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;ISyncContainerHandler&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;IEnumerable&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;uSyncAction&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;ExportContainer&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;Udi&lt;/span&gt; udi&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;string&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;]&lt;/span&gt;&lt;/span&gt; folders&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;HandlerSettings&lt;/span&gt; config&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;It takes a &lt;code&gt;Udi&lt;/code&gt; rather than an already-resolved entity, so the caller doesn&#39;t have to know
which Umbraco service resolves a container of your handler&#39;s type — your handler already knows
that, and does the lookup itself.&lt;/p&gt;
&lt;p&gt;The import side already knew what to do with container nodes when it found them — it was only
the export side that needed the way in.&lt;/p&gt;
&lt;h2&gt;Everything else&lt;/h2&gt;
&lt;p&gt;The rest of v18 is what you would expect from a major version:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Umbraco v18 dependencies throughout, and the build warnings from the upgrade cleared out —
we have moved off &lt;code&gt;ITemplate.MasterTemplateAlias&lt;/code&gt; to &lt;code&gt;LayoutTemplateAlias&lt;/code&gt;, and taken uSync&#39;s
own copy of the legacy &lt;code&gt;{localLink:x}&lt;/code&gt; parsing that Umbraco has removed, because uSync still
needs to be able to spot an un-migrated link.&lt;/li&gt;
&lt;li&gt;All the fixes that have gone into the v17 line over the last few months, merged forward.&lt;/li&gt;
&lt;li&gt;Some quiet performance work in the IO layer — folder reading is parallelised, and a few
list-scans in the import path have become set lookups.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Which version do I need?&lt;/h2&gt;
&lt;p&gt;The usual rule applies — the major version of uSync matches the major version of Umbraco:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Umbraco&lt;/th&gt;
&lt;th&gt;uSync&lt;/th&gt;
&lt;th&gt;Support&lt;/th&gt;
&lt;th&gt;End of life&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;v18&lt;/td&gt;
&lt;td&gt;v18&lt;/td&gt;
&lt;td&gt;STS&lt;/td&gt;
&lt;td&gt;25th June 2027&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;v17&lt;/td&gt;
&lt;td&gt;v17&lt;/td&gt;
&lt;td&gt;LTS&lt;/td&gt;
&lt;td&gt;27th November 2028&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;v16&lt;/td&gt;
&lt;td&gt;v16&lt;/td&gt;
&lt;td&gt;STS&lt;/td&gt;
&lt;td&gt;12th June 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;v13&lt;/td&gt;
&lt;td&gt;v13&lt;/td&gt;
&lt;td&gt;LTS&lt;/td&gt;
&lt;td&gt;14th December 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;v17 is the long term support release, so it will keep getting fixes for a good while yet. If you
are on v17 and happy, there is no rush. If you are moving to v18 for Elements, uSync is ready
for you.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;(End of life dates from &lt;a href=&quot;https://umbraco.com/products/knowledge-center/long-term-support-and-end-of-life/&quot;&gt;Umbraco&#39;s LTS/STS page&lt;/a&gt; — check there for the current schedule.)&lt;/em&gt;&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync
&lt;/pre&gt;
&lt;p&gt;As always, if something doesn&#39;t behave, &lt;a href=&quot;https://github.com/KevinJump/uSync/issues&quot;&gt;raise an issue&lt;/a&gt;
and we will take a look.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Extending uSync with uSync.Extend</title>
    <link href="https://blog.jumoo.co.uk/2026/extending-usync-with-usync-extend/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2026/extending-usync-with-usync-extend/</id>
    <published>2026-02-24T11:00:00Z</published>
    <updated>2026-02-24T11:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <category term="code"/>
    <content type="html">&lt;p&gt;uSync has always been extendable. If you have your own data in your own tables and you want it
to move between your environments the same way your doctypes and content do, you have always
been able to write a handler and a serializer and uSync will pick them up and treat your things
like they were built in.&lt;/p&gt;
&lt;p&gt;The problem is that &amp;quot;write a handler and a serializer&amp;quot; has historically meant quite a lot of
code, most of which is the same for everyone. So we have added a new package, &lt;strong&gt;uSync.Extend&lt;/strong&gt;,
which is a set of base classes to do all the boring bits for you.&lt;/p&gt;
&lt;h2&gt;What is in the box&lt;/h2&gt;
&lt;p&gt;uSync.Extend contains two base classes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;SyncObjectHandler&amp;lt;TObject&amp;gt;&lt;/code&gt; — the thing that controls the input/output of your data to and
from the file system. It is what gets called when an item is saved, and when uSync exports or
imports anything.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;SyncObjectSerializer&amp;lt;TObject&amp;gt;&lt;/code&gt; — the thing that turns your object into XML and back again.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Between them they cover the plumbing: file naming, folder structure, change detection, reporting,
the tree, the checkboxes on the dashboard, all of it. What is left for you to write is the small
bit that is actually about &lt;em&gt;your&lt;/em&gt; data.&lt;/p&gt;
&lt;h2&gt;A handler&lt;/h2&gt;
&lt;p&gt;The handler is mostly an attribute and two methods. The attribute is how uSync discovers it —
you don&#39;t need to register anything.&lt;/p&gt;
&lt;pre class=&quot;language-cs&quot;&gt;&lt;code class=&quot;language-cs&quot;&gt;&lt;span class=&quot;token comment&quot;&gt;/// &amp;lt;summary&gt;&lt;/span&gt;
&lt;span class=&quot;token comment&quot;&gt;///  the attribute set it all up. this is how it&#39;s discovered and registered in uSync&lt;/span&gt;
&lt;span class=&quot;token comment&quot;&gt;/// &amp;lt;/summary&gt;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;SyncHandler&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token string&quot;&gt;&quot;MyCustomObjectHandler&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
    &lt;span class=&quot;token string&quot;&gt;&quot;My Custom Object Handler&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
    &lt;span class=&quot;token string&quot;&gt;&quot;MyCustomObjects&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
    uSyncConstants&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;Priorites&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;USYNC_RESERVED_UPPER &lt;span class=&quot;token operator&quot;&gt;+&lt;/span&gt; &lt;span class=&quot;token number&quot;&gt;100&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;token comment&quot;&gt;// after all the core things&lt;/span&gt;
    Icon &lt;span class=&quot;token operator&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;icon-files&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
    EntityType &lt;span class=&quot;token operator&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;myCustomObject&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;]&lt;/span&gt;
&lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;class&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;MyCustomObjectHandler&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token type-list&quot;&gt;&lt;span class=&quot;token class-name&quot;&gt;SyncObjectHandler&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;MyCustomObject&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;string&lt;/span&gt;&lt;/span&gt; Group &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token string&quot;&gt;&quot;My Custom Group&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;private&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;readonly&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;IMyCustomObjectService&lt;/span&gt; _myCustomObjectService&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;MyCustomObjectHandler&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;
        &lt;span class=&quot;token comment&quot;&gt;/* ... the usual uSync services ... */&lt;/span&gt;
        &lt;span class=&quot;token class-name&quot;&gt;IMyCustomObjectService&lt;/span&gt; myCustomObjectService&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;base&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;logger&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; appCaches&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; shortStringHelper&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; syncFileService&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; mutexService&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; uSyncConfig&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; itemFactory&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
        _myCustomObjectService &lt;span class=&quot;token operator&quot;&gt;=&lt;/span&gt; myCustomObjectService&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;

    &lt;span class=&quot;token comment&quot;&gt;// here you would get all your items from your data source.&lt;/span&gt;
    &lt;span class=&quot;token keyword&quot;&gt;protected&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;async&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;IEnumerable&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;MyCustomObject&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;GetAllItems&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;await&lt;/span&gt; _myCustomObjectService&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;GetAllAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;protected&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;string&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;GetItemName&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;MyCustomObject&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;Name&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That is the whole handler. &amp;quot;Give me all your items&amp;quot; and &amp;quot;what is this one called&amp;quot;.&lt;/p&gt;
&lt;p&gt;The priority is worth a mention — &lt;code&gt;USYNC_RESERVED_UPPER + 100&lt;/code&gt; puts your handler after
everything uSync does itself, which is almost always what you want, because your objects
probably depend on doctypes or datatypes existing first.&lt;/p&gt;
&lt;h2&gt;A serializer&lt;/h2&gt;
&lt;p&gt;The serializer needs a few more methods, but they are all one-liners against your own service:&lt;/p&gt;
&lt;pre class=&quot;language-cs&quot;&gt;&lt;code class=&quot;language-cs&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;[&lt;/span&gt;&lt;span class=&quot;token attribute&quot;&gt;&lt;span class=&quot;token class-name&quot;&gt;SyncSerializer&lt;/span&gt;&lt;span class=&quot;token attribute-arguments&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token string&quot;&gt;&quot;c61e5987-020b-4ba8-899f-957d63443ac1&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt; &lt;span class=&quot;token comment&quot;&gt;// unique id, needs to be a GUID&lt;/span&gt;
    &lt;span class=&quot;token string&quot;&gt;&quot;My Custom Object Serializer&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;  &lt;span class=&quot;token comment&quot;&gt;// name&lt;/span&gt;
    &lt;span class=&quot;token string&quot;&gt;&quot;MyCustomObject&quot;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;]&lt;/span&gt; &lt;span class=&quot;token comment&quot;&gt;// the object type (node name in the xml)&lt;/span&gt;
&lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;class&lt;/span&gt; &lt;span class=&quot;token class-name&quot;&gt;MyCustomObjectSerializer&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token type-list&quot;&gt;&lt;span class=&quot;token class-name&quot;&gt;SyncObjectSerializer&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;MyCustomObject&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;MyCustomObject&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;CreateItem&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;XElement&lt;/span&gt; node&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;new&lt;/span&gt; &lt;span class=&quot;token constructor-invocation class-name&quot;&gt;MyCustomObject&lt;/span&gt;
        &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
            Key &lt;span class=&quot;token operator&quot;&gt;=&lt;/span&gt; node&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;GetKey&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
            Alias &lt;span class=&quot;token operator&quot;&gt;=&lt;/span&gt; node&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;GetAlias&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;,&lt;/span&gt;
        &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;async&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;MyCustomObject&lt;span class=&quot;token punctuation&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;FindItemAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;Guid&lt;/span&gt; key&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;await&lt;/span&gt; _service&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;FindByKeyAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;key&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;async&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;span class=&quot;token punctuation&quot;&gt;&amp;lt;&lt;/span&gt;MyCustomObject&lt;span class=&quot;token punctuation&quot;&gt;?&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;FindItemAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;string&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;alias&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;await&lt;/span&gt; _service&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;FindByAliasAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token keyword&quot;&gt;alias&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;SaveItemAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;MyCustomObject&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; _service&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;SaveAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;async&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Task&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;DeleteItemAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;MyCustomObject&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;
        &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;await&lt;/span&gt; _service&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;&lt;span class=&quot;token function&quot;&gt;DeleteAsync&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;&lt;span class=&quot;token keyword&quot;&gt;string&lt;/span&gt;&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;ItemAlias&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;MyCustomObject&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt; &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;Alias&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;

    &lt;span class=&quot;token keyword&quot;&gt;public&lt;/span&gt; &lt;span class=&quot;token keyword&quot;&gt;override&lt;/span&gt; &lt;span class=&quot;token return-type class-name&quot;&gt;Guid&lt;/span&gt; &lt;span class=&quot;token function&quot;&gt;ItemKey&lt;/span&gt;&lt;span class=&quot;token punctuation&quot;&gt;(&lt;/span&gt;&lt;span class=&quot;token class-name&quot;&gt;MyCustomObject&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;)&lt;/span&gt; &lt;span class=&quot;token operator&quot;&gt;=&gt;&lt;/span&gt; item&lt;span class=&quot;token punctuation&quot;&gt;.&lt;/span&gt;Key&lt;span class=&quot;token punctuation&quot;&gt;;&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Find it, save it, delete it, and tell uSync what its key and alias are. Everything else — the
XML shape, the hashing, the &amp;quot;has this changed?&amp;quot; comparison — comes from the base class.&lt;/p&gt;
&lt;p&gt;You do need a &lt;code&gt;Key&lt;/code&gt; (a GUID) and an &lt;code&gt;Alias&lt;/code&gt; on your objects. uSync uses the key to match items
between sites and the alias for the filename, so if your data doesn&#39;t have a stable GUID today,
that is the one bit of work you may have to do first.&lt;/p&gt;
&lt;h2&gt;Properties by reflection&lt;/h2&gt;
&lt;p&gt;Alongside the base classes we have added &lt;code&gt;ObjectPropertyExtensions&lt;/code&gt; to uSync.Core, which makes
it much less tedious to read and write properties onto an object when you only have the name of
the property as a string. It came out of tidying up our own serializers, but it is public
because if you are writing a serializer for an object with a lot of simple properties, you will
want it.&lt;/p&gt;
&lt;h2&gt;The example project&lt;/h2&gt;
&lt;p&gt;Reading base classes is not the same as seeing them used, so uSync.Extend ships with a working
example in its &lt;code&gt;Example&lt;/code&gt; folder — a custom object, a service to store them, a handler, a
serializer and a composer. It is deliberately dull: simple SQL-backed objects, no cleverness, so
you can see the shape of things without the noise.&lt;/p&gt;
&lt;p&gt;The example is excluded from release builds, so if you install the package you get the base
classes and not our imaginary objects. To read it, go and look at
&lt;a href=&quot;https://github.com/KevinJump/uSync/tree/v18/main/uSync.Extend&quot;&gt;the uSync.Extend folder on GitHub&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2026/custom-handler-group.png&quot; alt=&quot;The uSync dashboard showing a custom handler group alongside the built in ones.&quot; /&gt;&lt;/p&gt;
&lt;h2&gt;Why bother?&lt;/h2&gt;
&lt;p&gt;Because &amp;quot;it syncs everything except &lt;em&gt;that&lt;/em&gt; one thing&amp;quot; is a genuinely annoying place to be. If
you have built something bespoke into a site — a settings table, a set of reference data, a
custom editor&#39;s configuration — then the fact that it doesn&#39;t move with the rest of the site is
a papercut every single deployment.&lt;/p&gt;
&lt;p&gt;We use these base classes ourselves for the smaller things we sync, and they have made adding a
new one a job of half an hour rather than half a day. It seemed unfair to keep them to ourselves.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>AI Translations</title>
    <link href="https://blog.jumoo.co.uk/2025/AI-Translations/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2025/AI-Translations/</id>
    <published>2025-10-06T14:13:44Z</published>
    <updated>2025-10-06T14:13:44Z</updated>
    <category term="Umbraco"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;Today we have released the first full version of our new AI connector for Translation Manager
and you can install it today and get playing.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.Ai
&lt;/pre&gt;
&lt;h2&gt;More than just OpenAi.&lt;/h2&gt;
&lt;p&gt;You might not be aware, but we already have an AI based connector for Translation
Manager. our OpenAI connector is now over two years old! So why are we releasing
another one?&lt;/p&gt;
&lt;p&gt;Well 2 years is a very very long time in the world of AI and quite a long time in
the world of packages built around AI, in the time since we released our OpenAI we
have have 3 different underling AI libraries to help us talk to the AI, and now
most of them are out of date too.&lt;/p&gt;
&lt;p&gt;Also there are way more AI tools than just OpenAI and we think its time we looked
at making it easier to choose which tool you might want to use with your translations.&lt;/p&gt;
&lt;h2&gt;Multiple AIs&lt;/h2&gt;
&lt;p&gt;At the moment! for c# at least the world appears to be coalescing around the
Microsoft.Extensions.AI libraries and the Microsoft.SemanticKernel packages which
give an abstraction layer between your code and the AI&#39;s which mean its hopefully
simpler to switch between AI providers.&lt;/p&gt;
&lt;p&gt;As such our new AI provider uses these microsoft libraries and now requires significantly
less code to plug a new AI provider into the translation process in umbraco.&lt;/p&gt;
&lt;p&gt;With the release candidate we are supporting&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;OpenAI&lt;/li&gt;
&lt;li&gt;Azure AI Foundry&lt;/li&gt;
&lt;li&gt;Github reference models.&lt;/li&gt;
&lt;li&gt;Claude&lt;/li&gt;
&lt;li&gt;Ollama&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We are always looking to expand this to include as many of the popular AIs as we
can (assuming we get can find a supporting IChatClient library for them.)&lt;/p&gt;
&lt;h2&gt;Enhanced configuration&lt;/h2&gt;
&lt;p&gt;The new AI connector also supports way more configuration, You can now set more AI parameters and have more
insight into just how many tokens are being used for the translation. Great if you know your TopP from your TopK, and not really something to worry about if you don&#39;t&lt;/p&gt;
&lt;h2&gt;Translation Memory&lt;/h2&gt;
&lt;p&gt;One of the advantages of the new connector is support for Translation manager v16&#39;s Translation Memory feature,
which can reduce the amount of data being sent to the AI providers, increasing translation speed and reducing
the costs of the translations.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The Translation memory feature only works with machine and AI translators. and stores simple phase/language pairs to reduce the amount of round trips to external services.&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;Background support&lt;/h2&gt;
&lt;p&gt;Again with v16 this connector now also works with the new background submit feature which allows you to send jobs off to be translated in the background - great if you have 1000&#39;s of pages to translate you no longer have to sit and stare at the screen while it all happens.&lt;/p&gt;
&lt;h2&gt;AI/OpenAI Connector Support&lt;/h2&gt;
&lt;p&gt;At the moment the OpenAI connector is still supported has versions for Umbraco 13 through to v16. The Newer Jumoo.TranslationManager.AI connector supports Umbraco v13 and v16 (but not versions inbetween).&lt;/p&gt;
&lt;p&gt;As we progress towards v17 of Umbraco its our intention to only move the latest &amp;quot;AI&amp;quot; connector to v17 and
slowly removing support for the single OpenAI connector.&lt;/p&gt;
&lt;h2&gt;Extending.&lt;/h2&gt;
&lt;p&gt;The new AI connector can be extended by developing your own IAITranslator classes.
We will soon release documentation on how you can extend the connector to work with other AI providers (this will hopefully be a single file, not to much config!)&lt;/p&gt;
&lt;h2&gt;Try now.&lt;/h2&gt;
&lt;p&gt;You can download and install this version of our new AI Connector now, and use your &#39;favorite&#39; version of AI
to translate your content.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package Jumoo.TranslationManager.Ai
&lt;/pre&gt;
</content>
  </entry>
  <entry>
    <title>v16 Package Releases</title>
    <link href="https://blog.jumoo.co.uk/2025/v16-releases/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2025/v16-releases/</id>
    <published>2025-06-12T10:52:14Z</published>
    <updated>2025-06-12T10:52:14Z</updated>
    <category term="uSync"/>
    <category term="translations"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;Today (12th June 2025) sees the release of the next short-term support (STS) version of Umbraco.&lt;/p&gt;
&lt;p&gt;v16 of Umbraco is the 3rd release since the major updates to the backoffice using WebComponents and a modern set of APIs to manage Umbraco.&lt;/p&gt;
&lt;p&gt;Our packages have kept pace with these releases, so today we are releasing updates to all our major packages to run on Umbraco v16 with some of our more &amp;quot;minor&amp;quot; packages still to come.&lt;/p&gt;
&lt;h2&gt;Our v16 Releases&lt;/h2&gt;
&lt;p&gt;We have v16 releases for all our major (and some less major) packages:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/KevinJump/uSync/releases/tag/v16.0.0&quot;&gt;uSync&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/uSync.Complete.Issues/releases/tag/v16.0.0&quot;&gt;uSync.Complete&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/KevinJump/uSync.Forms/releases/tag/v16.0.0&quot;&gt;uSync.Forms&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/uSync.CommandLine/releases/tag/v16.0.0&quot;&gt;uSync.CommandLine&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Jumoo/Jumoo.TranslationManager.Issues/releases/tag/v16.0.0&quot;&gt;Translation Manager&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Translation Connectors&lt;/h3&gt;
&lt;p&gt;Translation Manager is released with a number of built in and additional connectors, so today we have also released updates to the following connectors:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;XLIFF Connector,&lt;/li&gt;
&lt;li&gt;Microsoft Connector,&lt;/li&gt;
&lt;li&gt;Google Connector,&lt;/li&gt;
&lt;li&gt;Passthrough Connector,&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nuget.org/packages/Jumoo.TranslationManager.Connector.DeepL/16.0.0&quot;&gt;DeepL Connector&lt;/a&gt;,&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nuget.org/packages/Jumoo.TranslationManager.OpenAi/16.0.0&quot;&gt;OpenAI Connector&lt;/a&gt;,&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://www.nuget.org/packages/Jumoo.TranslationManager.LanguageWire/16.0.0&quot;&gt;LanguageWire Connector&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Updated Documentation&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://docs.jumoo.co.uk/&quot;&gt;Our documentation&lt;/a&gt; has been updated too to reflect the latest versions.&lt;/p&gt;
&lt;h2&gt;Stability Towards v17&lt;/h2&gt;
&lt;p&gt;v16 of Umbraco is the last short-term support (STS) version before the next major long-term support (LTS) release v17. This is the release that most people will jump to from the last LTS release, v13. v13 uses the old backoffice, and it is quite a jump in terms of technology and setup.&lt;/p&gt;
&lt;p&gt;With that in mind, for the v16 releases of our products we are focusing on making the experience as stable and smooth as possible, so jumping from v13 to v17 will be as painless as it can be. This means we will not be adding any major functionality to the packages in v16 releases (we do have some in mind, but we are waiting!). Instead, we are testing and fixing all possible issues in v16 so it can be stable when we update.&lt;/p&gt;
&lt;h2&gt;Migrating&lt;/h2&gt;
&lt;p&gt;With v17 due out in November we are starting to looking at how our packages might help people migrate from v13 of Umbraco to v17 and beyond.&lt;/p&gt;
&lt;h3&gt;uSync &amp;quot;legacy&amp;quot; Migrations&lt;/h3&gt;
&lt;p&gt;uSync now has some simple migrations built in. If you start an Umbraco site with old uSync folders (e.g &amp;quot;uSync/v9&amp;quot;), uSync will present a legacy tab, and give you options to migrate this over to the latest version of uSync. Internally, uSync now has some basic migrations that it will do on the fly to bring a v13 style site up to v16. This includes adding support for variant blocks, updating block configs in RTE properties, and some other minor updates.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2025/legacy.png&quot; alt=&quot;uSync&#39;s legacy dashboard.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;It does not include larger migrations tasks, such as migrating grid elements to blockgrid elements. This is more complex and requires a slightly more complicated process.&lt;/p&gt;
&lt;h3&gt;uSync.Migrations&lt;/h3&gt;
&lt;p&gt;Our &lt;a href=&quot;https://github.com/Jumoo/uSyncMigrations&quot;&gt;uSync.Migrations&lt;/a&gt; package is much more powerfull and can migrate almost anything&lt;sup&gt;*&lt;/sup&gt; from one version of Umbraco to another. At the moment, Migrations only supports migrating up to Umbraco v13. With v17 just around the corner, we are starting to look at how Migrations might look on the new backoffice, and what we can do to make the transition easier (we expect a v13 to v17 migration to actually be a bit easier than a v8 to v13 one might have been).&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>2024 Price Updates</title>
    <link href="https://blog.jumoo.co.uk/2024/2024-prices/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2024/2024-prices/</id>
    <published>2024-10-01T18:30:01Z</published>
    <updated>2024-10-01T18:30:01Z</updated>
    <category term="Umbraco"/>
    <category term="uSync"/>
    <category term="translations"/>
    <content type="html">&lt;p&gt;It’s now seven years since we launched Translation Manager for Umbraco, and five years since the launch of uSync.Complete (uSync is thirteen years old!).&lt;/p&gt;
&lt;p&gt;In that time, there have been over 4 million downloads of uSync from Nuget and the Umbraco packages site(s). Thousands of sites are running uSync.Complete, and millions of pages of content have been translated into over a hundred languages using Translation Manager.&lt;/p&gt;
&lt;p&gt;uSync and uSync.Complete support every version up to and including v14, and v14 Translation Manager is in the works and will be out in the next few weeks!&lt;/p&gt;
&lt;p&gt;Every twelve months we review things including our prices (booo! 😔). In 2023 &lt;a href=&quot;https://blog.jumoo.co.uk/2023/2023-prices&quot;&gt;we decided not to raise the prices&lt;/a&gt; (Yeah 🎉), but this year to keep pace with inflation and costs and all the other boring things, we are having to increase the licence costs across our products.&lt;/p&gt;
&lt;blockquote&gt;
&lt;h3&gt;&lt;strong&gt;These price increases will come into effect on 1st November 2024&lt;/strong&gt;&lt;/h3&gt;
&lt;/blockquote&gt;
&lt;h2&gt;Licence costs from 1st November 2024&lt;/h2&gt;
&lt;p&gt;From 1st November 2024, licence costs will be increasing as set out below:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Product&lt;/th&gt;
&lt;th&gt;Nov 2024&lt;/th&gt;
&lt;th&gt;Old (pre Nov)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;h3&gt;uSync&lt;/h3&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;uSync.Complete Agency Licence&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£2750&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£2500&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;uSync.Complete Domain Licence&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£1150&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£1045&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;uSync.Complete Domain Subscription&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£550&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£500&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;uSync.Complete Upgrade (up to Umbraco v16)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£425&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£385&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;h3&gt;Translation Manager&lt;/h3&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Translation Manager&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£1025&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£935&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Translation Manager Upgrade (up to Umbraco v16)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;£425&lt;/td&gt;
&lt;td&gt;&lt;s&gt;£385&lt;/s&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;These price rises are in line with inflation 😔, and allow us to keep covering our basic costs, as well as the ongoing development of all our packages.&lt;/p&gt;
&lt;p&gt;As always, if you buy a licence now you will be covered for all current versions of the software we make, &lt;strong&gt;and&lt;/strong&gt; future versions, up until just before the next major Long Term Support release of Umbraco. So, a uSync.Complete licence you buy today will work on v8 though to v16 of Umbraco and uSync.Complete, and you would only need to buy an upgrade to go beyond version 17 of Umbraco.&lt;/p&gt;
&lt;h1&gt;Subscription updates&lt;/h1&gt;
&lt;p&gt;For people on existing subscriptions the cost will go up at the next renewal date, so if your renewal is Oct 2024 your price update will not hit until Oct 2025.&lt;/p&gt;
&lt;p&gt;We will be perfectly honest here: doing subscription price updates is a bit complicated, when stopping the system from pro-rating the increase across a 12 month period, so it might take us a few weeks to actually get this working. We won’t, however, implement the update without at least 30 days notice for existing subscriptions, so it&#39;s possible these price updates might hit a few weeks later than 1st Nov!&lt;/p&gt;
&lt;h1&gt;Lifetime licences&lt;/h1&gt;
&lt;p&gt;Domain licences are one-off payments that work forever on the version you purchase for and until you stop using them. That means you pay once and you have the product.&lt;/p&gt;
&lt;h1&gt;Subscription / Agency Licences&lt;/h1&gt;
&lt;p&gt;Subscription and agency licences are annual, and the licence will expire after 12 months. To continue using the product after the 12 month period, you need to renew your licence.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>v14.2 - uSync.Complete 🚀</title>
    <link href="https://blog.jumoo.co.uk/2024/uSyncComplete14/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2024/uSyncComplete14/</id>
    <published>2024-09-16T14:26:40Z</published>
    <updated>2024-09-16T14:26:40Z</updated>
    <category term="Umbraco"/>
    <category term="uSync"/>
    <content type="html">&lt;p&gt;A bit after the release of Umbraco v14, we are finally ready to announce full v14 release of the uSync.Complete packages!&lt;/p&gt;
&lt;h2&gt;uSync v14&lt;/h2&gt;
&lt;p&gt;uSync for Umbraco v14 has been out since the release date of Umbraco v14 and allows you to import and export all your settings between umbraco instances.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/usync-14.png&quot; alt=&quot;uSync v14 dashboard.&quot; /&gt;&lt;/p&gt;
&lt;p&gt;v14.2 of uSync - tidies up some of the rough edges in the UI, enhances the built-in mini-migrations that uSync does when you import from Umbraco v13 and generally is a little more solid and reliable on the latest versions of Umbraco.&lt;/p&gt;
&lt;h2&gt;uSync.Complete v14.2&lt;/h2&gt;
&lt;p&gt;The first full release of uSync.Complete for Umbraco v14 is version 14.2 - we have done this because the uSync.Complete release requires Umbraco v14.2 and so the versions are unified.&lt;/p&gt;
&lt;p&gt;uSync.Complete v14 contains all the same packages as previous versions of uSync brought up to date for the new Umbraco UI and inline with backend v14 code changes&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/publisher.png&quot; alt=&quot;uSync Publisher but in v14!&quot; /&gt;&lt;/p&gt;
&lt;h3&gt;Jumoo.Processing Engine.&lt;/h3&gt;
&lt;p&gt;Under the hood, uSync.Complete v14 is using our new internal processing engine that manages long running multi-step processes within umbraco and offers us a lot more flexibility in how we run things within all of the uSync.Complete packages.&lt;/p&gt;
&lt;p&gt;The processing engine is probably the main reasons why we&#39;ve had a bit of delay in getting uSync.Complete ready for Umbraco v14 but it does mean that going forward we have a solid platform to add and manage the complex processes in uSync.Complete (and we are going using the same processing the engine for Translation Manager!)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;At this time we don&#39;t think we will be opening up the processing engine as its own package, but maybe once we&#39;ve gotten our packages out we might polish some docs and get it out there.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;Existing Licences will work!&lt;/h3&gt;
&lt;p&gt;uSync.Complete licences work for a Long Term support release (LTS) and all following Short Term Support (STS) releases, as such if you have an uSync v13 licence then that will work with uSync.Complete on Umbraco v14.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;note if you purchased your uSync.Complete licence before 1st Oct 2023 then that will have been a v10 LTS licence and you will need to purchase an upgrade to work with v13 and above.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3&gt;Get the Package now.&lt;/h3&gt;
&lt;p&gt;You can install the uSync.Complete package on your Umbraco v14 site(s) now. without a licence you get a 60 trial to try out all the features and see if it works for you!&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync.Complete --version 14.2.0
&lt;/pre&gt;
</content>
  </entry>
  <entry>
    <title>uSync v14 Beta</title>
    <link href="https://blog.jumoo.co.uk/2024/uSync-14-beta/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2024/uSync-14-beta/</id>
    <published>2024-03-06T16:00:00Z</published>
    <updated>2024-03-06T16:00:00Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;&lt;a href=&quot;https://our.umbraco.com/download/releases/1400&quot;&gt;The Umbraco v14 beta is out!&lt;/a&gt; (6th March 2024), and as we try to be keep uSync as in sync as we can, we are releasing a beta version to go along with it.&lt;/p&gt;
&lt;h1&gt;Umbraco v14&lt;/h1&gt;
&lt;p&gt;Umbraco v14 is a complete rewrite of the Umbraco backoffice &#39;client&#39;, So AngularJs is gone, and in its place we have WebComponents, and new Management APIs. While these changes will make very little difference to how your website looks and behaves it does change quite a lot for package developers.&lt;/p&gt;
&lt;p&gt;The Umbraco v14 beta is very much aimed at package developers, and the &lt;a href=&quot;https://docs.umbraco.com/umbraco-cms/v/14.latest-beta/&quot;&gt;new Documentation&lt;/a&gt; is definitely the place to start looking.&lt;/p&gt;
&lt;h1&gt;uSync v14.&lt;/h1&gt;
&lt;p&gt;uSync v14 mostly works like previous versions of uSync, in fact the core of the code doing all the work is the same as v13. You get all the existing features, such as roots and background processing, but with a shiny v14 look.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/usync-14.png&quot; alt=&quot;uSync v14 dashboard&quot; /&gt;&lt;/p&gt;
&lt;h2&gt;One Does Not Simply Copy From v13 (yet).&lt;/h2&gt;
&lt;p&gt;One of our long term aims with uSync is for our files to be as close to 100% backward compatible as possible (you can take uSync v8 files and use them on v13), but there are some small changes in Umbraco v14 that means at the moment, copying v13 uSync files to a Umbraco v14 site won&#39;t work.&lt;/p&gt;
&lt;p&gt;In the long term we are looking to make this work, and you can see the start of that if you run uSync v14 with an old usync folder now.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/usync-14-legacy.png&quot; alt=&quot;uSync beta legacy warning box&quot; /&gt;&lt;/p&gt;
&lt;p&gt;But this means for the beta, while you could get some mileage from &amp;quot;simply&amp;quot; copying the v13 files, you might see that some of the datatype configuration settings don&#39;t make it across. Don&#39;t worry, we&#39;ll be on top of this in the final release.&lt;/p&gt;
&lt;h2&gt;What Isn&#39;t Beta&lt;/h2&gt;
&lt;p&gt;We are working on all our extra packages, such as &lt;a href=&quot;https://jumoo.co.uk/uSync/complete/&quot;&gt;uSync.Complete&lt;/a&gt;, &lt;a href=&quot;https://jumoo.co.uk/uSync/forms/&quot;&gt;uSync.FormsEdition&lt;/a&gt;, and uSync.Umbraco.Commerce. As the betas and release candidates progress, we will release those packages alongside the uSync beta. For now, you just have the core uSync package should you need it.&lt;/p&gt;
&lt;h2&gt;Gettting uSync Beta.&lt;/h2&gt;
&lt;p&gt;The uSync v14 beta can be installed just like any other nuget package (that bit hasn&#39;t changed).&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync --version 14.0.0-beta01
&lt;/pre&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
</content>
  </entry>
  <entry>
    <title>Introducing uSync Roots 🌳</title>
    <link href="https://blog.jumoo.co.uk/2024/roots/" rel="alternate" type="text/html"/>
    <id>https://blog.jumoo.co.uk/2024/roots/</id>
    <published>2024-01-23T22:05:27Z</published>
    <updated>2024-01-23T22:05:27Z</updated>
    <category term="uSync"/>
    <category term="Umbraco"/>
    <content type="html">&lt;p&gt;Ever wanted to build a new site that was just like that other site you built? or do you have loads of sites that almost the same and it would be good if you could have some sort of central base site that you could base them off and keep in sync with?&lt;/p&gt;
&lt;p&gt;Well, yes, the idea of a baseline or blueprinting isn&#39;t new in Content Management or even Umbraco land. but now, after mainly not getting around to it for years - We are very proud to announce uSync&#39;s own &amp;quot;blueprinting&amp;quot; solution - uSync Roots 🎉.&lt;/p&gt;
&lt;p&gt;uSync roots is fully integrated into the core uSync solution (so its part of the free bit!) you can download a beta build now, and see how and if could help you keep control of your Umbraco sites.&lt;/p&gt;
&lt;h1&gt;How uSync Roots works&lt;/h1&gt;
&lt;p&gt;uSync Roots lets you have a root (or many roots) sites that you can then base other sites on, and with those other sites you can either overwrite or sync them back to your root site as and when you feel like you need to.&lt;/p&gt;
&lt;p&gt;Root sites, put their files in &lt;code&gt;/uSync/roots&lt;/code&gt;. and &#39;child&#39; sites behave like normal sites and put their files in &lt;code&gt;/uSync/v9&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The magic happens when you import or export from the child site.&lt;/p&gt;
&lt;h2&gt;Importing with uSync Roots&lt;/h2&gt;
&lt;p&gt;When importing uSync will auto-magically merge the &lt;code&gt;uSync/roots&lt;/code&gt; and &lt;code&gt;uSync/v9&lt;/code&gt; trees into one Seamless uSync import - meaning you get both the changes from the root site and the changes from the child site all in one.&lt;/p&gt;
&lt;h2&gt;Saving/Exporting with uSync Roots&lt;/h2&gt;
&lt;p&gt;When you save on your child site, depending on your settings uSync will either save a copy of your changes the &lt;code&gt;uSync/v9&lt;/code&gt; folder or it will stop you from making the change.&lt;/p&gt;
&lt;p&gt;Files in the &lt;code&gt;uSync/v9&lt;/code&gt; folder take precedence, so a change on the child site will overwrite a change on the root site.&lt;/p&gt;
&lt;h2&gt;&amp;quot;Fancy&amp;quot; merging&lt;/h2&gt;
&lt;p&gt;So when you make a change on a child site it will overwrite the change you might have made on the root - changes on the child win.&lt;/p&gt;
&lt;p&gt;But we thought, what if you want to add a new property to a content type on a child site and you still want to get any updates from the root site ?&lt;/p&gt;
&lt;p&gt;Well with &amp;quot;fancy&amp;quot; merging, you can do that.&lt;/p&gt;
&lt;p&gt;Fancy merging means when you add a new property to a content type on a child site, uSync will store just that property change and not overwrite the settings from the root content type.&lt;/p&gt;
&lt;p&gt;Then when it comes time to import, uSync merges the two sets of properties for the content type together, and you get a combination of what you have on the child site and what you have on the root!&lt;/p&gt;
&lt;p&gt;This works for deletes too! you can delete a property that was set on the root, and still get all the other root properties and updates through to your site!&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/propertymerge.png&quot; alt=&quot;Fancy merge lets you add properties on child sites and still get updates from the master for exiting or new root values&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Its life changing, but there is more !&lt;/p&gt;
&lt;p&gt;We started with fancy merging on ContentType properties, and then we added MediaType and MemberType properties (because they are a basically the same internally 🤷), but then we thought could we go any further ?&lt;/p&gt;
&lt;h2&gt;&#39;Fancy&#39; DataType config merging&lt;/h2&gt;
&lt;p&gt;Fancy merging for DataTypes allows us to blend together configuration from both the root and the child sites so you get a mix of the things you setup on your root, and extra you might want to add for a child site.&lt;/p&gt;
&lt;p&gt;Now this might not ,ake sense for a lot of DataTypes - but for things like BlockLists and BlockGrids its really cool.&lt;/p&gt;
&lt;h2&gt;BlockList/BlockGrid merging.&lt;/h2&gt;
&lt;p&gt;You can have a core set of blocks defined in a BlockList on on your root site, and then you can add to that list on your child site.&lt;/p&gt;
&lt;p&gt;What happens if you add new blocks to the root ? well when you import them to the child site they are added straight in and you get to keep your additional child blocks too!&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://blog.jumoo.co.uk/images/2024/mergedblocklist.png&quot; alt=&quot;A merged block Grid, showing parent and child blocks in one&quot; /&gt;&lt;/p&gt;
&lt;p&gt;Out-of-the-box, uSync roots will fancy merge, BlockLists, BlockGrids, and imageCroppers, we
will probably add the other listy things too before final release.&lt;/p&gt;
&lt;h1&gt;Getting started.&lt;/h1&gt;
&lt;p&gt;We are in early access preview, you can install our beta for Umbraco 13.1 and get playing with roots.&lt;/p&gt;
&lt;pre class=&quot;nuget&quot;&gt;
dotnet add package uSync --version 13.1.0-beta01
&lt;/pre&gt;
&lt;h2&gt;1. Create a &amp;quot;Root&amp;quot; site.&lt;/h2&gt;
&lt;p&gt;you root site is defined with a setting in `appSettings.json``.&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;Settings&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
            &lt;span class=&quot;token property&quot;&gt;&quot;IsRootSite&quot;&lt;/span&gt; &lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;true&lt;/span&gt;
        &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Cleaning out the uSync folder and performing an export will get you your &lt;code&gt;uSync/root&lt;/code&gt; folder.&lt;/p&gt;
&lt;h3&gt;2. link a &amp;quot;Child&amp;quot; Site&lt;/h3&gt;
&lt;p&gt;Your child site just needs the &lt;code&gt;uSync/root&lt;/code&gt; folder copying into it. and its good to go.&lt;/p&gt;
&lt;p&gt;by default the child site will be locked from overwriting root items, and won&#39;t let you
save the changes in the UI. you can disable this behavior by setting &lt;code&gt;LockRoot&lt;/code&gt; to false in the config of the child site.&lt;/p&gt;
&lt;pre class=&quot;language-json&quot;&gt;&lt;code class=&quot;language-json&quot;&gt;&lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
    &lt;span class=&quot;token property&quot;&gt;&quot;uSync&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
        &lt;span class=&quot;token property&quot;&gt;&quot;Settings&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token punctuation&quot;&gt;{&lt;/span&gt;
            &lt;span class=&quot;token property&quot;&gt;&quot;LockRoot&quot;&lt;/span&gt;&lt;span class=&quot;token operator&quot;&gt;:&lt;/span&gt; &lt;span class=&quot;token boolean&quot;&gt;false&lt;/span&gt; 
        &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
    &lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;
&lt;span class=&quot;token punctuation&quot;&gt;}&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That the quick guide really, when you want to update a child site copy the root folder to its uSync folder and import.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;top tip:&lt;/strong&gt; uSync roots default config makes it work for one root, but it actually can have many. You can define a set of folders in the &lt;code&gt;Folders&lt;/code&gt; setting and uSync will merge them all (first -&amp;gt; last, so last folder takes precedence.)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1&gt;What&#39;s next?&lt;/h1&gt;
&lt;p&gt;We are looking for feedback and people to test the roots functionally, and we are also looking into how we might help people diagnose and understand how the roots and child sites are working together.&lt;/p&gt;
&lt;p&gt;In the world of uSync.Complete we think we might have a roots dashboard where you can remotely pull down the root from another site (along with views, js files etc) and then run the import, but that is probably a bit off, and likely at this stage to be a v14 thing.&lt;/p&gt;
&lt;p&gt;So please test, give us feedback, and hopefully this will become another valuable tool for people keeping all those sites in sync.&lt;/p&gt;
</content>
  </entry>
</feed>

