It kinda worked (I think), but now I've got some problems.
Is there a visible difference between the admin interface in 1.2.5 and
1.2.6beta2? Other than the styles section being more of an outline, I don't
notice anything else. Of course this could have to do with improper
upgrading.
I followed, to the tee (so I think), the instructions below. Replacing names
and paths for my configuration as mentioned. I made a backup of my 1.2.5
database and then proceeded to update it to the 1.2.6 (again as stated
below).
When I accessed my admin site the styles for one of my sites were duplicated
and even triplicated in some instances. When I modify the contends of any of
my host templates midgard places "\" with ever update.
Example:
<p class="abstract"> this is the way it is suppose to look
<p class=\"abstract\"> the result of clicking "modify"
<p class=\\"abstract\\"> the result of a second modify
With every modify it continues adding the "\" which renders my entire site
unusable.
Why is it doing this and how can I fix it?
Jamey
> -----Original Message-----
> From: Alexander Bokovoy [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, February 08, 2000 7:57 AM
> To: [EMAIL PROTECTED]
> Subject: [midgard] Safe upgrade to Midgard 1.2.6-beta2
>
> Hello all!
>
> For those who want to test new Midgard 1.2.6 beta but failed to find a
> way to transfer old sites to it, I'll suggest simple-and-dirty utility
> for this work.
>
> All described below requires that Midgard 1.2.6-beta2 is installed
> except database installation (it means that you compiled and installed
> Midgard-lib, Mod_Midgard, and Midgard-PHP, because dumper utility uses
> new Midgard-Lib, and Admin Site uses new Midgard-PHP, and Mod_Midgard).
>
> Admin and Examples sites in Midgard 1.2.6beta2 use the same IDs as their
> previous versions but content of some records was changed and will be
> changed before final release definitely too. In order to update your
> database, you'll need to walk several steps:
>
> 1. Update database structure in order to include three new tables -
> 'repligard', 'snippet', and 'snippetdir' - using update.sql file
> attached.
>
> 2. Create new MySQL database named 'testgard' and run mysql command line
> utility:
> mysqladmin create testgard
> mysql testgard <midgard.sql
> where midgard.sql is from midgard-data-1.2.6-beta2.tar.gz
>
> 3. Get attached dumper.c and change parameters for mgd_connect()
> function to fit your situation. First parameter is database name
> ('testgard') and others are username and password.
> Compile dumper.c against Midgard-lib 1.2.6beta2 using the following
> command line:
> gcc -o dumper dumper.c -I/usr/include/mysql -L/usr/lib/mysql
> -I/usr/local/include -I/usr/local/lib -lmidgard -lmysqlclient
> Note that actual paths to MySQL and Midgard includes and libraries
> depends on your installation.
>
> 4. Run dumper, it will write database content on stdout. You might
> redirect it to mysql command line client:
> ./dumper | mysql midgard
> where midgard is a name of your actual database but I suggest to
> redirect its output to file and do some modifications:
> ./dumper >midgard.update
>
> 5. Open midgard.update in an editor and find first occurence of
> "name='localhost'" (without double quotes). It will be definition of
> Admin Site host info. Change localhost to your actual host and correct
> 'prefix' field if it differs from '/admin'. Do the same with Example
> Site definition below.
>
> 6. Now you're ready to place update into your database:
> mysql midgard <midgard.update
>
> --
> Sincerely yours,
> Alexander Bokovoy
> <!-- 2:450/144.58 --- bokovoyATminsk.lug.net --- FractalsAtTheEdge --> <<
> File: dumper.c >> << File: update.sql >> << File: ATT09174.txt >>
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
