You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to create a custom setup recipe to install my own version of admin user and not use the default provided by Orchardcore.users Feature.
But this is not possible because the admin user Setup event handler is tied to the users feature.
I want to opt-out from the admin user setup when enabling the Users feature.
So i think we should place this in a separate feature . For the built in setup recipes just include this new feature to not break anything.
The text was updated successfully, but these errors were encountered:
Just remove it from the IoC in a feature that depends on OrchardCore.Users with something like this
var oldProvider = services.FirstOrDefault(x => x.ServiceType == typeof(ISetupEventHandler) && x.GetImplementationType() == typeof(SetupEventHandler));
if (oldProvider is not null)
{
services.Remove(oldProvider);
}
I don't think we need to create a new feature for this unless you have a better reason for this new feature that can't be achieved with the above approach.
I want to create a custom setup recipe to install my own version of admin user and not use the default provided by Orchardcore.users Feature.
But this is not possible because the admin user Setup event handler is tied to the users feature.
I want to opt-out from the admin user setup when enabling the Users feature.
So i think we should place this in a separate feature . For the built in setup recipes just include this new feature to not break anything.
The text was updated successfully, but these errors were encountered: