What's Changed

• Installer fixes - allow installer to run by @gavinfaux in #456
• Umbraco 15/16 compatability by @gavinfaux in #462
• Umbraco 16 (.NET 9) and Umbraco 17 (.NET 10) by @gavinfaux in #470
• Bump Umbraco.Cms from 13.9.2 to 13.12.1 by @dependabot[bot] in #469
• fix: Harden external import media fetches by @gavinfaux in #473
• fix: remove duplicate package reference by @gavinfaux in #472
• Security hardening, import fixes and QA improvements by @gavinfaux in #474
• Supporting Umbraco v15 by @Shazwazza in #455
• Ensure NuGet symbol packages include PDBs in Linux release builds by @Copilot in #476
• Consolidate the build workflow on Linux by @Copilot in #477
• chore: harden npm package install requirements by @gavinfaux in #478
• Add agentic workflow efficiency-improver by @Shazwazza in #480
• [efficiency-improver] perf: use FrozenDictionary for search fields in DefaultArticulateSearcher by @github-actions[bot] in #481
• [efficiency-improver] perf: cache publishedDate property type ID to eliminate per-request DB lookup by @github-actions[bot] in #485
• fix: prevent HMAC image 400 by using IHtmlContent for CSS url() values by @gavinfaux in #483
• Bump Umbraco 17.4.0 and update CI build workflow by @gavinfaux in #488

Full Changelog: v5.2.2...v6.0.0

• Fixes: newly installed articulate package , clicking on categories or tags gives --> NullReferenceException: Object reference not set to an instance of an object. #449

Full Changelog: v5.1.0...v5.1.1

What's Changed

• Fixes #446, #439, #432 - The issue where dynamically routed nodes like categories and tags would end up in a 404 if a custom 404 page in Umbraco or ILastChanceContentFinder was declared - was a doozy of a bug to figure out 😅
• Adds a .NET 8 target

Full Changelog: v5.0.3...v5.1.0

What's Changed

• bump System.ServiceModel.Syndication to 6.0.0 by @nvisage-gf in #443
• Add method GetAllCategories to the ArticulateTagService by @wvdweerd in #442
• 440 ArticulateRootNodeCache InvalidOperationException: Sequence contains no matching element by @nvisage-gf in #441
• Bump Umbraco.Cms from 10.1.0 to 10.8.1 in /src/Articulate.Tests.Website by @dependabot in #435

New Contributors

• @wvdweerd made their first contribution in #442

Full Changelog: v5.0.2...v5.0.3

What's Changed

• Bump Microsoft.AspNet.Identity.Owin from 2.2.2 to 2.2.4 in /src/Articulate.Web by @dependabot in #424
• Bump Microsoft.AspNet.Identity.Owin from 2.2.2 to 2.2.4 in /src/Articulate by @dependabot in #425
• Bump UmbracoCms.Core from 8.2.3 to 8.5.4 in /src/Articulate.Web by @dependabot in #426
• Bump UmbracoCms.Core from 8.2.3 to 8.5.4 in /src/Articulate by @dependabot in #427
• Fix for #444 by @Jeavon in #445

Full Changelog: v4.4.0...v4.5.0

What's Changed

• Bump Umbraco.Cms.Web.BackOffice from 10.1.0 to 10.6.1 in /src/Articulate by @dependabot in #428
• [FIX] Manual change to Umbaco version by @OwainWilliams in #429
• #432 all nodes except the homepage return 404 by @nvisage-gf in #436

New Contributors

• @OwainWilliams made their first contribution in #429

Full Changelog: v5.0.0...v5.0.2

What's Changed

Major release supporting Umbraco 10+

