Activities of "balessi75"

I needed to pass the root namespace name to options.FileSets.AddEmbedded...

options.FileSets.AddEmbedded<TimepieceApplicationContractsModule>("FM.Timepiece")

Great, thank you @gterdem

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.

Excellent, thanks for the support @EngincanV

Hi @balessi75, it seems there is not any check on UI for Create and Edit forms. I've created an issue for this. Thanks for reporting.

Thanks @EngincanV!

While working on this, would you also be able to add the following two properties as a new feature? We actually have a business need for them...

property.UI.OnCreateForm.IsReadOnly; property.UI.OnEditForm.IsReadOnly;

Ok, thanks for confirming.

I was using the wrong localization key.

Instead of: "Feature:TwoFactor": "Two Factor"

I needed: "DisplayName:Abp.Identity.TwoFactorBehaviour": "Two Factor"

Ok, that makes sense for two factor, but what we are actually testing here is the 'Require Verified Phone' option, which requires a verified Phone to sign in. Once verified, the user can sign in - this applies even if two factor is turned off.

When this setting is turned on, Abp allows the user to verify their phone during the sign in process. So what we are finding is that during the verification process, they get one chance to enter their phone, from there, if they entered the wrong phone, it's saved to the database and can never be updated again. Therefore, the user can never login.

I've updated the issue title to more accurately reflect the issue.

hi

https://community.abp.io/posts/how-to-override-localization-strings-of-depending-modules-ba1oy03l https://github.com/abpframework/abp-samples/tree/master/DocumentationSamples/ExtendLocalizationResource

Hi @maliming,

We've followed the community article and still can't seem to find were we are going wrong.

For the Feature:TwoFactor localization, should we be adding the virtualized json file from the Domain.Shared project's ConfigureServices method? Also, is it correct to be using the IdentityResource when adding the localized json file?

Application project reference to the DbMigrator project and I am still getting the same exception

Did you add the module dependency?

[DependsOn( 
    ..... 
    typeof(...ApplicationModule) 
    )] 
public class ...DbMigratorModule : AbpModule 

That was it! Thanks for the support @liangshiwei

Hi,

Setting definitions in the ..Account.Application project. you can add the Application project reference to the DbMigrator project.

Hi Liangshiwei,

I added our ...Application project reference to the DbMigrator project and I am still getting the same exception. The DataSeedContributer is in the Domain project. It needs to be there, correct? I tried adding a DataSeedContributer to the Application project, but DbMigrator does not discover the DataSeedContributer at runtime from that location.