Joomla! Discussion Forums

No, you've identified an issue with the Migration Assistant tool that occurs when you have a slightly larger SQL dump to load and the autoprogression doesn't behave the way it should. I've emailed you a new copy of the Migration Assistant that should fix the problem and if it does I will then proceed to publicly release it. If you haven't received the email, let me know and I'll post it somewhere else.

Trying to install the component Migrator RC7 even won't work for me. Get following error:

Warning: copy(/home/liquid/public_html/belle/administrator/components/com_migrator/migrator.xml) [function.copy]: failed to open stream: Permission denied in /home/liquid/public_html/belle/administrator/components/com_installer/installer.class.php on line 360
Upload component - Failed
Failed to copy file: /home/liquid/public_html/belle/media/install_48934791b3342/migrator.xml to /home/liquid/public_html/belle/administrator/components/com_migrator/migrator.xml

Hi Chamille,

Firstly try to get a more up to date release of the migrator, 1.0 is presently the latest release. Secondly the error is reporting that it can't create files on your install, check your file permissions and fix them up where necessary to install the extension.

Cheers,

Sam

Sam --

Re: "...you've identified an issue with the Migration Assistant tool that occurs when you have a slightly larger SQL dump to load and the autoprogression doesn't behave the way it should. I've emailed you a new copy of the Migration Assistant that should fix the problem and if it does I will then proceed to publicly release it."

Any idea when this newer version of the Migration Assistant might become more generally available? I, too, have a slightly larger migrate.sql file dump (2.1 MB) and the resulting migrated Joomla 1.5.5 site (migrated from a 1.0.15 site) is giving me fits. All of my content, sections, categories, and all but a few of my menus migrated over ok, but the new site does not behave as it should.

I'm working from my Linux Kubuntu based test server in order to familiarize myself with what I need to do before trying to replace my production 1.0.15 site with a new 1.5.x version. I set up a new clean standard model 1.5.5 site in order to have a comparison base line with my separate migrated target model. On the standard model all three of the provided templates sport three columns on the front page (and subsequent pages if I want them to). But on my migrated model only the Beez template gives me three columns. The other two templates only provide two columns. They seem to refuse to allow three columns no matter what. Further, 3rd party modules proven to work on 1.5.x sites install ok, but refuse to show up at all even if assigned to the first or second column (e.g "left" module location).

So, I'm thinking of trying to get the result I need by (1st) setting up a new clean standard site then (2nd) using the Migration Assistant to import my content, sections, etc., over. But the above discussion leads me to believe my larger migrate.sql file will fail to import all my stuff. The Migration Assistant version I have is the latest posted one from April 8, 2008. (To others who might be wondering, yes, I have tried the latest version of com_mtwmigrator to do the same thing. But it always leaves out key content items during the first pass and, contrary to the advice of its author, does not pick those items up on a subsequent trial. It just generates error messages.)

What do you think, Sam?

UPDATE!! NEVER MIND! Further research and fiddling with my template parameters fixed my problems. Now I feel like a fool. Oh, well. Live and learn.

Hi Tim,

Good to hear you've solved your problem. To answer your original question I'm hoping to have it out tomorrow (Monday) on JoomlaCode with a slight fix to the migrator as well. Menus are a bit problematic namely due to the way that they're designed, though the "Change Type" option for menu items mitigates this a lot. The rather unfortunate thing is that we completely changed how we handle menus from 1.0 to 1.5 (just look at the links that com_content generates in comparison) which isn't the most conducive to upgrade, as well as automatically disabling unknown links where possible.

Cheers,

Sam

I am interested in migrating. Can someone point me to a list/discussion on the differences between 1.0.15 and 1.5.1 so I can assess fully what is involved in terms of DB, comps, modules, procedures, etc.?

Will my current template work as is?

I think this is a good place to check out http://www.joomla.org/content/view/4483/118/
which I found in this also good discussion link here viewtopic.php?f=430&t=304018&p=1337490&hilit=why+migrate#p1337490

I think you should consider migrating from 1.0.15 to the much newer and improved 1.5.5, not 1.5.1 which is not old hat by a lot.



Without seeing it I really can't say. But most likely it won't work. And good free templates for 1.5 are very rare. But 1.5.5 does come with three good templates which you can customize.

Good luck!

If you enable legacy mode, a lot of templates will work out of the box. The ones that most likely won't work are the templates that build their own menu themselves or do a large amount of coding.

New error event to report:

After working through the various tests discussed in this forum and tweaking the migrated 1.5.4 site I'm creating, I needed to create a new migration dump from my 1.0.15 site in order to get the latest tables -- users, etc.

