Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
  • TomC Moderator

    With support for Joomla 1.5x nearing the end of it’s run . . . and it was a heckuva good run . . . we are encouraging most of our Members to update/migrate their sites from J1.5 to J1.7 (pending the particular needs and compatibility issues with one’s site/components, of course).

    For those of you who want/need to do this, here is the process – from the Wiki . . . .

    Don’t let the references to J1.6 fool or worry you – the steps are the same for updating for J1.7


    Before Upgrading
    Don’t let the numerical closeness of 1.5 and 1.6, mislead you. Joomla 1.6 took three years to develop and has been a major undertaking. Countless hours have been spent by many volunteers from around the world to put it all together. Although much of the code is the same from Joomla 1.5, much of it has been written from the ground up, and the changes are comparable to the changes from Joomla 1.0 to 1.5. Because the changes from Joomla 1.5 to 2.5 are so large and because of the massive effort put into getting Joomla 2.5 to where it is today, there is no core upgrade path, this is indeed a migration. In planned future releases of Joomla (which will be released every 6 months), such as Joomla 3.0, 3.5, etc, the changes from version to version will be more incremental and a core upgrade path is planned. Now that Joomla 2.5 is finally here and stable, a community initiative led by the developers of Joomla is turning towards jUpgrade (a 3rd party Joomla extension on the JED originally developed by Matias Aguirre) for help and to help. Many of Joomla’s developers (who are all volunteers that freely contribute their time) are volunteering to put the finishing touches on jUpgrade.
    jUpgrade allows you to migrate from Joomla 1.5 to 2.5. Lets get started!

    Review the Requirements
    Please, please save yourself (and possibly your clients) a lot of headaches and make sure that your server (and in the case of jUpgrade, your browser too) is up for the task. please review the technical requirements for Joomla! 1.6. Please review therequirements for jUpgrade as well.

    Before You Get Started
    Before you get started, there are a few things that you are going to have to check and/or think about:

    1. Is your Joomla 1.5 version up to date? The most up-to-date version of Joomla 1.5 is 1.5.25. If your version is not up-to-date, upgrade to 1.5.25 before migrating, especially if you are running Joomla 1.5.19 or lower, as JUpgrade does not support older versions. Read how to download older releases of Joomla!. You will need the Joomla! 1.5.0 to Joomla! 1.5.25 package with file name: < direct download link. Read how to update from Joomla! 1.5.x to the latest version how to update from Joomla! 1.5.x to the latest version.
    2. Do all your extensions have Joomla 2.5 native versions? You can use Advanced Search on the Joomla! Extensions Directory to see what extensions support 1.6/1.7/2.5. Please note that jUpgrade is not currently able to upgrade all Joomla 3rd party extensions, so those will have to be done via their respective upgrade procedures. Supported by jUpgrade on January 2012 are AdminPraise, Kunena, K2, JoomComment, Virtuemart, redSHOP, CommunityBuilder, JCE, Contact Enhanced, JomSocial, redForm, JEvents, Akeeba Backup, Jumi and redMEMBER.
    3. Have you modified any core files? Any changes that you have made to core files in Joomla will be lost so please be forewarned.
    4. Is there a Joomla 1.6 compatible template available from your template provider? If not, do you feel comfortable making the changes yourself? There are a couple good resources:
      1. Chad Windnagle’s Joomla Community blog
      2. Chris Davenport’s “Template Changes for Joomla 1.6” presentation
      3. Joomla’s Docs Template Tutorial Please note that although jUpgrade is not able to currently upgrade templates, the developers are working hard at implementing the feature.
    5. Is your language pack available in Joomla 1.6? Find your Joomla1 1.6 Translation.
    6. Do you have folder or file permissions issues in your Joomla 1.5 installation?
    7. Do you NEED to migrate to Joomla 1.6? Joomla 1.5 is powerful and very mature. For many people there is not a need to rush into Joomla 1.6. Joomla will continue to support Joomla 1.5 at least till April 2012, releasing security updates and bug squashing updates when needed.The two main features of Joomla 1.6 that makes it superior to Joomla 1.5 are: Access Control List (ACL) and nested categories. Gone are the days of simply having guests, registered users, authors, and editors, without being able to specify what they can and can’t do in the frontend. Also, with 1.6 you can have more flexibility of organizing (and therefore displaying) your content with nicely organized categories within categories. No more being restricted to the section >> category structure. Those are all great things to have (especially the ACL), however, for many 1.5 users, it isn’t needed. The main point is to decide for yourself.For a massive list of changes from Joomla 1.5 to Joomla 1.6, please see What’s new in Joomla 1.6.
    8. Backup, Backup, Backup
      Skipping this part is perhaps the biggest mistake you can make. If you have a proper backup (or several) you can always revert back if needed. However, if you don’t properly backup your site and something goes wrong, you are going to waste a lot of valuable time, and sometimes a lot money, getting things back to the way they were. So please backup!

      Using Akeeba to Backup

      • Akeeba Backup produces a .jpa file
      • The .jpa file contains all the folders/files and database files.
      • The .jpa file also contains an installer
      • Kickstart.php (from Akeeba) unpacks the .jpa file
      • You then run the installer and install your site like a Joomla install.
      • The installer has an option to change the configuration for restoring to a different location

      After you create the Database for your Joomla download and install Akeeba, it can be download from Joomla extension directory. There is a link to full instructions there as well.


      Download jUpgrade
      Download the latest version of jUpgrade. It is highly advisible, especially when development still is progressing, to always use the latest available version!
      Optional Testing Environment

      If you are really nervous by this point and your heart is beating fast, then you should probably set up a testing environment.

      Install XAMPP
      XAMPP is an easy-to-install package that bundles the Apache web server, PHP, XDEBUG, and the MySql database. This allows you to create the environment you need to run Joomla! on your local machine. The latest version of XAMPP is available at the XAMPP web site. Downloads are available for Linux, Windows, Mac OS X and Solaris. Download the package for your platform.
      Important Note Regarding XAMPP and Skype: Apache and Skype both use port 80 as an alternative for incoming connections. If you use Skype, go into the Tools-Options-Advanced-Connection panel and deselect the “Use 80 and 443 as alternatives for incoming connections” option. If Apache starts as a service, it will take 80 before Skype starts and you will not see a problem. But, to be safe, disable the option in Skype.


      As of August 5, 2010, XDebug has been updated (to version 2.1) which fixes some important bugs (for example, watching local variables for nesting functions). The latest XAMPP package (1.7.3) now includes this new version of XDebug. If you just want to update XDebug, you can download the latest module from [1]. There is a handy website that tells you which XDebug binary you need, depending on your phpinfo() information here. To use it, you just copy the output of your phpinfo() display and paste it into the form on the site.

      Installation on Windows
      Installation for Windows is very simple. You can use the XAMPP installer executable (for example, “xampp-win32-1.7.3-installer.exe”). Detailed installation instructions for Windows are available here.
      For Windows, it is recommended to install XAMPP in “c:xampp” (not in “c:program files”). If you do this, your Joomla! (and any other local web site folders) will go into the folder “c:xampphtdocs”. (By convention, all web content goes under the “htdocs” folder.)
      If you have multiple http servers (like IIS) you can change the xampp listening port. In <xamppDir>apacheconfhttpd.conf, modify the line Listen 80 to Listen [portnumber] (ex: “Listen 8080”).

      Installation on Linux

      Install XAMPP Open Terminal and enter:

      sudo tar xvfz xampp-linux-1.7.3a.tar.gz -C /opt(replace xampp-linux-1.7.3a.tar.gz with the version of xampp you downloaded). It has been reported that the MYSQL database of xampp 1.7.4 does not work with Joomla 1.5.22
      This installs … Apache2, mysql and php5 as well as an ftp server.

      sudo /opt/lampp/lampp startand

      sudo /opt/lampp/lampp stopstarts/stops all the services
      Test your XAMPP localhost server

      Open your Browser and point it to

      http://localhostThe index.php will redirect to

      http://localhost/xamppThere you will find instructions on how to change default usernames/passwords. On a PC that does not serve files to the Internet or LAN then changing the defaults is personal choice.

      Install jUpgrade

      Go to your Joomla backend. e.g.

      Extensions >> Install/Uninstall

      Browse >> Select com_jupgrade >> Upload File & Install

      Enable Mootools Upgrade Plugin

      1. Go to Extensions | Plugin Manager
      2. Search for “System – Mootools Upgrade”
      3. Enable the plugin

      It is important that this plugin is installed and that it has been set to enabled, as the proper functioning of jUpgrade depends on it.

      Configure Options

      As of jUpgrade version 1.1.1, support is present to migrate to Joomla! 1.6, Joomla! 1.7, and an old Molajo build. As well, for jUpgrade to be successful, you must configure your current table prefix prior to beginning the migration. The following are the options that can be configured with jUpgrade:

      • Distribution – Select whether to migrate to Joomla! 1.6, 1.7, or Molajo
      • Prefix for old database – Your current table prefix
      • Prefix for new database – Your selected table prefix for your migrated site


      • Skip checks – Skip pre-migration checks
      • Skip download – Skip downloading the package (Note: Must have a package already downloaded to your temp folder or set this and Skip Decompress if set to yes)
      • Skip decompress – Skip decompressing the downloaded package (Note: Must have a package already downloaded and decompressed to site_root/jupgrade if set to Yes)


      • Keep original positions – Keep the currently defined positions for modules


      • Enable Debug – Enable this to have messages displayed below the migration process concerning the progress, helpful if having issues


      Components >> jUpgrade

      Start Upgrade

      Do not exit the screen until everything has finished loading. Scroll down to check if finished.

      Please note that jUpgrade currently does not migrate templates, only default templates.

      Behind the Scenes
      As explained in the background information, the changes from Joomla 1.5 and 1.7 are quite significant. The fact that jUpgrade creates a new Joomla 1.7 installation for us is, in my opinion, pure genius. If the migration process was not 100% successful, your Joomla 1.5 is still perfectly intact and none of your users are affected. You have an opportunity to check out your site both in the frontend and the backend to make sure everything is up to par. So what actually happens? jUpgrade downloads the latest version of Joomla 1.7 for you to the jupgrade directory (which it creates) in the root folder of your Joomla 1.5 installation. It then extracts all the files from the download. Once extraction has completed, jUpgrade installs Joomla 1.6 and then proceeds to migrate your old database to the new Joomla 1.6 database which it has created. Your Joomla 1.6 site will be installed in assuming that your Joomla 1.5 installation is in your html root.

      Check Your Joomla! 1.7
      Please do a full site review of your Joomla 1.7 installation and make sure everything is set up properly. Your Joomla 1.6 site will be installed in assuming that your Joomla 1.5 installation is in your html root. Here is a general checklist to check:

      • Banners
      • Categories
      • Contacts
      • Content
      • Menus
      • Modules
      • Newsfeeds
      • Users
      • Weblinks
      • Templates – Work is currently being done on the template upgrade feature of jUpdate and it is not yet fully functional. Your module positions may have to be adjusted in module manager.

      Backup Joomla! 1.7
      If everything looks good to go, then let’s backup the new Joomla 1.6 installation.

      Overview of the Rest of the Process
      Quick overview of what we are going to try to do now:

      1. Relocate our Joomla 1.5 installation to a subfolder as a “just in case”.
      2. Relocate our Joomla 1.7 installation to the html folder.

      ‘It should happen in this order’ If you do it in reverse order, the Joomla 1.6 files will get mixed with the Joomla 1.5 files (many of 1.5 files will be overwritten) and you will have a big mess! Your site will likely still work, but it’s a security ticking time bomb waiting to go off.

      Going Live
      Next log onto your host’s file manager (e.g. cPanel, Plesk, etc) or an FTP Client, however, preferably a file manager. The general procedure is (it should take about 30 seconds if you review the steps before you start):

      1. Create a subfolder (e.g. myoldsite) for the Joomla 1.5 installation in your html root, e.g. public_html/myoldsite
      2. Select all the folders (***except the jupgrade folder***) and files in the html root and move them into the Joomla 1.5 subfolder (e.g. myoldsite)
      3. Select all the folders and files in the jupgrade folder and move them to the html root
      4. Double check the frontend and backend

      How to Manually Migrate Joomla

      If Jupgrade did not work out for you like many of us, you might want to consider manual upgrade. Be warned, however, that this process is very tedious (especially see step 6 below), and the procedure is not well tested as of yet (if at all). So just like the Jupgrade method, you will want to backup your database just in case. Before upgrading you should check to make sure every extension you want is joomla 1.6/1.7 compatible. Also back up your directory files just in case and keep a list of the extensions you used.
      Now onto the upgrade; please note that the following procedure should only be chosen if all else fails, and requires a good working knowledge of SQL! See the last paragraph of this section for a possibly less tedious alternative to doing steps 1, 2, 6 and 7) :

      Step 0:

      First of all, as always before big changes, backup all your data; that includes all files as well as exporting all database tables.

      Step 1:
      If you want, you can convert the prefixes of all the tables in your database. This is especially useful if you would like to keep your 1.5 database in parallel to your 1.6/1.7 installation, at least for the transition period. It is best done using a script; the “MySQL Table Prefix Changer Tool” available at Nilop is one that worked well.


      Executing this script will stop your old site from working because after the prefix conversion, your old installation can’t access the database anymore (it will still try to access the tables by their old prefix)! If you wish to re-enable your old Joomla installation, wait until the script has finished and import the database you exported in step 0.

      In order to run the script, first upload it via FTP to the root of your site. Now you can launch it by pointing your browser at (assuming you named the script “prefix.php”). The script will ask you for several pieces of information before it can do its job. Among them is of course the new prefix you wish to use for the new version of Joomla. Joomla 1.5 defaults to a prefix of “jos” — whatever prefix you choose make sure it is different from that; we recommend “jml” or “j16”, for example. Once you have filled in all the information, the script is ready to perform the prefix conversion.

      Notice in the following screen shot that the table prefix of our Joomla 1.5 installation is “jos”:

      For Joomla 1.6/1.7 you want it converted to “jml” as seen here:

      Step 2: Export all the database tables you would like to use on your Joomla 1.6+ site. Usually this corresponds to content and components.

      Step 3:
      Uninstall your old site including the database, files, and directories that are associated with Joomla. Or if you would rather just test the upgrade, skip this step and create a new directory for your joomla 1.6+ installation.

      Step 4:
      Install the new version of Joomla via FTP or cPanel. If you have no database associated with it, install a new database and user.

      Step 5:
      Install upgraded components and other extensions you used before onto your new Joomla 1.6+ site. This should be done now to prevent your old database tables from getting overwritten later. Note: It is possible that some developers made changes to the SQL schema of individual tables when they upgraded their extension to joomla 1.6+. We recommend that you check the documentation for each extension you had installed on your old Joomla site and for which you install an upgrade into your new Joomla site concerning special database upgrade considerations.

      Step 6:
      Convert the table schemas in the .sql file you exported in step 2 (containing your Joomla 1.5 tables) such that they are compatible with the version of Joomla! you are upgrading to. This is a very tedious process – you’ll have to check the database schemas for changes between the version of Joomla you’re upgrading from and the 1.6.+ version you’re upgrading to, and modify the SQL file accordingly. Note: This step could use a more detailed description, if you have ever done a manual Joomla migration, please help and share your experiences and knowledge here!

      Step 7:
      Import the upgraded .sql file into your Joomla 1.6+ database.

      Keep the following in mind:
      It is possible for settings to get lost depending on how each component stored them. From personal experience it worked just fine, but you may want to review the settings of each component.

      For an easier way to migrate articles, categories/sections, contacts, images, and users, be sure to use J2XML for exporting and J2XML Importer for importing the data.


      source –>


    TomC Moderator

    And when you’re ready to update from J1.7 to J2.5, see Bear’s HOW To UPDATE Joomla 1.7 to Joomla 2.5 video tutorial.


    TomC Moderator
    aardcom Friend

    First of all thanks to Joomlart for getting so many templates upgraded to 2.5 in such a short time frame.

    I was wondering if many JATC users were successful in using jUpgrade to migrate 1.5 to 2.5 with a JATC template. From what I am reading online it does not appear that many are successful and in fact most recommend a manual upgrade. Any comments or successful migrations.

    filmlover7 Friend

    Yes. We want to know the best way to get our site from 1.5 to 1.7 or 2.5.

    If anyone has had success, please tell us how you do it.
    Thank you.

    aardcom, did you have success?

    aardcom Friend

    We made several attempts but failed at the 1.6 upgrade before even getting to 2.5. I think it is issues with several 3rd party components. We are waiting for an update to one more component then will try again. In the meantime we have started with a manual transfer of articles to a 2.5 setup. Since we use K2 for articles the process should be easier in my view. It’s not ideal but likely will cause less issues in the end. I’ll post our results after.

    TomC Moderator

    Here are some additional resources with regard to migrating from J1.5 to J2.5 . . . .


    onedemian Friend

    Is it possible to migrate an older Ja Ores template to the new one for Joomla! 2.5?

    Thanks in advance.

    TomC Moderator

    Here is yet another tutorial resource – this one for UPDATING JOOMLA EXTENSIONS within J2.5

    Scott Lavelle Friend

    Hey all,

    I am almost complete with migrating from 1.5 to 2.5 on my site. I recently posted the 1.5 version in the “showcase” section of the forum. I’ve tried to do this on several occasions but have run into issues at one place or another until last week. A few things of note were that the 2.5.1 version of jUpgrade worked better for me, and there are a number of T3 related things that I had to do to get the whole thing to come accross.

    I think the biggest difference between success and not was the “discover” process I ran in the admin back end of the new site, which was able to “find” the T3 base template. Once that happened, I was able to apply it to my site and then I just had to deal with the individual 3rd party plugs (most of which failed in my implementation).

    One great piece of advice is to make sure that you are properly doing your templating if you are making mods to plugins – either code or css. Any sort of MVC stuff will need to be properly done or you will have a difficult time getting back to your individual customizations. Of course, this is always true, but especially so when you have so many other moving parts at once, such as during a migration (important distinction – this isn’t an upgrade…upgrades are easy).

    Hope this helps.

    Scott Lavelle - Technical Resource Solutions, LLC
    Certified Joomla Administrator

    TomC Moderator

    <em>@slavelle 313252 wrote:</em><blockquote>
    I think the biggest difference between success and not was the “discover” process I ran in the admin back end of the new site, which was able to “find” the T3 base template. Once that happened, I was able to apply it to my site and then I just had to deal with the individual 3rd party plugs (most of which failed in my implementation).

    One great piece of advice is to make sure that you are properly doing your templating if you are making mods to plugins – either code or css. Any sort of MVC stuff will need to be properly done or you will have a difficult time getting back to your individual customizations. Of course, this is always true, but especially so when you have so many other moving parts at once, such as during a migration (important distinction – this isn’t an upgrade…upgrades are easy).

    Hope this helps.</blockquote>

    THANK YOU for this MOST EXCELLENT insight and advice !!! This information is especially valuable because it is based on your own practical experience and success – rather than theory and “how it should work.”

    TomC Moderator

    Updating this link, as the info appears to have been updated itself –> UPDATING FROM AN EXISTING VERSION


    wrpaulsen Friend

    Those links are not so useful. They say to use jUpgrade, but that extension gets either 1 star or 5 stars, so people have had mixed success.

    And the link consists of just a video – which has poor quality screen shots and is not appropriate for trying to follow a series of steps.

    I’ve paid for a Joomlart template that was released in 2010, and I’ve paid for maintenance this year. Will Joomlart have any better migration support than just a link to another website?

    <em>@TomC 303357 wrote:</em><blockquote>Here are some additional resources with regard to migrating from J1.5 to J2.5 . . . .


    nataliia Friend


    I would like to do MIGRATING from J1.5 to J2.5 JA Teline IV
    I used jUpgrade, but it not work for me.

    I don’t have a lot money, but I can to pay a small fee for this work. How much a cost this work?

    Thank you.

    Anonymous Moderator

    <em>@nataliia 323420 wrote:</em><blockquote>Hi!

    I would like to do MIGRATING from J1.5 to J2.5 JA Teline IV
    I used jUpgrade, but it not work for me.

    I don’t have a lot money, but I can to pay a small fee for this work. How much a cost this work?

    Thank you.</blockquote>

    It’s will be difficult and time consuming to upgrade the site from 1.5 to 2.5.
    Your current modules are in 1.5, hence you need to remove all current modules and extensions. After that, you need to install new 2.5 extensions.
    Hope that helps.

    Viewing 15 posts - 1 through 15 (of 18 total)

    This topic contains 18 replies, has 10 voices, and was last updated by Anonymous 7 years, 7 months ago.

    We moved to new unified forum. Please post all new support queries in our New Forum