Activities of "alper"

this is not directly related to ABP. this is a subject of Identity Server. If you add your clients to the Identity Server front channels then account module will navigate to those logout endpoints to force them log out.

This is in the IdentityServerClients table and field is FrontChannelLogoutUri.


closing the issue since the main question is answered or timed out.

in your case the best practise is making the datatable row partial view and after adding a new row, rendering the partial view from host. but you didn't choose this way, and if you keep on your way, I can suggest you the alternative implementation:

  • add a custom attribute to your Version component . eg: <select id='version' data-rendered='0'></select>
  • add a custom attribute to your HowToAchieve component . eg: <select id='HowToAchieve' data-rendered='0'></select>
  • after datatable add row completes, run a JavaScript code to find all data-rendered=0 elements and make an ajax request to populate these components.

as your main question is answered I'm closing the question. thank you

In the active license period, all developer seats are being validated via license server. after the license expires you can continue your development with the specified developer seat limits.

You cannot integrate commercial into an open-source project. By doing this you allow ABP Commercial to be publicy available which violates the license rules. If you want to make an open-source project you can make it with the ABP open source (community) edition.

this is how you can get and set an extra property

//SET AN EXTRA PROPERTY
var user = await _identityUserRepository.GetAsync(userId);
user.SetProperty("Title", "My custom title value!");
await _identityUserRepository.UpdateAsync(user);

//GET AN EXTRA PROPERTY
var user = await _identityUserRepository.GetAsync(userId);
return user.GetProperty<string>("Title");

see https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Extending-Entities

sorry but we cannot reach you

Your message did not reach some or all of the intended recipients.

      Subject:	Angular Lepton Theme 
      Sent:	12.02.2021 18:18

The following recipient(s) cannot be reached:

      '張銀展' on 12.02.2021 18:18
            552 5.7.0 message content and attachment content guidelines. a15sm5844736edy.86 - gsmtp

      ABP Info on 12.02.2021 18:18
            552 5.7.0 message content and attachment content guidelines. a15sm5844736edy.86 - gsmtp

I haven't used tye therefore I can't predict anything. but for the ABP part, I also couldn't see an ABP code in the ex stack.

Answer

Hello

All automatic generated classes and repositories seem invalid. A piece of the summary seems to be included every time it should just need 'DynamicFieldEntityType type'

  • DynamicFieldGroupDto
  • DynamicFieldGroupCreateDto
  • DynamicFieldGroupUpdateDto
  • GetDynamicFieldGroupInput
  • DynamicFieldGroup
  • EfCoreDynamicFieldGroupRepository
  • IDynamicFieldGroupRepository

can you share us your entity.json and enum class. it's in your solution root directory .\suite\entities folder.

for the Angular side we have tried to reach you via email but your mail returns error with The following recipient(s) cannot be reached: yin****@gmail.com

Showing 1121 to 1130 of 1975 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 19, 2024, 12:56