Even having clicked Purge Migrator Tasks in the Migrator Component -- as suggested in the thread at http://forum.joomla.org/viewtopic.php?f=430&t=292163&start=0&st=0&sk=t&sd=a -- I still got Fatal error: Call to a member function writeFile() on a non-object in /serverpath/administrator/components/com_migrator/admin.migrator.php on line 269

I haven't made any other changes to the new site (including not yet applying the 1.5.5 patch).

Suggestions?

That usually happens when you hit "Start Migration" and then a list of the select plugins appears and you click next. Don't click next at this point, as its actually retreiving the next page and progressing the migration which causes an issue because it thinks that two migration events are happening and usually wipes out some session data along the line. The next iteration (when I get a chance) will disable this when the JS autoprogression is set so that this issue is avoided in situations. Originally the plugin selection list wasn't a feature so you would have had to click next so it is a bit ambiguous in retrospect.

I have tried migrating from 1.0.13 to 1.5.7 (with 3rd party components like Joom!Fish and VitueMart) as follows, but I ran into trouble when migrating data with the migration.sql-file.

First I got Duplicate Entry in table jos_menu: I found a recommendation to empty this table just prior to the migration step.
Having done that I instead received Duplicate Entry error in table jos_modules: At first I tried emptying this table too, resulting in a successful install, but a site not working at all.

Then I found another recommendation to edit the INSERTs in the migrate.sql, to avoid duplicate entries:
So I changed the row with ID=1 to ID=2 for jos_menu, and the rows with ID=1...ID=15 to ID101...ID=115 in jos_modules. Now at least I get the administrator to work (still get 404 for the site), but a lot seems to be missing. Eg the Menu Manager is entirely empty.

Somehow I feel that changing the IDs isn't right, but I'm pretty clueless on how to proceed...

Could the encoding be part of the problem? I checked on the old site under System Info/PHP Info and ISO-8859-1 is the only encoding I can find mentioned.

Typically if you're getting duplicate key errors in the menu and modules it means that you haven't put in the right prefix and the system hasn't been able to appropriately mitigate for the pre-existing data that is inserted by the initial load of Joomla!.

If you're having issues, please read the official guide thoroughly:
http://docs.joomla.org/Migrating_from_1 ... 1.5_Stable

I really have tried to follow the mentioned guide to the letter, also I think I have enter the correct prefix.
Notable is also that the data is truncated when entered to the 1.5 site. It looks alright in the migrate.sql, but at the site e.g. "Ståhl" has become "St"

However, I will start the whole process over from the very start paying even closer attention to the guide

Now I have gone through the whole process again, but get the same problems.

I also did a sample installation (without any migration) which went perfectly well, also with Scandinavian characters working, just to test that things are working on that level.
Then I tried to manually insert stuff into the database from the migrate.sql - I started to think that perhaps I could upload the migrate.sql to the successful install. So starting with a insert to jos_menu from migrate.sql:

And of course this is not working as there is already an entry in the jos_menu with ID=1, so I get the duplicate entry error. And of course the automated migration process will get the same error. I am very confused...

What prefix are you using?

If you're losing characters along the way this is typically an issue with your encoding. Working out the correct encoding can be fun and it depends on how your original site was set up. If your database is actually set up as UTF-8, then you'll need to follow David Gal's UTF-8 Joomla! 1.0 guide and regenerate your dump file - I've seen this in one case where the site worked fine but the database was actually in UTF-8 so regenerating the dump file and reimporting it solved the problem.

This is an unfortunate hump that we'll get over with 1.5 which I'm going to be eternally grateful for (then all we need is PHP6 with native Unicode support and we'll all be happy) which should hold us in good stead moving forward. Alternatively you're in some other form of encoding, perhaps native to what ever your area is and I can't really help you work that out. The Linux/UNIX/Mac OS X command line tool 'file' should tell you what format the dump file is in.

Prefix is jos_

Will revert on the other questions in a minute...

When I run file I get the following:


Not only am I losing characters, but the posts, articles, etc get truncated after the first å, ä or ö. "Jag är verkligen hoppfull att UTF-8 kommer att spara en massa tid." is truncated to "Jag "

I'm in Sweden by the way...

Definitely sounds like an encoding issue. It seems to think that its ISO-8859, so the default should be right. The file encoding of different countries is beyond my level of knowledge, perhaps dropping a line in the Swedish forum might help. Alternatively trying the UTF-8 guide and regenerating the dump may solve it as well (it has before, and is worth a try).

Thanks a lot - I will try this!