Activities of "enisn"

Hi again, I reached out to the ABP Suite team, and they clarified that ABP Suite generates code for a single UI—the main UI selected during project creation. However, if you create a module template, Suite can generate code for multiple UIs, but only within the module template.

So, the issue seems to stem from this design choice: ABP Suite is structured to generate code for the primary application UI, not additional UIs added manually later.

Hi,

We’ve successfully reproduced the problem and identified that it specifically affects Apple chipset Macs. Unfortunately, we haven’t found a solution just yet, our team is actively working on it.

Since this is a bug on our end, we’ll be refunding your ticket. We truly appreciate your patience and understanding as we work towards a fix.

If you have any further questions or concerns, please don’t hesitate to reach out. We're here to help!

Hi,

Thanks for reporting, It s working exctly what you described, we made an enhancement on TimeZones in ABP applications at v9.2.0 You can check this @maliming's article: https://abp.io/community/articles/developing-a-multitimezone-application-using-the-abp-framework-zk7fnrdq

This probably applies the logic what you need

Hi @yunusemrecaglar, Just to clarify—now that you've created a new Blazor Server project, has that resolved your issue, or do you still need assistance? Let us know how we can help.

Otherwise I can refund your ticket and close this issue since it was project generation problem on our side

Hi,

When you set SlidingExpiration as true, it won't be expired while user is currently using the system. It covers inactive duration. When user makes an action, countdown resets. If you set smaller durations, it won't be precise since it has tolerance. Most authentication servers, including identity providers like Keycloak, have a slight tolerance for token expiration. Typically, there is a grace period—often around five minutes—to account for slight variations in server time, network latency, and other technical factors. This ensures that users don't get abruptly logged out due to minor timing discrepancies.

There was a bug occurred when used documentation with FileSystem related to version. And also there is a merged PR about it: https://github.com/abpframework/abp/pull/22891

That might solve your case, too. You can apply changes of this PR in your application until this PR is shipped in the next release.

Similar issue: https://abp.io/support/questions/9278/Docs-Module-not-working-with-the-FileSystem-document-source#answer-3a19db6b-af40-1362-3269-1a3ec5ba8543

Hi,

We checked and couldn't find any problem currently. Can you share your scenario and environment with us to identify the problem better?

Hi,

IIdentityUserRepository implements IBasicRepository that does not have GetQueryableAsync() method on it.

If you need, you can use IRepository<IdentityUser,Guid> by injecting it.

It has GetQueryableAsync method that you can use:

public class MyService
{
    protected readonly IRepository<IdentityUser, Guid> _userRepository;
    public MyService(IRepository<IdentityUser, Guid> userRepository)
    {
        _userRepository = userRepository;
    }

    public async Task DoSomethingAsync()
    {
        var queryable = await _userRepository.GetQueryableAsync();
        // Do something with the users
    }
}

Hi,

Recently I dropped an article about the login page customization, you can check it for more detailed information: https://abp.io/community/articles/you-do-it-wrong-customizing-abp-login-page-correctly-bna7wzt5

As I understand you need to customize account layout.

• First, I suggest you to get source-code of the leptonx theme to a folder:

abp get-source Volo.Abp.LeptonXTheme

• Find /Themes/LeptonX/Layouts/Account/Default.cshtml file in the source code and copy it to the exact same folder structure in your AuthServer project.
  • It's located in Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX project in the source code.

And get one of the login page html structure from https://x.leptontheme.com/ website and apply it to that original file you copied to the project.

LeptonX theme MVC implementation doesn't have it built-in, you'll need to replace and implement it manually in that page

Hi,

• Which themes they're using currently?

• Do you need to customize the Login Page? or Account Layout?

I wrote an article for this recently: https://dev.to/enisn/you-do-it-wrong-customizing-abp-login-page-correctly-l2k

Here is the main takeaway from the article:

• What exactly do I want to change? Is it the overall look and feel (branding, colors, background) or the structure of the login form itself?
• Can this be achieved with CSS? Often, targeted CSS rules leveraging theme-specific layout classes are sufficient and the least intrusive method. This should be your first consideration for visual tweaks.
• Do I need to alter the content around the login form? If yes, overriding the Account Layout (e.g., Themes/Basic/Layouts/Account.cshtml or its LeptonX equivalent) is the correct approach. This gives you control over headers, footers, and surrounding content without touching the core login mechanism.
• Do I need to change the login form fields or its core submission logic? Only then should you consider overriding the Login Page component itself (e.g., Pages/Account/Login.cshtml) from the Account Module.

If you need to customize Login page, yes you could do for both applications in the same way. But if you need to customize Account layout, it won't be that easy, you'll need to override each theme manually. If you provide me more information about your both application's themes, I can share some sample code to customize it