Synopsis
A shorthand way to provide preprocess "hooks" for any content type.
This snippet can be placed in a template or your chosen module, I usually place this in both the node and page preprocess function eg
This snippet can be placed in a template or your chosen module, I usually place this in both the node and page preprocess function eg
A handy little Drupal plugin that let's users increase/decrease fonts with a single click
nb I tried the official drupalfont resizer, but could not get it working, on the off-chance that you have the same problem...
SynopsisA client requested the construction of a limited set of web services. Simpler solutions created the foundations for these services via a set of generic classes and libraries.
Details on how to implement these are given below
The signature verifier script provides a simple way to validate the arguments passed to a function. Most functions sanitize their arguments before proceeding. Often this is via a set of repeated checks ie checking that a required field is not null or that it is the correct data type (array or int for example). If a function requires many arguments then this can result in a lot of code before the function can start it's actual work. The aim of this class is to abstract out as much of this as possible to improve readability and cut down on code duplication.
The literal handling script illustrates a simple way of providing multi lingual capabilities to a website. Instead of having hard coded string literals within scripts, a simple call can be made to the literals class which will look for a match for the requested literal and the particular language it was requested in. The base literals class is extensible so that each site script can abstract it's own literals away into a seperate literal handling class.
Sometimes it is necessary to override the functionality of a particular module. You may wish to to customize some functionality but without hacking the core code of the module.
How do you do this ?
There are several ways, here is just one.....
As of drupal 5.x blocks are not processed on 403 and 404 error pages, instead the contents of the specified pages are used along with the site theme to create an error page (or simply the words 'page not found' if no error page has been specified).
This decision was a deliberate one....