Practical Guide Upgrade Joomla 2.5 to Joomla 3.x

[leolam]

This is a Practical Guide for upgrade/mini-migrate an existing Joomla 2.5 site to Joomla 3.x for those who want to (mini-migrate) to Joomla 3.x with it's exciting new features!

Going from Joomla 2.5 to Joomla 3.x is a (mini) Migration!!!

It is NOT a simple upgrade!

Joomla 2.5.28 can only be migrated in 2-steps at the moment. First migrate to 3.5.1 . You then need to upgrade from 3.5.1 to the latest 3.x through the one click installer

The guide is a basic guideline. Please post questions if you get stuck?
Before doing anything

BACKUP YOUR SITE!

(use Akeebabackup or similar for that! but whatever you use: BACKUP!)

then:

Step 1: Check that your server supports the requirements
Before doing anything you have to clarify that your hosting environment is suitable to host Joomla 3.x. The technical requirements are outlined clearly in this article on Joomla.org

Any good host is able to run Joomla 3.x. Nothing is special in the requirements! In case your host cannot provide the correct environment to support Joomla 3.x: CHANGE HOST

So assuming all is in the clear with the requirements you go to the next step!

Step 2: Check all extensions compatibility with Joomla 3.x!
Once again (and make a note of what you are doing on a piece of paper so you will remember!) before doing anything yet go and check all extensions (templates/components/plugin/modules) and make sure that any of these extensions are Joomla 3.x compatible. For sure when you have installed a Joomla 2.5 template you will need to change this with a Joomla 3.x compatible template. In general you can see in the Joomla Extension Directory pretty clear that an extension is compatible. (note: sometimes extension developers do not update their account on JED so double check on their website I suggest?)

Just look at this image to understand what it means: If it shows, as per this example of Mijoshop, you can be assured that the extension is Joomla 3.x compatible an is available!

mijo30.jpg

If it only shows the 2.5-icon rest assured the extension is not (yet) available for Joomla 3.x! This means that you have to wait or have to find an extension that IS available for Joomla 3.x...

(In this example you would for instance find out that your Virtuemart extension is only 2.5 compatible so you could to change to Mijoshop which as shown is 3.x compatible (or any other compatible 3.x shopping cart extension!) )

This is what you will have to do with all your extensions!

Make an inventory what is and what is NOT compatible with Joomla 3.x!

When you have written down this we go to Step 3!

Step 3: Update all extensions compatibility with Joomla 3.x!
This is a simple step! You just download and update all your extensions (not Joomla yet!) you have found to be compatible with Joomla 3.0 except your template (!) Only upgrade extensions that show compatibility with Joomla 1.5/2.5/3/x or 2.5/3.x!

Step 3a: Go to Manage Extensions > and choose "components" : delete those components that are not compatible with Joomla 3.x and do the same for successively "modules" and "plugins"
Is also inaccurate for the above readings and:
It is Extensions >>> Manage >>> uninstall
not delete

BACKUP YOUR SITE! and then

We go to the next step!

Step 4: Delete all extensions that are NOT compatible with Joomla 3.x!
Go to your admin panel and be very careful...Do not do this when your are tired, too much coffee, do not feel good etc... You should be fresh and have a clear mind!!!! Believe me I speak from experience!

Go to Manage Extensions > and choose "components" : delete those components that are not compatible with Joomla 3.x and do the same for successively "modules" and "plugins" Please be careful and do not delete things you have not changed. Do not delete any Joomla stuff for sure! Do NOT delete what you before in Step 3 have upgraded
Be Careful!

Now when you are done we are going to get your site to Joomla 3.x !

Step 5: Update Joomla 2.5 to Joomla 3.x!
Wow is that going to be easy!

But first Disable the System Plugin 'Remember Me' (and enable after your (mini) migration is successful completed)

So go to the component "Joomla Update" and select the global "options" icon (top right in your screen). Change the settings from Long Term Release (LTS) to STS and save. Now go back to Joomla update and you will see that the 3.x version is available!!!! Click UPDATE and within seconds your site will be on J3...so than
Welcome @ Exciting All New Joomla 3 Version!!!

So we are going to finish up now!

Step 6: Update remaining extensions

So Now it is the moment to upload your Joomla 3.x template, configure it. Also do that for extensions you have replaced since they had no Joomla 3.x version (refer to Step 2)

