
With Joomla 2.5 the upgrades are much easier, so I've decided to migrate all my Joomla sites to 2.5. There is a simple, new tool for making the transition, and it works - SP Upgrade. You may not need to do this today, but when that day eventually arrives, this tutorial will help you make this transition very smoothly. A note before we start: this extension is commercial. If you're looking for a free alternative, try our tutorial on jUpgrade. Step 1. Get ready to migrateTo make it quick, start with preparation.
Gathering the database information from the original site.![]() Before you start use a file manager or FTP to open your configuration.php file, All you need to know will be there. During the process you will need some information so you can fill in the fields correctly.
Tip: The path to your tmp or log folder will give you a clue to the path to your current J15 installation. Unless you changed the default tmp folder, it will probably say something like /home/username/public_html/tmp - just delete the /tmp from the path and you're at your Joomla 1.5 root. In this case, /home/username/public_html is what I need for now. If you changed the default path, you probably don't need any advice from me. Step 2. Check your J17 installation for MySQLi database installation.![]() Make this the first thing you do after you install J17. Check and/or modify the Global configuration. The first thing you'll see after you install the plugin is this warning, "Important Note: It is very important before you proceed with migration to make sure that your J16 installation is MySQLi and not MySQL (see note below in case it's not MySQLi). You can check from \Global Configuration\, tab \Server\, section \Database Settings\, field \Database Type\. "
Reading the comments online and some notes from the developer this seems to be the only stumbling block for beginners. In fact all the reviews are 5 stars on the JED except for one, and I'm betting that guy didn't do this first or didn't understand the note. If you have all the information ready, and understand how to fill in the forms, I can't see where you could possibly have any trouble using this extension. NOTE: MySQLi stands for My SQL Improved. You can get a quick explanation of it from Wikipedia or for the technical minded http:php.net has the manual online. Step 3. Download and install the plugin.![]() You can get the plugin from the JED. (Joomla Extension Directory) After you've downloaded it go to:
Step 4. Fill in the Database Information![]() All of this information is available in your configuration.php file. Refer back to Step 1. ![]() In the Template field, fill in the exact name that is on the directory in your templates directory. The template will be copied over, but if it is not compatible with J17, it's not going to work until you modify it. There was no updated version of the original template when I did this, so I just left this field blank and set to no. Everything was transferred and the default 2.5 template was used on the new site. Step 5. Monitor your progress.![]() You'll see pop up window that shows your progress through all the steps. Note that at the beginning of the progress log, it gives you some valuable information, so don't close the window right away when your finished. In this case I used the same username and password for the new site as the old, and as you can see here the plug-in added the old admin user but added v15 to the end to avoid conflicts. There were a few other messages as well. Nothing affected the migration, but you might want to look at these before you close this window. Step 6. Get ready to do the "hand work".![]() The last thing you see in the progress window is some advice on how to proceed from here. Also the path where you can find the log file for the migration in case you need to refer to it. It would be a good idea to record the path somewhere, just in case. The Original Site![]() On the original I have several modules published plus some graphics and a YouTube video. It's using RocketTheme Versatility 4 as the template. When I did the migration I did not specify any template migration. After migration![]()
The first time I tried this, none of the images originally showed, however on subsequent tests, everything transferred perfectly and I had no trouble. My problem was that I entered an incomplete path on the first entry form. If you look at the error log (See the message at the top of the image in Step 5), it shows that what i entered wasn't accessible, so images and templates were not transferred. If the images don't transfer, you can use a file manger to copy everything in the old images directory to the new one. Be sure to preserve the entire directory structure from the old site. J17 uses a different images directory ( no more stories directory in J17) and this plugin transfers the paths from the old site, so the easiest thing to do is maintain the folder and file structure for the images directory from J15. ![]()
Check for updates![]()
If you started with good preparation, you have everything you need at hand and can complete the rest of the migration fairly quickly. Work methodically and try not to rush. With J17, and Update as part of the Extensions component, maybe you won't procrastinate those security updates. |

