#BUGZILLA API FULL#

Where Extension Code GoesĮxtension code lives under the extensions/ directory in Bugzilla. There is a sample extension in extensions/Example/ that demonstrates most of the things described in this document, so if you find the documentation confusing, try just reading the code instead.

#BUGZILLA API FULL#

The directory will contain a full framework for a new extension, with helpful comments in each file describing things about them. That will create a new directory in the extensions/ directory with the name of your extension. To use it, pick a name for your extension and, in the base bugzilla directory, do:īut replace NAME with the name you picked for your extension. There is a script, extensions::create, that will set up the framework of a new extension for you. There is also a wiki page with additional HOWTOs, tips and tricks. This section gives more information on exactly how extensions work and how you write them. The 'SYNOPSIS' above gives a pretty good overview of what's basically required to write an extension. This is the base class for all Bugzilla extensions. Template hooks would go into extensions/Foo/template/en/default/hook/.

The following would be in extensions/Foo/Extension.pm or extensions/Foo.pm: package Bugzilla::Extension::FooĬustom templates would go into extensions/Foo/template/en/default/. Templates in extensions distributed on CPANīugzilla::Extension - Base class for Bugzilla Extensions.A Warning About Extensions That You Want To Distribute.

If Your Extension Needs Certain Modules In Order To Compile.If Your Extension Requires Certain Perl Modules.

Bugzilla api