See? That is all and not that difficult is it? Forgot one did you?????

BACKUP YOUR NEW JOOMLA 3.x SITE!
psssst: download it to your PC and do not leave it on your server....guess what is happening when your server's hard-disk crashes? Ouch...;-) )

Leo

[sovainfo]

Not only download it, use it locally. No use in downloading a corrupt file. You only know it is not corrupt when you use it locally. At least now you know it worked once!

[leolam]

Not only download it, use it locally. No use in downloading a corrupt file.

uhh, where are you talking about????

Leo

[sovainfo]

The only reason to make a backup is for restoring. If you don't restore the site, locally or remotely, at a different location you don't know you have a valid backup.
Not a nice thing to findout when the original is suffering from a harddisc crash!

[exoduser]

Yes, agree with you. It is a good practice to test the downloaded backup file whether it is working or not.

Not only download it, use it locally. No use in downloading a corrupt file.

uhh, where are you talking about????

Leo

[leolam]

@ sovainnfo:
This is about upgrading/mini-migrating a Joomla website.

Part of that process is backup. One should always check that a backup is not corrupted.

Akeebabackup for instance states very clearly on their website that a backup which has not been tested (for being corrupt) is "no backup" and I completely agree however what point you want to make by posting that in this particular thread without reference?

Leo

[sovainfo]

If you don't understand the point, there is no way I can explain that to you, sorry!

[leolam]

If you don't understand the point, there is no way I can explain that to you, sorry!

Good to see you modified your first reply above so anybody (even me) understands now what you mean!

Thanks!

Leo

[pvh123]

Great procedure Leo. It needs to be sticky.

I will try this out later.
Well done.

[leolam]

Great procedure Leo. It needs to be sticky.

I agree but that can only be done by a Moderator ;-) But no problem I am posting it also on our site

Leo

[brian]

Leo

A few typos and spelling corrections and you used than when you mean then

amended text attached

[leolam]

Leo

A few typos and spelling corrections and you used than when you mean then

amended text attached

As always....your guidance and positive input is highly appreciated. Thanks Brian!

Have gone quickly through it and corrected the most obvious ones. Thanks a ton and will use the corrected version a little later...I am putting it on our website first since I am afraid it might snow under if they don't want to make it sticky so users can find it than on the our website by just following the links in my signature...

Leo

[DonDinardoni]

Hi Leo,
followed all the steps and worked perfectly fine except after clicking on 'update' for the Joomla Update itself, I end up with a blank page and can not access backend nor frontend anymore. No error message, just white page. Any ideas?

EDIT:
I am a step further - my bad:

• - Restored backup
  - Set error reporting to max
  - Ran Joomla update
  - Got error about an incompatible plugin (which I apparently missed before)
  - Update finished with a long error message (see attached)
  - Backend/Admin works nicely and is on J3.1.1, but frontend shows error

Code: Select all

Fatal error: Call to undefined method JParameter::loadINI() in /home/.sites/704/site1092/web/libraries/joomla/html/parameter.php on line 76

[conlippert]

Please add a link to this page if you happen to be missing the Joomla Update component in your components dropdown: http://docs.joomla.org/Joomla_Update_Mi ... Admin_Menu

Thanks,
CL

[occultfish]

very good tutorial , too bad most components and modules are all the way from joomla 1.7

[jvrproductions]

Hello i am almost there following the tutorial but after change change on joomla update from long term to short term i still get the message that say

No updates available
You already have the latest Joomla! version, 2.5.11.

Any help will be appreciate....

P.D Sorry for my english :-)

Thanks
Jose

[DK180]

In control panel the update status says Joomla is up to date

Clicking the notice button it states...

Error loading component: com_joomlaupdate, 1
Error loading component: com_joomlaupdate, 1
The PHP allow_url_fopen setting is disabled. This setting must be enabled for the updater to work.

From here I have followed the above directions switching from LTS to STS and on saving I get....

The website cannot display the page
HTTP 500
Most likely causes:
•The website is under maintenance.
•The website has a programming error.
What you can try:
Refresh the page.
Go back to the previous page.
More information.

I do not have a Joomla update component in the components drop down?

Am I missing something?

[sovainfo]

