Activities of "enisn"

I have investigated this issue and it's correct. global.js is initialized twice because authentication check should be done before rendering layout. It checks authentication state and initializes global.js after authentication check.

It seems second one isn't downloaded from server, browser serves it from memory cache.

Do you use Blazor Wasm or Blazor Server?

We have fixed the issue that you mentioned lastly and it'll be released with next LeptonX release

Thank you. That information is very helpful. However, what I'm attempting to do here, and maybe this is my fault for not explaining correctly. My customer is wanting to have a custom CRM application that integrates with Stripe. The idea is that they would create a new customer from within the application, process payment if needed, and see regular updates on the status of each subscription. So, something like the following:

1. Customer is created.
2. Customer is assigned a subscription.
3. Administrator would like to see the status of this subscription (Active, Canceled, etc.).

If you want to use ABP Commercial Edition Subscription logic, customers have to be Tenants instead of custom entities. You should implement your own logic for your custom entities if it's not Tenant entity.

Hi @dev1_premierpoint

Can you try SelectedValueChanged property instead of onselect?

For more information you can visit Blazorise DropdownList documentation https://blazorise.com/docs/extensions/dropdownlist

Can you check this? https://support.abp.io/QA/Questions/3592/How-do-I-force-the-Blazor-toolbar-to-refresh#answer-2377648f-0b46-ed07-7678-3a05dc1c9234

It's a good demonstrate for managing toolbaritems according to other events in application.

You can define your own custom component instead of using .AddButton() method and that component can decide rendering itself or not according to a data.

I could reproduce this issue. Since it's a bug, your credit is refunded.

When you say older, what makes you think that? I grabbed that file when v6.0 came out and I downloaded the LeptonX theme files. This was not a RC version or anything that. It was the full released version.

LeptonX is a different project than ABP Framework. It has its own versioning. The stable version of LeptonX is released after ABP 6.0 stable version.

So the main difference that I saw here is usage of LanguagePlatformManager. After adding it to the code as I shared with you should solve the problem.

When you remove some sections, LeptonX JavaScript bundle can't find sections and can't be initialized. We aware the issue and working on it. This requirement will be removed in the next versions of LeptonX

Hi, can you share logs for 500 and 403 errors?

The root URL should have that parameter: {version}, so making it https://github.com/abpframework/abp/tree/{version}/docs/ should solve the problem