-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Georg wrote: > > Some problems occured to me with this "new" installation: > > 1) When language is set to "German" all special characters like "Ã,Ã, > ..." are replaced by "?" question marks and >
The localizations are propably still stored ISO-8859-1 encoded when Midgard itself uses UTF-8 as default from 1.6 onwards. I once adapted the localization fix script from http://www.nemein.com/people/rambo/upgrading_to_openpsa_1_10_1__and_later__in_latin1_encoded_db.html to fix Aegir localizations at an installation but was too stupid to save it anywhere, anyways the basic idea is to run nnloc_convert_charset_lib('/path', 'iso-8859-1', 'utf-8'); For each Aegir localization library (including comments), however I can't remember where to find them... *backup* your database before doing anything like this, if excrement hits the rotating blades the process is *not* reversible. > > 2) i do not have any editing buttons to create "new websites", "new > companies", > "new persons", ... in the left menu > PCRE problem, see http://kaukolaweb.com/blog/midgard_on_rhel3.html (though especially on a certain Fedora 1 box I had no end of issues with this, in the end having to install PHP from source). In fact it's funny that Aegir uses the ereg/eregi calls and trusts that thet happen to be Perl compatible [system dependent], when preg_match would certainly be Perl compatible and in most cases faster. > > 5) in the Companies settings in line 2 i found the following information: > ------------------------------------ > Port of Staging Server (eg. 8001) > Please read the staging server instructions at www.hklc.com/midgard_manual > before setting this you have to do alot of changes to the midgard setup > before staging and live work! > ------------------------------------ > In the mainframe of the stated url i get the message: "Fatal error: Call to a > member function on a non-object in snippet:///hklc_news_simple/newsbody on > line 132" > hklc.com is up ? (that URL really should be changed, alas Aegir development has mostly ended). Anyways that document would most certainly be obsolete, I think I (or Kaukola or Bergie) have posted somewhere about setting up the staging-live using my YAMP script for it (though the multilang version has a bug I should fix). > > I would be graceful for any explanations as i plan to go on working with > aegir but still do not feel familiar with the tool. > For basic content management I would definitely use MidCOM, I at times use Aegir for some things but mainly Spider if I have to do something outside MidCOM. /Rambo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCQaG0i7iLtQbxbW8RA9YMAJ9ArVS/pB7WvQWXpeo8jZO/C2pT4QCfe/Dr 8oP2EYjbx55tRLe+0HUpE34= =w7/e -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
