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:
- Customer is created.
- Customer is assigned a subscription.
- 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
Currently we have Smtp Sender. We'll consider this topic and plan to make alternative implementations.
If you wish, you can implement your own email sending logic via implementing IEmailSender interface. After replacing that service with your own implementation, the entire application & modules will use your implementation.
Hi, Can you validate that compiled DLL files and your end application are using the same version of ABP?
You can check the default tenant resolvers or you can even write your custom resolvers. https://docs.abp.io/en/abp/latest/Multi-Tenancy#default-tenant-resolvers
Tenant can be passed from header, querystring, etc. with parameter name __tenant.
If you want to list all the tenants, you can use tenant-management module endpoints to achieve this.
