You are reading the Drake CMS Official Forums archive, available for historical purposes only.
Drake CMS has been rebranded into Lanius CMS, visit the new Lanius CMS Official Forums if you need support about Lanius CMS or Drake CMS -> Lanius CMS migration.
Help & Support Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6 [SOLVED]
Author
Message:
jfanque
Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6 [SOLVED]
24 January 2008 18:26
Anonymous
Hi everyone,
I'm currently trying to update an old
Limbo 1.0.4.2 installation to the current version of drake, but
I'm experiencing lots of trouble with the process.
As
far as I understand, I basically have to do the following: 1. in Limbo: use the Database-Backup-Feature to get an sql-file
containing the structure and content of the db. 2. Import
this backup into a fresh drake installation.
When
doing step 2 Drake seems to produce a converted file of the
original, but unfortunately there seem to be some errors in the
conversion process which result in bad MySQL-syntax.
Only to mention one obvious example: ====================================== DROP TABLE
#__users;
CREATE TABLE #__users ( id int(10)
auto_increment, name text, username varchar(150) NOT
NULL DEFAULT '', email varchar(100) NOT NULL DEFAULT '', password varchar(100) NOT NULL DEFAULT '', usertype
varchar(75) NOT NULL DEFAULT '', block tinyint(4) NOT NULL
DEFAULT 0, sendEmail tinyint(4), gid
tinyint(3 unsigned) NOT NULL DEFAULT '1', registerDate datetime() NOT NULL DEFAULT '0000-00-00
00:00:00', lastvisitDate datetime() NOT
NULL DEFAULT '0000-00-00 00:00:00', activation varchar(100)
NOT NULL DEFAULT '', params text, lang varchar(2) NOT
NULL DEFAULT 'en', PRIMARY KEY (id) ); ======================================
After fixing
all the SQL-Syntax-errors by hand, it still wont work, as some
fields (timezone) are missing from the new table afterwards.
Did I do something wrong in the upgrade procedure? Is the Limbo-conversion not ready yet? Will it be in v0.5
stable?
Thanks to everyone in advance. Any help is
much appreciated!
Ingo
Btw: PHP is version
5.2.4 and MySQL is version 4.1.22-standard.
trex1512
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
24 January 2008 21:31
Anonymous
Hi Ingo
Just as a start are you using a Limbo install
that has had any additional modules or components added?
Just to validate the process for the flat file Limbo and Drake
Gladius, I have successfully exported a 1.0.4.2 using a flat file
database to the latest Drake CMS using Gladius without error.
Has anyone else tried with MySQL setup? I will do a test
install and see.
TerryF
trex1512
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
24 January 2008 23:25
Anonymous
Hi again
OK, had no problems with a MySQL Limbo
restoring into the latest Drake CMS...even a Limbo flatfile
backup into a Drake CMS MySQL install worked fine..
I
have no ideas sorry...
TerryF
jfanque
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
25 January 2008 01:42
Anonymous
Hi Terry,
thanks for getting back to me so soon and
for testing this issue. To answer your question: There are
several components installed in the Limbo install that I'm trying
to update, but it should be mostly standard stuff.
At
first glance the Limbo DB backup looks good btw, it seems that
things only get messed up in the conversion process.
I'll try to get an anonymized version of the .sql file online
soon, so you can test it if you want.
Maybe I'll also
be able to help debugging this particular issue, when I have more
time soon.
Thanks so far!
Ingo
trex1512
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
25 January 2008 04:38
Anonymous
Hi
"Conversion" peocess?
Just to
confirm the process....
Make a backup in Limbo, save
the file to your local system, open a Drake CMS installation, go
to Database=>Manage Backups, upload the sql file.
Carry out a Restore using the uploaded Limbo sql file..
I had to do a Rebase on the Limbo Txt backup to Drake CMS
MySQL install to resolve an error that came up when I closed and
reopened Drake..
My Limbo installs are of the version
that has had many of the addins already installed..and the
security update to C8..
Good Luck
jfanque
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
25 January 2008 09:49
Anonymous
This is exactly the process I followed, except for the Rebase,
which was not possible anymore, because the "restore"
of the Limbo Backup results in an syntax error while creating
#__user, so the #__user table is not existant anymore
afterwards.
With "conversion process" I was
refering to the internal conversion that Drake performs
automatically when restoring an old backup (that is:
admin.database.lm_compat.php).
As an example: My
Limbo backup (file: 24_01_2008_10_44_10.sql) contains this
section:
Code:
CREATE TABLE lm_users ( id int(10)
auto_increment, name varchar(50) NOT NULL DEFAULT '', username varchar(25) NOT NULL DEFAULT '', email
varchar(100) NOT NULL DEFAULT '', password varchar(100) NOT
NULL DEFAULT '', usertype varchar(25) NOT NULL DEFAULT
'', published int(1) NOT NULL DEFAULT '1', gid int(3)
NOT NULL DEFAULT '1', registerDate varchar(20) NOT NULL
DEFAULT '', lastvisitDate varchar(20) NOT NULL DEFAULT
'', PRIMARY KEY (id) );
After
the restore failed, there is a new file in the backup directory
of my Drake installation, called
"1201198042_24_01_2008_10_44_10.sql_converted.php"
containing among other stuff the following, which gives 3
SQL-Syntax errors. Code:
CREATE TABLE #__users ( id int(10)
auto_increment, name text, username varchar(150) NOT
NULL DEFAULT '', email varchar(100) NOT NULL DEFAULT '', password varchar(100) NOT NULL DEFAULT '', usertype
varchar(75) NOT NULL DEFAULT '', block tinyint(4) NOT NULL
DEFAULT 0, sendEmail tinyint(4), gid tinyint(3
unsigned) NOT NULL DEFAULT '1', registerDate datetime() NOT
NULL DEFAULT '0000-00-00 00:00:00', lastvisitDate datetime()
NOT NULL DEFAULT '0000-00-00 00:00:00', activation
varchar(100) NOT NULL DEFAULT '', params text, lang
varchar(2) NOT NULL DEFAULT 'en', PRIMARY KEY (id) );
I'll try to look further into this
and will let you know what I find.
Thanks again, ingo
jfanque
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
25 January 2008 10:17
Anonymous
Ok, after some further testing I got it to work.
I
deleted all custom (non-limbo) DROP/CREATE TABLES and INSERTS
from the Limbo backup file and after that the import works just
great.
Still some minor things to adjust, like: *
delete unavailable drabot-entries from the database * fix
the Menu-ordering (which is reversed in Drake?) * ... but that's to be expected of course, considering all that you
guys did in the last couple of years!
Only one
final feature request for the Limbo-import might make sense: * Do not import components, modules and limbots that are
currently unavailable to the drake installation.
Apart from that: awesome work, guys! Can't wait to get
the Drake version fully online! I.
trex1512
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
25 January 2008 10:52
Anonymous
Good job ingo, the nonstandard componnets whas what I was
alluding to first up...still strange as the Limbo I was testing
with is one of the last fully loaded releases that had most of
the addins already added...
Anyway all ends that ends
well..
TerryF
legolas558
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
26 January 2008 19:25
Anonymous
Quote by jfanque:
At
first glance the Limbo DB backup looks good btw, it seems that
things only get messed up in the conversion process.
I'll try to get an anonymized version of the .sql file online
soon, so you can test it if you want.
Maybe I'll also
be able to help debugging this particular issue, when I have more
time soon.
Hi Ingo,
I am
really interested in such anonymized version of
the SQL file; you can submit it as a bug tracker
item, marking also it as "private", and I will
personally test it and (possibly) fix the conversion process to
take care of these problems.
We are officially
supporting Limbo CMS database backups, and that needs lots of
testing because those backups are usually badly formatted if
created by Limbo CMS.
I hope you can give a hand with
the Limbo CMS database support.
Thanks!
legolas558
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
26 January 2008 19:28
Anonymous
Quote by jfanque:
With
"conversion process" I was refering to the internal
conversion that Drake performs automatically when restoring an
old backup (that is: admin.database.lm_compat.php).
Although barely documented, there is a
complex fix-and-convert block of code (that mentioned by Ingo)
that fixes the SQL sources produced by Limbo CMS and converts
them into the DKDB format.
Quote:
As an example: My Limbo backup (file:
24_01_2008_10_44_10.sql) contains this section:
Code:
CREATE TABLE lm_users
( id int(10) auto_increment, name varchar(50) NOT NULL
DEFAULT '', username varchar(25) NOT NULL DEFAULT '', email varchar(100) NOT NULL DEFAULT '', password
varchar(100) NOT NULL DEFAULT '', usertype varchar(25) NOT
NULL DEFAULT '', published int(1) NOT NULL DEFAULT '1', gid int(3) NOT NULL DEFAULT '1', registerDate varchar(20)
NOT NULL DEFAULT '', lastvisitDate varchar(20) NOT NULL
DEFAULT '', PRIMARY KEY (id) );
After the restore failed, there is a new file in the backup
directory of my Drake installation, called
"1201198042_24_01_2008_10_44_10.sql_converted.php"
containing among other stuff the following, which gives 3
SQL-Syntax errors. Code:
CREATE TABLE #__users ( id int(10)
auto_increment, name text, username varchar(150) NOT
NULL DEFAULT '', email varchar(100) NOT NULL DEFAULT '', password varchar(100) NOT NULL DEFAULT '', usertype
varchar(75) NOT NULL DEFAULT '', block tinyint(4) NOT NULL
DEFAULT 0, sendEmail tinyint(4), gid tinyint(3
unsigned) NOT NULL DEFAULT '1', registerDate datetime() NOT
NULL DEFAULT '0000-00-00 00:00:00', lastvisitDate datetime()
NOT NULL DEFAULT '0000-00-00 00:00:00', activation
varchar(100) NOT NULL DEFAULT '', params text, lang
varchar(2) NOT NULL DEFAULT 'en', PRIMARY KEY (id) );
I'll try to look further into this
and will let you know what I find.
Thanks again, ingo
Mumble mumble...theorically a
standard DKDB should be produced, not one with MySQL-specific
syntax.
I will further investigate.
legolas558
Re: Problems Updating from Limbo 1.0.4.2 to Drake 0.4.10 RC 6
26 January 2008 19:30
Anonymous
Quote by jfanque:
Ok,
after some further testing I got it to work.
I deleted
all custom (non-limbo) DROP/CREATE TABLES and INSERTS from the
Limbo backup file and after that the import works just great.
Those shouldn't be touched by the lm_compat
code, if they were touched well..there's a problem Quote:
Still some
minor things to adjust, like: * delete unavailable
drabot-entries from the database * fix the Menu-ordering
(which is reversed in Drake?) * ...
the
menu ordering of content items is a problem specific of v0.4.10
RC6 which will be fixed in RC7
Quote:
but that's to
be expected of course, considering all that you guys did in the
last couple of years!
A total change of
design!
Quote:
Only one final feature request for the Limbo-import might make
sense: * Do not import components, modules and limbots that
are currently unavailable to the drake installation.
Isn't already possible to remove them after
restore? Or got any trouble at it?