Joomla! Discussion Forums

Incorrect table name ''.jos_ .'modules' SQL=INSERT INTO `'.jos_ .'modules` VALUES (35, 'Breadcrumbs', '', 1, 'breadcrumb', 0, '0000-00-00 00:00:00', 1, 'mod_breadcrumbs', 0, 0, 1, 'moduleclass_sfx= cache=0 showHome=1 homeText=Home showComponent=1 separator= ', 1, 0, '');

I am getting the same error with both using tables prefixed with jos_ and with other prefixes. I thought I would give it a try to see if I could force it to use it since they the jos_ seems to be inserted anyway.  I am also getting the duplicate key entry.

The migratory rc1 is out, but with a .tgz . Is this a component or a patch?  There seems to be very little in way of documentation for the new changes.

The first bug has already been fixed in the SVN.  I don't know what the status is of the second one.  If you get the first one, you should still be able to proceed as this happens at the end and everything should have installed properly.

I think we're still trying to mail down the cause of the second issue you mentioned.

The migrator component is a component to be installed in Joomla! 1.0.  There is documentation inside the component (which you click on it in the admin panel) and from what I understand an additional tutorial is being written.

Ian

I kept getting "Duplicate key" errors on migration, too. Happens with jos_menu and jos_modules. Truncating all tables before starting the migration script does not help.

My system:
J! 1.0.12 ---> J!1.5 RC1 (latest nightly)
Migrator RC1

I am fixing database errors as they come up and re running the migration. The problem is that the script is adding a _migration each time I do that so I end up with this after a couple of attempts

Error at the line 496: INSERT INTO jos_modules_migration_migration_migration

Where can I go to clear the record of previous attempts so that this doesn't happen?

Cheers

Christina 

I will be waiting for the tutorial too, tried to migrate from 1.0.12 with the coponent I downloaded 08-05-2007 and it won't 'work'  not sure why.  The component did create a file, I downloaded it, I removed the 1.0.12 site (just sample data, as I was testing on a 'sandbox' site first) then uploaded 1.5RC to that same space, ran the install and it quit on error in the migrate process.... I have some 'real' Joomla sites to migrate, looking forward to the 'cure'

I get this error when i try to load the migration script...

Has there been any fix to these issues.

im trying to migrate from 1.0.12 to 1.5 RC1 (Nightly as of 08/13) but I am getting the following errors



ive checked those lines and found

in the file.php file line 331 it is a start of a "else" statment.



in the help.php file line 858 its



i was unable to find that component  in the help.php file

Hi,

I hot the following error message. Any idea what can be done to resolve it?



Thanks

@kalimati: Where does that occur specifically? Do you have cookies enabled? These should have been defined earlier in the installation process at the DB setup screen, they shouldn't be disappearing at this point...

@those chasing documentation: its coming, a few set backs have been killing me (lost data in a few cases) but its coming in a blog and a web page and a lot of other stuff; there is this presentation that I presented at Joomla!Day Bangkok (got to do a blog post about that when I get time as well!): http://joomlacode.org/gf/download/frsre ... grator.odp

@re some strange bugs: there is a bug in the migrator task resumption code where a task was deleted prematurely during its execution which left some rows unconverted and the appearance that other tables were working perfectly fine (took me a while to track it down), and this could be solved by increasing the php timeout (prevented the error from appearing). As such I'm going to release an update to the migrator by the end of the week and some updates to the 1.5 installer and libraries in svn to better handle the failure of move_uploaded_files when the target directory is unwriteable. I'm still working on these changes and testing them.

@re duped entries: still trying to work out where this comes from, the quick solution is to run the SQL file through the uniq command and it will strip the entries for some that are duping. I have run into this and can replicate but i'm still diagnosing where it comes from

@re testing and large sites: with regards to testing I asked Brad Baker to throw me a copy of joomla.org and I have that loaded into a Joomla! 1.0.13 site. I'm successfully exporting from this site (it does take a while) a SQL dump file and also successfully importing it into Joomla! 1.5 though I am running the SQL file through uniq because for some reason I'm getting dupes as I'm still investigating. So it is possible at present and I'm still working on things.

Sam

Thanks for all the effort, Sam.  We appreciate your work. 
As for investigating dups, open up the db on a new 1.5 install after the DB setup page during the install.  You will see that it is not empty, and there are rows in jos_menu and jos_modules.  I believe this is where the dups are coming from...

Thanks for the update Sam

Im looking forward to the updates to see if they work for my sites.
Ive been using joomla since the early days and I love it,  I cant wait to get my site updated to 1.5.


keep up the good work. 

@archangel519: This is a different problem, as the migration system in 1.5 actually recreates a seperate modules and menu table to migrate them so things don't clash. This is probably caused by not using jos_ as the prefix in the final migration screen. I'm wondering if this is something I want to keep because it seems to have caused more confusion than anything (was aiming for simplifying the documentation into a set of easily reproduceable steps and in doing so wiping out the old site prefix and making it jos_ for simplicity sake).

I've read this thread and there are tantalizing hints, but not sure how to apply them to my situation.

I had a full site up in 1.013, and backed up the sql database in phpmyadmin. I uploaded all the 1.5 files to my server, and now want to put the old data back into the new site. Is this possible from the new 1.5 install? Or do I need to put back the 1.0 files, install a migrator component (like this one: http://joomlacode.org/gf/project/pasami ... se_id=5090), and migrate the db, THEN upload the 1.5 files?

Not sure what to do. I want to be able to bring my old data over into a new 1.5 install. Is that possible?

thanks in advance.

rob

I tryd truncating all tables that give trouble but then your admin panel is empty 

@roblef: You will need a 1.0.13 install because the migrator performs row by row transformations on some tables on export of the data. I decided to this on the exporter since we're grabbing everything row by row instead of putting it into the 1.5 side (which has some heavy queries but since its executed by mysql skips the script timeout issue we'd get for that aspect). You could import it directly into 1.5 but you would lose a lot of information in the process as well as having to strip out some tables. Its possible but it would result in data loss.

