I was thinking it might be nice if the MODx system could redirect it’s user information and authentication database fields to another CMS or pre-existing database. I’m imagining something like a page in the manager where we could check a "redirect user authentication data fields" with places to set the url to the new database, the login ID, the password, the database type, etc. Then we could have a check boxes on a list of all the available user fields in MODx and and empty text field to tell MODx which table to use in the new database.
It might make MODx much easier to integrate with private systems such as the www.deverus.com system for background checks, or perhaps Google Apps, or possibly private internal systems where a company wants a web access to certain office data. Could even be used to possibly make a better integration with the SMF system than the plugin sync allows.
Could this be done from something like WebLoginPE or would it need to be in the core of MODx?
-
☆ A M B ☆
- 24,524 Posts
A plug-in would handle that just fine. Use the appropriate "event" to trigger the plugin, and have its code do whatever you want with the POSTed data. And from what Scotty has done with his WebLoginPE, you can see that it’s certainly possible to do whatever you like with the front-end registration and login process as well.
I would also like to see an option during new installations to store the user personal data in a separate database from the main MODx database. One use for that would be making it easier to have multiple MODx sites that shared users between them. Having an option to specify this during installation could make things plug and play simple as long as you stuck with MODx. For the more advanced integration with other brands of software the plugin could be used.
-
☆ A M B ☆
- 24,524 Posts
Unfortunately I don’t think it would be possible to have options in the installer for everything that everyone wants. The basic installer has to be as simple as possible just to get a clean, reasonably timely installed base. Anything "custom" that some people would want would then be added, using various plugins and other third-party add-ons, much as they are now. Personally, I’m hoping to see less in the core installation.
There is discussion of having different basic installations available, but that will have to come after the main core installation is finalized, and will, again, most likely be the product of other community members donating their time to organize and release the entire package that they found useful.
Integration with Google Apps would be excellent.
