Starts in:
1 DAY
5 HRS
24 MIN
30 SEC
Starts in:
1 D
5 H
24 M
30 S

Activities of "Sturla"

Here we have some extra information in the logs.

Could some CMS file be missing that is causing this error? Note that we have our CMS located in the IdentiService and not the public website.

And btw we have this ExceptionSubscriber in the IdentiService that only catches this unhandled exception with no details at all.

    public class OurExceptionSubscriber : ExceptionSubscriber
    {
        private readonly ILogger<OurExceptionSubscriber > logger;
        public OurExceptionSubscriber (ILogger<OurExceptionSubscriber > logger)
        {
            this.logger = logger;
        }

        public async override Task HandleAsync(ExceptionNotificationContext context)
        {
            logger.LogException(context.Exception);
            logger.LogError(context.Exception.StackTrace);
            logger.LogError(context.Exception.Source);
            logger.LogException(context.Exception.InnerException);
        }
    }

And then this article just came out https://community.abp.io/posts/prerendering-blazor-wasm-application-with-abp-6.x-2v8590g3

Hi, after complaining about this slow loding for almosst 1 year in development we figured out what was wrong and it is just that abp doesnt use compressed dlls.

That means in my case that the app needs to load ove 100 MB each first time (then it caches small part).

It is hopefully fixed in 6.0. So please try it out. See https://github.com/abpframework/abp/issues/13771 (note that there is still some issue with “dead time” doing nothing and that will hopefully be looked at in version 7.0.

Here is my latest issur on the matter https://github.com/abpframework/abp/issues/13114 where I point to Steve Sanders WASM example that is just blazing fast. Note that his example applies “a combination of static pre-rendering and max trimming settings.” so you might want to try that out also since the abp fix doesnt contain any of that stuff.

I’m not sure but I really dont think abp.io has any real performace tests (regression or otherwise) or done extensive search for bottle necks, at least when it comes to login and loading Blazor WASM. Hopefully they will put some effort into it in version 7.0.

Hope this helps you out. Please let me know if it did because Im counting on version 6 to fix my issue.

Thank you. All is good now.

Ok that solved it for my users (I could hide the two-factor part at least) in the MVC part of my app.

I then figured out I had to do the same for Blazor and overrode ISettingComponentContributor

and added this code to hide it

//Hide the account menu item (Self registration/Two-factor/captcha/google-fb-etc
var accountMenuToRemove = context.Groups.Find(x => x.Id == "Volo.Abp.Account");
context.Groups.Remove(accountMenuToRemove);

Two questions then (and them I´m done I promise)

  • Can I override/fix this styling? Unfortunately can´t use it like this...
  • I guess I need to setup a elastic service in my Azure portal and point to it, right? Or can it be used "locally" without having to buy an extra service? I can´t find more information on this in any abp.io documents. I just have never used it before...

And I managed to get this up and running on my commercial code so I will be closing this. Small caveat was that I did try to have it on my IdentityService instance but that caused me some "resource not found" exceptions so I just moved it to the Public page.

Awesome thank you! It worked!

So maybe it was the "index" vs "Index" thing?

But now I´ll try to replicate this in my real project. If that works fine I´ll come back and close this question.

One thing for you, there is something wrong with the styling of the header up in the left corner.

Thank you so much. I really appreciate it!

Have you really tried doing this with my code (Github+insert records)?

Shouldn´t it show some documents on the document page if there are records in the database?

I don´t know what to do here... file new project + module installing + connecting to Github and getting data == not working

I know how to guard against null exceptions 😉 its just that Groups never contains Volo-Abp-Account-TwoFactor, that is that error..

BUT the thing is that I want to remove the whole Account tab and not just from within it!

If I filter it out by "AbpAccount.SettingManagement" and try to remove it with the PermissionDataSeeder the whole Settings menu gets removed.

I have (as stated above) tried using PermissionDataSeedContributor to remove access to the menu item like this (my code is longer and little different of course)

.Select(p => p.Name)
            .WhereIf(x=>tenantId.HasValue && providerKey == RoleConstants.Tenantuser,
                            x => !x.Contains("AbpAccount.SettingManagement")
            .ToArray();   

and then using PermissionGrantRepository.InsertAsync() to give the user permissions (but not that one) BUT then the WHOLE Settings menu goes away

Showing 81 to 90 of 174 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06