Hi, as I know there is not any way to do that unless overriding the related page and applying the logic.
Or is there a way to manually create the input without using the <ExtensionProperties> component?
We use this component in modules to show extended properties on UI and it basically creates HTML tags for the extended properties by their type.
You can check the ExtensionProperties
component component and create a new component for you to show extended properties on UI by your needs.
BTW, I've created an issue (#12249) for your suggestion and we'll consider it.
It's good to hear that. I close the question since your problem is resolved.
Best regards.
Did you also change the _configuration.GetConnectionString("Default") to _configuration.GetConnectionString("<user-secret-key>")
?
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
if (!optionsBuilder.IsConfigured)
optionsBuilder.UseSqlServer(_configuration.GetConnectionString("<user-secret-key>"));
}
If you want to customize CSS, please see Customize Lepton Theme with Custom CSS.
For the overriding logo, please see ASP.NET Core MVC / Razor Pages: Branding.
To customize entity action extensions, see https://docs.abp.io/en/abp/latest/UI/AspNetCore/Entity-Action-Extensions
For toolbar extensions, see https://docs.abp.io/en/abp/latest/UI/AspNetCore/Page-Toolbar-Extensions
Also, there are some community articles to show how you can replace the current template with a new one. There might be helpful for you.
Hi, I guess you are storing your connection string as a user secret. Can you replace the Default keyword with your user secret key on your ConnectionStringName attribute?
It's defined top of your DbContext class:
[ConnectionStringName("<user-secret-key>")]
public class MyProjectNameDbContext {}
Hi, can you check your production environment settings are correct or not?
You can open the Environment.js and check the prod section. Please, ensure your apiUrl and issuer is correct and point to the backend server on production.
Hi @LinchArnold, we've created an internal issue (#9763) for this problem and will fix it asap. Therefore, I close the question.
Best regards.
Hi @adrianl, this was a known problem and fixed in the v5.2 version. You can upgrade your project to v5.2 and try it.
There is only one restriction for now, after renaming the role you need to re-login.
We've also created an issue (#8620) for this restriction and aim to fix it in v6.0.
Hi @Mikael, I close the question since we've created an internal issue for this problem and will take the necessary action for it. Thanks for reporting the problem.
Best regards.