Migrating Mambo 4.5 Stable-1.0.9 to Joomla 1.04

Gregorius · **Posted:** Fri Dec 02, 2005 3:55 am

I have a Mambo 4.5.1 site that i need to migrate to joomla. I have customised quite alot of the site, so i think doing a straight migration might be a problem...

i'm thinking the best way to do it would be to somehow migrate the content across to joomla, and then rebuild/ reconfigure the rest of the site to run on Joomla..

Does anyone know how i can achieve this, or perhaps suggest a better way to perform this migration.

The site in question is http://www.doofcentral.com - its a big site so i really have to plan this quite well...

Some things to note:
1. i will be using a new forum system so migrating the current forum (Simpleboard) is not necessary
- although if anyone knows how to migrate forum content from simpleboard to SMF would be grand
2. i will be using a differnet events system so dont need to migrate the events component
3. coppermine is not yet integrated so i'll hold off on integrating until the migration is complete
4. i will be installing a new links component, so not too worried about the links
5. Contact page was build with Phil-a-form.. i will probably not use this anymore as its proved quite buggy and troublesome, so no need to migrate that.

Hoping some of you guys can offer some good advice on how i can achieve this migration as smoothly as possible.

thanks heaps in advance
Greg

Gregorius · **Posted:** Wed Dec 07, 2005 1:17 am

So nobody can offer any advice on this migration??

absalom · **Posted:** Wed Dec 07, 2005 1:24 am

See here:
http://forum.joomla.org/index.php/topic,10120.0.html

Gregorius · **Posted:** Wed Dec 07, 2005 1:36 am

Tahnks absalom, but not much info there either.

Just posted this over there too... wondering what you guys think about this:

I have rebuilt a few parts of the site with Phil-a-Form... but i guess i can just do these again on Joomla - i dont think i'll Use PAF again.

So i'm thinking of trying this:

1. create a copy of my site
2. backup entire database and files
3. uninstall all components from the copy
4. upgrade the copy site (should be a pretty basic install at this point)
5. reinstall components on joomla

Has anyone tried this approach for a (slightly) hacked installation? Any comments?

Cheers
Greg

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

As long as the hacks are only made in files, you should be ok. My site had a few custom changes which I luckily documented. Once I changed it, I did them again in the new Joomla code. I started out from 4.5.2.3, and not from 4.5.1 though.

Gregorius · **Posted:** Wed Dec 07, 2005 9:51 am

Thanks for the info Tonie... Unfortunatly i didn't document my hacks, and they were all done about 2 years ago so i dont remember the extent of them, but i'm pretty sure they were all just file hacks and not DB hacks, so hopefully that means i can upgrade...

i mgiht give it a try.. will let u know how i go.

cheers
greg

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

From 4.5.1 to Joomla 1.0.4, quite a lot of code has changed. You probably would have to rewrite some core hacks anyway. Good luch with the migration!

Gregorius · **Posted:** Wed Dec 07, 2005 10:27 am

Tonie wrote:

From 4.5.1 to Joomla 1.0.4, quite a lot of code has changed. You probably would have to rewrite some core hacks anyway. Good luch with the migration!

