Remove ConfirmationMessage from Users, Roles, and Tenants MudBlazor
delete actions so only AbpMudCrudPageBase.ConfirmDeleteAsync prompts.
This restores the single-confirm behavior after ConfirmationMessage was
reintroduced on top of the base-class dialog.
Co-authored-by: Cursor <cursoragent@cursor.com>
- FeatureManagement ResetedToDefault: avoid a word that reads as "Oops".
- ExceptionHandling Unauthorized: same text as 401Message.
- AbpUi LoadMore: grammatical wording.
- Blogging and Docs ShareOn: no dangling prefix before the share icons.
- Blogging singular "ago" texts: drop the count, they are only used for 1.
- CmsKit MonthDayAt and FullDate: no prefix glued to the month name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds a he.json next to each of the 30 en.json resources under
framework/src and modules/*/src (1,124 texts). Each project already
embeds and loads its localization folder, so no code changes are needed.
Resolves#26368
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
update-gulp followed the latest dist-tag and rewrote @abp dependencies to 10.7.0 during the patch release.
Co-authored-by: Cursor <cursoragent@cursor.com>
VoloDocs only registered "pt-BR" as a supported culture in
VoloDocsWebModule, even though a "pt" localization resource file
(Localization/Resources/VoloDocs/Web/pt.json) already exists.
Any Docs project configured with a "pt" language (via its
docs-langs.json) triggers an infinite redirect loop between the
project page and /Abp/Languages/Switch, because the app never
recognizes "pt" as a valid culture and silently falls back to the
default one on every request.
- Add NavigationManager.ResolveBrandingUrl and ResolveBrandingCssUrl
- Move the url rules to Volo.Abp.Ui.Branding.BrandingUrlHelper, shared with the mvc themes
- Post the changed permission names from the MVC modal instead of the whole tree
- Replace the per-name list scans with dictionary lookups on the read path
- One namespace no longer spans two assemblies now that they live in the domain layer
- The Data Protection purpose keeps its old string, so outstanding 2FA codes stay valid
- Match the ASP.NET Core provider, which keeps the key id and key ring location out of the log
- Assert the provider the manager uses, not only the one the key's descriptor hands out
- The public ProviderType is the last type registered under a key, not the one the manager uses
- Add cross-host coverage for a second user type and for both hosts opting out
- Register them in AbpIdentityDomainModule so both ends of a distributed flow use the same provider
- Add AbpIdentityTokenProviderOptions.UseAbpTokenProviders to opt out on every host