Here's an example of an Addon.ini file for a simple plugin. The first few lines of code just tell us a little about the plugin.
The plugins actions begin with the line that reads [Gallery_Style]. This line tells gpEasy that this plugin would like to interact with the Gallery_Style hook. Everything after that line and before the next hook declaration will be interpreted as part of the Gallery_Style hook.
Addon_Name = 'Tall Gallery Style' Addon_Version = 1.0 ;The Gallery_Style hook [Gallery_Style] value = '{$addonRelativeCode}/gallery.css'
There are a number of options for passing information to the Gallery_Style hook, but we use the simplest: value. By assigning the value {$addonRelativeCode}/gallery.css, we're telling gpEasy to use the gallery.css file in the plugin's folder for the gallery style.
Note: the value option for hooks is only available as of gpEasy 2.0b3.
You probably notice in the previous example the use of {$addonRelativeCode}. This is one of a few variables that are replaced in the Addon.ini file before parsed to help developers create plugins that work on systems regardless of where they're installed. Here's a list of available variables.
A new release for Typesetter is in the works with a lot of improvements including the ... Read More
Typesetter 5.1Typesetter 5.1 is now available for download. 5.1 includes bug fixes, UI/UX improvements, ... Read More
More NewsFind out more about our Provider Spotlight
What CMS: Find out what CMS a site is using.
Who Hosts This: Find out who is hosting any web site
WordPress Theme Detect: Find out which theme a WordPress site is using