Lindor Posted May 30, 2023 Posted May 30, 2023 (edited) Hi team, I've activated to "always" the Require Subscription Purchase field and the users id=2338 or id=2334 was created without subscription purchase. This users was registered by Google Method (probably the same for other social methods). The users haven't access permisions to restricted content because no change the primary group assingment. But, this situation generates a zap and creates, wrongly, a new client registered and it add to the clients automatizations in my CRM, so it's a kaos. I think that can be an issue, because this users not shoub be created in IPS, with mail register method runs perfectly, not register without subcription purchase. Can you take a look and solve in upcoming updates? Thanks a lot. Edited May 30, 2023 by Lindor
Marc Posted May 30, 2023 Posted May 30, 2023 This is actually correct behaviour. You cannot require a subscription on an external login method unfortunately. This applies only to the internal login method. The reason for this is that in many cases its simply not allowed by the login provider.
Stuart Silvester Posted May 30, 2023 Posted May 30, 2023 It's also worth pointing out that (depending on your settings) the member will be asked to select a subscription in order to use your Community, but the account being able to exist before that point is not a bug (it would be the same scenario if the account was created via API etc) Marc 1
Lindor Posted May 30, 2023 Author Posted May 30, 2023 Thanks @Marc Stridgen and @Stuart Silvester for your answer, I understand. How can we "protect" the zapier trigger to not add this users in the CRM automatizations?
Marc Posted May 30, 2023 Posted May 30, 2023 Thats not a question easily answered, without knowing exactly what you have set up. The simplest solution however, would be to use only internal logins Lindor 1
Recommended Posts