Question Move K1.7 from J1.5.23 to J.1.7

DJ wrote: Thank you to all. I must add this--I used SPUpgrade even though my work is all volunteer and I am so very thankful I did. I did need to do a substantial amount of work, but most things were right where they were supposed to be and it even (in this case) upgraded the template with one miner problem. etkritikonspoudon, please post how you make out if you do it--I am almost done the one site with the exception of Kunena and JQuarks and then we'll be ready to move it to replace the current site. Thanks again, Everybody! DJ

It's good to hear an encouraging case. I am also volunteering for the work and had my doubts about both paying for a migration extension and for taking the step sooner - in the coming months maybe Jupgrade will be made to keep the same ids as well or the process overall might become much easier? I don't know

Maybe you could answer a couple of questions about the extension?

- Does it copy all the data in the folders inside the older Joomla installation? If not, what does it include/leave out?
- What does it leave to be desired? What was difficult about completing the migration?

Cheers

I would be very caution with any component that migrates into J! 1.7 as there are many small details that can go wrong. JUpgrade also does very good job on migrating data and seems to work out of the box, but I've noticed that you can get some issues later because all data isn't 100% the same as it would be if you created a new site by installing J! 1.7. And those small details can be fatal later, when you try to upgrade Joomla.

The code that imports Kunena into J! 1.7.0 can be found from Kunena itself. It's located in administrator/components/com_kunena/install/j16upgrade.php and xml files.

Instead of paying one person from the migration I recommend everyone to work together by testing and fixing bugs together. Most of the bugs in JUpgrade are very easy to fix - if someone would just report them.

What comes to Kunena migration, everything inside Kunena will get migrated. What comes to other extensions: someone needs to add support for those. Adding support to most components is very easy: you just need to say what to copy over... This can be done either in the extension itself or in JUpgrade.

I have run jupgrade but it always 'hangs' when it gets to 3rd party upgrading. I was thinking it is because I have a very large kunena forum.

I have written on jupgrade forum with no response. I am running k1.7 on my j1.5.23 site so I think I can just copy out the database tables and import in my new j1.7 site

I think your are imported Joomla! data with jUpgrade, so you can import Kunena tables to your new site and launch Kunena 1.7.0 installation.

Sorry, to confirm, i run jUpgrade and select to not migrate 3rd party extensions. Then once that is done, export with phpmyadmin the kunena (K1.7) database tables from the J1.5.23 site and then import them into the new J1.7 site's database.. is this the correct method?

Would be good if jupgrade just did it all for me, but v1.2.1 just never finishes for me. Always just 'hangs/freezes' on the 3rd party upgrading phase.

thanks