v14 - Insert AI generated image of a number 14 here.

[KevinJump]

This is a Major release of uSync for Umbraco v14 and the new Umbraco Backoffice.

Warning

Things have changed! Read all the release notes before running that add package command!,

The latest v14 release of uSync works on Umbraco v14 only. v14 of Umbraco is a complete replacement of the backoffice user interface, alongside significant changes to the API that Umbraco and packages use to communicate between the user interface and the server.

This release comes with a number of known issues with Umbraco v14, and you should check these, alongside our known issues, before you fully commit to using Umbraco v14 and/or uSync v14 on a live production site.

What's New

• New Backoffice UI.
• New Management API
• New shared npm library for other uSync packages

Known Issues

• Check Umbraco's list of v14 issues before you start.
• uSync.History is not yet part of this package

Installing

uSync can be installed as part of a calorie controlled diet. and via NuGet for your umbraco projects.

dotnet add package uSync --version 14.0.0

Umbraco v14 Support Lifetime

It is worth noting that Umbraco v14 is a Short-Term Support (STS) release and has a limited support lifetime. Bug fix level support ends in November 2024 and the release is End of Life (EOL) March 2025. v13 of Umbraco has Long Term Support (LTS) until Dec 2025 (security updates until Dec 2026) and we would still consider v13 the sensible choice for any large-scale production-ready site development at this time.

Migrating to Umbraco v14 using uSync

Where possible, we have attempted to make it as seamless as we can to use uSync v13 files on a new uSync v14 site. However, with the number of changes to the Backoffice, alongside several property editors being removed from v14, we strongly recommend that you only migrate sites to Umbraco 14 from Umbraco v13 if you are not using any obsoleted property editors (datatypes) and you are happy with the functionality of your site and the Backoffice on Umbraco v13.

Migrating while you are using obsolete property editors might result in data and content loss, and you can’t then easily know if the issue with your migrated site is related to the new v14 Backoffice / APIs or the property editor changes you will have made.

Converting uSync/v9 to uSync/v14

For uSync v14 we have changed the default folder that uSync files are stored in from the existing uSync/v9 folder to uSync/v14. This reflects the fact that there are some changes between the uSync files on v14 and it is better to have a new clean folder for your setup then continue with the existing v9 files.

Legacy Conversion

If your site contains a uSync/v9 folder uSync will detect this and display a ‘legacy’ tab in the uSync dashboard.

This legacy tab will provide you with some information about the v9 folder and any removed property editors that it finds. It will also give you the opportunity to either ignore the legacy folder or copy it to the uSync/v14 folder where you can use it to seed your new site.

**We strongly recommend that this is only performed on a development copy of your site where you have full database backups and are willing to reset the site should the migration not go smoothly. **

After copying the v9 folder to uSync/v14, you can import your settings to your new v14 site. If this is successful, you should perform a clean export to get the new uSync/v14 files in the latest format for the site.

Happy uSyncing...

---

This discussion was created from the release v14 - Insert AI generated image of a number 14 here..