Support

You can always update Joomla! by downloading the update package and installing it just like you'd install an extension.

The core Joomla! Update component is the same as Admin Tools' former Joomla! Update feature. The difference is where the update notifications come from. Admin Tools used to do page-scraping of the joomlacode.org site. Problem: if the Joomla! project pre-releases a version for testing it is picked up by Admin Tools as a stable release. Corollary: The Joomla! project had to release versions 3.1.3, 3.1.4 and 3.1.5 (as well as 2.5.12, 2.5.13 and 2.5.14) within a week because 2.5.12/3.1.3 were broken and due to the way the updates work they had to jump two version numbers. That's exactly when I decided to drop that feature. I have already written it, please stop asking me! The next time I will reply with RTFA (Read The Fine Article) ;)

The core Joomla! Update component fetches its update information from the update XML file which is the one and only official update source. In order for this to work you probably have to go to Extensions, Manage Extensions, Database and click on Fix. Then go to Extensions, Manage Extensions, Update and click on Purge. These steps should have fixed any db issues. Now let's make sure the updates are fetched afresh. Go to Components, Joomla! Update. Click on Options. Select the "Short Term Support" update server and click on Save & Close. DO NOT CLICK ON SAVE INSTEAD*! That's important. Right now it should tell you that Joomla! 3.1.5 is available. If not, your server is fubar** and you need to talk to your host. Click on Options again. Select the "Long Term Support (recommended)" update server and click on Save & Close. Again, DO NOT click on Save instead! It will now tell you that Joomla! 2.5.14 is the latest version and you're up to date.

* When you click on Save & Close my code which force-purges the update cache kicks in. I wrote this as a fallback, in case shit hits the fan and the update cache is totally stuck. Guess what hit the fan on your site?

** When I say that the server is fubar I mean that your host cocked up the php.ini setting. I've blogged about it and why it's utterly wrong at http://www.dionysopoulos.me/blog/135-flicking-the-wrong-switch.html