Joomla 1.0.x to 1.5 migrator

pasamio · **Posted:** Mon Mar 24, 2008 3:34 am

@Slideri812: good to hear its resolved

@crow: The menu and the modules have some modification done to them on the 1.5 site of the fence. Basically the menu links are converted here to provide a 1.5 compatible set of links (e.g. content was rewritten so those are updated, etc). You can look at the PHP script to see what it is, they're mostly SQL updates that you could manually apply (there are some variables used in one so you'll have to bring that across but its possible, just not easy).

Check out this post:
viewtopic.php?t=55065

Assuming things are all good, uncommenting the mentioned line in your 1.0 site should give you a UTF-8 dump.

sarskirulz · **Joined:** Sun Jul 06, 2008 9:08 am **Posts:** 1

Hi all,

I am having a problem migrating from version 1.0 to 1.5.

I have installed the migrator component on my joomla 1.0 and have created and downloaded the .sql file that was created by the Migrator.

While I was installing joomla 1.5, during the Database setup phase, I have entered the name of the existing database that I will be using, let's just say that it's called me_.

Then during the Configuration setup phase, I have:
1. entered the Old Table Prefix, which is jos_
2. changed the Old Site Encoding into utf-8
3. entered the directory where I placed the .sql file created by the Migrator, and
4. ticked the "This script is a Joomla! 1.0 migration script." box

When I clicked the "Upload and Execute" button , it gave me this error:

Error at the line 10: INSERT INTO josjos_migrationjos_backlinks VALUES(1,"Home","index.php?option=comjos_frontpage&Itemid=1","index.php?option=comjos_frontpage&Itemid=1","");

Query:INSERT INTO josjos_migrationjos_backlinks VALUES(1,"Home","index.php?option=comjos_frontpage&Itemid=1","index.php?option=comjos_frontpage&Itemid=1","");

MySQL: Table 'me_.josjos_migrationjos_backlinks' doesn't exist

Stopped on error

I have checked the me_ database, and it does have jos_migration_backlinks table, so why is it saying that the table doesn't exist??

Can anyone please help me in this?

Thanks in advance,
Sarah

an52 · **Joined:** Sun Oct 22, 2006 7:26 am **Posts:** 15

I have a few 1.0.15 sites so I use Fantastico to install/update them.

I took a small site as a guinea pig and ran the migrator to get a SQL migration file. I removed the old installation and used Fantastico to install 1.54.

The migration instructions tell you to go to example.com/dev but I don't have this directory (owing to Fantastico) and so I never see the step-by-step installation process where you get a chance to select "Load Migration Script".

J 1.54 runs fine, but the site is currently empty.

How can I complete the migration?

pasamio · **Posted:** Sun Jul 20, 2008 7:49 am

@an52: If you've got a blank new install, you can use the migration assistant component which is installed into a 1.5 site and will accept a migration script. It then handles migrating the data where the installer would have handled it. It should be available at http://joomlacode.org/gf/project/pasamioprojects/frs just above the migrator. Most of the layout is the same. If you have any third party extensions installed, remove them first because the Migration Assistant will wipe out your entire site data and replace it.

You should be able to convince Fantastico to create a site in a subdir and to use that. The migration assistant will help you here. The main idea is that you don't kill your live site until you're absolutely certain your site is going to work after the upgrade.

@sarskirulz:

sarskirulz wrote:

2. changed the Old Site Encoding into utf-8

This is typically not the right setting unless you followed David Gal's old UTF-8 Joomla! 1.0 guide. May not cause issues anyway but unless you've gone through that guide its probably wrong. If you do experience an issue where some characters in the migrated site appear strangely and your database is in UTF-8 then follow David Gal's guide and re-run the migration script to generate a new file and rerun the migration with that. This should resolve the issue for you.

sarskirulz wrote:

Error at the line 10: INSERT INTO josjos_migrationjos_backlinks VALUES(1,"Home","index.php?option=comjos_frontpage&Itemid=1","index.php?option=comjos_frontpage&Itemid=1","");