With Admincredible you can update and manage all your Joomla sites. If you have 5 or 500 sites, Admincredible will make your life easier! Visit Admincredible.com.
All of our tutorials are published under the Creative Commons Attribution-NonCommercial license. This means:
Open Source Training is not affiliated with or endorsed by the Joomla, WordPress or Drupal projects.
All product names and trademarks are the property of their respective owners.
Copyright 2013 Open Source Training, LLC. All rights reserved.
Comments
Kind regards,
Nick
The beauty of this compared to jUpgrade is the fact that it does not alter or affect the original site in any way. OK, so I will be giving this a try in a few days and will
Thanks for this tutorial...
Tony
Kind regards,
Nick
I wonder, do you think that I should upload all of the components that are on 1.5 to the new site in preparation for SP Upgrade... for example I use DocMan and it is a repository that contains about 80 documents (I presume that the documents are in the database - correct?)... I also have NSPro, iJoomla Surveys, etc... All of these have 1.7 versions. So, I guess I am guessing that it would be beneficial to upload these???
I plan on buying the component -- just waiting for a response from the developer.
Cheers,
Tony
When I wrote the tutorial i tested it with adding the plugins before I did the migration and after.
It worked both times, but when you have uploaded modules or other content, you get various error messages in the progress window. They aren't a big problem, but will make extra work for you tracking them down to see if they are critical or not.
Best to start with a clean install and keep the error messages to a minimum.
Cheers,
Ed
Well, I decided not to upload as you are suggesting and I got your email when I was actually at step 1! In the middle of the process... should be able to report soon.
Tony
My site has been migrated using this component... this is so great and thanks for your assistance in this!
Tony
Kind regards,
Nick
I asusme this is not an option if I want to keep my languages working?
Well, I am not sure how you would do this; but I do know that 1.7 supports languages better than 1.5. The company providing the component SP Upgrade have already offered support. I would guess they would be able to answer you questions.
However, you really don't have anything to lose. It is quick and simple and does not affect your 1.5 site. I believe it is worth the 30 euros...
Good luck,
Tony
the money is not the issue, but I do have like 3 languages with joomfish as as K2 listimg of news and boats? what about K2? is there a link to the company support?
I never used K2 in my 1.5 sites (didn't need it). But my understanding is that K2 is not quite so necessary with 1.7. Perhaps one of the OS team could answer that query better than I.
Whatever, 1.7 is surely much more adaptable in many ways...
Tony
We recommend waiting until Joomla 2.5 (which comes after 1.7 and is a direct upgrade of 1.7) when Joomfish releases a compatible version.
Kind regards,
Nick
You should use jUpgrade if you're using k2, see:
getk2.org/.../...
and:
ostraining.com/.../...
Kind regards,
Nick
Mind contacting the developer for this specific issue as there could be many different reasons for the internal server error? Here's the link to the contact forum: cyend.com/.../contact-us
Kind regards,
Nick
Yes you can use this tutorial to upgrade my 1.5 site to 1.7. Keep in your mind and do it step by step. It should be work with you.
Cheers,
Hossam
I tried using CODA, transferring files from the upgrade to public_html, and got into a real mess! I had to have the site restored completely. I wonder if there is a 'foolproof' way to do this...
Using CPanel, CODA, etc...
Tony
What you can do is use cpanel to move the contents of your live site to a subfolder then move your test site (if you have it in a subfolder) to your live site folder (usually public_html). Here's a tutorial using cPanel:
ostraining.com/.../...
Kind regards,
Nick
Thanks for that 'link' to the cPanel option. I have CODA and use it a lot to modify files.. I tried to make my 'test' site the main site and screwed up royally... Not sure why, it wasn't easy and I had to create 'substitute' folders etc.. I got lost in the process. It appears that the DB's were not accessible after this transfer. I had the hosting company I use do a system restore! Back to square one, so to speak.
I am now rewriting the site (it is a smallish one, my business site) as alongcameaspide r.ca/dev. The next job will be to make this the 'live' site as alongcameaspide r.ca.
It appears that the tutorial on cPanel should solve this problem... So, I will indeed report back!
Tony
Kind regards,
Nick
You can just install it in a subfolder of your Joomla root.
Then you can use the advice that I gave Tony above (see: ostraining.com/.../...
Hope this helps!
Kind regards,
Nick
Could not connect. Go back correct db 1.5 info and try again. Access denied for user 'XXXX'@'localho st' (using password: YES)
and:
Warning: mysql_connect() [function.mysql -connect]: Access denied for user 'XXXX1'@'localh ost' (using password: YES) in /home/XXXX/publ ic_html/XXXX.co m/community2/ad ministrator/com ponents/com_spu pgrade/controll er.php on line 72
Any thoughts?
The script ran well the first time. Even a second time during testing. But as I was working out kinks in getting Kunena to work with it, I ran into this issue after uninstalling Joomla, starting fresh.
Anyone else get this ERROR?
Thx
Upgrade but as yet have notmanaged to get it to work. This is the error I get: Could not connect. Go back correct db 1.5 info and try again. mysqlnd cannot connect to MySQL 4.1+ using the old insecure authentication. Please use an administration tool to reset your password with the command SET PASSWORD = PASSWORD('your_ existing_passwo rd'). This will store a new, and more secure, hash value in mysql.user. If this user is used in other scripts executed by PHP 5.2 or earlier you might need to remove the old-passwords flag from your my.cnf file
Been when I configure my DB information from the target sites config file - I fill in the information, hit "save and close" and site says:
"Failed to connect to source database.
Update source database connection credentials in options. "
But can find no troubleshooting help.
were this up to be for J1.5? I don't understand why it has to be done on the new installation (2.5)
Any way, I ran the installation and I got this:
"Failed to connect to source database.
Update source database connection credentials in options."
I have tried with Mysql or Mysqli...
any help will be appretiated =S