Activities of "enisn"

Hi @hansmogren

ABP v.4.4 is based on .NET 5.0,

So, if you want to use .Net 6.0, you should upgrade to ABP v5.0.

You can follow migration guide: https://docs.abp.io/en/abp/5.0/Migration-Guides/Abp-5_0

Hi @ChetanKumbhar

ABP Framework and ABP Commercial don't have such a table AppLitmusSetting.

As I can understand that is your application's table. So, if it's an AggregateRoot, you can use IRepository<LitmusSetting, Guid> do make operaitons on that table.

If it's not an AggregateRoot, you should add repositories with includeAllEntities as true

context.Services.AddAbpDbContext<FooDbContext>(options =>
{
    options.AddDefaultRepositories(includeAllEntities: true);
});

Then you can use IRepository<LitmusSetting, Guid> to perform database operations on that table.

Read more about repositories: https://docs.abp.io/en/abp/latest/Best-Practices/Repositories Read more about Entities & AggregateRoots: https://docs.abp.io/en/abp/latest/Entities

Hi @vinit

You can include source code of Lepton in your project via following steps below: https://support.abp.io/QA/Questions/632/How-can-I-download-the-source-code-of-the-framework-Angular-packages-theme-and-pro-modules

Then you can make changes however you want in scss files.

Lepton has 2 dark themes already. You can choose to use them. Even it can be changed in Theme Management UI on runtime.

Choosing custom colors and layouts depends on you. Create a choosing logic according to your requirements and you can call different layouts or styles in Layout, Layout is included in source code of lepton

Also we're currently working a new theme, named as LeptonX. All those problems are addressed in the LeptonX and it offers rich customization options. Currently it's not available on Blazor, but we're close to releasing a beta version. https://volosoft.com/blog/introducing-the-lepton-theme-next-generation

Seems there is no error in your log file. Do you use separated IdentityServer ? If yes, please share IdentityServer logs too

Did you paste file from your clipboard?

Physical files always have a name. Can you try with a physical file?

Also you can generate token in serverside instead of sending a authenticated request:

public class MyService : ApplicationService
{
    private IFileDescriptorAppService fileDescriptorAppService;

    public MyService(IFileDescriptorAppService fileDescriptorAppService)
    {
        this.fileDescriptorAppService = fileDescriptorAppService;
    }

    public async Task MyMethodAsync()
    {
        var token = await fileDescriptorAppService.GetDownloadTokenAsync(Guid.Parse("..."));
    }
}

In file management you'll see 2 endpoints to perform a download operation:

One of them creates & returns token but requires authenticated request. After, getting that token, you can download the file from second endpoint with that token without authentication. But token's life is 60secons by default.

For example; let say your media id is 1 to make it more understandable.

Firstly you need to create a download token for media with a authenticated request:

GET | /api/file-management/file-descriptor/download/1/token

You'll get a response something like below. Let say the token is a to make it simple:

{
  "token": "a"
}

Now, you can make a request from anywhere without authentication with that token.

GET | /api/file-management/file-descriptor/download/1?token=a

I don't suggest to replace entire entity because of maintainability issues. Upgrading newer versions of ABP & LanguageManagement will be tough. Also when you create a new entity, you'll lost Replace DbContext Feature, ILanguageManagementDbContextwon't be able to be replaced and you can't join any of data from ILanguageManagementDbContext. Also you might get a problem on AppService and mappings.

In that case, I suggest you to create a new entity with one to one relation with LanguageText entity and store extra datas in that table. You can even join with two table via using Replace DbContext Feature. Then provide new data over a new endpoint with new dto.

Hi @Radoslav

You're right, we can't support custom source while adding module right now.

We're working some amazing feature that solves that problem but it'll take a little bit more time and won't be shipped with v5.0

Can you share more information about error?

Please find & share your application logs. It default is placed under Logs folder under your application.