- Fix the allow_url_fopen problem.
- Try to discover Joomla! Update.
- Find out whether there is a Joomlaupdate extension and provide the id in component_id of the joomlaupdate menuitem. Or run code below in phpMyAdmin

Code: Select all

UPDATE #_menu SET component_id  = (SELECT extension_id from #_extentions WHERE name = "com_joomlaupdate" ) WHERE title = "com_joomlaupdate"

Replace # by your own prefix (twice)!

[DK180]

Thanks but How or where do I go to fix this? (The PHP allow_url_fopen setting is disabled)

I have done a search for update extension without luck so far.

[sovainfo]

It is a php setting, try the php.ini or .htaccess. See systeminformation to see which ini files apply.

I have done a search for update extension without luck so far.

Have no idea what you are saying, be more specific!

[sural98]

Hi leolam,
Thanks for your guide.
What is the case with language files if J 2.5 is multi-language? Will overwriting those with 3.x files suffice?

[webmuse]

Hi!

I've upgraded a 1.5 site to 2.5.11 using jUpgrade, but really want to get to 3.1.
I inserted the missing menu item for Joomla Update, and changed it's options to 'Short Term Support', as directed.

Not seeing any error messages. Have error reporting in PHP turned ON. Created a new .htaccess file containing the line:
php_flag allow_url_fopen On

The "notice" mentioned by DK180 is nowhere to be seen.

Still seeing the message: "No updates available" and "You already have the latest Joomla! version, 2.5.11."

I'm wondering if jUpgrade removed something that is needed?
Any ideas?

WebMuse

[sovainfo]

What does System Information => PHP Information => allow_url_fopen say?

[webmuse]

Joomla's System Information shows allow_url_fopen = On.
Running FPA, the only warnings are the PHP API is APACHE2HANDLER. (Why is this a concern?) and config mode = 444 (read only).

I'm running this locally, on my Mac OS Lion, running MAMP. Had a firewall turned on that I thought might be the cause, so turned it off, but still same results.

Can anyone tell me what has changed in the core system from 2.5 to 3.1? Can I simply copy the update code, and create any new tables? Or, are there also modifications to the tables? I have experience writing a component and module that extends Joomla, or in other words, I'm a developer, so could tackle the update manually, if it were only documented what changed.

Thought I read somewhere that I could simply "install" the update package like I would install any extension. Is this another option?

I've also tried jUpgradePro to upgrade directly to 3.1 starting from the old 1.5 copy, and even though it says it completed successfully, all tables are empty, including the menu table, thus losing access to all components in admin.

I've copied the code to my production server. Will give it a try there, after updating configuration.php so it runs.

If I cannot get this resolved in the next day or two, I'll have to make the decision to just stick with 2.5 as my current version. I have another 7 sites that need upgrading from 1.5, and was really hoping to get them all to 3.1 for the longevity factor.

Thanks,
WebMuse

[DK180]

(The PHP allow_url_fopen setting is disabled)

I've since spoke to my hosting company and they tell me that

"For security reasons the allow_url_fopen setting must be disabled on the shared hosting cluster"

Any way around it?

[webmuse]

Ok, so I have attempted to run Joomla Update with option set to "Short Term Support".
I updated php.ini, and verified in Joomla's Admin System Info - PHP Info that allow_url_fopen is ON.

Still getting the message: "You already have the latest Joomla! version, 2.5.11."

Here's what fpa shows, in case this helps any:

Joomla! Instance :: Joomla! 2.5.11-Stable (Ember) 26-April-2013
Joomla! Platform :: Joomla Platform 11.4.0-Stable (Brian Kernighan) 03-Jan-2012
Joomla! Configured :: Yes | Writable (604) | Owner: 4499 (uid: /gid: ) | Group: 450 (gid: ) | Valid For: 1.5
Configuration Options :: Offline: 0 | SEF: 1 | SEF Suffix: 0 | SEF ReWrite: 0 | .htaccess/web.config: No | GZip: 0 | Cache: 0 | FTP Layer: 0 | SSL: 0 | Error Reporting: default | Site Debug: 0 | Language Debug: 0 | Default Access: N/A | Unicode Slugs: N/A | Database Credentials Present: Yes

Host Configuration :: OS: Linux | OS Version: 2.6.18-238.19.1.el5PAE | Technology: i686 | Web Server: Apache | Encoding: gzip,deflate,sdch | Doc Root: /home/content/w/e/b/webmuseg/html | System TMP Writable: Yes

