Checking and Calling a Plugin
While looking at action.php code, I found this useful information how to check whether a plugin exist and to access it.
Benchmarking Nucleus
Here's a cookbook how to setup a simple benchmarking on your blog.
Getting a Dose of Parameters
I know, this is mostly HTTP stuff, but it is improtant for a plugin writer to understand this because this is how a plugin received inputs from external. And I found this useful information here and thought to make a note to it to remind myself.
Cookie business
Form time to time, a plugin might have a need to access cookie. So, this little post talks about it.
The Need for supportsFeature
Mr Data Goes to Town
So often a plugin need to track information in variables, I'm talking about data that is persistent through out the life of the plugin. This allow data to be passed from event to event, for example.
Having a getMinNucleusVersion
In the plugin API, there is a getMinNucleusVersion function that helps a plugin to report to Nucleus that the minimum Nucleus version it supports. This is a way to ensure a plugin is not install on a old Nucleus setup that certain support is missing. ie user defined table prefix
The Creation of permalink
I saw it sometimes when a plugin writer directly construct a permalink (also called item link) by doing this:
... ... echo "<a href=\"index.php?itemid=".$itemid."\">".$title."</a>";
... ...
Why sql_table...
Since Nucleus 2.5, sql_table() is introduced to construct the name of table name.
ie. sql_table('item') yields nucleus_item in a normal setup.
So, why a plugin should use this function to determine the table name, you ask?
I say, simple.
ie. sql_table('item') yields nucleus_item in a normal setup.
So, why a plugin should use this function to determine the table name, you ask?
I say, simple.