Activities of "Emanuele.Filardo"

I have the same issue, with all combination of CLI & nuget 4.4.4 / 5.0.0-beta3 on Blazor Server with EfCore. 1st run all is ok 2nd run error and log truncated: Unhandled exception in circuit '1p-8ASDVzLQleQfw2SNY1-9IQo226k0XJ5M-bbKlSC4'. Volo.Abp.AbpException: Undefined permission: AuditL

Undefined permission can be different on each run, and this appen only if there is an instance of browser left open

Hi, in v5 based on .net 6 I think that new types Date and Time should be added

I already updated to 4.4.2 and I have not customized any templates before.
In order to double check if this issue has been fixed or not, I ran
dotnet tool update -g Volo.Abp.Cli and
abp suite update again.

After doing that, I checked Server.AppService.AppService.txt in the Edit Templates page, the AppService name was still plural. You can see that in the picture below.

I've tried to unistall cli abp and now issue still there in 4.4.2

Probably I have tested changes before reset template or customized was restored by wrong git.

I have seen users reported this issue in the Bugs & Issues v4.3.X post. Until v4.4.2 this issue still exists.

ABP team please at least answer the question that other users also asked: "Is this a new approach for naming convention? Or is this a bug in the templates?"

Try to update abp cli, it was solved since 4.4.1. https://blog.abp.io/abp/ABP.IO-Platform-4.4-Final-Has-Been-Released!

If you have customized templates, you should remove those.

ABP Framework version: v4.4.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: no Steps to reproduce the issue: create solution with ABP Suite, Linked Account work only in "my profile" page

Expected: Linked Account modal work in all pages like demo

Still present in 4.4.2

• ABP Framework version: v4.4.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: no
• Steps to reproduce the issue:" AbpSuite "+Add Property" no "Guid" type available for reference AggregateRoot as you suggest in ebook at page 35 "Aggregate / Aggregate Root Rules & Best Practices"

ABP Framework version: v4.4.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: no Steps to reproduce the issue: ABP Suite create entity/aggregateroot with required navitagion properties, in generated class is missing NotNull attribute in property, it isn't added as constructor parameter and then not included in tests data seed

ABP Framework version: v4.4.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: no Steps to reproduce the issue: ABP Suite create user interface entity/aggregateroot, missing ValidateAll() invocation. https://github.com/abpframework/abp/pull/7598/files

Workaround: Edit Template Frontend.Blazor.Page.Item.razor_cs.txt

private async Task Create%%entity-name%%Async()
        {
            if(New%%entity-name%%Validations.ValidateAll())
            {
                await %%entity-name-plural%%AppService.CreateAsync(New%%entity-name%%);
                await Get%%entity-name-plural%%Async();
                Create%%entity-name%%Modal.Hide();
            }
        }

private async Task Update%%entity-name%%Async()
        {
            if(Editing%%entity-name%%Validations.ValidateAll())
            {
                await %%entity-name-plural%%AppService.UpdateAsync(Editing%%entity-name%%Id, Editing%%entity-name%%);
                await Get%%entity-name-plural%%Async();
                Edit%%entity-name%%Modal.Hide();
            }
        }

This is requided because SubmitButton -> PreventDefaultOnSubmit="true" doesn't work as expected

ABP Framework version: v4.4.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: no Steps to reproduce the issue: create solution with ABP Suite, Blazorise obsolete Direction message

Workaround: Edit templates -> Frontend.Blazor.Page.Item.razor_cs.txt replace Direction with SortDirection

ABP Framework version: v4.4.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no Exception message and stack trace: no Steps to reproduce the issue: create solution with ABP Suite, Linked Account work only in "my profile" page

Expected: Linked Account modal work in all pages like demo