WHM Perl Modules Documentation

[nickp666]

I am presently developing some plugins for WHM, but am unable to find any documentation whatsoever on any of the Whostmgr:: perl modules, I have managed to cobble a few things together by looking at chirpys work but dont know where to look for docs on the methods available.

For example, im looking for a list of methods for: Whostmgr::HTMLInterface

Does anyone know where I can find this info out?

TIA

[cpanelkenneth]

I am presently developing some plugins for WHM, but am unable to find any documentation whatsoever on any of the Whostmgr:: perl modules, I have managed to cobble a few things together by looking at chirpys work but dont know where to look for docs on the methods available.

For example, im looking for a list of methods for: Whostmgr::HTMLInterface

Does anyone know where I can find this info out?

TIA

Perl methods look like:

sub foo{

Thus, looking at all the lines that start with sub will give you a list of methods. As for parameters, those are usually just underneath the method name, like:

my( $self, $one, $two) =@_;

or

my $self = shift;
my $one = shift;
my $two = shift;

where $one and $two are the arguments you provide and [b]$self[/$b] is a reference to the object (not all will have $self).

UPDATE:
As for documentation itself, that is what the code is for.

[nickp666]

Thanks Kenneth, where will i find the perl module files?

TIA

[daveformerlyof]

/usr/local/cpanel/Whostmgr/

on any cPanel server. If you are looking to access specific WHM methods, the preferred method is through the XML API:

http://www.cpanel.net/plugins/xmlapi/

We do not recommend relying on perl modules as they will not remain constant.

[nickp666]

The plugins I am developing have no need for the functions provided by the XMLAPI.

I noticed this morning with the latest CURRENT that Whostmgr::HTMLInterface has been changed - surely this is a pre-requisite to any WHM Plugin?

[daveformerlyof]

While utilizing these libraries can help out, it is not required. We cannot guarantee that these modules will not change, in fact they change frequently to provide new/updated features in WHM. The core aspects of the software are provided through APIs and hooks which retain backwards compatibility.

[nickp666]

Thanks for the clarification, but is there some way we can be notified when there are changes to the WHM perl modules (as the changelog is a little unspecific)

Every plugin I have ever looked at for WHM (and every plugin I have developed) makes use of:

Cpanel::Form
Whostmgr::HTMLInterface
Whostmgr::ACLS
Cpanel::SafeFile

It would be nice to know when changes are made to these as they are so commonly used, realistically specific changes dont need to be detailed, as plugin developers should be expected to actually read the syntax, but knowing when we need to would be a good idea rather than waiting for our clients to scream that plugins dont work

[cpanelnick]

Thanks for the clarification, but is there some way we can be notified when there are changes to the WHM perl modules (as the changelog is a little unspecific)

Every plugin I have ever looked at for WHM (and every plugin I have developed) makes use of:

Cpanel::Form
Whostmgr::HTMLInterface
Whostmgr::ACLS
Cpanel::SafeFile

It would be nice to know when changes are made to these as they are so commonly used, realistically specific changes dont need to be detailed, as plugin developers should be expected to actually read the syntax, but knowing when we need to would be a good idea rather than waiting for our clients to scream that plugins dont work

All 4 of those as well as Whostmgr::UI are generally kept backwards compatible

[daveformerlyof]

Thanks for the clarification, but is there some way we can be notified when there are changes to the WHM perl modules (as the changelog is a little unspecific)

Every plugin I have ever looked at for WHM (and every plugin I have developed) makes use of:

Cpanel::Form
Whostmgr::HTMLInterface
Whostmgr::ACLS
Cpanel::SafeFile

It would be nice to know when changes are made to these as they are so commonly used, realistically specific changes dont need to be detailed, as plugin developers should be expected to actually read the syntax, but knowing when we need to would be a good idea rather than waiting for our clients to scream that plugins dont work

Nick,
We typically don't document changes to the modules as we don't encourage plugin developers to develop against these modules. We can offer you a development license however which can be set to a tree that will provide insight on changes before they hit your users. Please pm me for info on getting a development license set up.