Fatal error: Allowed memory size of 8388608 bytes exhausted when trying to create a subtopic
Currently MidCOM's component listing used in the "Create subtopic" dialog needs quite a bit of memory. While solution is being planned, the easier way is to edit your php.ini and set memory_limit to something like 32M
MidCOM's content authoring interface doesn't look right
If your MidCOM AIS doesn't look like in the screenshots, the most likely reason is that the AIS CSS or images are not getting loaded. To fix this, ensure that your style includes the <(head-extra)> call somewhere within the HTML <head /> section.
In addition, if you're using MidCOM 2.x you need to ensure that the static directory where MidCOM's CSS and image files are stored is symlinked under your DocumentRoot. To do this, run:
ln -s /usr/share/pear/midcom/static /var/lib/midgard/vhosts/www.example.net/80/midcom-static
The MidCOM site template on my site doesn't update when I update the midcom-template package
The Midgard website creation instructions instruct using MidCOM Site Template through Aegir's Template functionality. With this functionality the a site-specific version of the midcom-template gets created. And this obviously will not be updated when you upgrade MidCOM.
You can easily switch the site to using MidCOM Site template in shared mode. To do this log into Aegir as System Administrator, go to Websites, and open your site for editing (you have to click it twice to get the details to the right-hand frame). Then simply change the value of Root page to MidCOM Site Template/template_midcom.
How do I blog with Midgard CMS?
Once you have a MidCOM-powered site set up, creating a weblog is very easy. Just Log in to your site, click Create page and then Create subtopic. You will be presented with the MidCOM topic creation form. Fill in the URL name and Title, and select type as News listing (de.linkm.newsticker).
If you want to enable user comments, there is a short HOWTO available.
Browser says my site is latin-1. I thought Midgard used UTF-8 as default?
Midgard 1.6+ uses UTF-8 character encoding by default to support better internationalization. However, Apache uses latin-1 encoding by default, and so unless your layout specifies otherwise by having a line like this in the <HEAD /> section:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
The other, and more reliable option is to edit your httpd.conf file and add the line:
This will cause Apache to serve all documents as UTF-8 encoded.
Note: It can be dangerous to have the site (as recognized by browser) and Midgard use different character encodings. As the content is also edited through the browser this can cause broken characters to get in. Switch to serving your site using correct encoding as soon as you can!