E-Books for you

Create a new table that maintains a one-to-one relationship with the
#__users table.
Use the user's parameters to store additional data.
The first option can cause some major problems. If several extensions choose this
method, there is a chance that there will be a naming conflict between fields.
The second option is a good choice if the extra data is searchable, ordered, or used
to modify results returned from the queries. To maintain the table successfully,
we would have to create a plugin to deal with the events onAfterStoreUser and
onAfterDeleteUser, explained in Chapter 6.
The final option is ideal if the extra data is not subject to searches, ordered, or used to
restrict query results. We might implement these parameters in one of the three ways:
Manually edit the parameters using the setParam() method. This is suitable
if there are not many parameters or the user never modifies the parameters
using a form.
Use JParameter as the basis to create a form in which users can modify
the parameters.


Pages:
228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252