Activities of "cala"

if you realy want to improve your support than you need to define rules / standards for supports communication - as many people already mentioned, currently it is more time consuming to ask your support instead of doing it yourself ( and that does not include that in most cases you will not get a useful answer ).

one of the best support we know is syncfusion. they have strict communication rules that works pretty well. these rules are something like this ( for first and last anwser ):

• summary of the problem that you have understood
• statement if you can reproduce the problem or not
• sample project ( provided by you - not the request sender )
• for more complex request, sample video of the process
• time frame when the fix will be available or time frame when the final time frame will be available or time frame when the problem will be looked into
• link to issue tracker ( mostly private, can be made public on request )

than both side can use the sample project to concretize the problem. and all other people that have the same problem can use this to validate their approach and see the solution.

Hi,

would it be possible to move all obfuscated into one namespace to prevent poluting the global namespace ? Then we could ignore this namespace and prevent all random namespaces from appearing in the suggestion. ( like Obfuscated.aWb89AudWxndIojxMrf )

example: ( LeptonX )

aw ( await ), suggested: aWb89AudWxndIojxMrf fl ( float ), suggest: fLnKEy7smBogPhbwDFa st ( string ), suggest: sbTwL4GtJRCmTQuNiMd

even if the suggesting are not on top, it still polute the suggestion list

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'.