Activities of "enisn"

MVC bundling system does not support dynamic imports. If you use a 3rd party library that needs those imports, you need to bundle them together and serve it

Hi @VivekKoppula

Let me know if it happens while running published blazor-server applications

Hi,

You can use .RequireAuthenticated() extension method for MenuItem:

var administration = context.Menu.GetAdministration();

var languagesMenu = administration.FindMenuItem(LanguageManagementMenuNames.GroupName);

var menuItem = new ApplicationMenuItem(
                    "MySubLanguageMenu", 
                    "My Sub Language Menu", 
                    "#")
               .RequireAuthenticated(); // <-- You add this method.

languagesMenu.AddItem(menuItem);

We have published a section on Saas Documentation about it.

https://docs.abp.io/en/commercial/latest/modules/saas#tenant-edition-subscription

***Consts.cs files are not API Controllers and they don't have any endpoints. Proxy generation generates code from swagger.json. So if you expose your consts with a Controller, proxy generation will be able to generate that endpoint.

Or you can add your custom menu under existing module menu:

var administration = context.Menu.GetAdministration();

var languagesMenu = administration.FindMenuItem(LanguageManagementMenuNames.GroupName);

languagesMenu.AddItem(new ApplicationMenuItem("MySubLanguageMenu", "My Sub Language Menu", "#"));

Hi, Do you ask creating your own section like below?

var administration = context.Menu.GetAdministration();

var mySection = new ApplicationMenuItem("MySection", "My Section", "#", "fa fa-file");

administration.AddItem(mySection);

mySection.AddItem(new ApplicationMenuItem("MySubMenu", "My Sub Menu 1", "#"));
mySection.AddItem(new ApplicationMenuItem("MySubMenu2", "My Sub Menu 2", "#"));
mySection.AddItem(new ApplicationMenuItem("MySubMenu3", "My Sub Menu 3", "#"));

var mySubMenu4 = new ApplicationMenuItem("MySubMenu4", "My Sub Menu 4", "#");

mySubMenu4.AddItem(new ApplicationMenuItem("MySubMenu4A", "My Sub Menu 4.A", "#"));
mySubMenu4.AddItem(new ApplicationMenuItem("MySubMenu4B", "My Sub Menu 4.B", "#"));

mySection.AddItem(mySubMenu4);

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