PHP Configuration :: Version: 5.3.24 | PHP API: cgi-fcgi | Session Path Writable: No | Display Errors: 1 | Error Reporting: 22519 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: 0 | Open Base: | Uploads: 1 | Max. Upload Size: 4M | Max. POST Size: 33M | Max. Input Time: 60 | Max. Execution Time: 30 | Memory Limit: 64M

MySQL Configuration :: Connection Error: 2002:Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) : Database Credentials Present? in Configuration...

PHP Extensions :: Core (5.3.24) | date (5.3.24) | ereg () | libxml () | openssl () | pcre () | sqlite3 (0.7-dev) | zlib (1.1) | apc (3.1.13) | bcmath () | calendar () | ctype () | curl () | dba () | dom (20031129) | hash (1.0) | fileinfo (1.0.5-dev) | filter (0.11.0) | ftp () | gd () | gettext () | SPL (0.2) | iconv () | json (1.2.1) | mbstring () | mcrypt () | mysql (1.0) | mysqli (0.1) | session () | PDO (1.0.4dev) | pdo_mysql (1.0.2) | pdo_sqlite (1.0.1) | standard (5.3.24) | pspell () | Reflection ($Id: 4af6c4c676864b1c0bfa693845af0688645c37cf $) | Phar (2.0.1) | SimpleXML (0.1) | soap () | SQLite (2.0-dev) | exif (1.4 $Id$) | tokenizer (0.1) | wddx () | xml () | xmlreader (0.1) | xmlrpc (0.51) | xmlwriter (0.1) | xsl (0.1) | zip (1.11.0) | cgi-fcgi () | mhash () | Zend Engine (2.3.0) |
Potential Missing Extensions :: suhosin |

Switch User Environment (Experimental) :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Custom SU (LiteSpeed/Cloud/Grid): No
Potential Ownership Issues: Maybe

Core Folders :: images/ (705) | components/ (705) | modules/ (705) | plugins/ (705) | language/ (705) | templates/ (705) | cache/ (705) | logs/ (705) | tmp/ (705) | administrator/components/ (705) | administrator/modules/ (705) | administrator/language/ (705) | administrator/templates/ (705) |

Elevated Permissions (First 10) ::

Components :: SITE :: CB Ajax Text Field (1.2) | CB Auto Welcome (1.2) | CB Captcha (1.2) | CB Mamblog Tab (1.2) | CB Mambo Author Tab (1.2) | CB Privacy (1.2) | CB ProfileBook (1.2) | Yanc Integration (1.2) | com_mailto (2.5.0) | com_wrapper (2.5.0) |
Components :: ADMIN :: com_admin (2.5.0) | com_banners (2.5.0) | com_cache (2.5.0) | com_categories (2.5.0) | com_checkin (2.5.0) | comprofiler (1.2.2) | com_config (2.5.0) | com_content (2.5.0) | com_cpanel (2.5.0) | com_finder (2.5.0) | com_installer (2.5.0) | com_joomlaupdate (2.5.0) | com_languages (2.5.0) | com_login (2.5.0) | com_media (2.5.0) | com_menus (2.5.0) | com_messages (2.5.0) | com_modules (2.5.0) | com_newsfeeds (2.5.0) | com_plugins (2.5.0) | com_redirect (2.5.0) | com_search (2.5.0) | com_templates (2.5.0) | com_users (2.5.0) | com_weblinks (2.5.0) |

Modules :: SITE :: mod_articles_archive (2.5.0) | mod_articles_categories (2.5.0) | mod_articles_category (2.5.0) | mod_articles_latest (2.5.0) | mod_articles_news (2.5.0) | mod_articles_popular (2.5.0) | mod_banners (2.5.0) | mod_breadcrumbs (2.5.0) | mod_custom (2.5.0) | mod_feed (2.5.0) | mod_finder (2.5.0) | mod_footer (2.5.0) | mod_languages (2.5.0) | mod_login (2.5.0) | mod_menu (2.5.0) | mod_random_image (2.5.0) | mod_related_items (2.5.0) | mod_search (2.5.0) | mod_stats (2.5.0) | mod_syndicate (2.5.0) | mod_users_latest (2.5.0) | mod_weblinks (2.5.0) | mod_whosonline (2.5.0) | mod_wrapper (2.5.0) |
Modules :: ADMIN :: mod_custom (2.5.0) | mod_feed (2.5.0) | mod_latest (2.5.0) | mod_logged (2.5.0) | mod_login (2.5.0) | mod_menu (2.5.0) | mod_multilangstatus (2.5.0) | mod_popular (2.5.0) | mod_quickicon (2.5.0) | mod_status (2.5.0) | mod_submenu (2.5.0) | mod_title (2.5.0) | mod_toolbar (2.5.0) | mod_version (2.5.0) |

