Upgrading MidCOM from 2.4 to 2.6
MidCOM upgrade from 2.4 to 2.6 requires several manual steps.
Site initialization
MidCOM 2.6 uses the site initialization system specified in mRFC 0025. This differs quite much from the system used in the old MidCOM template.
Create a new site using the Site Wizard
Go to the site, log in, and click Website -> Website settings
Change the root topic to point to your existing root topic
Content conversion
Deprecated components
| Component used in 2.4 | Component used in 2.6 |
|---|---|
| de.linkm.taviewer | net.nehmer.static |
| de.linkm.newsticker | net.nehmer.blog |
| de.linkm.events | net.nemein.calendar |
| net.nemein.rss | net.nehmer.blog with RSS subscription mode enabled |
| midcom.admin.content | Not used, administration is now on-site |
Converting the content areas
Run the supplied migrate_26.php script to migrate the content to use MidCOM's new Access Control Lists and new components instead of the old 2.4 ones.
php ./migrate_26.php -u admin -p password
Style conversion
Since MidCOM template is not used with MidCOM 2.6, the MidCOM template style elements are not available either. Instead of them utilize direct MidCOM services instead. Some examples below:
Navigation
Use fi.protie.navigation instead of the old <(navi-dynamic)>
Breadcrumb trail
Use something like the following instead of the <(breadcrumb)> element:
<div class="breadcrumb"><?php echo $nap->get_breadcrumb_line(); ?></div>
Example <(ROOT)> element
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title><(title)> - <?php echo $_MIDCOM->get_context_data(MIDCOM_CONTEXT_PAGETITLE); ?></title>
<?php
echo $_MIDCOM->print_head_elements();
?>
</head>
<body <?php echo $_MIDCOM->print_jsonload(); ?> >
<?php
$_MIDCOM->toolbars->show();
?>
<(content)>
<?php
$_MIDCOM->uimessages->show();
?>
</body>
</html>
