Microsoft customers worldwide can now discover and use DotNest, a fully managed website hosting platform, through Microsoft Marketplace, accessing trusted solutions that accelerate innovation and business transformation with unified integration across Microsoft products

Why external login helpsWhen a portal has its own separate user account system, someone needs to manage those users separately too.

If you know Lombiq, you probably know us from GitHub, from the Orchard Core project itself, or from a developer conference. A chamber of commerce or a CMS industry panel isn't the first place you'd expect to find us. But over the past year, we joined five business and industry communities, and we did it on purpose.

Orchard Core updatesImprove the Admin Dashboard contentThe OrchardCore.AdminDashboard module lets you build the admin landing page from widgets. Each widget is a regular content item, so you can edit, secure, version, and localize it like any other content.

Orchard Core updatesSupport multiple content type IDs and stereotypes in admin contents list filteringThe admin contents list only accepted a single contentTypeId and a single stereotype to scope the filtered view. This change by Mike Alhayek makes the Contents admin list action support filtering by multiple content type IDs or stereotypes, while preserving the existing parameter names.

Orchard Core updatesAllow users to be granted read-only permission for RolesThis feature by Matt Varblow adds a new View Roles permission, letting you grant a group of users, like support staff who manage a subset of users, visibility into role definitions and their assigned permissions, without giving them the ability to change anything. The new permission only allows access to the Roles Index and Display actions, and is implied by Manage Roles, so admins keep full control.

Orchard Core updatesReplace ImageSharp.Web with NetVips for on-demand image processingImageSharp v4.0.0 is out, and the breaking changes are minimal for us. But this version enforces a license check, as noted on the Six Labors blog, requiring a license file to be present, see details here. The license itself didn't change: Orchard Core, as an open-source project, can keep using it, and the license doesn't affect transitive dependents, i.e. users of Orchard Core. But there are multiple issues:

Retrieve the Principal Id of the signed-in Azure user with the Azure CLI and use it to set environment variables for azd deployments.