Activities of "mrall"

Hello,

I'm using the ABP Suite to create CRUD-Entities for my project - all fine. Now I added a module to my solute - still fine. I open the module's solution in ABP suite with "add an existing solution" - fine. I create an entity and hit "save and generate" - this creates the entity inside the solution, but no additional artifacts for ui and db-migration.

How can I use ABP Suite to create CRUD-Entities the same way as for my "base"-solution?

cheers

hi

What's version of your ABP(cli and suite)?

both v4.4.0

ok, I found that the UI is generated, I missed the point that my User had no Access-Rights, so the menu was not shown

ok, I guess the main reason was that within my module the name of the connection-string setting pointed to a settings that doesn't exist (I didn't create it). I changed it to "Default" to use the same DB as my application and the Migrations were created.

it seems that I need to create the migrations for new module-entities manually with "add-migration..." - is that right ?

• ABP Framework version: v4.4.0
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: see image
• Steps to reproduce the issue:
• • Create new App with ABP Suite
• • Add custom module to ABD Suite
• • Add Entity via CRUD-Generator
• • look at CRUD's "index.js"

after changing the problem reported in #1666 it works...

• ABP Framework version: v4.4.0
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hello, I created a quite simple ABP.IO Projekt from the commercial template. I have a custom signup-page that inherits from "RegisterModel", in that page I call "var user = await RegisterLocalUserAsync();" to create the ABP-User.

That works fine in Development but in Production I get serveral Permission Errors:

2021-09-07 11:19:58.447 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2021-09-07 11:19:58.470 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2021-09-07 11:19:58.472 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: LeptonThemeManagement.Settings 2021-09-07 11:19:58.480 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement 2021-09-07 11:19:58.541 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2021-09-07 11:19:58.542 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2021-09-07 11:19:58.543 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: LeptonThemeManagement.Settings 2021-09-07 11:19:58.543 +00:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement

It's clear that the new (still anonymous) user has no permissions...

Now my questions:

• Why do I get this Errors only in Production ?
• How can I impersonate to the admin-user to signup the new user so I don't have to make all the above things public?
• Or what is the recommended way to execute protected logic for a user that doesn't have the correct permissions ?

cheers

Well, just create a new empty Application with abp suite (MVC, EF Core, not tiered), setup correct email settings, run in release mode and try to register -> results in permission denied-errors (and btw, the frontend stays in loading instead of displaying the error message).

The user is created in the Database, but no confirmation-mail is sent and automatic login is not working.

When trying to login with the new user the login/verify-email page is shown (which is correct), but clicking on "verify" again has no effect.

2021-09-08 09:36:06.036 +02:00 [INF] Executing endpoint 'Volo.Abp.Account.AccountController.SendEmailConfirmationTokenAsync (Volo.Abp.Account.Pro.Public.HttpApi)' 2021-09-08 09:36:06.039 +02:00 [INF] Route matched with {area = "account", action = "SendEmailConfirmationToken", controller = "Account", page = ""}. Executing controller action with signature System.Threading.Tasks.Task SendEmailConfirmationTokenAsync(Volo.Abp.Account.SendEmailConfirmationTokenDto) on controller Volo.Abp.Account.AccountController (Volo.Abp.Account.Pro.Public.HttpApi).

nothing happens after this line ....

after changing to MailKit (https://docs.abp.io/en/abp/latest/MailKit) as you suggested everything works fine - maybe you should check your default EMailSender.