Here are my notes (and problems) on upgrading MidCOM to 2.3.4 on Gentoo using the INSTALL instructions in the MidCOM-2.3.4.tar.bz2 file:
midgard-config --prefix shows that I'm using /usr/local bunzip2 MidCOM-2.3.4.tar.bz2 and tar extract into /usr/local/src, creating a MidCOM-2.3.4 directory. cp -r MidCOM-2.3.4/* /usr/local/midgard/midcom The requirement for PEAR HTML_Treemenu isn't difficult in spite of there being no emerge/ebuild for it. Just enter 'pear install HTML_Treemenu-1.2.0' and it installs itself, like this: pear install HTML_TreeMenu-1.2.0 downloading HTML_TreeMenu-1.2.0.tgz ... Starting to download HTML_TreeMenu-1.2.0.tgz (48,309 bytes) .............done: 48,309 bytes install ok: HTML_TreeMenu 1.2.0 The directions to create the symbolic link didn't work for me if I followed the directions exactly: ln -s static /var/local/lib/midgard/vhosts/<FQDN>/80/midcom-static/ ln: creating symbolic link `/var/local/lib/midgard/vhosts/<FQDN>/80/midcom-static/' to `static': No such file or directory # ln -s static /var/local/lib/midgard/vhosts/<FQDN>/80/midcom-static The command line above works (just remove the training slash from the original instructions.) If repligard gives you a login error, remember to update repligard.conf with whatever you set the admin password to in MySQL. Now I create a new company and website and try to set the Site Setting for localization to 'en-us' and I get the same problems listed below from the previous messages. How can I verify that the version 2.3.4 of MidCOM is being used? I had previously thought I upgraded to 2.2.1, but it apparently didn't work due to an undetected error on my part. I do see it reporting MidCOM 1.4.0 at the bottom of the page, so I suspect my update was not successful. Also, I need clarifications on these instructions: Updating MidCOM Template sites from Database MidCOM: ---------------------------------------------------- Do the same steps as above. Now your site should run with fs-midcom. To ensure this (if in doubt), you should rename the top-level snippet dirs "midcom", "de", "net" and "pl" to something like "midcom_old" etc. Note, that you might not have all of these. Is this referring to the files under /usr/local/midgard/midcom/lib ? Thanks again, Alan -----Original Message----- From: Torben Nehmer [mailto:[EMAIL PROTECTED] Sent: Thursday, June 02, 2005 11:55 PM To: [email protected] Subject: Re: [midgard-user] Cache won't invalidate -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, - --Alan wrote on 2005-06-03 08:43: > Thanks for clarifying the cache misconception. It would also appear that > since I'm trying to access http://<hostname>/midcom-admin/ais that there is > something about the 'en-us' entry that is missing on some lookup. I created > a new company and website and started fresh. I get the following errors, > like before: > > Notice: Undefined index: en-us in > /var/local/cache/midgard/29-97-14-0.php(307) : eval()'d code(46) : eval()'d > code on line 52 > > Notice: Undefined index: en-us in > /var/local/cache/midgard/29-97-14-0.php(307) : eval()'d code(46) : eval()'d > code on line 53 > > Notice: Undefined index: en-us in > /var/local/cache/midgard/29-97-14-0.php(307) : eval()'d code(58) : eval()'d > code on line 56 > > I follow it to this section of code: > > // Start MidCOM execution > eval(' ?>'.mgd_preparse(mgd_snippet("/midcom/midcom")).'<?php '); > > // We shouldn't need HTMLfilter now > > Since /midcom/midcom isn't a file I can look in, I don't know how to > proceed. In any event, if you set the Site Setting for "Site language > (two-letter abbreviation, default: from browser)" to en-us, you will easily > see the problem. [Note that setting it to 'en' will not produce a common use > date format for the U.S., but 'en-us' does; it just has other side-effects.] > > I did note that a languages.xml file does have an entry for 'en-us', so a > lookup on that file would succeed. > > I'd be happy to hunt this down with a little guidance. Can I be the only > American working with Midgard/MidCOM? Ok. For a start. This is not Midcom 2.2.x what you are using. This is still a pre 2.x database MidCOM as you include the snippet /midcom/midcom instead of the file midcom.php from the FS distribution. I would suggest that you upgrade to the 2.3.4 release I made yesterday. This is almost (99,999%) what gets to be 2.4.0 along with the midcom template bundled with it. Then try again using it. Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCn/7AJPh4Kn6d5FYRAv9VAKCKaBneF6SRZY6F60ofbHu9ACqwjwCgpsSV CZrzABpFLgGZRk9wV3keWJE= =IyXG -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
