Activities of "cala"

thanks

another question that came up: why don't you update v6 with all these fixes ?

abp v6 is not even half a year old and it looks like you have already stopped supporting it. We could not find any information about how long you will support each version.

we are using net 6 and abp v6 - leptopX v2 require abp v7 and net 7 so we cant update yet.

can you provide some information for including these in the abp v6 ? thanks

Hi

( follow up to missing footer )

we notice that in LeptonX the PageHeader is not always visible. sometimes it works after you trigger a manual render but not reliable so this workaround works for some pages but not all

protected override async Task OnAfterRenderAsync( bool firstRender )
{
	await base.OnAfterRenderAsync( firstRender );

	if( firstRender )
	{
		await InvokeAsync( StateHasChanged );
	}
}

it feels like something overrides the PageHeader as you can step through the initial rendering problem without problem ( and all parameter are correct ) but the result is not visible. test code:

<PageHeader BreadcrumbItems="@( new List<BreadcrumbItem> { new( "test" )  } )" />

<div>
	<div class="row entry-row">
		<div class="col-auto">
			<h1 class="content-header-title">Welcome!</h1>
		</div>
	</div>
</div>

result with and without workaround

but it works on some pages ( like the autogenerated dashboard ) after applying workaround:

• ABP Framework version: v6.0.2 ( leptonX 1.0.4 )
• UI type: Blazor (Server)
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no

Hi, we notice that the general settings menu is only localized in turkish. all other lanagues show the default english version.

• ABP Framework version: v6.0.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no

so you do check the license even in production - you stated you dont do this a couple of times. so this is a bug isnt it ?

no - its production

added Log.Information( "start as " + builder.Environment.EnvironmentName );

here is the log

can you provide some advice what went wrong if the published release version still require the appsettings.secrets.json ? double checked our publishing routine but everything looks good.

the application does NOT start if you delete appsettings.secrets.json

2023-02-16 09:33:12.136 +01:00 [ERR] ABP-LIC-0020 - License code not found! Ensure that your appsettings.json or appsettings.secrets.json has "AbpLicenseCode" key with your license code. 2023-02-16 09:33:12.136 +01:00 [ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.Identity.Pro.Domain-v6.0.2.0'.

Hi, we notice that the appsettings.secrets.json gets publish too - and deleting it cause a "ABP-LIC-0020". How to we prevent this sensitive information from deploying to our clients ? ( microsoft states that you should not use any secrets file outside the development process )

Beside, is there any documentation about how to publish abp correctly ? well the process is pretty much straight forward but the secret should not be contained in output. some advice about how to publish the migration project within the blazor project ( to prevent duplication of dll's ) and run it automaticly on blazor start would be great :)

Thanks

• ABP Framework version: v6.0.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no

it works with server.LeptonXTheme and Theme.LeptonX 1.0.4