Download joomla package 1.5

Even though it can not do that automatically, you can do so in your extension's dispatcher file, e. Here's the magic code to do that in the backend:. All your translation keys should consist of uppercase characters without spaces that is A-Z, and underscores. All translation values should be included in double quotation marks.

This allows the translation files to be parsed by Joomla! You are also suggested to prefix your translation keys with the extension's name, albeit this is not required. If you have double quotation marks in your translation values, please replace them with single quotation marks. While Joomla! The workaround is to take advantage of a little known fact about HTML, that attributes can be wrapped in single quotation marks. You can't always win, sorry.

If you have volunteer translators you can bet your head that most translations will not be in sync with your component and you will have untranslated strings. In Joomla! This is impossible in Joomla! We can use the same little trick in our component's dispatcher as with our component-local translation loading string above. Here's how to load the English translation file in the backend of your component, then overwrite only the keys which exist with the user's selected language, essentially allowing untranslated keys to show in English:.

Oh, the struggle! You need a custom widget in the configuration section of your component. But both? In a single file? You can employ a simple trick. In the following example I am going to create a rather lame element, called SQL2, which displays a multi-selection box out of the results of a SQL statement. First, let your configuration know where to load the custom widget files from, by putting this in your module's XML manifest file:.

As you see, we instruct both Joomla! Considering that most custom widgets have a lot more code than this, you can create two different initialisation sections for Joomla! This will eliminate the need to rewrite the same code over again just to cater for a new Joomla! Joomla 1. The content plugins in Joomla! The arguments have also changed. You can, however, create a single content plugin which runs on both Joomla! Here's how:. There is a small but very disturbing bug in Joomla!

You are stuck with no way to run SQL commands on component update! Reference that file in the end of your manifest XML file, just above the closing install tag, with:. This will force Joomla! In both cases, you need to create a file named en-GB. In the first case using a translation key , its contents should be:.

NB: Joomla! This leads to funny results, especially with non-English languages where the translated component names do not follow the same sorting order as their English names. It is risky to upgrade a live site without testing the upgrade process first. So before upgrading the live site you need to set up a test site which is as close as possible to the configuration of your live site, then test the upgrade on that.

When you are happy with the process you can apply it to the live site having taken a fresh backup of the live site first, of course. You can also use a Joomla! See Update Manager for Joomla! When upgrading from a version that is not the most recent, review release notes for the prior releases.

If you have questions about these instructions, read the Additional Information below this table. Before you actually upgrade, you really should make a backup of your site.

Backup your existing Joomla site files and store all the files and database in case something gets messed up, you wont have any problem reverting back. There are different ways of installing a package file depending on your particular circumstances. If you have difficulty with one of these methods, then simply try another. Don't assume that the upgrade will work flawlessly just because the test upgrade worked. Check to make sure that nothing untoward has happened.

It could be that differences between the live site and test site platforms will bring out a problem that you did not notice during testing.