← Back to all sparks
V

Virto Commerce

E-COMM
Velocity5.0

Open source B2B commerce platform on .NET

Virto Commerce backports a blade widget UI freeze fix across three active release trains while tightening module auth hooks

ecommercemulti-branchmodule-platformenterprisebug-fixes
Current state
Virto Commerce is simultaneously maintaining multiple release trains (3.1007, 3.1039, 3.1060, 3.1068-3.1070), applying the same fixes as backports across the board. The current batch addresses a UI freeze in blade widget containers triggered by repeated sign-in, pipeline hooks for routing and authentication lifecycle events, and a security fix ensuring user deletion targets only by ID. The multi-branch model reflects an enterprise customer base spread across versions.
Where it's heading
Module pipeline hooks — firing after routing and after authentication — represent a meaningful extension to the developer API, giving module authors reliable lifecycle callbacks. The bounded API key lookup cache and dedup notifier hot-path optimizations point to ongoing performance work on the auth layer.
Prediction
Pipeline hook coverage will likely expand to more module lifecycle events in coming releases; the security-focused user-deletion fix (by ID only) suggests a broader audit of identifier handling across the platform may be underway.

Recent moves

  1. 1d ago

    3.1007.27

    Backport of the blade widget $digest loop fix to the 3.1007 maintenance branch — same fix as the main and mid-range branches, applied for customers on the older supported release train.

    View source ↗
  2. 1d ago

    3.1039.12

    Same $digest loop fix backported to the 3.1039 branch — part of the multi-train patch deployment pattern Virto uses to serve customers across supported versions simultaneously.

    View source ↗
  3. 1d ago

    3.1070.0

    The $digest loop fix on the main (3.1070) branch — fixes an infinite digest cycle in blade widget containers triggered by repeated sign-in within a single browser tab.

    View source ↗
  4. 6d ago

    3.1060.2

    Adds module pipeline hooks that fire after routing and after authentication, plus a bounded cache for API key lookups. The hooks give module developers predictable lifecycle insertion points; the cache cap prevents unbounded memory growth under API key-heavy request patterns.

    View source ↗
  5. 6d ago

    3.1069.0

    Tightens user deletion to target by ID only, never by username — a correctness fix that prevents accidental deletion of a wrong user record when usernames are non-unique or shared across tenants.

    View source ↗
  6. 7d ago

    3.1060.1

    Intermediate patch on the 3.1060 branch applying the module pipeline hooks and API key cache work — same content as 3.1060.2, published as the initial backport before the follow-up patch.

    View source ↗