Actions

Developer Area/Plugin migration between Mahara 1.3 and 1.4

From Mahara Wiki

< Developer Area
Revision as of 07:15, 12 July 2011 by Dirkca (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Mahara 1.4 has some changes to the menu bars. For example the top level tabs 'Profile' and 'My Portfolio' have become 'Content' and 'Portfolio'.

Also, the 'My' has been dropped from some other tabs such that, for example, 'My Plans' becomes 'Plans' and has moved from under the 'My Portfolio' tab to 'Content'.

The table below has examples of the code differences required for plugins in Mahara 1.3 and Mahara 1.4.

This may help anyone upgrading a plugin to work in Mahara 1.4 or backporting a plugin to Mahara 1.3 and ensuring that the plugins are correctly located on the menu bar

It is not comprehensive. Feel free to add further examples

Plugin File Mahara 1.3 Mahara 1.4
blocktype

/externalfeed

lib.php 
public static function get_categories() {
    return array('feeds');
}

public static function get_categories() {
    return array('external');
}
blocktype

/externalvideo

lib.php 
public static function get_categories() {
    return array('fileimagevideo');
}

public static function get_categories() {
    return array('external');
}
artefact

/plans

lib.php 
public static function menu_items() {
    return array(
        array(
            'path' => 'myportfolio/plans',
            'url'  => 'artefact/plans/',
            'title' => get_string('myplans', 'artefact.plans'),
            'weight' => 40,
        ),
    );
}

public static function menu_items() {
    return array(
        'content/plans' => array(
            'path' => 'content/plans',
            'url'  => 'artefact/plans/',
            'title' => get_string('Plans', 'artefact.plans'),
            'weight' => 60,
        ),
    );
}

artefact/plans

index.php new.php plan.php 

define('MENUITEM', 'myportfolio/plans');

define('MENUITEM', 'content/plans');

artefact/learning

index.php 

define('MENUITEM', 'profile/mylearning');

define('MENUITEM', 'content/mylearning');

artefact/learning

lib.php 

public static function menu_items() {
    return array(
        array(
            'path' => 'profile/mylearning',
            'title' => get_string('mylearning', 'artefact.learning'),
            'url' => 'artefact/learning/',
            'weight' => 20,
        )
    );
}

public static function menu_items() {
    return array(
        array(
            'path' => 'content/mylearning',
            'title' => get_string('mylearning', 'artefact.learning'),
            'url' => 'artefact/learning/',
            'weight' => 20,
        )
    );
}

artefact/europass

index.php editlanguage.php 

define('MENUITEM', 'profile/europass');

define('MENUITEM', 'content/europass');

artefact/europass

lib.php 

   public static function menu_items() {
       return array(
           array(
               'path' => 'profile/europass',
               'title' => get_string('europass', 'artefact.europass'),
               'url' => 'artefact/europass/',
               'weight' => 90,
        )
    );
}

   public static function menu_items() {
       return array(
           array(
               'path' => 'content/europass',
               'title' => get_string('europass', 'artefact.europass'),
               'url' => 'artefact/europass/',
               'weight' => 90,
        )
    );
}


In some cases, it may be worth considering conditional statements to enable a plugin to work with either Mahara 1.3 or 1.4. For example 

public static function get_categories() {
    require_once(get_config('libroot') . 'version.php');
    $release = $config->release;
        if ($release < 1.4) {
            return array('feeds');
        }
    return array('external');
}
Retrieved from ‘https://wiki.mahara.org/index.php?title=Developer_Area/Plugin_migration_between_Mahara_1.3_and_1.4&oldid=2183’