Activities of "enisn"

Hi @ElifKaya,

Some of entities can not be created without a domain logic, DDD aims to keep domain integrity. So, you have to create them with their own Manager. For example, you can create a Page with the PageManager. See example below:

    public class MyDataSeedContributor : IDataSeedContributor, ITransientDependency
    {
        private readonly PageManager _pageManager;
        private readonly IPageRepository _pageRepository;

        public MyDataSeedContributor(PageManager pageManager, IPageRepository pageRepository)
        {
            _pageManager = pageManager;
            _pageRepository = pageRepository;
        }

        public async Task SeedAsync(DataSeedContext context)
        {
            var page = await _pageManager.CreateAsync("Hello World", "hello-world", "Some long content");

            await _pageRepository.InsertAsync(page);
        }
    }

Inject Manager class of entity with inaccessible constructor and create them with Manager.

Hi @ElifKaya

Multilingual Entities is the one of hardest topic we have to decide. We haven't find the best way to do in ABP Framework. We have tried in a couple of ways in earlier versions but never done properly. You can see earlier discussions and development attempts below:

• https://github.com/abpframework/abp/issues/1754
• https://github.com/abpframework/abp/pull/5265

The Multilingual Entities feature is still in our backlog and we're discussing about it. But issues above might help you.

Are you working on your local or did you deployed them into a server and you're accessing them via IP or a domain?

Please check AllowedRedirectUris parameter is 'http://localhost/signin-oidc' or 'http://yourdomain.com/signin-oidc'.

If you're sure about IdentityServer Client configuration, the problem might be protocol issue. Incoming requests are always http if pods are communicating behind load balancer.

Try to add following line into OnApplicationInitialization method in your each Service Module class.

app.Use((context, next) =>
{
    context.Request.Scheme = "https";
    return next();
});

See more about running behind load balancer

You can see abp & abp commercial roadmaps below:

• https://docs.abp.io/en/abp/4.4/Road-Map
• https://docs.abp.io/en/commercial/latest/road-map

It seem next version (v5.0) won't include new input types of Form Module. It's on our backlog now and unfortunetely I can't say an exact date about when it be done.

Also your credit is refunded.

Hi @viswajwalith

If you really need in a hurry, you can customize the Forms module on your own until we support date & time types officially.

Following documentations might help:

• https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Guide
• https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Overriding-User-Interface
• https://docs.abp.io/en/abp/latest/Customizing-Application-Modules-Overriding-Services

Hi @drg_tverkroos,

I've contacted with design team and they confirmed it's a bug not a feature. So it'll be fixed at new preview of v5.0 release.

• Do you have [Dependency(ReplaceServices = true)] over you BrandingProvider class?
• Did you override any component including Main Layout?

Hi @drg_tverkroos, Lepton Theme Style 6 doesn't have a hover effect. If you want a hover effect, try to use another Style of lepton theme.

Style 3 and Style 4 supports hover effect:

Yeah you're right, table-hover comes from bootstrap and lepton theme doesn't have that class. I'm working on it

Hi @drg_tverkroost

I've tested as you say and it worked for me. Can you please share much more information?

Are you sure you've overrided in *.Blazor project?