Query:INSERT INTO josjos_migrationjos_backlinks VALUES(1,"Home","index.php?option=comjos_frontpage&Itemid=1","index.php?option=comjos_frontpage&Itemid=1","");

MySQL: Table 'me_.josjos_migrationjos_backlinks' doesn't exist
Stopped on error

I have checked the me_ database, and it does have jos_migration_backlinks table, so why is it saying that the table doesn't exist??

Well its saying the table "josjos_migrationjos_backlinks" doesn't exist. This is typically caused by not putting in a prefix and then putting one in without deleting the file /installation/sql/migration/migrate.sql somewhere along the line. It sounds like you're trying to upload things which may not be working, especially if you've tried the "I've already uploaded" option previously. Try deleting the above mentioned file and then trying to migrate again. Also try redownloading a fresh copy of the migration SQL file (or creating a new copy) from the 1.0 site just to be safe.

an52 · **Joined:** Sun Oct 22, 2006 7:26 am **Posts:** 15

pasamio wrote:

@an52: If you've got a blank new install, you can use the migration assistant component which is installed into a 1.5 site and will accept a migration script. It then handles migrating the data where the installer would have handled it. It should be available at http://joomlacode.org/gf/project/pasamioprojects/frs just above the migrator. Most of the layout is the same. If you have any third party extensions installed, remove them first because the Migration Assistant will wipe out your entire site data and replace it.

You should be able to convince Fantastico to create a site in a subdir and to use that. The migration assistant will help you here. The main idea is that you don't kill your live site until you're absolutely certain your site is going to work after the upgrade.

I couldn't find instructions for the script, so I tried the Joomla installer but it generated this error:

* JFile::read: Unable to open file: '/home/crm911/public_html/sem/tmp/migrationassistant.tgz'
* Unable to read archive

Warning: fopen(/home/crm911/public_html/sem/tmp/migrationassistant.tgz) [function.fopen]: failed to open stream: No such file or directory in /home/crm911/public_html/sem/libraries/joomla/filesystem/file.php on line 240
Unable to find install package

pasamio · **Posted:** Sun Jul 20, 2008 11:37 am

How very strange I'll put up a zip package and see if that fixes things. What environment are you hosting on? Does it not have gzip support?

pasamio · **Posted:** Sun Jul 20, 2008 11:40 am

Actually, I just thought that this might be something far simpler, can you check the permissions on your tmp folder and make sure that it is writeable. Look at Help -> System Info

an52 · **Joined:** Sun Oct 22, 2006 7:26 am **Posts:** 15

pasamio wrote:

Actually, I just thought that this might be something far simpler, can you check the permissions on your tmp folder and make sure that it is writeable. Look at Help -> System Info

/tmp is writable and I have no problem installing .tgz archives, so it is strange. Still same error.

pasamio · **Posted:** Mon Jul 21, 2008 1:44 am

Very strange, so your tmp, cache and media folders in your Joomla! directory are all writeable in the system info dialogue. Can you check your PHP upload limit to see if the file is under the that as well. Seems like a rather strange error to be having. Really sounds like something had a hard time uploading the file given its not there. Can you install something else? Below is a link to a simple test component, see if that works:
http://joomlacode.org/gf/download/track ... _alpha.zip

an52 · **Joined:** Sun Oct 22, 2006 7:26 am **Posts:** 15

pasamio wrote:

Very strange, so your tmp, cache and media folders in your Joomla! directory are all writeable in the system info dialogue. Can you check your PHP upload limit to see if the file is under the that as well. Seems like a rather strange error to be having. Really sounds like something had a hard time uploading the file given its not there. Can you install something else? Below is a link to a simple test component, see if that works:
http://joomlacode.org/gf/download/track ... _alpha.zip

I could not install the test component: "Unable to find install package"

Max upload permitted (shared server) is 2 MB.

pasamio · **Posted:** Mon Jul 21, 2008 10:56 am

Can you take a screenshot of the directory permissions tab in Help -> System Info and a copy of the upload_tmp_dir as well in the PHP information tab.

roggiero · **Joined:** Wed Feb 06, 2008 7:56 pm **Posts:** 3

