I’m working on a module that does member registration and authentication from a third party service.. single sign-on.
Since there’s no way to feed into the existing methods directly and my module replicates the registration and authentication processes, that means that a lot of my code is essentially borrowed from the EE core. And I don’t really see a way around it. The built-in methods are designed to work directly with POST data submitted by the user.
So, I’m just curious what EllisLab’s take on this is. Obviously we’re not allowed to copy and resell existing EE code, but how does one get around that here, when I need to follow the same series of steps to register or authenticate a member?
Any experience from other commercial add-on developers would be great too.
I’d say just email EllisLab the module in question, outlining what has been ‘borrowed’ and they should get back to you with a yes or no.
I’ve been in the same boat with a module I wrote some time ago, unfortunately the response I got meant I couldn’t post/host the code publicly. EL were very helpful/responsive with my questions though and their (fair) responses didn’t leave a bitter taste in my mouth 😊
Thanks Iain!
Jeremy, as Iain, said, the best way to go about this is to email sales and attach the add-on. We can get it to the dev team for review and figure things out from there.
Thank you!
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.