LiveWhale CMS

Welcome, Guest Login

Support Center

Our documentation is moving:

Please check for the most up-to-date LiveWhale CMS and LiveWhale Calendar documentation. The below legacy documentation will remain available as a reference until the documentation migration is complete.

Module Naming

Last Updated: Jun 26, 2014 07:30AM PDT
When developing modules, you’ll want to make sure that the name you choose matches with what LiveWhale expects, so that all the pieces are loaded properly. An example is below, but if key pieces are based on the name “My Module,” they would appear as follows:
  1. In the client/modules folder the enclosing folder would be:
  2. The files within the /my_module folder would be (examples):
  3. In each of the files, there should be a leading reference to append the module to the proper registered scope:
    $_LW->REGISTERED_APPS['my_module'] = ...
    $_LW->REGISTERED_WIDGETS['my_module'] = ...
  4. In the same file, there should be a matching class, using a camelCased version of the name:
    class LiveWhaleApplicationMyModule { ...
    class LiveWhaleWidgetMyModule { ...
  5. Within that class, there should be public methods matching any handlers you intend to use, but all other methods or properties are then open, as they are limited to your class alone. You may include/require other classes as desired, but avoid calling the same class twice (for obvious reasons). Do not call one module from another.
Here is an example with a notification module:
// in clients/modules/public_notifier/public.application.public_notifier.php
     'title'=>'Public Submission Notifier',
      'handlers' => array('onAfterPublicSubmission')

class LiveWhaleApplicationPublicNotifier {
    public function onAfterPublicSubmission () {

​Expertise Needed: Developer

Software: LiveWhale CMS, LiveWhale One, LiveWhale Calendar

Version Applicability: Current

SFTP Access Required? Yes
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found