Hello Everyone.
V1.1.2 of https://marketplace.umbraco.com/package/umbraco.community.aivisibility is out now. I have updated:
Hijacked controllers with custom view models now work out of the box. v1.1’s Auto strategy only fell back to Loopback on ModelBindingException, but the RenderController.CurrentTemplate(viewModel) + @model CustomViewModel pattern (very common agency convention) throws InvalidOperationException at view-activation instead — and the package was caching that as “permanently failed” and never trying Loopback. v1.1.2 widens the fallback trigger to recognise both hijack shapes; agency sites now work without needing to pin Mode = Loopback manually.
:
: TagHelper now auto-registers. was rendering as literal markup unless adopters manually added @addTagHelper *, Umbraco.Community.AiVisibility to their _ViewImports.cshtml. v1.1.2 ships an MSBuild target inside the .nupkg that injects the directive on first build — idempotent, leaves existing _ViewImports.cshtml content alone, works on fresh dotnet new umbraco projects too.
:
: LoopbackUrlResolver now prefers HTTPS. Default dotnet new umbraco projects ship with both HTTP + HTTPS Kestrel bindings AND UseHttpsRedirection middleware in the pipeline. The v1.1 resolver was picking HTTP and getting 307’d to HTTPS on every loopback request, surfacing as a render failure. v1.1.2 prefers HTTPS when both bindings are observed; HTTP-only containers keep working unchanged.
dotnet add package Umbraco.Community.AiVisibility --version 1.1.2
Let me know if you are using it and have any feedback at all!