I am trying to migrate from 1.0.15 to 1.5.3. I followed all the steps carefully, the sql dump created fine, and the migration process apparently went without problems. However, when I go to the new 1.5.3 site, this is empty. I checked the new database, and the tables are empty, like a totaly new installation. Not even a trace of the original site.

The only hint I have is that the migrate.sql dump is quite large (20 MB) and the internal php limit is set to 7MB. Probably that is the problem. May I use a compressed migration dump (i.e. migrate.sql.gz) instead of the uncompressed migrate.sql one?

Thanks in advance for your advise.

roggiero · **Joined:** Wed Feb 06, 2008 7:56 pm **Posts:** 3

Me again. I fount that migrate.sql.gz doesn't work.

So I tryied again with the 20M migrate.sql, and this time I got this error:

Quote:

Error at the line 16: INSERT INTO jos_migration_backlinks VALUES(124,"Cargar Im'2006-11-25 01:32:05','0','Unknown','Unknown');

Query:INSERT INTO jos_migration_backlinks VALUES(124,"Cargar Im'2006-11-25 01:32:05','0','Unknown','Unknown');

MySQL: 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 '"Cargar Im'2006-11-25 01:32:05','0','Unknown','Unknown')' at line 1

Detenido en un error

Any hint why I am getting this error?

pasamio · **Posted:** Fri Jul 25, 2008 12:29 am

I can't quite say from the message alone. Can you send me your original file (sam DOT moffatt AT joomla DOT org) preferably directly from your 1.0 site and I will have a look at it and see if I can work out what is going wrong. All fields should have been escaped when it left so I'm not quite sure whats going on.

pasamio · **Posted:** Fri Jul 25, 2008 2:50 am

It looks like an encoding issue, check that you're using the right encoding. By default 1.0 isn't UTF-8, it will typically be whatever your database is set to by default, which for most Latin character set languages is ISo-8859-1, but it may be different.

an52 · **Joined:** Sun Oct 22, 2006 7:26 am **Posts:** 15

pasamio wrote:

Can you take a screenshot of the directory permissions tab in Help -> System Info and a copy of the upload_tmp_dir as well in the PHP information tab.

I concluded it was something in my shared host's settings, not mine, so I moved the domain to my own VPS and the migrator worked just fine. Thanks for the help!

roggiero · **Joined:** Wed Feb 06, 2008 7:56 pm **Posts:** 3

You were right. Keeping the ISO-8859-1 encoding did the trick! Then, the migration went smooth. Even the Docman migration worked fine (after reinstalling Docman in the new site).

Thanks.

StealthyC · **Joined:** Sun Jul 27, 2008 5:11 am **Posts:** 3

Hello,

I'm migrating from 1.0 for 1.5.4. I recieved the following error.

Code:

Migration failed:

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 'WHERE `type` = "contact_category_table"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("catid=", link), 0, "view=category&"), `type` = "component", `componentid` = WHERE `type` = "contact_category_table"

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 'WHERE `type` = "contact_item_link"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=view", link), 20, "view=contact&id"), `type` = "component", `componentid` = WHERE `type` = "contact_item_link"

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 'WHERE `link` LIKE "%option=com_frontpage%"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = "index.php?option=com_content&view=frontpage", `type` = "component", `componentid` = WHERE `link` LIKE "%option=com_frontpage%"

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 'WHERE (`type` = "content_archive_category" OR `type` = "content_archive_section"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = "index.php?option=com_content&view=archive", `type` = "component", `componentid` = WHERE (`type` = "content_archive_category" OR `type` = "content_archive_section")

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 'WHERE `type` = "content_blog_category"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=blogcat", link), 17, "view=category&layout=blog"), `type` = "component", `componentid` = WHERE `type` = "content_blog_category"

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 'WHERE `type` = "content_blog_section"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=blogsec", link), 16, "view=section&layout=blog"), `type` = "component", `componentid` = WHERE `type` = "content_blog_section";

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 'WHERE `type` = "content_category"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=", link), LOCATE("&id=", link) - LOCATE("task=", link), "view=category"), `type` = "component", `componentid` = WHERE `type` = "content_category"

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 'WHERE (`type` = "content_item_link" OR `type` = "content_typed")' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=", link), 9, "view=article"), `type` = "component", `componentid` = WHERE (`type` = "content_item_link" OR `type` = "content_typed")

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 'WHERE `type` = "content_section"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=", link), 12, "view=section"), `type` = "component", `componentid` = WHERE `type` = "content_section"

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 'WHERE `type` = "component" AND link LIKE "%option=com_newsfeeds%"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = CONCAT(link, "&view=categories"), `componentid` = WHERE `type` = "component" AND link LIKE "%option=com_newsfeeds%"

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 'WHERE `type` = "newsfeed_category_table"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("catid=", link), 5, "view=category&catid"), `type` = "component", `componentid` = WHERE `type` = "newsfeed_category_table"

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 'WHERE `type` = "newsfeed_link"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("task=", link), 9, "view=newsfeed"), `type` = "component", `componentid` = WHERE `type` = "newsfeed_link"

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 'WHERE `type` = "component" AND link LIKE "%option=com_weblinks%"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = CONCAT(link, "&view=categories"), `componentid` = WHERE `type` = "component" AND link LIKE "%option=com_weblinks%"

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 'WHERE `type` = "weblink_category_table"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = INSERT(link, LOCATE("catid=", link), 5, "view=category&catid"), `type` = "component", `componentid` = WHERE `type` = "weblink_category_table"

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 'WHERE `type` = "wrapper"' at line 1 SQL=UPDATE `jos_menu_migration` SET `link` = CONCAT(link, "&view=wrapper"), `type` = "component", `componentid` = WHERE `type` = "wrapper"

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 'WHERE link = "index.php?option=com_login"' at line 1 SQL=UPDATE `jos_menu_migration` SET componentid = WHERE link = "index.php?option=com_login"

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 'WHERE link like "index.php?option=com_search%"' at line 1 SQL=UPDATE `jos_menu_migration` SET componentid = WHERE link like "index.php?option=com_search%"

pasamio · **Posted:** Sun Jul 27, 2008 5:32 am

What version of MySQL are you using?

Can you also email me a copy of your migration file as well.

StealthyC · **Joined:** Sun Jul 27, 2008 5:11 am **Posts:** 3

mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2

Which email address?

pasamio · **Posted:** Mon Jul 28, 2008 4:56 am

The email address mentioned four post previous to yours, sam DOT moffatt AT joomla DOT org

tngenewhiz · **Joined:** Thu Mar 23, 2006 5:04 am **Posts:** 29

pasamio wrote:

@an52: If you've got a blank new install, you can use the migration assistant component which is installed into a 1.5 site and will accept a migration script. It then handles migrating the data where the installer would have handled it. It should be available at http://joomlacode.org/gf/project/pasamioprojects/frs just above the migrator. Most of the layout is the same. If you have any third party extensions installed, remove them first because the Migration Assistant will wipe out your entire site data and replace it.

I had the same Error at Line 10 issue as Sarah (sarskirulz), but I didn't change the language setting.

One irksome issue: the Joomla 1.5.4 installer said "Migration Complete" when I pressed the PREVIOUS button and tried to restart the Migration. I didn't check the database -- I suppose it installed a blank database. Documentation would be helpful here.

So, I went to the link above and downloaded the Migration Assistant. I ran it on the brand new site, uploading the .sql file from my local machine. Things appeared okay, but all I saw was LOADSQLFILE in the window. After several minutes, I decided to look around. Some records were migrated; others were not (see next paragraph). May I suggest a "we're done" notice or something?

Was it done?

All my articles were present. ZERO Weblinks (of 104 in the 1.0.15 site) were transferred (so now how do I do that?).

My Main Menu has nothing but HOME as a link.

More troublesome, I found that only 469 of 585 users were in the User List.

I am only a novice at SQL, so I don't know how to begin comparing tables, converting them manually, and making sure things don't go haywire.

I hope some kind soul here can point me toward information that will guide me toward resolving these issues!

On a related note: what becomes of Static Content if I use the Migration Tools to move content from a 1.0.15 site to a 1.5.4 site?

pasamio · **Posted:** Mon Jul 28, 2008 7:50 am

For anyone reading this afterwards, if you have an issue, send me an email with a copy of your SVN dump and I'll try to replicate things. I have no issues with people sending emails out of nowhere to the email I've got above with issues relating to what I do with the migrator. For reference can you also send your forum ID as well so I can work out who you are easily. Just don't sell me something...

The installer will lock out any attempts to remigrate in a session because it cannot detect if your database is empty or if something didn't quite work somewhere along the line and the database has partial data. Its not the most friendly system in the world I do agree, but for the most part it is functional and short of redesigning the entire installer to accommodate things better its what I've had to work around with. The installer wasn't designed with this sort of bulk data import task in mind, which is rather unfortunate and leads to not quite as informative messages. I'm hoping this will be the black sheep with regards upgrading/migrating so we don't all have to go through this with 1.6 (yay!)

The line ten thing is usually when you've tried to migrate something more than once or when you've forgotten a prefix somewhere along the line (which is usually what happens when you get the josjos_migration_migrationjos_backlinks issue). As is stressed in the documentation, use a clean SQL file for each migration and this prevents this from happening.

Migration Assistant is still very much beta, its something I built in a day or so to help address some simple problems, first with configuration.php migration and then with a full migration. The full Joomla! install is even less friendly to migration with the migration assistant (replace a full instance from underneath of itself), however it should work most times. What is probably missing is a language file somewhere that probably hasn't come across in my packaging, LOADSQLFILE is actually "Loading SQL File...please wait." and it should display a "Migration Successful" message when its done. It can take a while to import because using PHP is rather expensive for this sort of an operation, so you will need to be patient. So it probably wasn't done, and might have been half way through your users table. If there was an SQL error it will usually throw up an error message informing you. Other tables after that might not have been migrated either if the process was interrupted and you may notice your menu links not behaving properly. Again, throw me your SQL file and I'll give it a hit in the installation migrator and the migration assistant to see if I can replicate some problems. These tools do require patience (I've left some large sites overnight but they still chugged away) I should probably give the migration assistant some more attention, and the migrator as well, but at the moment I'm busy making the update functionality for 1.6 work.

Static content will become uncategorised content when it is migrated and is managed in the same interface as everything else. If you find your web links don't come across when you do a fresh migration (remember to use a new file), then drop a line and I'll see if I can replicate that with your data.

Edit: added request for forum id when mailing me

tngenewhiz · **Joined:** Thu Mar 23, 2006 5:04 am **Posts:** 29

Thanks -- for the illuminating reply and for your efforts.

Before I send anything, I'll start the migration again and let it sit for a while. I have plenty of other stuff to do to get other sites ready to convert. A little distraction is occasionally nice! :pop

StealthyC · **Joined:** Sun Jul 27, 2008 5:11 am **Posts:** 3

pasamio wrote:

The email address mentioned four post previous to yours, sam DOT moffatt AT joomla DOT org

Sent

tngenewhiz · **Joined:** Thu Mar 23, 2006 5:04 am **Posts:** 29

pasamio wrote:

For anyone reading this afterwards, if you have an issue, send me an email with a copy of your SVN dump and I'll try to replicate things. I have no issues with people sending emails out of nowhere to the email I've got above with issues relating to what I do with the migrator. Just don't sell me something...

A quick follow-up --

It appears I'll be sending you a file. I ran the Migrator again from the 1.0.15 site and then went back to the new 1.5.4 site. Had to reinstall the Migration Assistant, because the failed Migration Assistant pass even wiped itself out!

The new file started uploading 10.25 hours ago, and it's still showing LOADSQLFILE. I aborted my original attempt after maybe 10 minutes, and at that time the script was done 3/4 of the way through the users table.

I took at peek at the public side of the site. The main site screen is up, with the default template, content assigned to the front page, and only HOME in the Menu.

I had a peek at the .sql file. It's 3161KB and 3220 lines. The Weblinks table was at the end. That explains why aborting my first attempt kept the Weblinks from migrating.

Additional observation edited later: I left the computer alone for another 4.5 hours. The screen still said LOADSQLFILE. So, I aborted. My initial attempt to login as administrator resulted in a simple message on screen: "invalid token." I hit back, thinking I'd return to the admin login screen, but it took me to the Site Control Panel. As far as I could tell, nothing had changed in the ensuing 4.5 hours. No additional users had been inserted; Weblinks were missing; public front page still shows only HOME in the Menu.

Here are some other questions I had --

* Does it make any difference in processing time/resources if you upload the migrator .sql file to the server?
* Is it possible to just execute the commands in the migrator .sql file as regular SQL queries?

The Migrator and Migration Assistant scripts are great tools. I appreciate your continued support of our issues here.

pasamio · **Posted:** Tue Jul 29, 2008 12:00 am

I'll test your file out later today to see if I can replicate things. What browser are you using and do you have JavaScript enabled?

The Migration Assistant will usually recreate itself after a migration but part way through a migration it will have removed itself as part of the process. It will also create a dummy user as well to ensure that you remain 'logged in' as the rest of the system is wiped.

Quote:

* Does it make any difference in processing time/resources if you upload the migrator .sql file to the server?

Once this file is uploaded via HTTP it doesn't make a difference because its on the server and processed in the same way from there

Quote:

* Is it possible to just execute the commands in the migrator .sql file as regular SQL queries?

Sort of. You can run them through and they should run, but you're also going to have to run the post migration steps otherwise your menu items are going to be broken because they're still using 1.0 style and 1.5 rewrote a lot of the way links are done.

tngenewhiz · **Joined:** Thu Mar 23, 2006 5:04 am **Posts:** 29

pasamio wrote:

I'll test your file out later today to see if I can replicate things. What browser are you using and do you have JavaScript enabled?

FF3.0.1, and yes to JS for this migration.

pasamio wrote:

The Migration Assistant will usually recreate itself after a migration but part way through a migration it will have removed itself as part of the process. It will also create a dummy user as well to ensure that you remain 'logged in' as the rest of the system is wiped.

That may be the state on my migrations that failed, because it never timed out the admin backend.

pasamio wrote:

Once this file is uploaded via HTTP it doesn't make a difference because its on the server and processed in the same way from there

Good to know -- thanks. I wonder if it may be the hosting company's processor... I shall alert them to this recent discussion, since they offer Joomla as a one-click install and are having to deal with customers upgrading to 1.5.4 (they did not keep a 1.0.x path in the one-click install options).

pasamio wrote:

{response to manually executing commands} Sort of. You can run them through and they should run, but you're also going to have to run the post migration steps otherwise your menu items are going to be broken because they're still using 1.0 style and 1.5 rewrote a lot of the way links are done.

I see. Could the less-experienced users (me!) recreate the menu manually? Of course, that would require all the extensions to have been successfully migrated first!

FWIW, I just realized the aborted migration assistant attempts did not insert any modules or components. I did not look at the .sql file to see where those queries are located.

I have sent the file separately and look forward to your observations.

pasamio · **Posted:** Tue Jul 29, 2008 1:25 am

tngenewhiz wrote:

I see. Could the less-experienced users (me!) recreate the menu manually? Of course, that would require all the extensions to have been successfully migrated first!

FWIW, I just realized the aborted migration assistant attempts did not insert any modules or components. I did not look at the .sql file to see where those queries are located.

Extensions should already be there in their normal form. It will be in the file sql/mysql/joomla.sql so I'm not quite sure what is going on there. The system runs that first, then the migrate.sql file, and then the post migration processes.

Recreating the menu isn't too much of an issue, all of the entries will be there but just pointing to the wrong place. Editing each menu item individually will fix things, though that isn't too much fun.

tngenewhiz · **Joined:** Thu Mar 23, 2006 5:04 am **Posts:** 29

Add'l follow-up: Web host tech support said they aren't aware of any other customers who've had migration issues.
The adventure continues! :geek:

Joomla! Discussion Forums

Forum rules

Joomla 1.0.x to 1.5 migrator

Quick reply

Who is online