|
Update: OK. The key to all my problems was
overlooking this piece of info: http://www.midgard-project.org/documentation/installation/additional-packages.html It says I have to copy the .xml files in
the new midcom release (there’s just one; it’s midcom-template.xml)
to /usr/local/share/midgard/data. Then when you run datagard import, it
actually imports the new midcom template. This got 2.4.0 working!! Yea!!! Now when I
changed the language in the site setting for site language to ‘en-us’
I got an error that was much easier to hunt down. It turns out that the file:
/usr/local/share/midgard/midcom/lib/midcom/services/_i18n_language-db.dat did
not have an entry for US English. I quickly added one and the errors went away.
It is very important to be able to specify ‘en-us’ so that dates
are understandable to the Americans. I suggest that the MidCOM INSTALL document
include the simple step of copying the .xml files to the midgard/data directory
and running datagard import after that to save the newcomers lots of grief. Yikes, that was painful. From: Alan
[mailto:[EMAIL PROTECTED] I’m still struggling (and learning) with MidCOM. My
basic problem is still dealing with the errors introduced by using
‘en-us’ for the localization setting. My install is on a current Gentoo box, using the AllInOne
1.6.1 Midgard install. The midgard-data portion includes MidCOM 1.4.0. After that I have followed the instructions in the INSTALL
to update MidCOM to 2.2.1 and 2.3.4, and now 2.4.0 to no effect. I have verified that my MySQL Midgard database (using
en-iso.8859-1 for its language setting) has the tables: snippetdir, snippet,
and snippet_i Within those tables, there are records with code. SQL
[select si.code from snippet_i si, snippet s, snippetdir sd where sd.name =
‘midcom’ and s.name = ‘version’ and sd.id = s.up and
s.id = si.sid] shows me the version number for MidCOM in all instances recorded
in the database. They are all 1.4.0 1. Is the code in the database just a cache and the actual
code is coming from a disk file somewhere? If so, where? Using Aegir, I navigate to the left nav
‘snippet’ link, and I can expand the midcom section, such that I
see the very same code referenced above. Even after upgrading, I see new companies get assigned this
code, which displays the MidCOM version as 1.4.0. 2. The INSTALL guide recommends renaming midcom, net, pl,
de. Is this to be done in Aegir on the snippetdirs? (Essentially updating the
records in Midgard:snippetdir so that the “name” field is changed
to midcom_old, etc?) Or is the name change to take place on an actual
filesystem directory or file? Looking on disk, I see
/usr/local/share/midgard/midcom/lib/version.php. This file has version 2.4.0
defined in it. Before it had 2.3.4. I assume that these files get called from the latest MidCOM template. Looking in Aegir, I navigate to the left nav
‘websites’ link. Opening up a new company (subsequent to the
upgrade of MidCOM 2.4.0), I see line 29 of <[code-global]> is
mgd_include_snippet(“/midcom/midcom”); This would appear to be
pointing to the old MidCOM 1.4.0 installation. Commenting this line out or
altering it does not affect the display of the page (why?) 3. What should be called here? Is there an
fs_midcom(“lib/midcom.php”) call of some sort? Why is the new
template not getting uploaded? 4. The INSTALL document instructs me to create a symbolic
link, “ln –s /usr/local/share/midgard/midcom/static
/var/lib/midgard/vhosts/<vhost name>/80/midcom-static/ Since this doesn’t work unless there is a directory
under ../80 called midcom-static, should I be creating the midcom-static
directory before executing this command? I assume the structure of the
directory should be ../80/midcom-static/static pointing to
/usr/local/share/midgard/midcom/static but I hold out the possibility that it
should be ../80/midcom-static pointing to the same location. Which one is it?
Also, did I do something wrong that I don’t have a midcom-static
subdirectory if the answer is the former, not the latter? 5. It would appear that a major re-thinking of MidCOM took
place between 1.4.0 and 2.x. Perhaps it used to keep code and templates in the
database, but now they are kept on disk? Am I correct? Can you point me to some
documentation on this? I have studied: http://www.midgard-project.org/documentation/concepts/midcom http://www.midgard-project.org/documentation/installation/ INSTALL in the MidCOM tarball root. http://www.nehmer.net/~bergie/oscom3/ http://www.nehmer.net/~torben/midcom-docs/ The documentation does not really cover MidCOM upgrades from
what I see. I would rip everything out and start all over, but the
Midgard AllInOne install bundles in MidCOM 1.4.0, so I would just be back where
I started. I assume the same issue with using Mike Bedwell’s ebuilds. Thanks to Torben and Tarjei for getting me closer to the
solution. -Alan |
