I am committed to Silverstripe 3 at a new development house and have, after some initial issues (install Widgets first!), am enjoying the CMS/framework.
At present there seems to be a real patchy coverage of modules however. In particular there is no module to support user registration which is what I need to look at with some urgency.
So what I was wondering is whether I could use the Forums module code (that offers registration etc. from the documentation) and use that to register users. My idea is that I could simply hide the forum itself from my site menu but use the backend administation tools to manage the userbase.
Is that a really bad idea or would that be a quick way to get a fully featured user registration 'module' working?
I have just checked the head of GitHub against 3.0.3 - the functionality doesn't build. I get a deprecation error:
[User Deprecated] DataObjectDecorator is deprecated. DataObjectDecorator is deprecated. Use DataExtension instead
Looking at GitHub there is very little activity with a pull-request outstanding. It certainly doesn't appear that the module has been updated to work with SilverStripe 3.0
I'm not sure you have the power but is there some way of SilverStripe contacting AJShort about this module? The thing is that registering users is pretty fundamental stuff and would be great to do in a standard way. What is the standard way in 3.0 is the question I guess?
If you check out the development branch from the repository, that's where the SS3 compatible version lives. It hasn't yet been fully upgraded, but I think most of the basics work. If you run into any issues it would be good if you could open an issue.
I will eventually finish upgrading the module, but unfortunately at the moment I haven't had the time.
I have installed the module and can register / update / login etc. a new user so that is great. I will be working with the module over the coming month so will certainly log anything I find.
If you feel the module is at the stage it can be tested (if not deployed live) it might be worth updating the master readme file to highlight where the 3.0 branch lives. I didn't think of checking for a branch which is silly of me but others might miss it too.