#Bugzilla bugzilla code#

Its useful as a convenience method for those scripts/templates which are only use via CGI, though. Not all Bugzilla actions are cgi requests. Note that modules should not be using this in general. If the argument is '' (empty string), the language is reset to the current one (the one used by Bugzilla->template). If no argument is passed, it uses the last language set. Also use it if you want to specify the language to use. If you ever need a Bugzilla::Template object while you're already processing a template, use this.

The current Template object, to be used for output template_inner Nothing cares about this now, but don't rely on that. Note that all Bugzilla functionality is method based use Bugzilla->dbh rather than Bugzilla::dbh.

#Bugzilla bugzilla code#

Note that items accessible via this object are demand-loaded when requested.įor something to be added to this object, it should either be able to benefit from persistence when run under mod_perl (such as the a template object), or should be something which is globally required by a large ammount of code (such as the current user object).

We can reuse objects across requests using mod_perl where appropriate (eg templates), whilst destroying those which are only valid for a single request (such as the current user).

Code in modules can get access to these objects without having to have them all passed from the caller, and the caller's caller, and.

Everything is in one central place, so it's easy to access, modify, and maintain.

They're not global variables, so we don't have issues with them staying around with mod_perl.

This module is a singleton intended as a central place to store these objects. This includes database handles, template objects, and so on. Several Bugzilla 'things' are used by a variety of modules and scripts.

Bugzilla - Semi-persistent collection of various objects used by scripts and modules SYNOPSIS use Bugzilla