We should consider the use of JRegistry before we create any
settings files.
The user is a complex entity and how we handle it is very important. We can
extend users in various ways. Whichever mechanism we choose, we should always
consider creating a 'repair' function to allow administrators to check the database
for errors, which may have occurred in relation to any customization of the user
made by our extensions.
Chapter 7
[ 191 ]
We must always remember to use the global JSession object to handle sessions.
Directly accessing the $_SESSION variable can have some unexpected results.
Modifying our site to suit a browser may seem drastic, but when checking for
features and quirks in the browser is as easy as one simple method, it makes sense.
Bulletproof extensions always consider the unexpected, and quirks in the browser
are just one of those things.
Beyond common code, there is land full of imagery, multimedia, and the occasional
unicorn. If we want to give administrators full control over an extension, being able
to modify an extension's repository of assets is necessary.
Pages:
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269