Hi,
The same applies to local
Hi,
I think it looks like a problem with MAUI: https://github.com/dotnet/maui/issues/9400, https://github.com/dotnet/runtime/issues/74292
Hi,
It looks like only restore packages from the hangfire-pro nuget source, did you add the nuget and abp commercial source?
BTW, could you share the full error logs? thanks.
Hi,
https://github.com/abpframework/abp/pull/9170#issuecomment-850250509
This is a known issue, creating RequestLocalizationOptions for each request is unacceptable, It can cause huge performance problems。
After you add a new language, you need to re-run the application.
If you really need it, you can change the lifecycle of the service:
context.Services.RemoveAll(x => x.ServiceType == typeof(IAbpRequestLocalizationOptionsProvider));
context.Services.AddScoped<IAbpRequestLocalizationOptionsProvider,DefaultAbpRequestLocalizationOptionsProvider>();
Hi,
I will check it.
Hi,
Sorry I forget the LayoutHooks is available for 2.0.0.
EmptyLayout.razor
@inherits LayoutComponentBase
@using Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.Common
@using Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.TopMenu
@using Volo.Abp.Ui.Branding
@using Volo.Abp.AspNetCore.Components.Web.Theming.Components
@inject IBrandingProvider BrandingProvider
<link rel="stylesheet" href="/_content/Volo.Abp.AspNetCore.Components.Web.LeptonXTheme/top-menu/css/bootstrap-light.css">
<link rel="stylesheet" href="/_content/Volo.Abp.AspNetCore.Components.Web.LeptonXTheme/top-menu/css/light.css">
<link rel="stylesheet" href="/_content/Volo.Abp.AspNetCore.Components.Web.LeptonXTheme/top-menu/css/layout-bundle.css">
<link rel="stylesheet" href="/_content/Volo.Abp.AspNetCore.Components.Web.LeptonXTheme/top-menu/css/abp-bundle.css">
<link rel="stylesheet" href="/_content/Volo.Abp.AspNetCore.Components.Web.LeptonXTheme/top-menu/css/blazor-bundle.css">
<div id="lpx-wrapper">
<div class="lpx-topbar-container">
<div class="lpx-topbar">
<div class="lpx-breadcrumb-wrapper d-flex">
<Breadcrumbs />
</div>
</div>
</div>
<div class="lpx-content-container" style="margin-left: 0; margin-right: 0">
<div class="lpx-content-wrapper">
<div class="lpx-content">
<ContentToolbar />
<PageAlert />
@Body
<DynamicLayoutComponent />
<UiMessageAlert />
<UiNotificationAlert />
</div>
</div>
<Footer />
</div>
</div>
Index.razor
@layout EmptyLayout
<Card>
<CardBody>
<h2>
Hello world
</h2>
</CardBody>
</Card>
Could you provide the JS for initLeptonX and afterLeptonXInitialization, or are those built in?
It's built-in, but you don't need it in the empty layout.
Hi,
The problem was fixed: https://github.com/abpframework/abp/pull/14022
You can upgrade your project to the latest version.
you can try this if you don't want to upgrade project:
[ExposeServices(typeof(ChatUserSynchronizer), typeof(MyChatUserSynchronizer))]
public class MyChatUserSynchronizer :
ChatUserSynchronizer
{
protected ICurrentTenant CurrentTenant { get; }
public MyChatUserSynchronizer(
IChatUserRepository userRepository,
IChatUserLookupService userLookupService,
ICurrentTenant currentTenant) : base(userRepository, userLookupService)
{
CurrentTenant = currentTenant;
}
public override async Task HandleEventAsync(EntityUpdatedEto<UserEto> eventData)
{
using(CurrentTenant.Change(eventData.Entity.TenantId))
{
var user = await UserRepository.FindAsync(eventData.Entity.Id);
if (user == null)
{
user = await UserLookupService.FindByIdAsync(eventData.Entity.Id);
if (user == null)
{
return;
}
}
if (user.Update(eventData.Entity))
{
await UserRepository.UpdateAsync(user);
}
}
}
}
another question that came up: why don't you update v6 with all these fixes
This is an enhancement of leptonX, not a bug, If it is a bug, we will release a patch version like (6.0.x).
You can consider use abp new myproject -v 7.0.1 command to create a specific version of the project