• 'Upgrade to v9.0.0' by @erikjanwestendorp in #389
• Fixes @Html.Table() by @warrenbuckley in #390
• Small fixes in phantom theme by @erikjanwestendorp in #391
• Small changes for mini theme by @erikjanwestendorp in #392
• OpenSearch Route by @warrenbuckley in #393
• Fix GitHub Actions CI Build - Remove old examine feed by @warrenbuckley in #395
• Fixes RSD route in ArticulateRouter by @warrenbuckley in #394
• Fix Category & Tags RSS Feeds by @warrenbuckley in #397
• V9 Fix - Theme Errors by @warrenbuckley in #399
• V9: Fix Markdown mobile editor by @warrenbuckley in #398
• Upgrade to Umbraco 10.0.1 by @warrenbuckley in #402
• Fix up build for creating a Nuget package by @warrenbuckley in #400
• Fixes: Dynamic routes from Articulate Route Node are updated on publish by @warrenbuckley in #403
• Routing windowslivewriter manifest & XMLRPC MetaWeblog to support OpenLiveWriter by @warrenbuckley in #396
• umbraco-backoffice-extensions-js throws 500 error by @dinc5150 in #423
• Bump Microsoft.AspNet.Identity.Owin from 2.2.2 to 2.2.4 in /src/Articulate.Web by @dependabot in #424
• Bump Microsoft.AspNet.Identity.Owin from 2.2.2 to 2.2.4 in /src/Articulate by @dependabot in #425
• Bump UmbracoCms.Core from 8.2.3 to 8.5.4 in /src/Articulate.Web by @dependabot in #426
• Bump UmbracoCms.Core from 8.2.3 to 8.5.4 in /src/Articulate by @dependabot in #427

New Contributors

• @erikjanwestendorp made their first contribution in #389
• @dinc5150 made their first contribution in #423

Full Changelog: v4.4.0...v5.0.0

What's Changed

• Fixes BlogMl exporter doesn't handle code fences with language aliases #416
• Added https to call fonts by @simonech in #377
• Fix Culture Varying Blog Page not returning BlogLogo in GetArticulateCropUrl by @marcemarc in #410
• Bump Newtonsoft.Json from 12.0.1 to 13.0.2
• Bump Microsoft.Owin.* from 4.0.1 to 4.2.2
• Resolves #385. by @FloppyChips in #386

New Contributors

• @marcemarc made their first contribution in #410
• @FloppyChips made their first contribution in #386

Full Changelog: v4.3.2...v4.4.0

What's Changed

• fix-362 using content attribute for twitter:card meta tag by @fbranicky in #363

Full Changelog: v4.3.1...v4.3.2

See milestone for details: https://github.com/Shazwazza/Articulate/milestone/21?closed=1

See 4.3.0 release blog post for more detailed info on the 4.3.0 release.

Articulate is available on Nuget or via Our

PM> Install-Package Articulate

❤️ If you use and like Articulate please consider becoming a GitHub Sponsor ❤️

New Installs

Via Nuget

Articulate will add an Articulate dashboard in the Settings section. If you install via Nuget, then you won't have the Articulate data automatically installed for you so once you load up your back office, go to the Dashboard and install the data:

Via Back office

If you install Articulate through the back office - it's just like it was before and Articulate will populate all of the demo data automatically. https://our.umbraco.org/projects/starter-kits/articulate/

Upgrading

4.3.0 specifics - To have the new markdown with code snippet feature, you'll need to make sure that the Articulate Markdown Data Type is using the Articulate Markdown property editor. In many cases, this will just be configured to use Umbraco's default Markdown property editor. All you need to do is change it to use Articulate Markdown and everything will work.

If you are upgrading from articulate 3.x, please see these notes: https://github.com/Shazwazza/Articulate/releases/edit/v4.0.0

If you are upgrading from 4.x then upgrading is straight forward: Just update the package via nuget if that's what you use, else just install the package in the back office and it will upgrade.

2 bugs fixed, see milestone for full details: https://github.com/Shazwazza/Articulate/milestone/20?closed=1

See 4.3.0 release blog post for more detailed info on the 4.3.0 release.

Articulate is available on Nuget or via Our

PM> Install-Package Articulate

❤️ If you use and like Articulate please consider becoming a GitHub Sponsor ❤️

New Installs

Via Nuget

Articulate will add an Articulate dashboard in the Settings section. If you install via Nuget, then you won't have the Articulate data automatically installed for you so once you load up your back office, go to the Dashboard and install the data:

Via Back office

If you install Articulate through the back office - it's just like it was before and Articulate will populate all of the demo data automatically. https://our.umbraco.org/projects/starter-kits/articulate/

Upgrading

4.3.0 specifics - To have the new markdown with code snippet feature, you'll need to make sure that the Articulate Markdown Data Type is using the Articulate Markdown property editor. In many cases, this will just be configured to use Umbraco's default Markdown property editor. All you need to do is change it to use Articulate Markdown and everything will work.

If you are upgrading from articulate 3.x, please see these notes: https://github.com/Shazwazza/Articulate/releases/edit/v4.0.0

If you are upgrading from 4.x then upgrading is straight forward: Just update the package via nuget if that's what you use, else just install the package in the back office and it will upgrade.