@ljd: not sure what you're doing. if you wipe out the modules table it will clearly kill the admin modules in your install because they're in there as well...

Yeah i noticed that  

I just trying to help you out 

I cannot get the migrator to work for me. Here's the steps I'm taking:

1. Install the migration component on my 1.0.13 site.
2. Use it to create the migration SQL
3. Download the migration SQL to my test server, where I will be trying 1.5
4. Point a browser at the test server and go through the initial steps. I've created a new database for the 1.5 install to use as part of the process.
5. Click "Load Migration Script" instead of "Install Sample Data"
6. Provide "jos_" as the table prefix despite the fact that my old table prefix is not "jos_". This quirk is really bush league, by the way.
7. Click "this script is a Joomla! 1.0 migration script."
8. Start the process with the "Upload and Execute" button.

I invariably get this error:

Migration failed:

Incorrect table name ''.jos_ .'modules' SQL=INSERT INTO `'.jos_ .'modules` VALUES (35, 'Breadcrumbs', '', 1, 'breadcrumb', 0, '0000-00-00 00:00:00', 1, 'mod_breadcrumbs', 0, 0, 1, 'moduleclass_sfx= cache=0 showHome=1 homeText=Home showComponent=1 separator= ', 1, 0, '');

What's the deal?

Update: Above, someone suggests:



However, choosing "next" from the screen that presents the error above loops me back to the upload-your-migration-script screen. It's not "done" by any stretch, so the install isn't usable.

If the error IS fixed in a post-RC1 rev, can someone tell me how to get a fixed version?

Sam has indicated that a new update to the migrator will be released in the coming day or two.  My suggestion would be to wait and try out your migration with the updated migrator. 



the jos_ prefix is used becuase the migration component converts the prefix to jos_, even if you had a different prefix.  There has been discussion on whether this will be changed or not to allow different prefixes.  Not sure what the final decision will be.


Comments like this are not constructive.  If you feel that something needs to be changed, either contribute code or something else that will benefit the cause.  That's the  beauty of Open Source! 

A little question...

I have a 1.0.12 Joomla site in the root. I want to upgrade to 1.5 . Where must i install it?

In a subdirectory? And the database? the same DB as the 1.0?

Thank you guys

I suppose I'll try again next week, then. I'd love to see clear documentation of  what the migration tool is doing, by the way. Does any exist?

I'm sorry you feel my commentary was inappropriate. Frankly, though, I stand by my evaluation. I understand the OS world, and have been working with, on and using FOSS packages for a long time. It's unusual to me to see a quirk like this one, which is why I said something.

@Gianmarco: Create a whole new site on your server. Don't put the 1.5 files in the same folder as your 1.0.12, or even in a subfolder. For example, on my box, I have

/var/www/mydomain.com (where the joomla 1.0.13 site lives)
and
/var/www/joomla15 (where the new joomla files live)

When I'm happy with 1.5, I'll make the required directory-name adjustments (and apache & joomla config file changes) to make IT the live site.

chetman, can you give me an helping hand with the joomla migration?

I want to know if there is a bug in the migrator or i' m the bug

Sam just posted this article, hope it helps:
http://www.joomla.org/component/option, ... 105/p,401/

just seen....tank you

Good, and I actually thought so, decided to post the link anyway so that other readers of this thread will notice it too.

Hi all,

I have updated the migrator to fix issues with duplicates and some other issues. It still resets the prefix to jos_

http://joomlacode.org/gf/download/frsre ... or_rc2.tgz

Additionally there have been some changes made in the 1.5 trunk SVN that should remove some other issues that might be encountered. So update everything to the latest version and see how things fare,

Sam

tahnk you sam, i' ll try it!!!

Installed the migrator:

Warning: Call-time pass-by-reference has been deprecated - argument passed by value; If you would like to pass it by reference, modify the declaration of makeHeaderTableDef(). If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file. However, future versions may not support this any longer. in /var/www/vhost/gianmarcoodorizzi.com/home/html/administrator/components/com_migrator/legacy/legacy.php on line 219

On the top of the com_migrator

Thought I got all of those wiped out, thanks Gianmarco fixed in SVN.

Thank you Sam.
A question: must the new joomla 1.5 installation be in the same DB of the 1.0?

Thank you

I got this and couldn't get around it so after messing with the helper.php script unsucessfully I just commented out the INSERT INTO line after  // "Put in breadcrumb module as per sample data" around line 1287 in installation/installer/helper. The installer worked great (always use a clean database) then I logged into mysql and entered the following lines.

use joomlatest;                                        <- my database name
INSERT INTO jos_modules VALUES (35, 'Breadcrumbs', '', 1, 'breadcrumb', 0, '0000-00-00 00:00:00', 1, 'mod_breadcrumbs', 0, 0, 1, 'moduleclass_sfx=\ncache=0\nshowHome=1\nhomeText=Home\nshowComponent=1\nseperator=\n\n', 1, 0, '');
quit;

And everything seems to be fine. I'm sure the bug is small (and has been fixed) but I didn't have time work it out. As a note I was using com_migrator RC2 and Joomla 1.5 RC1.

Grant