What do u mean i probably would have to rewrite some core hacks? do you mean core hacks that i performed before (i'm expecting this, or actually hoping i can get away without having to do it due to the many extra components available now), or that i'd have to hack the joomla core to make the upgrade work?

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

Because code is different betwee 4.5.1 (Mambo 4.5.2) and Joomla 1.0, some core hacks you applied on 4.5.1 might not work exactly the same on Joomla 1.0 if you applied them by just copying and pasting old code.

Gregorius · **Posted:** Wed Dec 07, 2005 10:41 am

Ah yup, thats what i thought... really all i want to migrate is the core content (features, news, etc), and will redo templating and hacks after... just didn't really want to have to re-enter hundreds of pages of content.

thanks

iainshaw · **Posted:** Sat Dec 10, 2005 12:09 pm

It's not even from 4.5.1, this is a migration from 4.5.0 - 1.0.9 ins't it?
Let us know how you get on - I'm still planning my migraiton from 4.5.0.2

Gregorius · **Posted:** Sat Dec 10, 2005 1:36 pm

iainshaw wrote:

It's not even from 4.5.1, this is a migration from 4.5.0 - 1.0.9 ins't it?
Let us know how you get on - I'm still planning my migraiton from 4.5.0.2

Yes, I think you're right Iain. I'm pretty sure it wasn't yet 4.5.1... in the credits it states "4.5 Stable-1.0.9". Dunno what that means, but from memory i think 4.5.1 was released after i'd set this site up.

As for how i got on.. not so good. My hosting provider, siteground, has attempted a few times to do the upgrade for me, but failed each time. The last attempt i removed all third-party components, deleted 3p component database tables, stripped it down to a bare installation (with content), but still they could not do it. I'm waiting to hear what errors they got, but they have pretty much said, in not as many words, that it can't be done. I already have a fresh joomla installation, so i might just start the (horribly tedious and time-consuming) task of migrating my content manually.

If anyone out there can suggest anything else, perhaps for content migration, i'm all ears.

thanks for the assistance guys, unfortunately i think i'm out of luck on this one.

cheers
greg

Gregorius · **Posted:** Sat Dec 10, 2005 11:54 pm

Quoting my host, who attempted the upgrade:

"The sql query for the upgrade hasn't been successful. It returned no detailed errors I can provide you with.
After that I couldn't continue with available upgradeable version."

shen brood · **Joined:** Sun Dec 11, 2005 4:41 am **Posts:** 127

I think the best way is to upgrade first to Mambo 4.5.2 and then migrate to the latest Joomla since that will be easier right .. or migrate to Joomla 1.0 then upgrade it.

Gregorius · **Posted:** Sun Dec 11, 2005 5:06 am

I dont even think they were able to upgrade to Mambo 4.5.2 ... they reckon there are database issues (corruption or something).

i really dont know.. all i know is i'm almost ready to give up and just rebuild the site from scratch.. which sucks but might just be the only way to go.

kenmcd · **Posted:** Sun Dec 11, 2005 8:40 am

The Mambo 4.5 Stable-1.0.9 to Mambo 4.5.1 SQL upgrade file (upgrade45_109to451.sql) has some errors which may be the problem.
There are duplicates for some of the entries made in the 4.014 to 4.5 SQL file (upgrade4014to45.sql).

Commenting-out the duplicates may allow the upgrade to complete properly.
See attached file: upgrade45_109to451_fixed.sql.txt

FAQ: Upgrade Mambo to Joomla
I have been working on an FAQ to document the Mambo to Joomla upgrade process.
Many people will have to do a step upgrade.
Mambo 4.014 > 4.5.0 > 4.5.1 > 4.5.2 > Joomla 1.0 > Joomla 1.1

I have not been able to determine where the duplicates above are coming from.
The entries are not in the 4.5.1 installation SQL file.
If the entries were introduced in 4.5.0, they should be there in 4.5.1.

Does any one know where I can get a copy of full installation files for Mambo 4.014 and Mambo 4.5.0?

Thanks.

Gregorius · **Posted:** Sun Dec 11, 2005 11:04 am

Hmm interesting.. I've had a quick look at that script, and it seems some of the tables it tries to insert rows into don't exist in my database, for example, mos_templates_menu

Apparently this is one of the errors my hosting company had when they tried to upgrade, so i think your script would give the same error as the table doesn't exist (i just checked).

any idea why it wouldn't exist on my current site? and how important that table is?

kenmcd · **Posted:** Sun Dec 11, 2005 1:23 pm

Gregorius wrote:

Hmm interesting.. I've had a quick look at that script, and it seems some of the tables it tries to insert rows into don't exist in my database, for example, mos_templates_menu

Apparently this is one of the errors my hosting company had when they tried to upgrade, so i think your script would give the same error as the table doesn't exist (i just checked).

That is why those lines are commented out.

The # at the beginning turns the line into a comment with no effect on the database.

kenmcd · **Posted:** Sun Dec 11, 2005 1:59 pm

kenmcd wrote:

Does any one know where I can get a copy of full installation files for Mambo 4.014 and Mambo 4.5.0?

Thanks.

Nevermind.
I found 4.5-1.0.9 on JoomlaOS.de and 4.014 on SourceForge.

Gregorius · **Posted:** Sun Dec 11, 2005 11:14 pm

kenmcd wrote:

That is why those lines are commented out.

The # at the beginning turns the line into a comment with no effect on the database.

Ahh good point.. sorry i didnt notice that. Will try that script and let u know how i go.

cheers
greg

Gregorius · **Posted:** Mon Dec 12, 2005 2:04 am

Yaaay i ran the script and it worked... so now in admin backend it looks just like before (assumedly because i need to upgrade the filebase too?)

The frontend reports that "Template File Not Found!", and when i try to publish a different template in the backend, it doesnt work. Any idea why this is so?

Backend reports version number 4.5 Stable-0.2 [Spider Recoiled] 02-Jun-2005 03:30 GMT ... is this correct? Would the Help > Credits report the latest database number, or filebase number?

Is there a filebase patch to upgrade from 4.5.0.1.09 > 4.5.1, or should I just overwrite the filebase with the 4.5.1 filebase??

I think i'm actually getting somewhere now... yaaay, i was just about to give up too. Thanks heaps Ken.

Gregorius · **Posted:** Mon Dec 12, 2005 2:24 am

Okay, making some progress but have some issues, firstly the frontend now shows these errors:

Code:

Notice: Table 'doofcent_forupgrade.mos_templates_menu' doesn't exist in /home/doofcent/public_html/FORMODDING/includes/database.php on line 184

Notice: Table 'doofcent_forupgrade.mos_templates_menu' doesn't exist in /home/doofcent/public_html/FORMODDING/includes/database.php on line 184

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/includes/mambo.php on line 274

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/index.php on line 192

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/index.php on line 193

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/index.php on line 194

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/index.php on line 195

Warning: Cannot modify header information - headers already sent by (output started at /home/doofcent/public_html/FORMODDING/includes/database.php:184) in /home/doofcent/public_html/FORMODDING/index.php on line 196
Template File Not Found! Looking for template:

Also, the backend logs in, but shows these errors:

Code:

Notice: Table 'doofcent_forupgrade.mos_templates_menu' doesn't exist in /home/doofcent/public_html/FORMODDING/includes/database.php on line 184

Notice: Table 'doofcent_forupgrade.mos_templates_menu' doesn't exist in /home/doofcent/public_html/FORMODDING/includes/database.php on line 184

So it seems those tables that didn't exist originally now need to exist... is there a script to fix these problems?

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

That table is the following in joomla.sql in the /installation/sql directory:

Code:

#
# Table structure for table `#__templates_menu`
#

CREATE TABLE `#__templates_menu` (
  `template` varchar(50) NOT NULL default '',
  `menuid` int(11) NOT NULL default '0',
  `client_id` tinyint(4) NOT NULL default '0',
  PRIMARY KEY  (`template`,`menuid`)
) TYPE=MyISAM;

#_ needs to be replaced with mos in your scenario.

Gregorius · **Posted:** Mon Dec 12, 2005 8:21 am

Okay, so the backend works fine now, but still the front end shows the same errors.

seems strange because the table does exist now.

I've tried changing templates.. tried a few different ones, but none of them change anything on the front.

Could it be because the mos_templates_menu table is now empty? Do i need to run a script to insert some records?

lol... baby steps hey. but at least we're getting somewhere.

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

There are only two rows in that table, one for the frontend template and one for the backend template. Here is the sql code:

Code:

INSERT INTO `mos_templates_menu` VALUES ('joomla_admin', 0, 1);
INSERT INTO `mos_templates_menu` VALUES ('name_template', 0, 0);

Exchange name template with the template of your choice. Make sure that the table is empty before adding.

Gregorius · **Posted:** Mon Dec 12, 2005 9:09 am

woohooo.. we're getting somewhere... i can see the front end now, but having some template issues...

1. after each category link, it shows the description for that category (should only show on the actual category page)
2. error on the category pages:

Code:

Notice: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 9 in /home/doofcent/public_html/FORMODDING/includes/database.php on line 184

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

What version are you on now? Still on Mambo, or already on Joomla?

Gregorius · **Posted:** Mon Dec 12, 2005 9:34 am

i'm on mambo 4.5.1

slowly slowly working my way towards joomla... its no easy feat let me tell ya

Tonie · **Joined:** Thu Aug 18, 2005 7:13 am **Posts:** 13187

I don't have access to that version at the moment, but it probably means that a few columns don't have a value where they should. I will check when I get back home.

Gregorius · **Posted:** Mon Dec 12, 2005 9:59 am

Ok cool.. thanks Tonie.. so its a template issue?

I'm going to have to do all of this again soon, once i've go the procedure sorted... as i have new content on the site since i started the 'test migration'... i guess once i have the templating and filebase all under control, it'll just be a matter of upgrading the database again. then installing all the components again. argh.

Joomla! Discussion Forums

Forum rules

Migrating Mambo 4.5 Stable-1.0.9 to Joomla 1.04

Quick reply

Who is online