This feature is available since:
The release of 126.96.36.199
introduces a preliminary plugin architecture that allows Wikka users to override core functionality with custom actions, headers, formatters, and templates. The advantages of such a setup are numerous:
- A component that "misbehaves" or does not perform to your expectations can simply be removed.
- Future Wikka upgrades are guaranteed not to change or modify anything in the /plugins folders.
- Testing of a new action, handler, formatter, or template is greatly enhanced: There is no need to modify core functionality, and it's easy to revert back to the core if necessary.
To use the new plugin folders for your add-ons, you will have to create the /plugins
tree and add the corresponding paths in wikka.config.php
file (automatically added in fresh installs since 188.8.131.52). Components will be loaded following the path order specified in the config file (so for instance a custom action called /plugins/actions/contact.php
will override the default actions/contact.php
). You can use a comma (,
) a colon (:
) or a semicolon (;
) as a path separator in the config file. For example:
'wikka_formatter_path' => 'plugins/formatters,formatters',
'wikka_template_path' => 'plugins/templates,templates',
'handler_path' => 'plugins/handlers,handlers',
'action_path' => 'plugins/actions,actions'
Version 2.0 will herald an even more robust plugin architecture (backwards-compatible with the one in this release) that will include "hooks" that can be called from a user's custom component, eliminating the need to modify code in the Wikka core.
If your wiki runs on an Apache server and is configured to use clean URLs via ModRewrite
, you will need to disable redirection for files in the /plugins
tree. Just save the following file in the /plugins
# turn on rewrite engine
has been set up as a repository for Wikka plugins. While the use of WikkaCase is beyond the scope of this document, we will be updating the WikkaCase documentation
as progress on the new architecture continues. Currently, SVN and bug tracker access is available for developers who want to start building plugin modules for Wikka. Please visit the WikkaCase development
page for details.