Activities of "russel.krause@painworth.com"

  • ABP Framework version: v5.3.2 commercial
  • UI type: Blazor Server
  • DB provider: EF Core

Hello,

We have noticed an intermittent issue with EmailSenderBase.QueueAsync() where emails are not always being sent (about 50% of the emails "queued" are never received by their recipients).

We have noticed that for the emails sent to QueueAsync(), some of the emails are immediately sent via our custom SendEmailAsync(MailMessage mail) override, whereas the others neither reach this method, nor are ever received by the recipient.

Simultaneously in our logs, we have noticed some SMTP errors indicating:

  • Message Failure sending mail. Connection refused
  • Exception type System.Net.Sockets.SocketException
  • Failed method Volo.Abp.Emailing.Smtp.SmtpEmailSender+<SendEmailAsync>d__5.MoveNext

If we use SendAsync(), the emails are delivered 100% of the time.

We wonder if we have missing configuration that is causing the emails to be queued to be missent to perhaps the wrong endpoint. Can you point us to any documentation that might help us confirm if our queuing system is misconfigured?

Thanks. Russel

  • ABP Framework version: v5.3.2
  • UI type: Blazor
  • DB provider: EF Core
  • **Tiered

Hello,

We are interested in enhancing the menu system of the Lepton theme to present/hide options in the menu based on functional (context-sensitive) logic based on more than simply role membership.

We have found MainSiderbar.razor component in the ABP Commercial Source where the following code is executed:

< nav role="navigation" class="lp-sidebar-navi" >
   < ul>
      @if (Menu != null)
       {
           @foreach (var menuItem in Menu.Items)
           {
               < MainSiderbarMenuItem Menu="@Menu" MenuItem="@menuItem"/>
           }
       }
   < /ul>
< /nav>

It is this code that we would like to over-ride. What we are hoping is that there is a mechanism to override the default behaviour of this file by replacing it with our own component, much like how we have done so to replace the MainFooterComponent by configuring the following in our Module:

Configure<Volo.Abp.AspNetCore.Components.Web.LeptonTheme.LeptonThemeOptions>(options =>
        {
            options.FooterComponent = typeof(MainFooterComponent);
        });

Our questions are these:

  • Are there any plans by ABP to extend the LeptonThemeOptions that can be made configurable to include the MainSiderbar.razor component?
  • If there are no immediate plans to extend this as an over-ridable option, what is the best approach to enhance this behaviour?

In reviewing the documentation, a "Copy & Customize" approach is suggested where, we would download and customize the Lepton Theme code. Since the Lepton theme is a very large module containing over 6-8 projects, we are disinclined to do so as that would fork our code base from the supported theme.

What would be our best approach / what are our other options to enhance the menu system?

Thank-you

Russel Krause Director of Development PainWorth.com

Showing 1 to 2 of 2 entries
Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11