As per @Maliming comment in https://github.com/abpframework/abp/issues/1082 can we get more details about what is being done to enhance editions, subscriptions & payments that will be included in v4.4 preview for commercial.
Also I dont see that 1082 (& 2611?) have been assigned to v4.4 preview?
We are using Blazor WASM and it is much slower to load (many 10's of seconds)... Once the application is running it is OK.
This is our first SPA as we are migrating products from Aspnetzero Core/MVC... Apart from getting it up to the same level of functionality, we hope the framework loading gets faster.
Cheers @Maliming ! - Now can you fix the login/impersonate a tenant user from the host side too like in ASPNetZero.. :)
Hi @maliming, yes, but we'd like a demo for multi-tenant that shows how to login to tenant without having to create subdomains, and where the username is unique, as per question in 917.
It would be good if we could have an explanation/demo for that. :)
Andrew
@maliming - Is it possible to include the way to do unique user logins for multi-tenant in the demo you are building for this issue using sub domains?;
https://support.abp.io/QA/Questions/917/Tenant-Login-Without-Selecting-Tenant-and-without-a-Hostname-specific-for-the-URL
@maliming - I see this is closed, but still not answered? Can you help?
Thanks, It would be great if we can have that as part of v4.3?
It's obviously a major issue for a SaaS product allowing customers to self sign up..
@Alper - Thanks for the response.
Login - It would be good if there was an option to just turn off the intermediate landing page and go straight to the login page rather than having to inject a redirect and the delay in that process.
Notification - The notification is just the trigger/alert part. The aspnetzero version has a whole infrastructure including bell icon/badge, form and acknowledgement process, etc. So it would be very helpful if that whole system was in ABP.io.
Maybe someone else has built it and can share?
@Alper - Thanks for the response, but isnt that setting for User (of a tennat) self registration, not actual Tenant self registration?
Why would it be a tenant level setting when they are already registered?
We are re-writing an aspnetzero based multi-tenant SaaS product.
It looks like only a user of an existing tenant can self register?
So you can't have new customers register/signup by themselves?
Are we missing something?