Plugins :: SITE :: plg_authentication_gmail (2.5.0) | plg_authentication_joomla (2.5.0) | plg_authentication_ldap (2.5.0) | plg_captcha_recaptcha (2.5.0) | plg_content_emailcloak (2.5.0) | plg_content_finder (2.5.0) | plg_content_geshi (2.5.0) | plg_content_joomla (2.5.0) | plg_content_loadmodule (2.5.0) | plg_content_pagebreak (2.5.0) | plg_content_pagenavigation (2.5.0) | plg_content_vote (2.5.0) | plg_editors_codemirror (1.0) | plg_editors_tinymce (3.5.4.1) | plg_editors-xtd_article (2.5.0) | plg_editors-xtd_image (2.5.0) | plg_editors-xtd_pagebreak (2.5.0) | plg_editors-xtd_readmore (2.5.0) | plg_extension_joomla (2.5.0) | plg_finder_categories (2.5.0) | plg_finder_contacts (2.5.0) | plg_finder_content (2.5.0) | plg_finder_newsfeeds (2.5.0) | plg_finder_weblinks (2.5.0) | plg_quickicon_extensionupdate (2.5.0) | plg_quickicon_joomlaupdate (2.5.0) | plg_search_categories (2.5.0) | plg_search_contacts (2.5.0) | plg_search_content (2.5.0) | plg_search_newsfeeds (2.5.0) | plg_search_weblinks (2.5.0) | plg_system_cache (2.5.0) | plg_system_debug (2.5.0) | plg_system_highlight (2.5.0) | plg_system_languagecode (2.5.0) | plg_system_languagefilter (2.5.0) | plg_system_log (2.5.0) | plg_system_logout (2.5.0) | plg_system_p3p (2.5.0) | plg_system_redirect (2.5.0) | plg_system_remember (2.5.0) | plg_system_sef (2.5.0) | plg_user_contactcreator (2.5.0) | plg_user_joomla (2.5.0) | plg_user_profile (2.5.0) |

Templates :: SITE :: atomic (2.5.0) | beez5 (2.5.0) | beez_20 (2.5.0) | JA_Purity (1.2.0) | rhuk_milkyway (1.0.2) | rhuk_milkyway25 (1.0.2) |
Templates :: ADMIN :: bluestork (2.5.0) | hathor (2.5.0) |

Is there a custom URL I could specify in Joomla Update Options instead?

Thought I read somewhere else that I could simply "install" the update package like any extension. Is this another option?

Thanks,
WebMuse

[sovainfo]

@DK180:Now they have made it clear they don't take security seriously I can advice you to change provider.

FYI: allow_url_include must be disabled, allow_url_fopen should be allowed.

BTW: Try to upgrade the oldfashioned way: use extension installer with the update.

[leolam]

@ DK180

"For security reasons the allow_url_fopen setting must be disabled on the shared hosting cluster"

You host has no idea where they are talking about! That remark shows little knowledge about PHP-security!

re: Sovainfo:

FYI: allow_url_include must be disabled, allow_url_fopen should be allowed.

this is completely correct

Leo

[leolam]

@ Webmuse: Your files and folder permissions are wrong: folders= 755 and files = 644

and clear all Joomla caches and browser caches...shutdown browser, wait for 10 seconds and reload... Issue should be resolved.

Leo

[shoulders]

thanks for this guide. it is just what i need for a bit of reassurance. All over the web they say just go ahead and upgrade with the one click but never mentioned about modules and plugins and what to do about them and their data.

- this module is 2.5 and 3.0 compatable, does this mean it will install on both but i should uninstall it for the upgrade?
- will it keep my data during the upgrade?
- do i need to export my data?

and so on.....

all my questions answered here.