Hallo!
Now that there is a possibility of having custom fields
in the xoops_user_profile table, I see that it would be
very convinient to have a split in two following areas:
xoops_user_profile
AND
xoops_user_preferences
This kind of division may help at various levels. The
preferences are the xoops CMS specific ones that may be
stored seperately in a table that may be of really no
interest to other scrips interfacing with xoops.
Whereas if the profile data is stored into a seperate
table, it would help to export import and interface
with the data with much more ease.
Logged In: YES
user_id=882380
The 2.3 preferences management system already allows to
specify user-specific preferences.