5
I would not minimize the work of the profile hack.
However, if You add the possibility to extend those fields, You want, soon or later, You need a way to deal with multiple screeens.
Currently we wrote for another CMS a profile hack with tabbed screens as sections of web related, IM related, location, etc
But after all, You see a need to create several custom screens to provide information and to use the CMS for other tasks as well. In our case this is a dating board.
We like to help to create a nice custom profile addon for xoops, but as said before, we wait to help until we have postgreSQL support.
In our project we will store images in BLOBS in the database, and not in folders, for security reasons etc. That's why we prefer postgreSQL and secondly, when You make huge use of storing advanced profiles, You want to have an option to activate rollback and a better way of locking rows etc.
Ok, I say an option to activate in prefs, because our vision
is to have a transparant layer of the SQL engine and until now this is not ready, we suppose.
Thanks for the hack for study.
