81
Despite a number of other posts elsewhere in various forums saying that this particular feature is part of the 2.1 roadmap, it isn't. So here it is to get it registered on dev team radar
1st one:
- User/member data needs to be extensible by site admin.
A number of admins would like to be able add new data and/or functionality to the user/member class. For instance one of my sites (valentinewalton.co.uk) would like to add snail mail address, joining dates, d.o.b., telnums etc so that we can actually use the site as central membership register. the carrot here is that if it becomes relatively straightforward to extend user/member class then quite a few people (myself included) are going to go flat out to produce CRM capabilities that will make XOOPS stand out head and shoulders above the competition.
I've tried to decipher what is going on in the user/member classes to see if I could extend myself but clearly (and obviously from other users's comments and experience) this is a daunting task as you really are playing deep in the guts of the core system. The amount of published info is sparse, So ...
2nd one:
- Clear unambigous developer notes/instructions on the system that would allow developers to build on the system. I recall from somewhere else that the team are moving towards 'Xoops Certified' modules, rather than core mods etc. Perhaps one of the tests for inclusion is that bods like me can read and understand proper system documentation for the module? In the same vein, a 'how to' would seem appropriate. I am not sufficiently familiar with php to know if it supports 'morphing classes for instance so that I can replace the user class with my own, but perhaps I digress.
Kind regards
Ashley