Actions

User

Tom Hutchison/DPL

From Joomla! Documentation

< User:Tom Hutchison(Redirected from User:Hutchy68/DPL)

Contents

Other FAQ Categories

Adding images


Joomla! 
2.5

<translate> These are the methods available for uploading images to your Joomla! website.

Upload Using Media Manager

</translate> <translate> The simplest way to add images is to upload them from your computer using the Media Manager. First, of course, you have to download the image onto your computer and be able to find it. Then, from the Control Panel (back-end administrative interface) navigate to Content  Media Manager.

On the left is a directory tree, with the root directory "Media". This corresponds to the default "images" directory, yoursite/joomla/images. Pick a subdirectory where you want the image located, or else do nothing to upload the image to the default images directory.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server. </translate>

<translate>=== FTP ===

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.</translate>

<translate>=== Extensions ===

There are several extensions available from the Joomla Extensions Directory which can upload images.</translate>


Adding images/ar


Joomla! 
2.5

يوجد طرق متوافرة لرفع الصور لموقع جوملا الخاص بك

الرفع باستخدام مدير الوسائط

أبسط طريقة لإضافة صورة هي عن طريق رفع الصور من حاسبك باستعمال مدير الوسائط. في البداية , يجب تنزيل الصورة الى حاسبك ويكون بامكانك ايجاد هذه الصورة . بعد ذلك , من خلال لوحة التحكم (واجهة الادارة الخلفية) انتقل الى المحتوى  مدير الوسائط

على اليسار يوجد شجرة الفهرس , على الجذر الأساسي الوسائط "media". وهذا يتوافق مع الفهرس الصور "images" الافتراضي ,yoursite/joomla/images . اختر فهرس فرعي حيث تريد أن تتوضع الصورة , او لاتفعل شيء لرفع الصورة الى الفهرس الافتراضي للصور

في الجانب الأعلى الأيسر للصفحة اضغط على "الرفع". وبعدها سترى صندوق الرفع. اضغط على "استعراض" لتحديد موقع الصورة من حاسبك . ثم اختر "بدء الرفع" لرفع الملف على المخدم.

بروتوكول نقل الملفات

طبعا يمكنك رفع الصور الى المخدم باستخدام أي من برامج نقل بروتوكول نقل الملفات القياسية FTP. قد تجد هذه الطريقة أكثر عملية لاضافة الصور الى مجلدات القوالب, ومع ذلك إذا كنت تستخدم برنامج FTP لربما لاتحتاج لهذا الشرح عن كيفية اضافة الصور . كما أن العديد من لوحات ادارة المخدمات مثل Cpanel و Plesk يملكون هذه القابلية .

الملحقات

يوجد العديد من الملحقات المتوافرة من Joomla Extensions Directory والتي يمكنها رفع الملفات.


Adding images/da


Joomla! 
2.5

Disse er metoderne der er tilgængelige for upload af billeder til dit Joomla! Websted.

Upload ved hjælp af Medier

Den letteste måde at tilføje billeder er ved at uploade dem fra din computer ved at anvende Medier. Selvfølgelig skal du først have downloadet billedet på din computer og kunne finde det. Derefter, fra kontrolpanelet (backend administraionsinterfacet) naviger til Content  Media Manager.

On the left is a directory tree, with the root directory "Media". This corresponds to the default "images" directory, yoursite/joomla/images. Pick a subdirectory where you want the image located, or else do nothing to upload the image to the default images directory.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server.

FTP

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.

Extensions

There are several extensions available from the Joomla Extensions Directory which can upload images.


Adding images/en


Joomla! 
2.5

These are the methods available for uploading images to your Joomla! website.

Upload Using Media Manager

The simplest way to add images is to upload them from your computer using the Media Manager. First, of course, you have to download the image onto your computer and be able to find it. Then, from the Control Panel (back-end administrative interface) navigate to Content  Media Manager.

On the left is a directory tree, with the root directory "Media". This corresponds to the default "images" directory, yoursite/joomla/images. Pick a subdirectory where you want the image located, or else do nothing to upload the image to the default images directory.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server.

FTP

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.

Extensions

There are several extensions available from the Joomla Extensions Directory which can upload images.


Adding images/et


Joomla! 
2.5

Need on meetodid, mis on Joomla! veebisaidi jaoks saadaval.

Laadi üles kasutades failihaldurit

The simplest way to add images is to upload them from your computer using the Media Manager. First, of course, you have to download the image onto your computer and be able to find it. Then, from the Control Panel (back-end administrative interface) navigate to Content  Media Manager.

On the left is a directory tree, with the root directory "Media". This corresponds to the default "images" directory, yoursite/joomla/images. Pick a subdirectory where you want the image located, or else do nothing to upload the image to the default images directory.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server.

FTP

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.

Lisaprogrammid

There are several extensions available from the Joomla Extensions Directory which can upload images.


Adding images/fa


Joomla! 
2.5

These are the methods available for uploading images to your Joomla! website.

Upload Using Media Manager

The simplest way to add images is to upload them from your computer using the Media Manager. First, of course, you have to download the image onto your computer and be able to find it. Then, from the Control Panel (back-end administrative interface) navigate to Content  Media Manager.

On the left is a directory tree, with the root directory "Media". This corresponds to the default "images" directory, yoursite/joomla/images. Pick a subdirectory where you want the image located, or else do nothing to upload the image to the default images directory.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server.

FTP

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.

Extensions

There are several extensions available from the Joomla Extensions Directory which can upload images.


Adding images/nl-informal


Joomla! 
2.5

Zo kun je afbeeldingen op je Joomla! website zetten.

Uploaden met Mediabeheer

De eenvoudigste manier om afbeeldingen toe te voegen is om ze te uploaden vanaf je computer met behulp van de Media Manager. Eerst plaats je de afbeelding op je computer om hem kunnen vinden. Daarna navigeer je vanuit het Controlepaneel (beheergedeelte administrator-interface) naar Inhoud  Mediabeheer.

Aan de linkerkant staat de mapjes , met de basis-map "Media". Dit komt overeen met de standaardmap "images", je-site/joomla/images. Kies een sub-map waar je de afbeelding wilt hebben, of doe niets om de afbeelding naar de standaardmap met afbeeldingen te uploaden.

At the top left of the page click on "Upload". Then, you'll see Upload box. Click "Browse" to locate the image on your computer, then "Start Upload" to upload the file to the server.

FTP

Of course, you can upload images to a server using any standard FTP client. You might find this handier for adding images to template directories; however, if you have FTP set up, you probably don't need an explanation of how to add an image. Also, many server administration panels such as Cpanel and Plesk have upload capabilities.

Extensions

There are several extensions available from the Joomla Extensions Directory which can upload images.


All HTML markup is stripped when you save an article

In some cases (for example, when you have a database error during the update), when you edit an article, all of the HTML markup is removed when the article is saved.

To fix this, navigate to Global Configuration → Text Filters, make sure the filters are set correctly, then Save.

This is caused by moving the Text Filter function from Article ManagerOptions → Global Configuration. In a normal 2.5.0 update, these Text Filter settings are transferred automatically.


Broken-configuration-screen-in-2.5.10

If you use memcached you may have a broken configuration screen. The best solution to this is to update to 2.5.11. If for some reason you cannot update to 2.5.11 you may apply the following hotfix.

Find the file libraries/joomla/cache/storage/memcached.php

At line 317 change Memcache to Memcached.

-    $memcached = new Memcache;
+    $memcached = new Memcached;


Can I add registration fields?


Since Joomla! 1.6 you can add extended registration fields by using a profile plugin. A sample profile plugin is included in the standard installation, offering a number of commonly requested fields such as mailing address, telephone number and date-of-birth.

See: What is a profile plugin? See also: Creating a profile plugin


Can articles be assigned to multiple categories or sections?


No, Articles and other content items cannot be assigned to multiple categories or sections.

In Joomla! Joomla 1.0 and Joomla 1.5: Content items are restricted to a single category in a single section. In Joomla! Joomla 2.5 and newer: Content items are restricted to a single category in a category tree.

Possible work-arounds include:

  • creating duplicate articles in multiple categories.
  • using menus rather than dynamic lists of content items.
  • using various third party extensions that simulate assignment to multiple categories.
  • using key words to simulate categories and sections.


Can you remove the "Powered by Joomla!" message?

Joomla 2.5 and newer Joomla 2.5Joomla 3.1

Starting with Joomla 1.5 and its move to Internationalization and full support of UTF-8, messages for footer.php and other Joomla pages has been moved to a language specific file.

As before if you want to change the text, go to the language directory, go to the folder of the language you want to change, find the mod_footer.ini file and change the relevant text. For British English, the specific file is language/en-GB/en-GB.mod_footer.ini. Remember that you may not remove copyright and license information from the source code. However note that this means that every time you update Joomla the language file will be overwritten with the old copyright.

A better solution is to create a language string override in the language. See the Joomla! 2.5 or Joomla! 3.1 help screens for more information on how to do this

If you want to remove the footer entirely, go to Extensions > Module Manager and unpublish the footer module.

Other places where can look for options to make changes are these. If you find code related to footers in these files, you can either "comment it out" or remove it:

  • /includes/footer.php file.
  • index.php file for your active template

Joomla 1.5Joomla 1.5

Starting with Joomla 1.5 and its move to Internationalization and full support of UTF-8, messages for footer.php and other Joomla pages has been moved to a language specific file.

If you want to change the text, go to the language directory, go to the folder of the language you want to change, find the mod_footer.ini file and change the relevant text. For British English, the specific file is language/en-GB/en-GB.mod_footer.ini. Remember that you may not remove copyright and license information from the source code.

If you want to remove the footer entirely, go to Extensions > Module Manager and unpublish the footer module.

Other places where can look for options to make changes are these. If you find code related to footers in these files, you can either "comment it out" or remove it:

  • /includes/footer.php file.
  • index.php file for your active template


Cannot-upload-file-in-2.5.10

If you get a message saying you cannot upload in 2.5.10 the best solution is to upgrade to 2.5.11.

If it is not possible to upgrade to 2.5.11 you can click the options button in the media manager and save, and the error will be gone.

Please note that the Flash uploader has been removed completely for security reasons.


Control Panel Breaks When Upgrading to 2.5.0

When upgrading from 1.7.3 to 2.5.0, the Control Panel may appear "broken" after the upgrade. See the image on this page.

Control Panel may appear "broken" after the upgrade

Cause

This issue is caused by changes to the Administrative template. Your browser may still be holding portions of the administrative supporting files (CSS & JavaScript) in your browser's cache.

How to Fix

The fix is to clear your browser's cache.

Mozilla / Firefox / Safari: hold Shift while clicking Reload, or press either Ctrl-F5 or Ctrl-R (Command-R on a Macintosh); Konqueror: click Reload or press F5; Opera: clear the cache in Tools → Preferences; Internet Explorer: hold Ctrl while clicking Refresh, or press Ctrl-F5.


Database Errors When Upgrading to 2.5.0

When upgrading from an earlier, compatible version, to 2.5.0, you may experience a database error such as the following

JInstaller: :Install: Error SQL DB function failed with error number 1060 Duplicate column name 'ordering' SQL=ALTER TABLE `j17_languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`; SQL = ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`; Files Update: SQL error file DB function failed with error number 1060 Duplicate column name 'ordering' SQL=ALTER TABLE `j17_languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`; SQL = ALTER TABLE `#__languages` ADD COLUMN `ordering` int(11) NOT NULL default 0 AFTER `published`;"

To fix this issues, go to Extension Manager -> Database then click the fix button. This will attempt to fix any database issues caused by changes in the database structure that occurred between versions.


Disappearing articles after 2.5 upgrade

Problem: I have just upgraded to 2.5 from 1.7.3 and the only problem I have is that the articles that a specific user wrote are not being published. They still show up in the backend but not in the frontend. Other articles written by other users do show up.

Cause: If you have a user linked to a contact that is unpublished, the articles written by this user don't show up in the front.

Solution: Please check if you have a unpublished contact linked to user that wrote the articles. Also check the trashed contacts for this. The solution would be to publish the contact or to completely remove them, so empty the trash.


Editors buttons Issues in FireFox

When you are inserting images or page break (on tinyMCE), the location of the item you added is on beginning position of the article and not the original location when the mouse cursor was before press the button.

For fixing this issue, you'll require to add the next css code to the end of the file media/system/css/modal.css:

@-moz-document url-prefix() {
    .body-overlayed {
        overflow: visible;
    }
}

See also


Empty-$path-issue-in-2.5.10

In version 2.5.10 some extensions show an empty $path error. The best solution for this is to update to 2.5.11.

If for some reason you cannot update to 2.5.11 you can apply the following hot fix.

Navigate to libraries/joomla/filesystem/path.php.

At about line 202 change

if (!is_string($path)) 
to
if (!is_string($path) && !empty($path))


diff --git a/libraries/joomla/filesystem/path.php b/libraries/joomla/filesystem/path.php
index d4c8bb9..d5116c8 100644
--- a/libraries/joomla/filesystem/path.php
+++ b/libraries/joomla/filesystem/path.php
@@ -199,7 +199,7 @@ class JPath
         */
        public static function clean($path, $ds = DIRECTORY_SEPARATOR)
        {
-               if (!is_string($path))
+               if (!is_string($path) && !empty($path))
                {
                        throw new UnexpectedValueException('JPath::clean: $path is not a string.');
                }


Enabling user's registration approval by admins


A new feature added to the user registration process in Joomla 2.5 and newer is the New User's Approval by Administrators, where a user will only be able to login after an administrator approves and activates the account.

To enable it set User Activation to "Admin".

This new feature required a slight change to the parameters set in the Users Manager. The User Activation parameter now has 3 options (as opposed to 2 options in Joomla! 1.5.x) and the options can be chosen from a select list box instead of the previous radio buttons.

The options are:

  • None - No activation is needed. The user may login right after finishing the registration.
  • Self - The user will receive an e-mail message containing a link with a token to activate their account.
  • Admin - It is necessary that an administrator approves the account. Here is how the process goes:
    • After registering the new user receives an e-mail message containing a link with a token to verify their e-mail address;
    • After the user's e-mail address has been verified, all users with the Receive System Messages option enabled will receive an e-mail message notifying them that a user has verified their e-mail address and requests that their account be activated. That email message will contain a link with a token to activate the account;
    • Once an administrator has activated the account, the user will receive an e-mail message notifying them that they may now login.

This feature was a product of many suggestions made by users in the Administration Forum [1].


Error notice using search

Issue

When making a search within the search module, the next notice appears:

Notice: Trying to get property of non-object in /path/to/joomla/plugins/search/content/content.php on line 234

Fix

Go to  plugins/search/content/content.php 


Search $itemid = isset($item) ? '&Itemid='.$item->id : '';

Replace with the following line:

$itemid = isset($item->id) ? '&Itemid='.$item->id : '';


Save

See also


Fatal error: Call to undefined method JInstaller::parseXMLInstallFile()

Fatal error: Using $this when not in object context in /libraries/joomla/application/base.php on line 87

See this tracker item. Apply the patch of the tracker item.


Ftp-update-not-working

There have been reports that updates with the FTP layer enabled are not working. Currently there is not a fix for this, but it is suggested that rather than use the updater you install the new Joomla version using the standard extension manager install. If that does not work, you can ftp the update zip filed to your host and unzip the new files, replacing the old ones. You will need to manually run the database changes using the appropriate version script found in administrator/components/com_admin/sql.

You will also need to manually delete the Flash uploader files from the media folder.

How can you view a live site while developing, but hide it from others?

Introduction

The method described below should be used for relatively minor modifications, such as adjusting menus or quickly reorganizing content sections. More complex tasks, such as installing new components or adjusting complex configuration settings should be performed and tested on a development server first. Not only does this keep your public site up and running, but it also lets you test at your leisure, thus reducing errors. One way to do it is to create a sub-domain (i. e., dev.yourdomain.com) and install Joomla! there just as it is installed on your public site.

Directions

  1. Log in to the Back-end, and choose: Site > Global Configuration.
  2. The first option you'll see is is to set the site offline. Choose "Yes" and press the Save button. This will prevent display of all site pages and replace them with the following message:
    This site is down for maintenance. Please check back again soon.
    
  3. While you are logged into the Back-end administrator system, you can still view the Front-end, by
    • Joomla 3.x: clicking the site name in the top left corner
    • Joomla 2.5: clicking the Preview link in the top right corner
    This will display the site as it would appear to users along with a warning at the top that the site is down for maintenance.


How do I upgrade to Joomla! 3.x?


<translate>

  • First, review the system requirements for Joomla! 3.x and make sure that your server environment meets those requirements.
  • Second, make sure that all your extensions (especially, your templates) are Joomla 3.x compatible.
  • Third, create a test site and test the upgrade on the test site first.
  • Fourth, consult a trusted developer if you’re not 100% certain about anything.
  • Fifth, make a full backup of your site (files and database).

</translate>

<translate> Once ready, go to the Joomla! Update component. Click on options and change the setting to Short Term Support. Save. You should be notified of the availability of Joomla! 3.x. Click the button to install. Clear your browser’s cache to make sure you see the latest changes. That’s it!

Finally, double check and make sure that everything is working properly. </translate>

<translate> See Planning for Mini-Migration - Joomla! 2.5 to 3.x and Joomla! 2.5 to 3.x Step by Step Migration for detailed instructions.

Note: On some hosts you may need to use alternative update methods such as using the extensions installer. </translate>


How do I upgrade to Joomla! 3.x?/de


  • 1. überprüfe die System Anforderungen für Joomla! 3.x und vergewissere Dich, dass Deine Serverumgebung diese Anforderungen erfüllt.
  • 2. überprüfe alle Deine Erweiterungen (vor allem, die Templates), ob sie Joomla! 3.x kompatibel sind.
  • 3. erstelle eine Test-Seite und probiere das Upgrade zuerst auf der Test-Seite aus.
  • 4. solltest Du nicht zu 100% sicher sein, beauftrage einen vertrauenswürdigen Entwickler mit dem Upgrade.
  • 5. Erstelle ein vollständiges Backup Deiner Webseite (Dateien und Datenbank).

Wenn Du bereit bist, rufe im Backend die Komponente Joomla! Aktualisierung auf. Klicke auf die Optionen und ändere die Einstellungen auf Kurzzeit Support. Jetzt Speichern. Jetzt solltest Du einen Hinweis über die Verfügbarkeit von Joomla! 3.x angezeigt bekommen. Klicke auf den Button zum Installieren. Lösche den Browser-Cache um die letzten Änderungen zu sehen. Fertig!

Überprüfe zum Abschluß Deine Webseite und stelle sicher, dass alles richtig funktioniert.

Siehe Planung für eine Mini-Migration - Joomla 2.5-3.x und Joomla! 2.5 nach 3.x Schritt für Schritt Migration für detaillierte Anleitungen.

Hinweis: Auf einigen Webhosts ist es notwendig alternative update-Methoden einzusetzen, wie z.B. den Erweiterungs-Installer.


How do I upgrade to Joomla! 3.x?/en


  • First, review the system requirements for Joomla! 3.x and make sure that your server environment meets those requirements.
  • Second, make sure that all your extensions (especially, your templates) are Joomla 3.x compatible.
  • Third, create a test site and test the upgrade on the test site first.
  • Fourth, consult a trusted developer if you’re not 100% certain about anything.
  • Fifth, make a full backup of your site (files and database).

Once ready, go to the Joomla! Update component. Click on options and change the setting to Short Term Support. Save. You should be notified of the availability of Joomla! 3.x. Click the button to install. Clear your browser’s cache to make sure you see the latest changes. That’s it!

Finally, double check and make sure that everything is working properly.

See Planning for Mini-Migration - Joomla! 2.5 to 3.x and Joomla! 2.5 to 3.x Step by Step Migration for detailed instructions.

Note: On some hosts you may need to use alternative update methods such as using the extensions installer.


How do you find a Joomla! extension?

The official Joomla! extensions site: http://extensions.joomla.org/ is the main source for extensions. If you cannot find what you need there, you should also search the Joomla! Extensions Directory Forum.

If you still cannot find the right component then you should post a request or question in the Extensions Directory forum.

</noinclude>

How do you list your extension in the extensions site?

Information on how to list extensions in the extensions site is available here: http://extensions.joomla.org/help2


Before submitting an extension to JED you should read the 4 steps checklist process


How do you set global preferences for content?


Global preferences in content are set in the article manager.

In the backend, go to Content>Article manager.

On the tool bar, second from the right, there is the options icon.

Click that and set your global preferences.


How do you set parameters for articles and other content items?


In Joomla!, many Article parameters, such as Show Title, Show Author, and so on, can be set in three places:

  1. The individual article (the Article:[Edit] screen)
  2. The menu item (Menu Item:[Edit] screen)
  3. Global parameters (Article Manager / Options)

Typically, parameters at the individual article and menu item levels can be set to a specific value or to a value of "Use Global". If the individual article's parameter is set, then that value controls the setting. If this is set to "Use Global" then the menu item parameter is checked. If the menu item is set to a specific value, that value is used. If the menu item is set to "Use Global", then the global parameter setting is used.

A similar hierarchy is used for other content items, such as Banners, Contacts, News Feeds, and Web Links.

How do you use Recaptcha in Joomla?



<translate> Native reCAPTCHA was added into Joomla in version Joomla 2.5. Using reCAPTCHA is a great way of preventing bots from making fake accounts and content on your site. </translate> <translate> There are four steps to setting up reCAPTCHA: </translate>

<translate>

  1. Log in to your administrator back-end (How do I do this?)

</translate> <translate>

  1. Go to your Plugin Manager. You can find this under the Extensions drop down menu in the top menu or in the Control Pannel page.

</translate> <translate>

  1. Edit the Plugin Captcha - ReCaptcha
    • Set Status to Enabled
    • Copy and paste the Public and Private keys in their appropriate fields.
      • You will get the Public and Private keys by signing in with your Google account (create it if you don't have one) here: Create a reCAPTCHA key
      • Once you have register your website domain, Google will provide your ReCAPTCHA keys.
    • Click Save & Close

</translate> <translate>

  1. To enable reCAPTCHA
    • For Contact forms and the Registration form
      • Go to Global Configuration, and select the Site tab.
      • Choose Captcha - ReCaptcha in the Default Captcha field.
      • Click Save & Close.
    • For the Registration form only
      • Go to the User Manager. You can find it under the Users top menu or in the Control Pannel page.
      • In the Component tab in the Options choose one of the following for the Captcha:
        • Use Default - that is the default setting and follows the Default Captcha field setting in your Global Configuration.
        • None Selected - that setting ignors the Default Captcha setting in Global Configuration. Use it when you want ReCAPTCHA in the Contact forms but not in the Registration form.
        • Captcha - ReCaptcha - Only needed if the Default Captcha in the Global Configuration is set to None Selected but you want the ReCAPTCHA not in Contact forms but in the Registration form.
      • Click Save & Close.

</translate>

<translate> That's it! You're done! </translate>


How do you use Recaptcha in Joomla?/de



Native reCAPTCHA wurde in Joomla! ab der Version Joomla 2.5 hinzugefügt. reCAPTCHA ist ein gutes Mittel, um zu verhindern dass Bots Fake-Accounts anelegen oder Inhalte auf Ihrer Website posten. Es gibt vier Schritte zum Einrichten von reCAPTCHA:

  1. Anmelden am Administrator-Backend (Wie geht das?)
  2. Navigiere zu den Plugins, zu finden im Dropdown-Menü unter dem Navigationspunkt Erweiterungen.
  3. Edit the Plugin Captcha - ReCaptcha
    • Set Status to Enabled
    • Copy and paste the Public and Private keys in their appropriate fields.
      • You will get the Public and Private keys by signing in with your Google account (create it if you don't have one) here: Create a reCAPTCHA key
      • Once you have register your website domain, Google will provide your ReCAPTCHA keys.
    • Click Save & Close
  4. To enable reCAPTCHA
    • For Contact forms and the Registration form
      • Go to Global Configuration, and select the Site tab.
      • Choose Captcha - ReCaptcha in the Default Captcha field.
      • Click Save & Close.
    • For the Registration form only
      • Go to the User Manager. You can find it under the Users top menu or in the Control Pannel page.
      • In the Component tab in the Options choose one of the following for the Captcha:
        • Use Default - that is the default setting and follows the Default Captcha field setting in your Global Configuration.
        • None Selected - that setting ignors the Default Captcha setting in Global Configuration. Use it when you want ReCAPTCHA in the Contact forms but not in the Registration form.
        • Captcha - ReCaptcha - Only needed if the Default Captcha in the Global Configuration is set to None Selected but you want the ReCAPTCHA not in Contact forms but in the Registration form.
      • Click Save & Close.

That's it! You're done!


How do you use Recaptcha in Joomla?/en



Native reCAPTCHA was added into Joomla in version Joomla 2.5. Using reCAPTCHA is a great way of preventing bots from making fake accounts and content on your site. There are four steps to setting up reCAPTCHA:

  1. Log in to your administrator back-end (How do I do this?)
  2. Go to your Plugin Manager. You can find this under the Extensions drop down menu in the top menu or in the Control Pannel page.
  3. Edit the Plugin Captcha - ReCaptcha
    • Set Status to Enabled
    • Copy and paste the Public and Private keys in their appropriate fields.
      • You will get the Public and Private keys by signing in with your Google account (create it if you don't have one) here: Create a reCAPTCHA key
      • Once you have register your website domain, Google will provide your ReCAPTCHA keys.
    • Click Save & Close
  4. To enable reCAPTCHA
    • For Contact forms and the Registration form
      • Go to Global Configuration, and select the Site tab.
      • Choose Captcha - ReCaptcha in the Default Captcha field.
      • Click Save & Close.
    • For the Registration form only
      • Go to the User Manager. You can find it under the Users top menu or in the Control Pannel page.
      • In the Component tab in the Options choose one of the following for the Captcha:
        • Use Default - that is the default setting and follows the Default Captcha field setting in your Global Configuration.
        • None Selected - that setting ignors the Default Captcha setting in Global Configuration. Use it when you want ReCAPTCHA in the Contact forms but not in the Registration form.
        • Captcha - ReCaptcha - Only needed if the Default Captcha in the Global Configuration is set to None Selected but you want the ReCAPTCHA not in Contact forms but in the Registration form.
      • Click Save & Close.

That's it! You're done!


J2.5:How to add a span element to menu entries

To add a span element to your menu items (like there was in Joomla 1.5), you have to override the layout for mod_menu. You can follow the general approach described in How to override the output from the Joomla! core.

You need to override the following layout from mod_menu:

  • defult_url.php
  • default_component.php

After copying the files into your template (see How to override the output from the Joomla! core for details) do the following:

In both these files look for the following statement:

<?php echo $linktype; ?>

It should occur three times in both files.

Replace each of these with:

<span><?php echo $linktype; ?></span>

And you're done.


How to check the Joomla version?


<translate> You need to know which version of Joomla! is running on your website and you don't know where to find it in the backend? Here are the different methods, depending on the Joomla! version.</translate>

<translate> Remember, you should always use a supported version of Joomla!</translate>

Joomla! 1.0.x

<translate>===How To Access===

From the Backend

  • Log in the backend of your website,
  • Go to Information  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-1.0.x-<translate> en</translate>.png]]

<translate>====Other Ways==== If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  includes  joomla  version.php
  • You can also view the source code of the page. In the head section, even if the version is not clearly mentioned, you know that you are running 1.0 version if the content of the meta generator tag is Copyright (C) 2005 - 2007 Open Source Matters.</translate>

Joomla! 1.5.x

<translate>===How To Access===

From the Backend

  • Log in the backend of your website,
  • Go to Help  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the top right of every pages of the backend.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-1.5.x-<translate> en</translate>.png]]

<translate>====Other Ways==== If you don’t have access to the backend, here are other ways to find the Joomla! version :</translate> <translate>

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).</translate>

<translate>

  • By FTP, go to root  template  system  css  template.css: the version is not clearly mentioned, but you know that you are running 1.5 version thanks to this line: @copyright Copyright (C) 2005 - 2010 Open Source Matters. If you do not have a FTP access, you can also open the template.css file in your browser.</translate>

<translate>

  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.5.26 thanks to the 1st line of this .ini file: # $Id: en-GB.ini 11391 2009-01-04 13:35:50Z ian $.</translate>

<translate>

  • You can also view the source code of the page. In the head section, the version is mentioned in the content of the meta generator tag: Joomla! 1.5 - Open Source Content Management.</translate>


Joomla! 1.6.x

<translate>===How To Access===

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-1.6.x-<translate> en</translate>.png]]

<translate>====Other Ways==== If you don’t have access to the backend, here are other ways to find the Joomla! version :</translate> <translate>

  • By FTP, go to root  libraries  joomla  version.php.</translate>

<translate>

  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.6 version thanks to this line: @version $Id: system.css 20196 2011-01-09 02:40:25Z ian $. If you do not have a FTP access, you can also open the system.css file in your browser.</translate>

<translate>

  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.6.0 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20196 2011-01-09 02:40:25Z ian $ or 1.6.5 if the 1st line is ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $.</translate>

Joomla! 1.7.x

<translate>===How To Access===

From the backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-1.7.x-<translate> en</translate>.png]]

<translate>====Other Ways==== </translate> <translate> If you don’t have access to the backend, here are other ways to find the Joomla! version :</translate> <translate>

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).</translate>

<translate>

  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.7 version thanks to this line: @version $Id: system.css 21322 2011-05-11 01:10:29Z dextercowley $. If you do not have a FTP access, you can also open the system.css file in your browser.</translate>

<translate>

  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.7.1 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $, 1.7.3 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $, 1.7.5 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $.</translate>

Joomla! 2.5.x

<translate>===How To Access===

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-2.5.x-<translate> en</translate>.png]]

<translate>====Other Ways==== </translate> <translate> If you don’t have access to the backend, here are other ways to find the Joomla! version:</translate> <translate>

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).</translate>

<translate>

  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 2.5 thanks to this line: Copyright (C) 2005 - 2014 Open Source Matters, Inc. If you do not have a FTP access, you can also open the system.css file in your browser.</translate>

<translate>

  • By FTP, go to root  languages  en-GB  en-GB.xml: the version is mentioned in the file, in the version tag.</translate>

Joomla! 3.x.x

<translate>===How To Access===

From the Backend

  • Log in the backend of your website,
  • Go to System  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom right of every pages of the backend.</translate>

<translate>===Screenshot=== </translate> [[Image:Joomla-Version-3.4.x-<translate> en</translate>.png]]

<translate>====Other Ways==== If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).</translate>



How to check the Joomla version?/de


Du willst wissen welche Version von Joomla! auf Deiner Webseite läuft und Du weist nicht, wo es im Backend zu finden ist? Hier sind die verschiedenen Methoden, abhängig von der Joomla! - Version.

"'Denke daran, setze immer eine unterstützte Version von Joomla! ein!"'

Joomla! 1.0.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu Information  System Info: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, und auch PHP, Datenbank-Versionen und so weiter.

Screenshot

Joomla-Version-1.0.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff ins Backend hast, findest Du hier andere Möglichkeiten um die Joomla! Version herauszufinden :

  • Via FTP, gehe zu root  includes  joomla  version.php
  • Du kannst auch den Quellcode der Seite ansehen. Im Head-Bereich, auch wenn die Version nicht klar genannt wird, erfährts Du dass Version 1.0 läuft, wenn der Meta Generator Tag Copyright (C) 2005 - 2007 Open Source Matters. lautet.

Joomla! 1.5.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu Hilfe  System Info: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, und auch die PHP -, Datenbank Versionen u.s.w.

Die Joomla! Version wird auch auf allen Seiten des Backends oben rechts angezeigt.

Screenshot

Joomla-Version-1.5.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff auf das Backend hast, sind hier noch andere Möglichkeiten die Joomla! Version herauszufinden:

  • Per FTP, gehe zu root  librairies  joomla  version.php: die Version findest Du in den Zeilen var $RELEASE (in der Release-Version) und var $DEV_LEVEL (in der Wartungs-Version).
  • Per FTP, gehe zu root  template  system  css  template.css: nicht deutlich wird die Version erwähnt, aber wenn die folgende Zeile erscheint, kannst Du dir sicher sein, dass Version 1.5 läuft: @copyright Copyright (C) 2005 - 2010 Open Source Matters. Hast Du keinen FTP-Zugang, kannst Du auch die Datei template.css in Deinem Browser aufrufen.
  • Per FTP, gehe zu root  languages  en-GB  en-GB.ini: die Version wird nicht deutlich genannt. Du kannst dir aber sicher sein, dass Version 1.5.26 läuft, wenn # $Id: en-GB.ini 11391 2009-01-04 13:35:50Z ian $ in der 1.Zeile dieser .ini Datei steht.
  • Du kannst Dir auch den Quell-Code von der Seite ansehen. Im Head-Bereich steht die Version bereits in der Zeile: Meta-Generator-Tag: "Joomla! 1.5 - Open Source Content Management".


Joomla! 1.6.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu Site  System Information: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, und auch PHP, Datenbank-Versionen und so weiter.

Die Joomla! Version wird auch auf allen Seiten des Backends unten angezeigt.

Screenshot

Joomla-Version-1.6.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff auf das Backend hast, sind hier noch andere Möglichkeiten die Joomla! Version herauszufinden:

  • Per FTP, gehe zu root  libraries  joomla  version.php.
  • Per FTP, gehe zu root  template  system  css  system.css: die Version wird nicht klar genannt, aber wenn die folgende Zeile erscheint, kannst Du dir sicher sein dass Version 1.6 läuft: @version $Id: system.css 20196 2011-01-09 02:40:25Z ian $. Hast Du keinen FTP-Zugang, kannst Du auch die Datei system.css in Deinem Browser aufrufen.
  • Per FTP, gehe zu root  languages  en-GB  en-GB.ini: die Version wird nicht klar genannt, aber Du kannst Du dir sicher sein dass Version 1.6.0 läuft, wenn in der 1.Zeile der .ini-Datei $Id: en-GB.ini 20196 2011-01-09 02:40:25Z ian $ steht. Findest Du dort ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $ in der 1.Zeile, dann ist es Version 1.6.5.

Joomla! 1.7.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu Site  System Info: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, auch die PHP - und Datenbank Versionen u.s.w.

Screenshot

Joomla-Version-1.7.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff auf das Backend hast, sind hier noch andere Möglichkeiten die Joomla! Version herauszufinden:

  • Per FTP, gehe zu root  librairies  joomla  version.php: die Version findest Du in den Zeilen var $RELEASE (für die Release-Version) und var $DEV_LEVEL (für die Wartungs-Version).
  • Per FTP, gehe zu root  template  system  css  system.css: die Version wird nicht klar genannt, aber wenn die folgende Zeile erscheint, kannst Du dir sicher sein dass Version 1.7 läuft: @version $Id: system.css 21322 2011-05-11 01:10:29Z dextercowley $. Hast Du keinen FTP-Zugang, kannst Du auch die Datei system.css in Deinem Browser aufrufen.
  • Per FTP, gehe zu root  languages  en-GB  en-GB.ini: die Version wird nicht klar genannt, aber Du kannst Du dir sicher sein dass Version 1.7.1 läuft, wenn in der 1.Zeile der .ini-Datei $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $ steht. Findest Du dort ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $ in der 1.Zeile, dann ist es Version 1.7.3, oder Version 1.7.5 bei: ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $.

Joomla! 2.5.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu Site  System Information: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, auch die PHP - und Datenbank Versionen u.s.w.

Die Joomla! Version wird auch unten auf jeder Seite des Backends angezeigt.

Screenshot

Joomla-Version-2.5.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff auf das Backend hast, sind hier noch andere Möglichkeiten die Joomla! Version herauszufinden:

  • Per FTP, gehe zu root  librairies  joomla  version.php: die Version findest Du in den Zeilen var $RELEASE (in der Release-Version) und var $DEV_LEVEL (in der Wartungs-Version).
  • Per FTP, gehe zu root  template  system  css  template.css: nicht deutlich wird die Version erwähnt, aber wenn die folgende Zeile erscheint, kannst Du dir sicher sein, dass Version 2.5 läuft: Copyright (C) 2005 - 2014 Open Source Matters, Inc. Hast Du keinen FTP-Zugang, kannst Du auch die Datei system.css in Deinem Browser öffnen.
  • Per FTP gehe zu root  languages  en-GB  en-GB.xml: die Version steht in in der Datei, im "version" Tag.

Joomla! 3.x.x

Wie zugreifen

Aus dem Backend

  • Logge Dich im Backend Deiner Webseite ein,
  • Gehe zu System  System Information: diese Ansicht enthält alle System Informationen die Du brauchst, die aktuell laufende Joomla! Version, und auch PHP, Datenbank-Versionen und so weiter.

Die Joomla! Version wird auch auf allen Seiten des Backends unten rechts angezeigt.

Screenshot

Joomla-Version-3.4.x-en.png

Andere Möglichkeiten

Wenn Du keinen Zugriff auf das Backend hast, gibt es hier noch andere Möglichkeiten, die Joomla! Version zu finden :

  • Per FTP, gehe zu root  librairies  cms  version  version.php: die Version findest Du in den Zeilen public $RELEASE (in der Release-Version) und public $DEV_LEVEL (in der Wartungs-Version).



How to check the Joomla version?/en


You need to know which version of Joomla! is running on your website and you don't know where to find it in the backend? Here are the different methods, depending on the Joomla! version.

Remember, you should always use a supported version of Joomla!

Joomla! 1.0.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Information  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

Screenshot

Joomla-Version-1.0.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  includes  joomla  version.php
  • You can also view the source code of the page. In the head section, even if the version is not clearly mentioned, you know that you are running 1.0 version if the content of the meta generator tag is Copyright (C) 2005 - 2007 Open Source Matters.

Joomla! 1.5.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Help  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the top right of every pages of the backend.

Screenshot

Joomla-Version-1.5.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  template.css: the version is not clearly mentioned, but you know that you are running 1.5 version thanks to this line: @copyright Copyright (C) 2005 - 2010 Open Source Matters. If you do not have a FTP access, you can also open the template.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.5.26 thanks to the 1st line of this .ini file: # $Id: en-GB.ini 11391 2009-01-04 13:35:50Z ian $.
  • You can also view the source code of the page. In the head section, the version is mentioned in the content of the meta generator tag: Joomla! 1.5 - Open Source Content Management.


Joomla! 1.6.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.

Screenshot

Joomla-Version-1.6.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  libraries  joomla  version.php.
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.6 version thanks to this line: @version $Id: system.css 20196 2011-01-09 02:40:25Z ian $. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.6.0 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20196 2011-01-09 02:40:25Z ian $ or 1.6.5 if the 1st line is ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $.

Joomla! 1.7.x

How To Access

From the backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

Screenshot

Joomla-Version-1.7.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.7 version thanks to this line: @version $Id: system.css 21322 2011-05-11 01:10:29Z dextercowley $. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.7.1 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $, 1.7.3 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $, 1.7.5 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $.

Joomla! 2.5.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.

Screenshot

Joomla-Version-2.5.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version:

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 2.5 thanks to this line: Copyright (C) 2005 - 2014 Open Source Matters, Inc. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.xml: the version is mentioned in the file, in the version tag.

Joomla! 3.x.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to System  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom right of every pages of the backend.

Screenshot

Joomla-Version-3.4.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).



How to check the Joomla version?/pt-br


You need to know which version of Joomla! is running on your website and you don't know where to find it in the backend? Here are the different methods, depending on the Joomla! version.

Remember, you should always use a supported version of Joomla!

Joomla! 1.0.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Information  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

Screenshot

Joomla-Version-1.0.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  includes  joomla  version.php
  • You can also view the source code of the page. In the head section, even if the version is not clearly mentioned, you know that you are running 1.0 version if the content of the meta generator tag is Copyright (C) 2005 - 2007 Open Source Matters.

Joomla! 1.5.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Help  System Info: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the top right of every pages of the backend.

Screenshot

Joomla-Version-1.5.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  template.css: the version is not clearly mentioned, but you know that you are running 1.5 version thanks to this line: @copyright Copyright (C) 2005 - 2010 Open Source Matters. If you do not have a FTP access, you can also open the template.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.5.26 thanks to the 1st line of this .ini file: # $Id: en-GB.ini 11391 2009-01-04 13:35:50Z ian $.
  • You can also view the source code of the page. In the head section, the version is mentioned in the content of the meta generator tag: Joomla! 1.5 - Open Source Content Management.


Joomla! 1.6.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.

Screenshot

Joomla-Version-1.6.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  libraries  joomla  version.php.
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.6 version thanks to this line: @version $Id: system.css 20196 2011-01-09 02:40:25Z ian $. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.6.0 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20196 2011-01-09 02:40:25Z ian $ or 1.6.5 if the 1st line is ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $.

Joomla! 1.7.x

How To Access

From the backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

Screenshot

Joomla-Version-1.7.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  joomla  version.php: the version is mentioned in the lines var $RELEASE (for the release version) and var $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 1.7 version thanks to this line: @version $Id: system.css 21322 2011-05-11 01:10:29Z dextercowley $. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.ini: the version is not clearly mentioned, but you know that you are running 1.7.1 thanks to the 1st line of this .ini file ; $Id: en-GB.ini 20990 2011-03-18 16:42:30Z infograf768 $, 1.7.3 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $, 1.7.5 if the 1st line is ; $Id: en-GB.ini 22183 2011-09-30 09:04:32Z infograf768 $.

Joomla! 2.5.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to Site  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom of every pages of the backend.

Screenshot

Joomla-Version-2.5.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version:

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).
  • By FTP, go to root  template  system  css  system.css: the version is not clearly mentioned, but you know that you are running 2.5 thanks to this line: Copyright (C) 2005 - 2014 Open Source Matters, Inc. If you do not have a FTP access, you can also open the system.css file in your browser.
  • By FTP, go to root  languages  en-GB  en-GB.xml: the version is mentioned in the file, in the version tag.

Joomla! 3.x.x

How To Access

From the Backend

  • Log in the backend of your website,
  • Go to System  System Information: this screen contains all system information you may need, the Joomla! Version currently running, and also PHP, database versions and so on.

The Joomla! version is also mentioned at the bottom right of every pages of the backend.

Screenshot

Joomla-Version-3.4.x-en.png

Other Ways

If you don’t have access to the backend, here are other ways to find the Joomla! version :

  • By FTP, go to root  librairies  cms  version  version.php: the version is mentioned in the lines public $RELEASE (for the release version) and public $DEV_LEVEL (for the maintenance version).



Issues with the Contact form and Gmail and GoogleApps

Problem

The reply-to email address is not used when replying to emails sent from the Contact component and the email is sent to yourself.

Explanation

Joomla sends emails from the Contacts component with the following headers

From: email address set as the site email address in the global configuration '"To:'" email address set in the contact component '"Reply-to:'" email address of the person who submitted the contact form

Expected Behaviour

On receiving the email you should be able to hit reply and the email is sent to the email address set in the reply-to field. This is the correct behaviour as defined in the Internet (http://tools.ietf.org/html/rfc5322).

Known Issue

IF you are using Gmail or GoogleApps AND the "From" address is one of your "Send mail as" addresses then the "Reply-to" email address is ignored and the reply is sent to the "From" address.

Solution

The best solution to this is to set the site email address in the global configuration for your website to an email address that is NOT one of your "Send mail as" addresses in Gmail.


Joomla Update Missing in from Admin Menu

Starting with version 2.5.4, the Joomla core is updated with the new component Joomla Update instead of in Extensions/Install/Update.

If Joomla Update does not shows as an installed component the menuitem could be wrong. Run this SQL statement:

UPDATE #__menu
SET component_id =
  (SELECT extension_id FROM #__extensions WHERE name = "com_joomlaupdate")
WHERE title = "com_joomlaupdate"

It should update 1 row, if not use the Discover function and install it as a component.

If Joomla Update shows as an installed component but is not in the Admin Menu under Components, you are missing the entry in the database table #__menu.

INSERT INTO `#__menu` (`menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) 
VALUES ('menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, (SELECT extension_id FROM #__extensions WHERE `name` = 'com_joomlaupdate'), 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);

Replace the "#_" of #__menu and #__extensions with the prefix of your database table (System --> Global Configuration --> Server --> Database Tables Prefix).

Example: vy2bp_menu and vy2bp_extensions (only one underline)

Missing-intro-text-and-images-in 2.5.10

Updating to 2.5.10 may lead to the "disappearance" of intro text and images from featured or blog article views. To fix please update to 2.5.11.

If for some reason updating to 2.5.11 is not possible, change "Show Intro Text" to Show. This may temporarily cause your full article to display the intro text when you don't want that. In that case you should change the Show Intro Text for each impacted article to Hide. A more complete solution can also be implemented by creating a template override.


Missing Save buttons on editing an article

When trying to edit an article there are missing buttons

  • Save & New
  • Save as Copy

See this tracker item, including the patch.


Modals Stop Working When Upgrading to 2.5.0

When upgrading from 1.7.3 to 2.5.0, modal "pop-ups" may stop working and be displayed full-page (as seen below) with the Save, Save and Close, and Cancel buttons unresponsive.

Joomla-2-5-0-upgrade-article-options-modal-browser-cache-issue.png

This issue is caused by changes to the Administrative template. The fix is to clear your browser's cache. For specific instructions on how to do this, please see:

Multilingual-problems-after-updating-to-2.5.11-or-3.1.1

Some (but not all) multilingual sites experience a problem where all content not in the default language is not displayed and the language filter module does not seem to work.


An official fix is not yet announced. However there were two changes that may be causing this issue and users may want to try fixing these. Try each fix in order and test to see if it resolves the problem.

First, if you have contact data you must ensure that every contact has a language (if it says "Undefined" in the contact manager, that tells you no language is assigned) and every contact that has a linked user should either have a version set to language ALL or else have one version set to each content language used on your site. That is if you have 3 languages you must either have 3 separate contacts or you must have one set to all.


Second, open the language filter plugin, make sure the cookie lifetime is set to year and save.



No-updates-shown-in-current-version

There are some reports that updates that have been released are not shown in the current (older) version. If this occurs, go to the Updates tab of the Extensions Manager. Click the clear cache icon. Then click the check for updates icon.


Please first make a selection from the list

This error message manifests on Administrator Forms for many non-core extensions even when an item has been selected.

This backwards compatibility error will be fixed in core for 2.5.1.

Temporary Workaround

Install the plugin from this forum item [2]

Extension Developers

To address this problem now so that your users do not have to wait for a core fix, update your Administrator forms and change name="adminForm" to id="adminForm". If backwards compatibility is required, simply use both values in the form definition. In future releases, Joomla will only support id="adminForm"

Patch

A patch has been created to fix the backwards compatibility in 2.5.1


Should I launch a Joomla! 2.5 site or a 3.x site?


<translate> Joomla! 2.5 reached EOS (end of support) the 31 Dec 2014. That means that since that day it will recieve no further attention or support from the Joomla! Project. No more maintenance or security releases. So you should not start a new site with Joomla! 2.5, but always Joomla! 3.3 or greater. </translate>

<translate> Sites that are currently on Joomla! 2.5 are encouraged to start planning now for a migration to 3.3 or greater now. We’ve provided a one-click upgrade from Joomla! 2.5 to any Joomla! 3 version and you just have to make sure that all your extensions and template are compatible with Joomla! 3.x before upgrading. See Planning for Mini-Migration - Joomla 2.5 to 3.x (See the “How do I find Joomla 3.x compatible extensions?” FAQ below for more information) </translate>

<translate> See also: Why Migrate and all the related pages.</translate>


Should I launch a Joomla! 2.5 site or a 3.x site?/en


Joomla! 2.5 reached EOS (end of support) the 31 Dec 2014. That means that since that day it will recieve no further attention or support from the Joomla! Project. No more maintenance or security releases. So you should not start a new site with Joomla! 2.5, but always Joomla! 3.3 or greater.

Sites that are currently on Joomla! 2.5 are encouraged to start planning now for a migration to 3.3 or greater now. We’ve provided a one-click upgrade from Joomla! 2.5 to any Joomla! 3 version and you just have to make sure that all your extensions and template are compatible with Joomla! 3.x before upgrading. See Planning for Mini-Migration - Joomla 2.5 to 3.x (See the “How do I find Joomla 3.x compatible extensions?” FAQ below for more information)

See also: Why Migrate and all the related pages.


Should I update from Joomla! 2.5 to 3.x?


<translate> In most cases, you will need to start planning on an upgrade to Joomla! 3.x ASAP. Joomla! 2.5 has reached EOS (end of support) as of December 31st of 2014. Joomla 3 is stable and should be the choice for production sites. </translate>

<translate> You will need to verify your template and components will work with Joomla! 3.x before upgrading. All core components are upgrade ready right now. </translate>

<translate> Please see Why Migrate for more details on migration from 2.5 to 3.x. </translate>


Should I update from Joomla! 2.5 to 3.x?/en


In most cases, you will need to start planning on an upgrade to Joomla! 3.x ASAP. Joomla! 2.5 has reached EOS (end of support) as of December 31st of 2014. Joomla 3 is stable and should be the choice for production sites.

You will need to verify your template and components will work with Joomla! 3.x before upgrading. All core components are upgrade ready right now.

Please see Why Migrate for more details on migration from 2.5 to 3.x.


Update did not finish successfully

In some slower shared host environments (for example, godaddy.com), the automatic update methods can fail in some cases. This appears to happen when the server is busy and the update is unable to complete within a given amount of time (for example, in 2 minutes for godaddy.com).

In this case, the update may be partially completed and the site may be damaged. You can repair the site using the Manually Copy New Program Files update method.

Also, there is a free third party extension called Admin Tools that can do updates on slower shared host systems.

See also


Version number is missing in back-end 2.5.0

In older versions of Joomla the version number is displayed in the footer of the back-end.

In Joomla 2.5.0 the version is shown in the System Information and is no longer coded in the admin template for security reasons. This is inconvenient and this has been discussed in the Joomla BugSquad.

The Joomla Bug Squad has developed a little admin module that shows the version in the footer position of your admin template like

Joomla! 2.5.0 Stable [ Ember ] 24-Jan-2012 14:00 GMT

and will be updated automatically with each release in your administrator back-end.

More information, see: http://forum.joomla.org/viewtopic.php?p=2727456#p2727456


What are the major differences between Joomla! 2.5 and 3.x?


<translate> The most noticeable difference is the totally revamped administrator, which is updated to a modern design with many simpler and more friendly user-interfaces. Also, starting with Joomla! 3.0, Joomla! is now device responsive. Simply, Joomla! is mobile friendly and can be used with any modern device. </translate>

<translate> In addition, there are dozens of improvements to the details of all of the Joomla core. Some highlights are: </translate>

  • <translate>

A new installer which you will notice when creating a new Joomla! 3.x install.</translate>

  • <translate>

Joomla! 3 is packed with goodies for extension developers, such as Bootstrap support and jQuery support.</translate>

Joomla! 3.1

  • <translate>

Tags</translate>

Joomla! 3.2

<translate>

  • Content version control
  • Many user interface improvements
  • Easy multi-lingual setup for 64 officially supported languages
  • Built-in Joomla! Extensions Finder as an onsite interface to the Joomla! Extensions Directory (that currently lists over 6,000 extensions) providing one-click extensions installation
  • Increased security with strong passwords and two step authentication
  • New rapid development framework for new extension coding

</translate>

Joomla! 3.3

  • <translate>

Microdata</translate>

Joomla! 3.4

<translate>

  • Front-end Module Editing,
  • Decoupling com_weblinks,
  • Composer Integration,
  • No CAPTCHA reCAPTCHA,
  • Core en-GB standardisation...

</translate>

<translate>

Joomla! 3.5

</translate> <translate>

  • PHP 7 Support
  • Update Notifications via Email
  • System Information Export
  • Drag & Drop Images
  • Anonymised System Data
  • Easily Insert Modules in Articles
  • Item counter (+ click through filter) in Category Manager
  • Random category blog and list order view.</translate>

<translate>

Joomla! 3.6

</translate> <translate>

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.</translate>


What are the major differences between Joomla! 2.5 and 3.x?/en


The most noticeable difference is the totally revamped administrator, which is updated to a modern design with many simpler and more friendly user-interfaces. Also, starting with Joomla! 3.0, Joomla! is now device responsive. Simply, Joomla! is mobile friendly and can be used with any modern device.

In addition, there are dozens of improvements to the details of all of the Joomla core. Some highlights are:

  • A new installer which you will notice when creating a new Joomla! 3.x install.
  • Joomla! 3 is packed with goodies for extension developers, such as Bootstrap support and jQuery support.

Joomla! 3.1

  • Tags

Joomla! 3.2

  • Content version control
  • Many user interface improvements
  • Easy multi-lingual setup for 64 officially supported languages
  • Built-in Joomla! Extensions Finder as an onsite interface to the Joomla! Extensions Directory (that currently lists over 6,000 extensions) providing one-click extensions installation
  • Increased security with strong passwords and two step authentication
  • New rapid development framework for new extension coding

Joomla! 3.3

  • Microdata

Joomla! 3.4

  • Front-end Module Editing,
  • Decoupling com_weblinks,
  • Composer Integration,
  • No CAPTCHA reCAPTCHA,
  • Core en-GB standardisation...

Joomla! 3.5

  • PHP 7 Support
  • Update Notifications via Email
  • System Information Export
  • Drag & Drop Images
  • Anonymised System Data
  • Easily Insert Modules in Articles
  • Item counter (+ click through filter) in Category Manager
  • Random category blog and list order view.

Joomla! 3.6

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.


What are the major differences between Joomla! 2.5 and 3.x?/fa


The most noticeable difference is the totally revamped administrator, which is updated to a modern design with many simpler and more friendly user-interfaces. Also, starting with Joomla! 3.0, Joomla! is now device responsive. Simply, Joomla! is mobile friendly and can be used with any modern device.

In addition, there are dozens of improvements to the details of all of the Joomla core. Some highlights are:

  • A new installer which you will notice when creating a new Joomla! 3.x install.
  • Joomla! 3 is packed with goodies for extension developers, such as Bootstrap support and jQuery support.

Joomla! 3.1

  • Tags

Joomla! 3.2

  • Content version control
  • Many user interface improvements
  • Easy multi-lingual setup for 64 officially supported languages
  • Built-in Joomla! Extensions Finder as an onsite interface to the Joomla! Extensions Directory (that currently lists over 6,000 extensions) providing one-click extensions installation
  • Increased security with strong passwords and two step authentication
  • New rapid development framework for new extension coding

Joomla! 3.3

  • Microdata

Joomla! 3.4

  • Front-end Module Editing,
  • Decoupling com_weblinks,
  • Composer Integration,
  • No CAPTCHA reCAPTCHA,
  • Core en-GB standardisation...

Joomla! 3.5

  • PHP 7 Support
  • Update Notifications via Email
  • System Information Export
  • Drag & Drop Images
  • Anonymised System Data
  • Easily Insert Modules in Articles
  • Item counter (+ click through filter) in Category Manager
  • Random category blog and list order view.

جوملا! 3.6

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.


What are the major differences between Joomla! 2.5 and 3.x?/it


La differenza più evidente è l'amministrazione che è stata totalmente rinnovata, è stata aggiornata con un design moderno e molto più semplice. Inoltre, a partire dalla versione 3.0, Joomla! è ora di dispositivo responsivo. Semplicemente, Joomla! è mobile-friendly e può essere utilizzato con qualsiasi dispositivo moderno.

In aggiunta, ci sono decine di miglioramenti ai dettagli di tutti i core di Joomla. Alcuni punti salienti sono:

  • Un nuovo programma di installazione che si noterà quando si crea una nuova installazione di Joomla! 3.x.
  • Joomla! 3 è pieno di chicche per gli sviluppatori di estensioni, come il sostegno e il supporto a Bootstrap e a jQuery.

Joomla! 3.1

  • Tag

Joomla! 3.2

  • Controllo di versione dei contenuti
  • Molti miglioramenti dell'interfaccia utente
  • Impostazione multilingue facile per 64 lingue ufficialmente supportate
  • Built-in Joomla! Estension Finder come interfaccia al posto di Joomla! Extensions Directory (che attualmente annovera più di 6.000 estensioni) che fornisce l'installazione di estensioni con un solo click
  • Maggiore sicurezza con password complesse e l'autenticazione in due fasi
  • Nuovo framework di sviluppo per l'implementazione di nuove estensioni

Joomla! 3.3

  • I microdati

Joomla! 3.4

  • Front-end Module Editing
  • Il disaccoppiamento com_weblinks,
  • Compositore Integrazione
  • No CAPTCHA reCAPTCHA,
  • Core standardizzato per en-GB ...

Joomla! 3.5

  • Supporto a PHP 7
  • Notifiche di aggiornamento via e-mail
  • Export delle Informazioni di sistema
  • Drag & Drop Immagini
  • Anonimizzazione dei dati di sistema
  • Inserimento facilitato dei moduli negli articoli
  • Conteggio delle operazioni (+ clicca attraverso il filtro) nella Gestione Categorie
  • Categoria blog casuale e liste ordinate.

Joomla! 3.6

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.


What are the major differences between Joomla! 2.5 and 3.x?/pt


A mais notável diferença é a total renovada administração, que é atualizada para um design moderno, com muitas e as mais simples e amigável interface para utilizador. Também, começando com o Joomla! 3.0, o Joomla! é agora responsive para qualquer dispositivo. O Joomla!, é Simplesmente amigável e pode ser usado com qualquer dispositivo moderno.

Além disso, existem dezenas de melhorias para os detalhes de todas as Joomla core. Alguns destaques são:

  • Um novo instalador onde vai notar com a criação do novo instalador do Joomla! 3.x .
  • Joomla! 3 está repleto de guloseimas para os programadores de extensão, como o apoio ao Bootstrap, jQuery.

Joomla! 3.1

  • Tags

Joomla! 3.2

  • Controle de versão de conteúdo
  • Muitas melhorias na interface de utilizador
  • Fácil multi-línguas de instalação para as versões de 64 suportadas oficialmente idiomas
  • Construído-em Joomla! Extensões Finder como um local de interface para o Joomla! Diretório de extensões (que atualmente inclui mais de 6.000 extensões), proporcionando um clique de instalação de extensões
  • Maior segurança com senhas fortes e duas etapas de autenticação.
  • Novo framework de desenvolvimento rápido para a nova extensão de codificação.

Joomla! 3.3

  • Microdados

Joomla! 3.4

  • Front-end do Módulo de Edição
  • Dissociação com_weblinks,
  • Compositor De Integração,
  • No CAPTCHA reCAPTCHA,
  • Núcleo de en-GB normalização...

Joomla! 3.5

  • PHP 7 Support
  • Update Notifications via Email
  • System Information Export
  • Drag & Drop Images
  • Anonymised System Data
  • Easily Insert Modules in Articles
  • Item counter (+ click through filter) in Category Manager
  • Random category blog and list order view.

Joomla! 3.6

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.


What are the major differences between Joomla! 2.5 and 3.x?/ru


Наиболее заметное различие - это полностью измененный административный [интерфейс], который обновлен на современный дизайн со многими более простыми и более дружелюбными пользователю элементами. Также, начиная с версии 3.0, Joomla! теперь респонзивна [для мобильных] устройств. [Говоря] по-простому, Joomla! является дружелюбной мобильным [устройствам] и может быть использована на любом современном устройстве.

В дополнение, существуют дюжины мелких улучшений, [внесенных в] ядро Joomla!. Некоторые из них:

  • Новый установщик, который Вы заметите при создании новой установки Joomla! 3.x.
  • Joomal! 3 забита цацками для разработчиков расширений, таких как поддержка [библиотеки CSS] "Bootstrap" и [библиотеки JavaScript] "jQuery".

Joomla! 3.1

  • Метки

Joomla! 3.2

  • Контроль версий содержимого
  • Много улучшений интерфейса пользователя
  • Легкая настройка мульти-языковости с 64 официально поддерживаемыми языками
  • Встроенный поиск расширений Joomla! в качестве встроенного интерфейса [официального каталого расширений] "Joomla! Extensions Directory" (который в настоящее время перечисляет более шести тысячи расширений)
  • Укрепленная защита сильными паролями и двух-факторной аутентикацией
  • Новый фреймворк быстрой разработки для кодирования новых расширений

Joomla! 3.3

  • Микроданные

Joomla! 3.4

  • Редактирование модулей с лицевых страниц
  • Изъятие [компонента] com_weblinks
  • Интеграция с менеджером зависимостей РНР "Composer"
  • Интеграция с "No CAPTCHA reCAPTCHA" от Google
  • Стандартизация британского английского языка ядра

Joomla! 3.5

  • PHP 7 Support
  • Update Notifications via Email
  • System Information Export
  • Drag & Drop Images
  • Anonymised System Data
  • Easily Insert Modules in Articles
  • Item counter (+ click through filter) in Category Manager
  • Random category blog and list order view.

Joomla! 3.6

  • Show all menu items
  • Menu type ACL
  • Improved UX
  • Categories on the fly
  • Subform field
  • Improved Joomla! Updates
  • Allow stream connections to support proxies
  • Build more complex database queries with new database query classes
  • Delete all cache
  • Delete and rebuild Extension Update Sites
  • Easier template development with deeper JLayout integrations
  • htaccess authentication for calls
  • Improved Storage of dynamic JavaScript variables
  • Improved Validation performance
  • jQuery Update
  • More Extension Details in System info
  • Multilanguage ToS
  • New “Showon” Option for fieldsets in component config
  • New Log folder (for new installs only)
  • New positioning settings for Bootstrap tooltips extended
  • Protostar adds a new override for the Site Offline Page
  • Reverse Caching Support
  • SASS & SCSS File Support in Joomla! Template Manager
  • Updated version of the CodeMirror editor.


What do the locks mean and how do you get rid of them?

At any given time you may see a padlock next to a specific item in Joomla!'s administrative backend. These padlocks may be displayed next to any of the following (Content Items, Menu Items, Modules, etc).

The Joomla! system places these padlocks next to an item to indicate that a user is currently editing the item (i.e. the item is "checked out"). The lock is removed when the user clicks on the "Save" or "Close" button for that item. If the user never clicks "Save" or "Close" and instead hits the "Back" button or navigates to another page, then the item remains locked. If a different user needs to work with an item that is in the "checked out" state he or she must first ask a manager or administrator to check the item in before any new changes can be made.

Checking Items In

There are three ways of checking items back in. One way is to contact the person that has the item checked out to see if they are done with the item. You can hover the cursor above the lock and the tooltip popup will display the name of the user who checked out the article.

If you have access to the administrative backend and sufficient rights and can also either click on the padlock to check only this item back in or click on Site->Maintenance->Global Check-in to check all items in.

The later option should be used very carefully, especially in multi-user environments. This single action checks in all previously checked out items, whether they were checked out by you or not. Possible undesirable side effects may be that multiple editors end up working on the same document. In this case whoever clicks the save button last has their version saved as the final copy.


What if an extension only works on Joomla! 2.5 and not 3.x?


<translate> You need to speak with the extension developer to see if they have plans to release that extension for Joomla! 3 in the immediate future. Developers do have to make some changes but how extensive they are depends on the extension.

</translate>

What if an extension only works on Joomla! 2.5 and not 3.x?/en


You need to speak with the extension developer to see if they have plans to release that extension for Joomla! 3 in the immediate future. Developers do have to make some changes but how extensive they are depends on the extension.


What is the contact creator?


The contact creator is a plugin that automatically creates a linked contact record every time you create a new user.

The contact creator is disabled by default; enable it in the plugin manage.


What is the profile plugin?


The profile plugin makes it possible to add extra fields to the user profile form in 4 places:

  • The registration form
  • The frontend profile editing view
  • The backend profile editing view (My Profile)
  • The backend user manager user edit view.

Each of these are controlled independently. They can all be the same or specific fields can be available in each form. Similarly, fields can be set as required independently for each form or all can be the same.

Any field type from the form library can be used.

Optionally the profile for a linked user can be displayed in linked content record.

Multiple profile plugins may be used.

See Creating a profile plugin for more details.


What version of Joomla! should you use?


<translate> First of all, you may want to check which version of Joomla! is running on your website.</translate> {{:Joomla! CMS versions/<translate> en</translate>}}

<translate>

Included External Libraries

</translate> {{:External Libraries in Joomla/<translate> en</translate>}}

<translate>

Joomla! versions explained

</translate> {{:Release_and_support_cycle/<translate> en</translate>}}

<translate>==References and Notes== </translate>


What version of Joomla! should you use?/bg


Преди всичко, трябва да се провери каква е версия на Joomla, с която работи Вашия уеб сайт. Joomla! CMS versions/bg

Допълнителни външни библиотеки

External Libraries in Joomla/bg

Преглед на Joomla! версиите

Release and support cycle/bg

Линкове и бележки


What version of Joomla! should you use?/de


Zu allererst solltest Du prüfen, mit welcher Joomla! Version Deine Webseite läuft.

Überprüfe die neueste Version des Joomla! CMS. Wenn Sie nicht die neueste Version installiert haben, lesen Sie die Release Notes und schauen Sie nach, ob Sie ein Upgrade benötigen. Wurde ein Release auf Grund von Sicherheitsproblemen erstellt, raten wir dringend dazu das Upgrade so bald wie möglich einzuspielen. Die Veröffentlichungshistorie jeder Serie wird in der unten angegebenen Tabelle aufgeführt. Klicken Sie den Link zur Versionsgeschichte in der Spalte Notizen um Details zum exacten Release Datum, den Release Notes, den Packages und den MD5s zu bekommen.

  • Normalerweise sollten Sie die neueste Version von Joomla! für eine neue Website verwenden, es sei denn, Sie haben einen bestimmten Grund, dies nicht zu tun.
  • Die neueste Version kann hier herunter geladen werden Joomla! Download-Seite.

Versichern Sie sich, dass Sie den Joomla! Sicherheitsmeldungen Feed abboniert haben. Dieser RSS Feed wird für Meldungen und Ankündigungen neuer Releases genutzt, die die Sicherheit Ihrer Seite betreffen könnten. Sie können sich für den Feed mit E-Mail oder per RSS anmelden.

  • Wenn Sie mit einer früheren Version als der aktuellen Version arbeiten (zum Beispiel arbeiten Sie mit 3.1.6 und die aktuelle Version ist bereits 3.4.1), sollten Sie ein Upgrade auf die aktuelle Version vornehmen. Jedes Minor-Release behebt eine Reihe von Fehlern und/oder Sicherheitslücken. Ein Upgrade auf die neueste Version ist immer der beste Weg um die ersten Schritte in der Fehlersuche zu machen und neu entdeckte Sicherheitslücken zu schließen.

Joomla! CMS Versionen

CMS Version Verfügbar Support Ende der Lebenszeit Upgrade-Typ Hinweise Neueste Veröffentlichungen
Bugs Sicherheit
1.5
X-mark.png
X-mark.png
X-mark.png
Sep 2012 Migration auf 2.5 Planen Sie die Migration auf 2.5 jetzt
Joomla 1.5 version history
EOL für 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Aug 2011 One-click auf 2.5 Upgrade auf 2.5 jetzt
Joomla 1.6 version history
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Feb 2012 One-click auf 2.5 Upgrade auf 2.5 jetzt
Joomla 1.7 version history
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
31. Dezember 2014 One-click auf 3.x Upgrade auf 3.6.0 jetzt
Joomla 2.5 version history
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
Mai 2013 One-click auf 3.1 Nutzen Sie das One-Click Upgrade
Joomla 3.0 version history
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Dez 2013 One-click auf 3.2 Sie sollten das One-Click upgrade verwenden
Joomla 3.1 version history
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Okt 2014

[1]

One-click auf 3.3 PHP sollte serverseitig auf 5.3.10 oder höher eingestellt werden, bevor Sie auf Joomla! 3.3 upgraden.
Joomla 3.2 version history
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
3.4 Release One-click Sie sollten das One-Click upgrade verwenden
Joomla 3.3 version history
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
3.5 Release One-click Für alle Neuinstallationen empfohlen
Joomla 3.4 Versions-Historie
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
3.6 Release One-click Für alle Neuinstallationen empfohlen
Joomla 3.5 Versions-Historie
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
3.7 Release One-click Für alle Neuinstallationen empfohlen
Joomla! 3.6 Versions-Historie
3.6.0
3.7[2] noch offen[2][3] - - 3.8 Release One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Eingebundene Externe Bibliotheken

Eine Joomla! Installation enthält externe Bibliotheken, die in veröffentlichten Joomla! CMS-Versionen enthalten sind. Diese externen Bibliotheken sind kein Bestandteil des Kern-Codes. Bitte lies den Abschnitt Hinweise, da dieser weitere Informationen enthält, zum Beispiel die Änderung der externen Bibliothekenversion in einer Wartungsversion.

Externe Bibliotheken je Joomla! Version

CMS-Version Unterstützte CMS-Version Mootools Mehr Mootools jQuery jQuery UI
(Kern, Widget -, Maus -, Position und Sortierung)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)
password _compat[4] lessphp random _compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 N/A[7] N/A[7] N/A[7] 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Erklärte Joomla! Versionen

Joomla! 
3.6.0
Stabile Version

Diese Seite enthält eine Zusammenfassung der am 25. April 2014 veröffentlichten aktuellen Entwicklungs-Strategie. Alle vor dem 25. April 2014 veröffentlichten Joomla!-Versionen wurden entsprechend dem vorherigen Release - und Support Kreislauf entwickelt. Für eine ausführlichere Erklärung lies den vollständigen Text über die Joomla! Entwicklungs-Strategie.

Joomla! wird in Anlehnung an die Semantische Versionierung (2.0.0) entwickelt. Nicht mehr eingesetzt werden LTS (Lang Zeit Support) und STS (Kurz Zeit Support). Die Begriffe direkt unterhalb erklären die Versionierungs-Begriffe und Ihre Bedeutungen.

  • supported - (unterstützt) letzte Minor-Version(en) einer Major-Version bekommt Patches mit Fehlerbehebungen und Schließung von Sicherheitslücken
  • current - (gültig) die jüngste oder 'letzte' Major.x.x offiziell veröffentlichte Version
  • legacy - (überholt) jede Major.Minor.Patch Version(en) welche nicht die gültige Version ist[16]
  • stable - (stabil) die zur Nutzung in einer produktiven Umgebung fertige Major-Version mit den eingebundenen gültigen und überholten Versionen[17]
  • EOS - eine Abkürzung für 'End Of Support / Supportende' und bedeutet, dass keine weiteren Patches mit Fehlerbehebungen oder Schließung von Sicherheitslücken veröffentlicht werden
  • EOL - eine Abkürzung für 'End Of Life / Lebensende' und hat die gleiche Bedeutung wie EOS[18]

Jede Major-Version von Joomla! wird vom Joomla! ProjectTM für einen begrenzten Zeitraum unterstützt, anfangend vom ersten Tag der offiziellen Veröffentlichung. Joomla! wird die weitere Entwicklung einer Major-Version für mindestens 2 Jahre fortsetzen. Es kann die weitere Entwicklung einer Major-Version folgen, gemäß der Major-Version Roadmap. [19] Eine kurze Zusammenfassung wäre:

  • Jede Major-Version wird mindestens 4 Jahre unterstützt
  • Du solltest immer die letzte Major-Version einsetzen oder zur letzten Major-Version Minor.Patch aktualisieren
  • Jedes veröffentlichte Minor-Versions-Update ist abwärts kompatibel mit der vorherigen Minor-Version der gleichen Major-Version[20]

Bitte verwende die Joomla! CMS Entwicklungs Roadmap oder das Joomla! CMS Versions-Diagramm um das geschätze EOS (Supportende) für jede Major.Minor Version oder die gesamte Major-Version zu bestimmen.

Erklärung der Versions-Nummerierung

Die Versions-Bezeichner für Joomla! folgen einer dreistufigen Zahlen-Konvention in denen die Stufen von bedeutenden Software-Veränderungen definiert werden.

[major].[minor].[patch]

Diese 3 Ebenen sind wie folgt definiert:

  1. Eine Änderung der Zahl der Major Version kennzeichnet eine Unterbrechung in der Abwärtskompatibilität.
  2. Eine Änderung der Zahl der Minor Version kennzeichnet das Hinzufügen von neuen Funktionen oder eine wesentliche Änderung an bestehenden Funktionen.
  3. Eine Änderung der Zahl der Patch Version kennzeichnet, dass Fehler behoben wurden.

Beispiele

Du benutzt Joomla! Version 3.3.6. Das bedeutet, dass Deine Version die Major-Version 3, die Minor-Version 3 und Patch-Version 6 ist. Wenn ein Patch für 3.3.6 veröffentlicht wird, würde er Deine Joomla!-Version auf 3.3.7 erhöhen. Wenn eine neue Minor-Version für die Major-Version 3 veröffentlicht wird, würde die 3.4.0 daraus werden. Diese Seite wird immer die gültige stabile unterstütze Version von Joomla! einschließlich der kleineren Patch-Version in der oberen rechten Ecke anzeigen.


Verweise und Hinweise

  1. Bug Fixes enden im April 2014, dann nur noch Sicherheitsupdates, siehe http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.

    "Außerdem wird das Joomla! Projekt für weitere sechs Monate nach dem Joomla! 3.3 veröffentlicht worden ist, weiterhin Sicherheitsupdates für beide Versionen 3.2 UND 3.3 zur Verfügung stellen, damit jede Schwachstelle umgehend mit einem One-Click Update gepatched werden kann, ohne gleich auf Joomla! 3.3 updaten zu müssen. Das gibt Dir etwas Zeit, Deinen Provider zu bitten die PHP Version zu aktualisieren."

  2. 2.0 2.1 2.2 Siehe J3 Roadmap für den Zeitrahmen für alle zukünftigen Versionen von Joomla! 3.
  3. 3.0 3.1 Bitte beachte, dass Termine sich ändern können, je nach Verfügbarkeit von Freiwilligen und der Umstände die außerhalb der PLT-Kontrolle liegen.
  4. This library is intended to provide forward compatibility with the password_* functions which were added to PHP 5.5. See password_compat git for further information.
  5. This library is intended to provide forward compatibility with the random_bytes and random_int functions which were added to PHP 7.0. See random_compat git for further information.
  6. Enthält eine 1.2-Kompatibilitäts-Ebene
  7. 7.0 7.1 7.2 Nicht anwendbar, diese Bibliothek war nicht in der Joomla! CMS-Version 2.5. enthalten
  8. 8.0 8.1 8.2 Not applicable, this library was not included with the Joomla! CMS prior to version 3.1.2.
  9. 9.0 9.1 9.2 9.3 Nicht anwendbar, diese Bibliothek war nicht in den Joomla! CMS-Versionen vor 3.2. enthalten. Die in Joomla! 3.2 enthaltene Version von FOF ist jedoch mit Joomla! 2.5 kompatibel.
  10. 10.0 10.1 10.2 10.3 Nicht anwendbar, diese Bibliothek war nicht in den Joomla! CMS-Versionen vor 3.2 enthalten.
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Not applicable, this library was not included with the Joomla! CMS prior to version 3.4
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 Not applicable, this library was not included with the Joomla! CMS prior to version 3.5
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Diese Bibliothek war für JFeedFactory in der Joomla! CMS Version 3.1.0 veraltet.
  14. 14.0 14.1 14.2 14.3 14.4 14.5 Enthält einige 2.1 Abwärtskompatibilitäts-Standards.
  15. 15.0 15.1 15.2 15.3 15.4 Inkludiert das jQuery Migrate Plugin 1.2.1 für die Abwärtskompatibilität.
  16. Hinweis, überholt (legacy) ist ein Begriff der nur verwendet wird, um den Status einer Version in Bezug zur gültigen Version zu beschreiben. Anwender und Entwickler sollten auf genau auf das EOS Datum achten, um die Lebensfähigkeit oder weitere Nutzung der Legacy-Version zu erkennen.
  17. Version(en) markiert mit alpha, beta oder rc (release candidate) sollte nur zu Testzwecken eingesetzt werden.
  18. EOS kann genauso verwendet werden wie EOL. Beide Begriffe bedeuten das 'Ende der Unterstützung' und nicht mehr oder weniger. Verwechsel 'EOL' nicht mit der Bedeutung, dass die Software nicht mehr funktioniert.
  19. Die vollständige Erklärung der unterstützten Versionen findest Du unter der Rubrik 4.3 Unterstützte Veröffentlichungen im Joomla! Entwicklungs-Strategie Dokument.
  20. Eine installierte Erweiterung oder Template in einer Major.0.x Version funktioniert auch in einer Major.7.x Version. Von Drittanbietern entwickelte Erweiterungen oder Templates und die Veröffentlichung von Updates für diese liegen in der Verantwortung der einzelnen Entwickler. Die Installation von Updates für Erweiterungen oder Templates liegen in der Verantwortung des Anwenders.


What version of Joomla! should you use?/en


First of all, you may want to check which version of Joomla! is running on your website.

Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the version history link in the notes column to find details on exact release date, release notes and package and MD5s.

  • Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.
  • The latest version can be downloaded from Joomla! download page.
  • Make sure you subscribe to the Joomla! Security Announcements feed. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.
  • If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and/or security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.

Joomla! CMS versions

CMS Version Available Support End of Life Upgrade Type Notes Latest Release
Bugs Security
1.5
X-mark.png
X-mark.png
X-mark.png
Sept 2012 Migration to 2.5 Plan to migrate to 2.5 now
Joomla 1.5 version history
EOL at 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Aug 2011 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.6 version history
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Feb 2012 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.7 version history
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
December 31st, 2014 One-click to 3.x Upgrade to 3.6.0 now
Joomla 2.5 version history
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
May 2013 One-click to 3.1 You should use the one click upgrade
Joomla 3.0 version history
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Dec 2013 One-click to 3.2 You should use the one click upgrade
Joomla 3.1 version history
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Oct 2014[1] One-click to 3.3 You should upgrade your server's PHP to 5.3.10 or greater and upgrade to 3.3
Joomla 3.2 version history
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
3.4 release One-click You should use the one click upgrade
Joomla 3.3 version history
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
3.5 release One-click Recommended for all new installs
Joomla 3.4 version history
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
3.6 release One-click Recommended for all new installs
Joomla 3.5 version history
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
3.7 release One-click Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] to define[2][3] - - 3.8 release One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Included External Libraries

A Joomla! installation contain external libraries which are included with Joomla! CMS version releases. These external libraries are not part of the core code. Please read the Notes section as they may contain more information, such as a external library version change released with a maintenance release.

External Libraries by Joomla Release

CMS Version CMS Version Supported Mootools Mootools More jQuery jQuery UI
(Core, Widget, Mouse, Position, and Sortable)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)
password _compat[4] lessphp random _compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 N/A[7] N/A[7] N/A[7] 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Joomla! versions explained

Joomla! 
3.6.0
Stable Version

This page provides a summary of the current development strategy published on 25 April 2014. All Joomla versions released before 25 April 2014 have been developed according to previous release and support cycle. You should read the full text of the Joomla development strategy for a more detailed explanation.

Joomla! is developed following Semantic Versioning (2.0.0). The use of LTS (Long Term Support) and STS (Short Term Support) is no longer relevant or observed. The terms found directly below will be used for clarity. You should understand these terms and their meanings.

  • supported - latest minor version(s) of a major version will receive patches which will include bug and security fixes
  • current - the youngest or 'latest' major.x.x officially released version
  • legacy - any major.minor.patch version(s) which are not the current version[16]
  • stable - major version ready for use in a production environment implied with current and legacy[17]
  • EOS - an acronym for 'end of support' which indicates no further patches will be released for bugs or security fixes
  • EOL - an acronym for 'end of life' which indicates the same meaning as EOS[18]

Each major version of Joomla! is supported by The Joomla! ProjectTM for a limited amount of time, begenning from the initial date of its official release. Joomla will actively develop each major version for a minimum of 2 years. This may be followed by continued development of a major version as per scheduled on a major version's roadmap.[19] A short summary would be:

  • each major version will have a minimum of 4 years of support
  • you should always use or update to the latest major version's minor.patch
  • each minor version update released is backwards compatible with the previous minor version of the same major version[20]

Please use the Joomla! CMS Development Roadmap or the Joomla! CMS versions chart to determine the estimated EOS (end of support) for each major.minor version(s) or the entire major version.

Version Numbering Explained

The version identifiers for Joomla follow a three level numerical convention where the levels are defined by the software change significance.

[major].[minor].[patch]

These 3 levels are defined as:

  1. An increment in the major version identifier indicates a break in backward compatibility.
  2. An increment in the minor version identifier indicates the addition of new features or a significant change to existing features.
  3. An increment in the patch version identifier indicates that bugs have been fixed.

Examples

You are using Joomla version 3.3.6. This means your version is major version 3, minor version 3, patch version 6. If a patch is released for 3.3.6, it would increase your Joomla version to 3.3.7. If a new minor version for major version 3 is released, your new Joomla version would become 3.4.0. This page will always show the current stable supported version of Joomla, including the minor and patch, in the top right corner.


References and Notes

  1. Bug fixes will cease April 2014, security fixes only, see http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.

    "Also, for the six months after Joomla! 3.3 is released, the Joomla! Project will be releasing Security Updates for both 3.2 AND 3.3 so any new vulnerabilities can be promptly patched with a one-click update without the need to immediately update to Joomla! 3.3, giving you time to request your hosting provider to update their PHP version."

  2. 2.0 2.1 2.2 See J3's roadmap for time frames of all future releases of all Joomla! 3 versions.
  3. 3.0 3.1 Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond the PLT's control.
  4. This library is intended to provide forward compatibility with the password_* functions which were added to PHP 5.5. See password_compat git for further information.
  5. This library is intended to provide forward compatibility with the random_bytes and random_int functions which were added to PHP 7.0. See random_compat git for further information.
  6. Contains a 1.2 compatibility layer
  7. 7.0 7.1 7.2 Not applicable, this library was not included with Joomla! CMS version 2.5.
  8. 8.0 8.1 8.2 Not applicable, this library was not included with the Joomla! CMS prior to version 3.1.2.
  9. 9.0 9.1 9.2 9.3 Not applicable, this library was not included with the Joomla! CMS prior to version 3.2. The version of FOF included in Joomla 3.2 is compatible with Joomla 2.5 however.
  10. 10.0 10.1 10.2 10.3 Not applicable, this library was not included with the Joomla! CMS prior to version 3.2
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Not applicable, this library was not included with the Joomla! CMS prior to version 3.4
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 Not applicable, this library was not included with the Joomla! CMS prior to version 3.5
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 This library was deprecated for JFeedFactory in Joomla! CMS version 3.1.0
  14. 14.0 14.1 14.2 14.3 14.4 14.5 Contains some 2.1 backward compatibility defaults
  15. 15.0 15.1 15.2 15.3 15.4 Includes jQuery Migrate plugin 1.2.1 for backwards compatibility
  16. Note, legacy is a term used to only designate the status of a version in relation to the current version. Users and developers should pay close attention to the EOS date(s) to determine the viability of legacy version use or continued use.
  17. Version(s) marked with alpha, beta or rc (release candidate) should be used for testing only.
  18. EOS may be used interchangeably with EOL. Either term indicates the 'end of support' and nothing more. Do not confuse 'EOL' to mean the software will cease to work.
  19. The full explanation of supported releases can be found under the heading 4.3 Supported releases on the Joomla Development Strategy document.
  20. An extension or template installed on major.0.x version will work on major.7.x version. Extension or template are created by a 3rd party developer and their updates are the responsibility of each developer to publish. The installation of extension or template updates are the responsibility of the user.


What version of Joomla! should you use?/et


Alustuseks soovid ehk vaadata mis Joomla! versiooni sinu veebisait kasutab. Joomla! CMS versions/et

Kaasatud välised teegid

A Joomla! installation contain external libraries which are included with Joomla! CMS version releases. These external libraries are not part of the core code. Please read the Notes section as they may contain more information, such as a external library version change released with a maintenance release.

Välised teegid Joomla versioonide järgi

Sisuhalduse versioon Toetatud sisuhalduse versioon Mootools Mootools More jQuery jQuery UI
(tuum, vidin, hiir, asukoht ja sorteeritav)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)
password _compat[1] lessphp random _compat[2]
2.5
X-mark.png
1.4.5[3] 1.4.0.1 N/A[4] N/A[4] N/A[4] 1.2 5.2.1 0.5 N/A[5] N/A[6] N/A[7] N/A[8] N/A[9]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[5] N/A[6] N/A[7] N/A[8] N/A[9]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[10] 5.2.3 0.5 N/A[5] N/A[6] N/A[7] N/A[8] N/A[9]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[11] 1.2[10] 5.2.6 0.5 0.8.0 N/A[6] N/A[7] N/A[8] N/A[9]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[12] 1.9.2 2.3.2[11] 1.2[10] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[8] N/A[9]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[12] 1.9.2 2.3.2[11] 1.2[10] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[8] N/A[9]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[12] 1.9.2 2.3.2[11] 1.2[10] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[9]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[12] 1.9.2 2.3.2[11] 1.2[10] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[12] 1.9.2 2.3.2[11] 1.2[10] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Joomla! versioonide selgitused

Release and support cycle/et

Viited ja märkused

  1. This library is intended to provide forward compatibility with the password_* functions which were added to PHP 5.5. See password_compat git for further information.
  2. This library is intended to provide forward compatibility with the random_bytes and random_int functions which were added to PHP 7.0. See random_compat git for further information.
  3. Contains a 1.2 compatibility layer
  4. 4.0 4.1 4.2 Not applicable, this library was not included with Joomla! CMS version 2.5.
  5. 5.0 5.1 5.2 Not applicable, this library was not included with the Joomla! CMS prior to version 3.1.2.
  6. 6.0 6.1 6.2 6.3 Not applicable, this library was not included with the Joomla! CMS prior to version 3.2. The version of FOF included in Joomla 3.2 is compatible with Joomla 2.5 however.
  7. 7.0 7.1 7.2 7.3 Not applicable, this library was not included with the Joomla! CMS prior to version 3.2
  8. 8.0 8.1 8.2 8.3 8.4 8.5 Not applicable, this library was not included with the Joomla! CMS prior to version 3.4
  9. 9.0 9.1 9.2 9.3 9.4 9.5 9.6 Not applicable, this library was not included with the Joomla! CMS prior to version 3.5
  10. 10.0 10.1 10.2 10.3 10.4 10.5 10.6 This library was deprecated for JFeedFactory in Joomla! CMS version 3.1.0
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Contains some 2.1 backward compatibility defaults
  12. 12.0 12.1 12.2 12.3 12.4 Includes jQuery Migrate plugin 1.2.1 for backwards compatibility


What version of Joomla! should you use?/id


Pertama-tama, Anda mungkin ingin memeriksa versi Joomla! mana yang berjalan di situs web Anda.

Periksa versi terakhir Joomla!. Jika Anda tidak berada pada rilis terakhir, bacalah catatan rilis untuk melihat apakah Anda perlu menaikkannya atau tidak. Apabila rilis dibuat dengan tujuan isu keamanan maka sangat disarankan Anda menaikkannya secepat mungkin. Anda dapat melihat sejarah rilis masing-masing seri pada tabel dibawah. Klik tautan sejarah versi yang ada di dalam kolom catatan untuk menemukan detail selengkapnya mengenai tanggal rilis, catatan rilis dan paket serta MD5s.

  • Biasanya, Anda harus menggunakan versi terakhir Joomla! untuk sebuah situs baru kecuali bila Anda punya alasan tertentu untuk tidak melakukannya.
  • Versi terakhir dapat diunduh dari halaman unduh Joomla!.
  • Pastikan Anda berlangganan pengumpan Pengumuman Keamanan Joomla!. Pengumpan RSS ini dipakai untuk membuat pengumuman, termasuk ketersediaan rilis-rilis baru, yang dapat berdampak pada keamanan situs Anda. Anda punya pilihan untuk berlangganan ke pengumpan RSS ini atau melalui email.
  • Apabila Anda menjalankan rilis terawal dari versi terkini (contohnya, Anda menjalankan 3.1.6 dan versi terkini adalah 3.4.1), maka Anda harus menaikkannya ke versi terkini. Setiap rilis minor memperbaiki sejumlah bug dan/atau isu-isu keamanan. Adalah suatu praktek terbaik untuk menaikkan ke versi pemeliharaan terakhir sebagai langkah awal dalam menemukan masalah dan memperbaiki isu-isu keamanan apapun yang baru ditemukan.

Versi CMS Joomla!

Versi CMS Tersedia Dukungan End of Life (Masa Akhir) Jenis Upgrade Catatan Rilis Terakhir
Bug Keamanan
1.5
X-mark.png
X-mark.png
X-mark.png
Sep 2012 Migrasi ke 2.5 Rencana bermigrasi ke 2.5 sekarang
Sejarah versi Joomla! 1.5
EOL pada 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Agus 2011 Sekali-klik ke 2.5 Upgrade ke 2.5 sekarang
Sejarah versi Joomla! 1.6
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Feb 2012 Sekali-klik ke 2.5 Upgrade ke 2.5 sekarang
Sejarah versi Joomla! 1.7
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
31 Desember 2014 Sekali-klik ke 3.x Upgrade ke 3.6.0 sekarang
Sejarah versi Joomla! 2.5
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
Mei 2013 Sekali-klik ke 3.1 Ada harus gunakan sekali-klik upgrade
Sejarah versi Joomla! 3.0
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Des 2013 Sekali-klik ke 3.2 Anda harus gunakan sekali-klik upgrade
Sejarah versi Joomla! 3.1
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Okt 2014[1] Sekali-klik ke 3.3 Anda harus upgrade PHP server Anda ke 5.3.10 atau yang lebih tinggi dan upgrade ke 3.3.
Sejarah versi Joomla! 3.2
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
rilis 3.4 Sekali-klik Anda harus gunakan sekali-klik upgrade
Sejarah versi Joomla! 3.3
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
rilis 3.5 Sekali-klik Direkomendasikan untuk semua pemasangan baru
Sejarah versi Joomla! 3.4
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
rilis 3.6 Sekali-klik Direkomendasikan untuk semua pemasangan
Sejarah versi Joomla 3.5
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
rilis 3.7 Sekali-klik Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] mempertegas[2][3] - - rilis 3.8 Sekali-klik
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Pustaka Eksternal yang Disertakan

Sebuah pemasangan Joomla! mengandung pustaka-pustaka eksternal yang disertakan bersama versi rilis CMS Joomla. Pustaka eksternal ini bukan bagian dari kode inti. Bacalah bagian Catatan karena mungkin ada informasi yang lebih lengkap, seperti perubahan pustaka eksternal yang dirilis dengan sebuah rilis pemeliharaan, yang dibutuhkan.

Pustaka Eksternal berdasarkan Rilis Joomla!

Versi CMS Versi CMS yang Didukung Mootools Mootools More jQuery jQuery UI
(Inti, Pengaya, Tetikus, Posisi, dan Pemilahan)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 Ubah IDNA Kerangka Rapid Application Development (RAD)
Kerangka Akeeba pada Kerangka (FOF)
password _compa[4] lessphp random _compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 N/A[7] N/A[7] N/A[7] 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Penjelasan versi Joomla!

Joomla! 
3.6.0
Versi Stabil

Halaman ini menyediakan sebuah ringkasan strategi pengembangan saat ini yang diterbitkan pada 25 April 2014. Semua versi Joomla! yang dirilis sebelum 25 April 2014 telah dikembangkan berdasarkan pada rilis sebelumnya dan siklus dukungan. Anda harus membaca lengkap artikel Joomla development strategy untuk penjelasan yang lebih detail.

Joomla! dikembangkan dengan mengacu pada Semantic Versioning (2.0.0). Pemakaian LTS (Long Term Support—Dukungan Jangka Panjang) dan STS (Short Term Support—Dukungan Jangka Pendek) tidak lagi relevan atau diamati. Kondisi-kondisi yang ditemukan dibawah berikut ini akan digunakan untuk kejelasannya. Anda harus mengerti kondisi-kondisi ini dan pengertiannya.

  • supported [didukung] - versi minor terakhir dari sebuah versi mayor yang akan menerima patch yang akan menyertakan perbaikan-perbaikan bug dan keamanan
  • current [saat ini] - versi rilis resmi major.x.x yang termuda atau 'terakhir'
  • legacy [warisan] - versi major.minor.patch apapun yang bukan versi saat ini[16]
  • stable [stabil] - versi mayor yang siap pakai untuk di lingkungan produksi tersirat saat ini dan warisan[17]
  • EOS - singkatan dari 'end of support' [akhir dukungan] yang menandakan tidak ada lagi patch yang akan dirilis untuk perbaikan-perbaikan bug dan keamanan
  • EOL - singkatan dari 'end of life' [akhir masa] yang menandakan pengertian yang sama dengan EOS[18]

Setiap versi mayor Joomla! didukung oleh Joomla! ProjectTM untuk waktu yang terbatas, dimulai dari tanggal mulai resmi rilisnya. Joomla! akan secara aktif mengembangkan setiap versi mayor untuk minimal 2 tahun. Ini mungkin akan diikuti dengan pengembangan lanjutan versi mayor sesuai jadwal roadmap versi mayor.[19] Sebagai ringkasan pendeknya adalah:

  • setiap versi mayor akan memiliki minimal 4 tahun dukungan
  • anda harus selalu menggunakan atau memperbarui ke versi mayor terkini minor.patch
  • setiap pembaruan versi minor yang dirilis kompatibel ke belakang dengan versi minor sebelumnya dari versi mayor yang sama[20]

Gunakanlah Roadmap Pengembangan CMS Joomla! atau carta versi CMS Joomla! untuk menentukan perkiraan EOS (end of support) masing-masing versi major.minor atau keseluruhan versi mayor.

Penjelasan Penomoran Versi

Pengenal versi untuk Joomla! mematuhi konvensi penomoran tiga level dimana level ditentukan oleh perubahan perangkat lunak yang signifikan.

[major].[minor].[patch]

3 level ini didefinsikan sebagai berikut:

  1. Penambahan di pengenal versi mayor menandakan sebuah jeda kompatibiltas ke belakang.
  2. Penambahan di pengenal versi minor menandakan adanya penambahan fitur-fitur baru atau perubahan signifikan terhadap fitur-fitur yang ada.
  3. Penambahan di pengenal versi patch menandakan bahwa bug telah diperbaiki.

Contoh

Anda sedang menggunakan Joomla! versi 3.3.6. Ini artinya adalah versi Anda adalah versi mayor 3, versi minor 3, versi patch 6. Bila sebuah patch dirilis untuk 3.3.6, maka akan menaikkan versi Joomla! Anda ke 3.3.7. Bila sebuah versi minor untuk versi mayor 3 dirilis, maka versi Joomla! Anda yang baru akan menjadi 3.4.0. Halaman ini akan selalu menampilkan Joomla! versi stabil yang didukung saat ini, termasuk minor dan patch, di sudut kanan atas.


Referensi dan Catatan

  1. Perbaikan bug akan berakhir pada bulan April 2014, hanya perbaikan keamanan, lihat http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html

    "Juga, pada enam bulan sejak Joomla! 3.3 dirilis, Proyek Joomla! akan melepas Pembaruan Keamanan untuk 3.2 DAN 3.3 sehingga kerentanan baru dapat segera di tampal dengan pembaruan sekali-klik tanpa harus segera memperbarui ke Joomla! 3.3, memberikan Anda waktu untuk meminta penyedia hosting Anda guna memperbarui versi PHP mereka."

  2. 2.0 2.1 2.2 Lihat roadmap J3 untuk kerangka waktu semua rilis Joomla! versi 3 yang akan datang.
  3. 3.0 3.1 Mohon dicatat bahwa tanggal dapat berubah sewaktu-waktu tergantung ketersediaan relawan dan keadaan diluar kendali PLT.
  4. Pustaka ini ditujukan untuk memberikan kompatibilitas ke depan terhadap fungsi password_* yang ditambahkan ke PHP 5.5. Lihat password_compat git untuk informasi selengkapnya.
  5. Pustakan ini ditujukan untuk memberikan kompatibilitas ke depan terhadap fugnsi random_bytes dan random_int yang ditambahkan ke PHP 7.0. Lihat random_compat git untuk informasi selengkapnya.
  6. Mengandung sebuah lapis kompatibilitas 1.2
  7. 7.0 7.1 7.2 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! versi 2.5.
  8. 8.0 8.1 8.2 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! sebelum versi 3.1.2.
  9. 9.0 9.1 9.2 9.3 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! sebelum versi 3.2. Meskipun versi FOF yang disertakan di dalam Joomla! 3.2 kompatibel dengan Joomla! 2.5.
  10. 10.0 10.1 10.2 10.3 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! sebelum versi 3.2.
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! sebelum versi 3.4.
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 Not applicable [tidak dapat diterapkan], pustaka ini tidak disertakan di dalam CMS Joomla! sebelum versi 3.5.
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Pustaka ini sudah tidak berlaku lagi untuk JFeedFactory di dalam CMS Joomla! versi 3.1.0.
  14. 14.0 14.1 14.2 14.3 14.4 14.5 Mengandung beberapa standar kompatibilitas ke belakang 2.1
  15. 15.0 15.1 15.2 15.3 15.4 Termasuk plugin jQuery Migrate 1.2.1 untuk kompatibilitas ke belakang
  16. Catat, warisan adalah kondisi yang dipakai hanya untuk menunjuk kepada status dari sebuah versi dalam hubungannya dengan versi saat ini. Para pengguna dan pengembang harus teliti dengan tanggal EOS untuk menentukan kelangsungan penggunaan versi warisan atau kelanjutan pemakaiannya.
  17. Versi yang ditandai dengan alfa, beta atau rc (release candidate—kandidat rilis) yang hanya dipakai untuk pengujian.
  18. EOS mungkin dipakai bergantian dengan EOL. Baik itu kondisi yang menandakan 'end of support' maupun tidak ada lagi. Jangan bingung dengan pengertian 'EOL' yang berarti perangkat lunak akan berhenti bekerja.
  19. Penjelasan selengkapnya tentang rilis-rilis yang didukung dapat ditemukan dibawah tajuk 4.3 Supported releases di dokumen Strategi Pengembangan Joomla.
  20. Sebuah ekstensi atau templat yang dipasang pada versi major.0.x akan bekerja pada versi major.7.x. Ekstensi atau templat yang dibuat oleh para pengembang pihak ke-3 dan pembaruannya adalah tanggungjawab masing-masing pengembang untuk menerbitkannya. Pemasangan pembaruan ekstensi atau templat adalah tanggungjawab para pengguna.


What version of Joomla! should you use?/it


Prima di tutto, è necessario controllare quale versione di Joomla! è in esecuzione sul tuo sito web.

Controllare l'ultima versione del CMS Joomla!. Se non si usa l'ultima versione, leggere le note di rilascio per verificare se è necessario aggiornare. Se una nuova versione è stata fatta per questioni di sicurezza, si consiglia vivamente di eseguire l'aggiornamento il più presto possibile. Si può vedere la storia di rilascio di ogni serie nella tabella sottostante. Fare clic sul collegamento cronologia delle versioni nella colonna note per trovare i dettagli sulla data esatta di rilascio, note di rilascio e il pacchetto e MD5s.

  • Generalmente, si dovrebbe usare l'ultima versione di Joomla! per un nuovo sito, a meno che non ci siano motivi particolari per non farlo.
  • L'ultima versione può essere scaricata dalla pagina di download di Joomla!.
  • Assicurati di sottoscrivere al feed Avvisi di sicurezza Joomla! . Questo feed RSS è usato per fare gli annunci, tra cui la disponibilità di nuove versioni, che potrebbero influenzare la sicurezza del tuo sito. Hai la possibilità di sottoscriverti a questo feed via RSS o via e-mail.
  • Se utilizzi una versione precedente alla versione corrente (ad esempio, se stai eseguendo 3.1.6 e la versione corrente è 3.4.1), si consiglia di aggiornare alla versione corrente. Ogni release minore corregge una serie di bug e/o problemi di sicurezza. E' sempre buona norma eseguire l'aggiornamento all'ultima versione di manutenzione come un primo passo nella risoluzione di un problema e risolvere gli eventuali problemi di sicurezza recentemente scoperti.

Versioni del CMS Joomla!

Versione del CMS Disponibile Supporto Fine della Vita Tipo Di Aggiornamento Note Ultima Versione
Bug Sicurezza
1.5
X-mark.png
X-mark.png
X-mark.png
Settembre 2012 Migrazione a 2.5 Pianificare la Migrazione a 2.5 ora
Joomla 1.5 version history
"'EOL"' a 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Agosto 2011 Un-click per 2.5 Aggiornamento a 2.5 ora
Joomla 1.6 version history
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Febbraio 2012 Un-click per 2.5 Aggiornamento a 2.5 ora
Joomla 1.7 version history
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
31 Dicembre 2014 Un-click per 3.x Aggiornamento a 3.6.0 ora
Joomla 2.5 version history
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
Maggio 2013 Un-click per 3.1 Si consiglia di utilizzare l'aggiornamento un click
Joomla 3.0 version history
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Dicembre 2013 Un-click per 3.2 Si consiglia di utilizzare l'aggiornamento un click
Joomla 3.1 version history
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Ottobre 2014 [1] Un-click per 3.3 Si consiglia di aggiornare la versione di PHP del server web a 5.3.10 o successiva e di passare a Joomla! 3.3
Joomla 3.2 version history
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
al rilascio della versione 3.4 One-click Si consiglia di utilizzare l'aggiornamento un-click
Joomla 3.3 version history
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
al rilascio della versione 3.5 One-click Recommended for all new installs
Joomla 3.4 version history
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
al rilascio della versione 3.6 One-click Recommended for all new installs
Joomla 3.5 version history
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
al rilascio della versione 3.7 One-click Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] da definirsi [2][3] - - al rilascio della versione 3.8 One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Librerie Esterne Incluse

Una installazione di Joomla! contiene librerie esterne che sono incluse nel CMS di Joomla!. Queste librerie esterne non fanno parte del codice di base. Si prega di leggere la sezione Note in quanto potrebbero contenere più informazioni, come ad esempio un cambio di versione libreria esterna rilasciato con una versione di manutenzione.

Librerie esterne di Joomla

Versione del CMS Versione del CMS Supportata Mootools Mootools More jQuery jQuery UI
(Core, Widget, Mouse, Posizione e Ordinamento)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Framework per lo sviluppo rapido di Applicazioni (RAD)
Framework di Akeeba (FOF)
password_compat[4] lessphp password_compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 N/A[7] N/A[7] N/A[7] 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Spiegazione delle versioni Joomla!

Joomla! 
3.6.0
Versione Stabile

Questa pagina offre una sintesi della strategia di sviluppo attuale pubblicata il 25 Aprile 2014. Tutte le versioni di Joomla rilasciate prima del 25 Aprile 2014 sono state sviluppate secondo il ciclo di rilascio e supporto precedente. Si consiglia di leggere il testo integrale della strategia di sviluppo Joomla per una spiegazione più dettagliata.

Joomla! è stato sviluppato seguendo Semantic Versioning (2.0.0). L'uso di LTS (Long Term Support) e STS (Short Term Support) non è più rilevante o osservato. I termini trovati direttamente sotto verranno utilizzati per chiarezza. È necessario comprendere questi termini e il loro significato.

  • supportata - le ultime versioni minori di una versione principale riceveranno le patch per bug e problemi di sicurezza
  • corrente - è la versione ufficiale più giovane o la più recente major.x.x
  • legacy - qualsiasi versione major.minor.patch che non sia la versione corrente[16]
  • stabile - versione major pronta per l'uso in un ambiente di produzione [17]
  • EOS - un acronimo per "fine del supporto" indica che non verranno rilasciate future patch per i bug o correzioni di sicurezza
  • EOL - un acronimo per 'fine vita', ha lo stesso significato EOS[18]

Ogni versione principale di Joomla! è supportata dal Progetto Joomla!TM per un periodo di tempo limitato, a partire dalla data di rilascio ufficiale. Ogni major release di Joomla sarà sviluppata in maniera attiva per almeno 2 anni. A ciò può seguire uno sviluppo costante fino ad una versione major pianificata sulla tabella di marcia.[19] Una breve sintesi sarebbe:

  • ogni versione principale avrà un minimo di 4 anni di supporto
  • si dovrebbe sempre usare o aggiornarsi all'ultima versione principale del minor.patch
  • ogni minimo aggiornamento della versione rilasciata è compatibile con la precedente versione minore della stessa versione principale[20]

Si prega di utilizzare il grafico Joomla! CMS Roadmap di Sviluppo o Versioni del CMS Joomla! per determinare e prevedere il EOS (fine del supporto) per ogni versione major.minor o per l'intera versione principale.

Spiegazione dei numeri di versione

Gli identificatori di versione per Joomla seguono una convenzione numerica a tre livelli in cui i livelli sono definiti da quanto sono significativi i cambiamenti.

[major].[minor].[patch]

Questi 3 livelli sono definiti come segue:

  1. Un incremento dell'identificativo di versione major indica un'interruzione di retrocompatibilità.
  2. Un incremento dell'identificativo di versione minor indica l'aggiunta di nuove funzionalità o un cambiamento significativo di funzioni esistenti.
  3. Un incremento dell'identificativo di versione patch indica che dei bug sono stati corretti.

Esempi

Stai usando la versione di Joomla 3.3.6. Questo significa che la versione major è 3, la versione minor è 3, la versione di patch è 6. Se una patch viene rilasciata per 3.3.6, verrebbe rilasciata la versione Joomla 3.3.7 . Se una nuova versione minor viene rilasciata, la nuova versione di Joomla diventerebbe 3.4.0 . Questa pagina mostrerà sempre la l'ultima versione stabile rilasciata di Joomla, nell'angolo in alto a destra.


Riferimenti e Note

  1. La correzione di bug cesserà ad aprile 2014, solo aggiornamenti di sicurezza, vedi http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.

    Inoltre, per sei mesi dopo il rilascio di Joomla! 3.3, Il Progetto Joomla! rilascerà aggiornamenti di sicurezza per 3.2 e 3.3, in modo che qualsiasi nuova vulnerabilità possa essere prontamente corretta con un aggiornamento un click, senza la necessità di aggiornare immediatamente a Joomla! 3.3, dandovi il tempo di chiedere al vostro fornitore di Hosting per aggiornare la versione di PHP.

  2. 2.0 2.1 2.2 Vedere J3 roadmap per la programmazione delle future versioni di Joomla! 3.
  3. 3.0 3.1 Si prega di notare che le date possono essere soggette a modifiche a seconda della disponibilità dei volontari e delle circostanze che non dipendono dal PLT.
  4. Questa libreria serve a fornire la compatibilità con le funzioni password_* che sono state aggiunte a PHP 5.5. Per ulteriori informazioni vedere password_compat git.
  5. Questa libreria serve a fornire la compatibilità con le funzioni random_bytes e random_int che sono state aggiunte a PHP 7.0. Per ulteriori informazioni vedere random_compat git.
  6. Contiene un livello 1.2 di compatibilità
  7. 7.0 7.1 7.2 Non applicabile, questa libreria non è stata inclusa nella versione 2.5 del CMS Joomla!.
  8. 8.0 8.1 8.2 Non applicabile, questa libreria non è stata inclusa nelle versioni precedenti alla 3.1.2 del CMS Joomla!
  9. 9.0 9.1 9.2 9.3 Non applicabile, questa libreria non è stata inclusa nelle versioni precedenti alla 3.2 del CMS Joomla!. La versione di FOF incluso in Joomla 3.2 è compatibile con Joomla 2.5.
  10. 10.0 10.1 10.2 10.3 Non applicabile,questa libreria non è stata inclusa nelle versioni precedenti alla 3.2 del CMS Joomla!
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Non applicabile, questa libreria non è stata inclusa nelle versioni precedenti alla 3.4 del CMS Joomla!
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 Non applicabile, questa libreria non è stata inclusa nelle versioni precedenti alla 3.5 del CMS Joomla!
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Questa libreria è stata deprecata per JFeedFactory nel CMS Joomla! versione 3.1.0
  14. 14.0 14.1 14.2 14.3 14.4 14.5 Contiene alcune compatibilità con la 2.1
  15. 15.0 15.1 15.2 15.3 15.4 Include il plugin jQuery Migrate versione 1.2.1 per la compatibilità all'indietro
  16. Nota, il legacy è un termine usato per designare unicamente lo stato di una versione rispetto alla versione corrente. Gli utenti e gli sviluppatori dovrebbero prestare particolare attenzione alla data di EOS per determinare se è opportuno utilizzare la versione.
  17. Le versioni contrassegnate con alfa, beta o rc (release candidate) dovrebbero essere utilizzate solo a scopo di test.
  18. EOS può essere usato in modo intercambiabile con EOL. Il termine indica la "fine del supporto" e niente di più. 'EOL' non significa che il software cesserà di funzionare.
  19. La spiegazione completa delle versioni supportate può essere trovato sotto la voce 4.3 Release supportate sul documento sulla Strategia di Sviluppo.
  20. Un'estensione o un template installato sulla versione major.0.x funziona anche sulla versione major.7.x. L'estensione o il template sono creati da sviluppatori di terze parti e i loro aggiornamenti sono a carico di ogni sviluppatore. L'installazione degli aggiornamenti delle estensioni e dei template sono a carico dell'utente.


What version of Joomla! should you use?/pt


First of all, you may want to check which version of Joomla! is running on your website.

Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the version history link in the notes column to find details on exact release date, release notes and package and MD5s.

  • Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.
  • The latest version can be downloaded from Joomla! download page.
  • Make sure you subscribe to the Joomla! Security Announcements feed. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.
  • If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and/or security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.

Joomla! CMS versions

CMS Version Available Support End of Life Upgrade Type Notes Latest Release
Bugs Security
1.5
X-mark.png
X-mark.png
X-mark.png
Sept 2012 Migration to 2.5 Plan to migrate to 2.5 now
Joomla 1.5 version history
EOL at 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Aug 2011 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.6 version history
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Feb 2012 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.7 version history
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
December 31st, 2014 One-click to 3.x Upgrade to 3.6.0 now
Joomla 2.5 version history
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
May 2013 One-click to 3.1 You should use the one click upgrade
Joomla 3.0 version history
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Dec 2013 One-click to 3.2 You should use the one click upgrade
Joomla 3.1 version history
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Oct 2014[1] One-click to 3.3 You should upgrade your server's PHP to 5.3.10 or greater and upgrade to 3.3
Joomla 3.2 version history
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
3.4 release One-click You should use the one click upgrade
Joomla 3.3 version history
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
3.5 release One-click Recommended for all new installs
Joomla 3.4 version history
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
3.6 release One-click Recommended for all new installs
Joomla 3.5 version history
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
3.7 release One-click Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] to define[2][3] - - 3.8 release One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Incluídas Bibliotecas Externas

External Libraries in Joomla/pt

Joomla! versões explicadas

Joomla! 
3.6.0
Versão Estável

Esta página fornece um resumo da estratégia de desenvolvimento atual, publicada no 25 de abril de 2014. Todas as versões do Joomla lançadas antes de 25 de abril de 2014, têm sido desenvolvidas de acordo com o lançamento anterior e ciclo de suporte. Deverá ler o texto completo da estratégia de desenvolvimento do Joomla para uma explicação mais detalhada.

Joomla! é desenvolvido Semântica de controle de versão (2.0.0). O uso de LTS (Long Term Support) e PTS (Suporte a Curto Prazo) não é mais relevante ou observado. Os termos encontrados diretamente abaixo serão utilizados para fins de clareza. Você deve compreender estes termos e seus significados.

  • suportado - a mais recente versão menor(es) de uma versão principal irá receber patches que irá incluir erros e correções de segurança
  • atual - a mais jovem ou 'mais recente' principais.x.x lançado oficialmente versão
  • o legado - qualquer principais.menor de idade.patch versão(s) que não sejam a versão atual[4]
  • estável - versão principal, pronto para uso em um ambiente de produção implícita com o actual e o legado[5]
  • EOS - uma sigla para 'fim do suporte', o que indica que não existe mais nenhuma correção será lançado para erros ou correções de segurança
  • EOL - um acrónimo para "fim de vida", que indica o mesmo significado que a EOS[6]

Cada versão principal do Joomla! é suportado por Joomla! ProjetoTM para uma quantidade limitada de tempo, begenning a partir da data inicial de seu lançamento oficial. Joomla vai desenvolver activamente a cada versão principal, por um período mínimo de 2 anos. Isto pode ser seguido por um desenvolvimento continuado de uma versão principal como por agendada em uma grande versão do guião.[7] com Um breve resumo seria:

  • cada versão principal terá um mínimo de 4 anos de suporte
  • você deve sempre usar ou atualização para a última versão principal do menor.patch
  • cada menor a atualização da versão lançada é compatível com a anterior versão menor da mesma versão principal[8]

Por favor, use o Joomla! CMS Development Roadmap ou Joomla! CMS versions gráfico para determinar o valor estimado EOS (fim do suporte) para cada principais.menor versão(s) ou toda a versão principal.

Numeração De Versões Explicada

Os identificadores de versão para o Joomla seguem um de três níveis de convenção numéricos, onde os níveis são definidos pela importância da alteração do software.

[major].[minor].[patch]

Estes 3 níveis são definidos como:

  1. Um incremento na maior versão indica uma quebra de compatibilidade com versões anteriores.
  2. Um incremento, no menor identificador de versão indica a adição de novas funcionalidades ou uma mudança significativa para os recursos existentes.
  3. Um incremento, o patch identificador de versão indica que os erros foram corrigidos.

Exemplos

Está a utilizar a versão Joomla 3.3.6. Isso significa que sua versão é a versão principal 3, menor a versão 3, versão do patch 6. Se um patch é lançado para 3.3.6, aumentaria sua versão Joomla para 3.3.7. Se uma nova versão secundária para a principal versão 3 é lançado, o novo Joomla versão se tornaria 3.4.0. Esta página irá mostrar sempre o estável atual versão suportada do Joomla, incluindo o menor e o patch, no canto superior direito.


Referências

  1. Bug fixes will cease April 2014, security fixes only, see http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.

    "Also, for the six months after Joomla! 3.3 is released, the Joomla! Project will be releasing Security Updates for both 3.2 AND 3.3 so any new vulnerabilities can be promptly patched with a one-click update without the need to immediately update to Joomla! 3.3, giving you time to request your hosting provider to update their PHP version."

  2. 2.0 2.1 2.2 See J3's roadmap for time frames of all future releases of all Joomla! 3 versions.
  3. 3.0 3.1 Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond the PLT's control.
  4. Nota, o legacy é um termo usado para designar apenas o status de uma versão em relação à versão atual. Utilizadores e desenvolvedores devem prestar muita atenção para a EOS data(s) para determinar a viabilidade do legado versão de uso ou uso continuado.
  5. Versão(s) marcado com alfa, beta ou rc (release candidate) deve ser usado somente para teste.
  6. EOS pode ser usado de forma intercambiável com o EOL. Um termo indica o 'fim do suporte a' e nada mais. Não confunda 'EOL' significa o software deixará de funcionar.
  7. A explicação completa das versões com suporte pode ser encontrado sob o título 4.3 as versões com Suporte no Joomla Estratégia de Desenvolvimento do documento.
  8. Uma extensão ou modelo instalado em principais.0.x versão irá funcionar em principais.7.x versão. Extensão ou modelo são criados pela 3ª festa do desenvolvedor e suas atualizações são de responsabilidade de cada desenvolvedor para publicar. A instalação da extensão ou atualizações do modelo, são da responsabilidade do utilizador.


What version of Joomla! should you use?/pt-br


First of all, you may want to check which version of Joomla! is running on your website.

Check for the latest Joomla! CMS version. If you are not on the latest release, read the release notes to see if you need to upgrade. If a release is being made in order to address security issues then it is strongly advised that you upgrade as soon as possible. You can see the release history of each series in the table below. Click the version history link in the notes column to find details on exact release date, release notes and package and MD5s.

  • Normally, you should use the latest version of Joomla! for a new site unless you have a specific reason not to.
  • The latest version can be downloaded from Joomla! download page.
  • Make sure you subscribe to the Joomla! Security Announcements feed. This RSS feed is used to make announcements, including the availability of new releases, that could affect the security of your site. You have the option to subscribe to this feed by RSS or email.
  • If you are running an earlier release of the current version (for example, you are running 3.1.6 and the current version is 3.4.1), you should upgrade to the current version. Each minor release fixes a number of bugs and/or security issues. It is always good practice to upgrade to the latest maintenance version as a first step in troubleshooting a problem and fixing any newly discovered security issues.

Joomla! CMS versions

CMS Version Available Support End of Life Upgrade Type Notes Latest Release
Bugs Security
1.5
X-mark.png
X-mark.png
X-mark.png
Sept 2012 Migration to 2.5 Plan to migrate to 2.5 now
Joomla 1.5 version history
EOL at 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Aug 2011 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.6 version history
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Feb 2012 One-click to 2.5 Upgrade to 2.5 now
Joomla 1.7 version history
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
December 31st, 2014 One-click to 3.x Upgrade to 3.6.0 now
Joomla 2.5 version history
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
May 2013 One-click to 3.1 You should use the one click upgrade
Joomla 3.0 version history
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Dec 2013 One-click to 3.2 You should use the one click upgrade
Joomla 3.1 version history
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Oct 2014[1] One-click to 3.3 You should upgrade your server's PHP to 5.3.10 or greater and upgrade to 3.3
Joomla 3.2 version history
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
3.4 release One-click You should use the one click upgrade
Joomla 3.3 version history
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
3.5 release One-click Recommended for all new installs
Joomla 3.4 version history
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
3.6 release One-click Recommended for all new installs
Joomla 3.5 version history
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
3.7 release One-click Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] to define[2][3] - - 3.8 release One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Included External Libraries

A Joomla! installation contain external libraries which are included with Joomla! CMS version releases. These external libraries are not part of the core code. Please read the Notes section as they may contain more information, such as a external library version change released with a maintenance release.

External Libraries by Joomla Release

CMS Version CMS Version Supported Mootools Mootools More jQuery jQuery UI
(Core, Widget, Mouse, Position, and Sortable)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)
password _compat[4] lessphp random _compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 N/A[7] N/A[7] N/A[7] 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Joomla! versions explained

Joomla! 
3.6.0
Stable Version

This page provides a summary of the current development strategy published on 25 April 2014. All Joomla versions released before 25 April 2014 have been developed according to previous release and support cycle. You should read the full text of the Joomla development strategy for a more detailed explanation.

Joomla! is developed following Semantic Versioning (2.0.0). The use of LTS (Long Term Support) and STS (Short Term Support) is no longer relevant or observed. The terms found directly below will be used for clarity. You should understand these terms and their meanings.

  • supported - latest minor version(s) of a major version will receive patches which will include bug and security fixes
  • current - the youngest or 'latest' major.x.x officially released version
  • legacy - any major.minor.patch version(s) which are not the current version[16]
  • stable - major version ready for use in a production environment implied with current and legacy[17]
  • EOS - an acronym for 'end of support' which indicates no further patches will be released for bugs or security fixes
  • EOL - an acronym for 'end of life' which indicates the same meaning as EOS[18]

Each major version of Joomla! is supported by The Joomla! ProjectTM for a limited amount of time, begenning from the initial date of its official release. Joomla will actively develop each major version for a minimum of 2 years. This may be followed by continued development of a major version as per scheduled on a major version's roadmap.[19] A short summary would be:

  • each major version will have a minimum of 4 years of support
  • you should always use or update to the latest major version's minor.patch
  • each minor version update released is backwards compatible with the previous minor version of the same major version[20]

Please use the Joomla! CMS Development Roadmap or the Joomla! CMS versions chart to determine the estimated EOS (end of support) for each major.minor version(s) or the entire major version.

Version Numbering Explained

The version identifiers for Joomla follow a three level numerical convention where the levels are defined by the software change significance.

[major].[minor].[patch]

These 3 levels are defined as:

  1. An increment in the major version identifier indicates a break in backward compatibility.
  2. An increment in the minor version identifier indicates the addition of new features or a significant change to existing features.
  3. An increment in the patch version identifier indicates that bugs have been fixed.

Examples

You are using Joomla version 3.3.6. This means your version is major version 3, minor version 3, patch version 6. If a patch is released for 3.3.6, it would increase your Joomla version to 3.3.7. If a new minor version for major version 3 is released, your new Joomla version would become 3.4.0. This page will always show the current stable supported version of Joomla, including the minor and patch, in the top right corner.


References and Notes


What version of Joomla! should you use?/ru


Прежде всего, Вы, возможно, пожелаете проверить какая версия системы Joomla! работает на Вашем веб-сайте.

Проверьте [какая] весия Joomla CMS [является] наипоследней. Если Вы не на самой последней версии, [то] познакомтесь с заметками по ее выпуску и проверьте нужна ли Вам миграция. Если какая-либо версия была выпущена для того, чтобы устранить проблемы с безопасностью, то Вам настоятельно рекомендуется мигрировать [на эту версию] как можно скорее. Вы можете взглянуть на историю выпусков каждой серии [системы Joomla] в ниже расположенной таблице. Щелкните на ссылку "История версии" в колонке "Примечания" чтобы найти точную дату выпуска, заметки по этому выпуску и [его] пакет и [коды] MD5.

  • Обычно, на новом веб-сайте Вам следует использовать наипоследнюю версию Joomla!, за исключением случаев, когда [против этого] у Вас имеется веская причина.
  • Наипоследняя версия может быть скачана с Joomla! этой страницы.
  • Удостоверьтесь в том, что Вы подписались на канал объявлений по безопасности Joomla!. Этот RSS канал используется для того, чтобы делать объявления, включая [о] наличии новых выпусков, которые распространяются на безопасность Вашего веб-сайта. У Вас имеется выбор подписаться на этот канал по RSS или по электронной почте.
  • Если Вы работаете на какой-либо более старой, по отношению к текущей, версии (например, Вы работаете на 3.1.6 и текущая версия - 3.4.5), то Вам следует перейти на текущую версию. Каждый не главный выпуск устраняет какое-либо число багов и/или проблем с безопасностью. Переход на наипоследний выпуск обслуживания как первый шаг при поиске и устранении какой-либо проблемы или только что обнаруженной уязвимости в безопасности - это всегда хорошая практика.

Версии Joomla! CMS

Версия CMS Имеется Поддержка Окончание поддержки (ОП) Тип обновления Заметки Наипоследний выпуск
Баги Безопасность
1.5
X-mark.png
X-mark.png
X-mark.png
Сент 2012 Миграция на 2.5 Планируйте мигрировать на 2.5 сейчас
История версии Joomla 1.5
ОП для 1.5.26
1.6
X-mark.png
X-mark.png
X-mark.png
Авг 2011 Одним щелчком на 2.5 Перейдите на 2.5 сейчас
История версии Joomla 1.6
1.6.6
1.7
X-mark.png
X-mark.png
X-mark.png
Фев 2012 Одним щелчком на 2.5 Перейдите на 2.5
История версии Joomla 1.7
1.7.5
2.5
X-mark.png
X-mark.png
X-mark.png
31 декабря 2014 Одним щелчком на 3.х Обновиться на 3.6.0 сейчас
История версии Joomla 2.5
2.5.28
3.0
X-mark.png
X-mark.png
X-mark.png
Май 2013 Одним щелчком на 3.1 Вы должны использовать переход одним щелчком
История версии Joomla 3.0
3.0.4
3.1
X-mark.png
X-mark.png
X-mark.png
Дек 2013 Одним щелчком на 3.2 Вы должны использовать переход одним щелчком
История версии 3.1
3.1.6
3.2
X-mark.png
X-mark.png
X-mark.png
Окт 2014[1] Одним щелчком на 3.3 Вам следует обновить версию PHP своего веб-сервера на 5.3.10 или новее и перейти на Joomla! 3.3
История версии Joomla! 3.2
3.2.7
3.3
X-mark.png
X-mark.png
X-mark.png
Выпуск 3.4 Одним щелчком Вы должны использовать переход одним щелчком
История версии Joomla 3.3
3.3.6
3.4
X-mark.png
X-mark.png
X-mark.png
Выпуск 3.5 Одним щелчком Recommended for all new installs
Joomla 3.4 version history
3.4.8
3.5
X-mark.png
X-mark.png
X-mark.png
Выпуск 3.6 Одним щелчком Recommended for all new installs
Joomla 3.5 version history
3.5.1
3.6[2]
Checkmark.png
Checkmark.png
Checkmark.png
3.7 release One-click Recommended for all new installs
Joomla! 3.6 version history
3.6.0
3.7[2] to define[2][3] - - 3.8 release One-click
... ... ... ... ... ... ... ...
4.0 2016[3] - -


Дополнительные внешние библиотеки

Какая-либо установка [системы] Joomla! содержит включенные в выпуски версий Joomla! CMS внешние библиотеке. Эти внешние библиотеке не являются часть кода ядра. Познакомтесь, пожалуйста, с разделом "Примечания", поскольку в нем содержимтся больше информации, такой как изменение версии сторонней библиотеки, вошедшей в выпуск ослуживания.

Внешние библиотеки по выпускам Joomla

Версия CMS Поддерживаемая версия CMS Mootools Mootools More jQuery jQuery UI
(Core, Widget, Mouse, Position и Sortable)
Bootstrap Simple Pie PHP Mailer PHP UTF-8 IDNA Convert Rapid Application Development (RAD) Framework
Akeeba's Framework on Framework(FOF)
password _compat[4] lessphp random _compat[5]
2.5
X-mark.png
1.4.5[6] 1.4.0.1 Н/П[7] Н/П[7] Н/П[7] 1.2 5.2.1 0.5 N/A[8] Н/П[9] Н/П[10] N/A[11] N/A[12]
3.0
X-mark.png
1.4.5 1.4.0.1 1.8.1 1.8.23 2.1.0 1.2 5.2.1 0.5 N/A[8] Н/П[9] Н/П[10] N/A[11] N/A[12]
3.1
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.1.0 1.2[13] 5.2.3 0.5 N/A[8] N/A[9] N/A[10] N/A[11] N/A[12]
3.1.2
X-mark.png
1.4.5 1.4.0.1 1.8.3 1.8.23 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 N/A[9] N/A[10] N/A[11] N/A[12]
3.2
X-mark.png
1.4.5 1.4.0.1 1.10.2[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.6 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.3
X-mark.png
1.4.5 1.4.0.1 1.11.1[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.8 0.5 0.8.0 2.1 1.0.3 N/A[11] N/A[12]
3.4
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.9 0.5 0.8.0 2.4.3 1.0.4 0.3.9 N/A[12]
3.5
X-mark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.6
Checkmark.png
1.4.5 1.4.0.1 1.11.3[15] 1.9.2 2.3.2[14] 1.2[13] 5.2.14 0.5 0.8.0 2.4.3 1.0.4 0.5.0 1.0.10
3.7


Обзор версионности Joomla!

Joomla! 
3.6.0
Стабильная версия

Эта страница предоставляет обзор текущей стратегии разработки, опубликованной 25-го апреля 2014 года. Все версии Joomla!, выпущенные до 25-го апреля 2014, были разработаны согласно предыдущего цикла выпусков и разработки. Для более подробной информации познакомтесь, пожалуйста, со стратегией разработки Joomla!.

Joomla! разрабатывается следуя семантическому версионированию (2.0.0). [Применяемые раньше термины] LTS (долгосрочная поддержка) и STS (краткосрочная поддержка) больше не действуют и не соблюдаются. Для ясности, [вместо них] используются термины, приведенные ниже. Вы должны понимать их и их значение.

  • поддерживается - самая последняя минорная версия(ии) мажорной версии, [которая] будет получать патчи, включающие исправления программных ошибок и патчи безопасности
  • текущая - самая молодая или самая последняя мажорная.x.x официально выпущенная версия
  • наследие - любая мажорная.минорная.патч версия(ии), которая не является текущей.[16]
  • стабильная - мажорная версия в отношении [версий со статусами] текущая и наследие, готовая для использования на производственных веб-сайтах.[17]
  • ОСП - сокращение от 'окончание срока поддержки', что означает что [для данной версии] больше не будет выпущено патчей с исправлениями программных ошибок и патчей безопасности
  • ОСЖ - сокращение от 'окончание срока жизни', что имеет то же значение что и 'окончание поддержки'.[18]

Каждая мажорная версия Joomla! поддерживается проектом Joomla!TM некоторое ограниченное время, начиная с даты ее официального выпуска. Проект Joomla! будет активно разрабатывать каждую мажорную версию как минимум в течении двух лет. За этим может последовать продолжение разработки мажорной версии согласно плана разработки мажорной версии.[19].

Вкратце можно сказать так:

  • каждая мажорная версия будет поддерживаться как минимум 4 года
  • Вам всегда необходимо использовать наипоследнюю версию минорная.патч наипоследней мажорной версии или обновиться на нее
  • каждая выпущенная минорная версия является обратно совместимой с предыдущим минорным выпуском[20]

Для определения приблизительной даты окончания срока поддержки каждой версии(ий) мажорная.минорная или всей мажорной версии, используйте, пожалуйста, маршрут разработки Joomla! CMS или версии Joomla! CMS.

Объяснение нумерации версий

Идентификаторы версий Joomla! соблюдают трех уровневую нумерную конвенцию, где данные уровни определяются значением [примененного в] системе изменения.

[major].[minor].[patch]

Эти 3 уровня определяются следующим образом:

  1. Инкрементное увеличение номера идентификатора мажорной версии указывает на разрыв в обратной совместимости.
  2. Инкрементное увеличение номера идентификатора минорной версии указывает добавление новых характеристик или значительное изменение существующих.
  3. Инкрементное увеличение номера идентификатора версии патч указывает на устранение каких-либо программных ошибок.

Примеры

Вы используете версию Joomla! 3.3.6. Это означает, что Ваша версия - мажорная версия 3, минорная версия 3, патч версия 6. Если для версии 3.3.6 будет выпущен какой-либо патч, то он увеличит версию Joomla! на 3.3.7. Если для мажорной версии 3 выпущена новая минорная версия, то версия Вашей Joomla! станет 3.4.0. Эта страница будет всегда показывать в правом верхнем углу текущую стабильную поддерживаемую версию Joomla!, включая минорную и патч.


Ссылки и примечания

  1. Устранение багов было остановлено в апреле 2014, [проводится] только устранение [багов] с безопасностью, смотрите http://community.joomla.org/blogs/leadership/1798-raising-the-bar-on-security.html.

    "Также, в течении шести месяцев по выпуску Joomla! 3.3 проект Joomla! будет выпускать обновления безопасности для 3.2 И 3.3, чтобы новые уязвимости можно было быстро пропатчить обновлением одним щелчком, без необходимости немедленного перехода на Joomla! 3.3, предоставляя Вам время для запроса у Вашего хостера обновить их версию PHP. "

  2. 2.0 2.1 2.2 See J3's roadmap for time frames of all future releases of all Joomla! 3 versions.
  3. 3.0 3.1 Please note that dates may be subject to change depending on availability of volunteers and circumstances beyond the PLT's control.
  4. This library is intended to provide forward compatibility with the password_* functions which were added to PHP 5.5. See password_compat git for further information.
  5. This library is intended to provide forward compatibility with the random_bytes and random_int functions which were added to PHP 7.0. See random_compat git for further information.
  6. Содержит слой совместимости с 1.2
  7. 7.0 7.1 7.2 Не применимо. Эта библиотека не была включена в версию 2.5 Joomla! CMS.
  8. 8.0 8.1 8.2 Not applicable, this library was not included with the Joomla! CMS prior to version 3.1.2.
  9. 9.0 9.1 9.2 9.3 Не применимо. Эта библиотека не была включена в систему Joomla! CMS до версии 3.2. Однако эта версия FOF включена в Joomla 3.2 и совместима с Joomla 2.5.
  10. 10.0 10.1 10.2 10.3 Не применимо. Эта библиотека не была включена в [версиях] Joomla! CMS до версии 3.2.
  11. 11.0 11.1 11.2 11.3 11.4 11.5 Not applicable, this library was not included with the Joomla! CMS prior to version 3.4
  12. 12.0 12.1 12.2 12.3 12.4 12.5 12.6 Not applicable, this library was not included with the Joomla! CMS prior to version 3.5
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Эта библиотека была снята как устаревшая и заменена на JFeedFactory в версии 3.1.0 системы Joomla! CMS.
  14. 14.0 14.1 14.2 14.3 14.4 14.5 Содержит некоторую обратную совместимость с 2.1
  15. 15.0 15.1 15.2 15.3 15.4 Включает плагин 'jQuery Migrate plugin 1.2.1' для обратной совместимости.
  16. Учтите, что наследие - это термин, который используется только для обозначение статуса какой-либо версии в отношении версии, текущей [на данный момент]. Для определения целесообразности использования какой-либо версии [со статусом] наследие пользователи и разработчики должны внимательно рассмотреть дату(ы) окончания срока ее поддержки.
  17. Версии, отмеченные как Альфа, Бета или RC, необходимо использовать только для тестирования
  18. 'ОСП' и 'ОСЖ' можно использовать как взаимо заменяемые термины. Любой [из этих двух терминов] означет 'окончание срока поддержки', не более того. Не принимайте 'окончание срока жизни' [данной версии] как [термин, означающий что начиная с данной даты] данная версия перестанет работать.
  19. Полное объяснение поддерживаемых выпусков можно найти под заголовком 'Поддерживаемые выпуски 4.3' на странице документа стратегии разработки Joomla!
  20. Какое-либо расширение или шаблон, установленные на версии минорная.0.х, будут работать на версии мажорная.7.х. Не принадлежащие ядру Joomla расширения или шаблоны разрабатываются сторонними разработчиками и обновление и публикация обновлений сторонних расширений и шаблонов - ответственность их разработчиков. Установка обновления какого-либо расширения или шаблона - ответственность используемого это расширение или шаблон пользователя.


Where are the sections?

Joomla! 2.5 eliminates sections and instead allows you to use categories within categories, with as many levels of categories as you choose. All content must be in a category, but it is not necessary to have multiple categories or levels.


Where is the auto update for Joomla?

Starting with version 2.5.4, the auto update for Joomla is now located in Components→Joomla! Update, as shown here:
Version-2-5-5-faq-screenshot.png
Extensions are still updated using the Extension Manager (Extensions→Extension Manager). If you click on the Joomla! Update icon in the Control Panel, it will link you to the Joomla! Update component automatically.


Why can't a user see anything on the backend?

This usually happens because a user has been given membership in a group with rights to access the backend but the group has not been assigned to a viewing access level. By default most assets (mainly modules such as the administrator menu and Quick Icons) in the backend are assigned to viewing access level Special. So, most commonly you will want to assign any group with backend rights to the special access level in addition to any other levels it might be assigned.


Why is my Joomla! 2.5 site update manager showing an update to 3.x?


<translate> Not unless you’re 1000% sure. By default, Joomla will not let you update to 3.x unless you activate the option within the Joomla! Update component (administrator >> Component >> Joomla! Update >> Options >> Update server >> Short Term Support). If for some reason you’ve changed this, and you’d like the updater to stop letting you upgrade, change the setting to Long Term Support. After making this change, you’ll only receive updates for Joomla! 2.5. </translate>

<translate> Notice: You should not upgrade from Joomla! 2.5 to Joomla! 3.x unless you are certain that all of your additionally installed extensions (from third party developers), especially templates, are Joomla! 3.x ready or have a Joomla! 3.x version that you can upgrade to. You should only upgrade from 2.5 to 3.x on a development site not on your live site. See Why Migrate and follow the pages for more information on upgrading from 2.5 to 3.x. </translate>


Why is my Joomla! 2.5 site update manager showing an update to 3.x?/en


Not unless you’re 1000% sure. By default, Joomla will not let you update to 3.x unless you activate the option within the Joomla! Update component (administrator >> Component >> Joomla! Update >> Options >> Update server >> Short Term Support). If for some reason you’ve changed this, and you’d like the updater to stop letting you upgrade, change the setting to Long Term Support. After making this change, you’ll only receive updates for Joomla! 2.5.

Notice: You should not upgrade from Joomla! 2.5 to Joomla! 3.x unless you are certain that all of your additionally installed extensions (from third party developers), especially templates, are Joomla! 3.x ready or have a Joomla! 3.x version that you can upgrade to. You should only upgrade from 2.5 to 3.x on a development site not on your live site. See Why Migrate and follow the pages for more information on upgrading from 2.5 to 3.x.


Will my Joomla! 2.5 extensions work with Joomla! 3.x?


Joomla! 
3.x
<translate> series</translate>

<translate> Extensions that are native to Joomla! 2.5 should work on Joomla! 3.0 with very little change, if any. Components and templates will need the most work, while modules and plugins should work without issue (assuming they do not use deprecated methods). Extensions that support Joomla! 2.5 and 1.5 in the same package will likely not work right away, until the developers update them for Joomla! 3 compatibility. </translate>

<translate> In short, it depends on the extension. The Joomla! Project has made the process relatively easy for most extensions, however for some extensions it’s going to take some work. To be certain, let the developers of the extensions know that you want to use their extension on Joomla 3 and consult with their documentation. </translate>


Will my Joomla! 2.5 extensions work with Joomla! 3.x?/en


Joomla! 
3.x
series

Extensions that are native to Joomla! 2.5 should work on Joomla! 3.0 with very little change, if any. Components and templates will need the most work, while modules and plugins should work without issue (assuming they do not use deprecated methods). Extensions that support Joomla! 2.5 and 1.5 in the same package will likely not work right away, until the developers update them for Joomla! 3 compatibility.

In short, it depends on the extension. The Joomla! Project has made the process relatively easy for most extensions, however for some extensions it’s going to take some work. To be certain, let the developers of the extensions know that you want to use their extension on Joomla 3 and consult with their documentation.


Will my Joomla! 2.5 extensions work with Joomla! 3.x?/pt


Joomla! 
3.x
série

Extensões que são nativos do Joomla! 2.5 deve trabalhar em Joomla! 3.0 com poucas alterações, se houver. Componentes e modelos terão mais trabalho, enquanto módulos e plugins devem funcionar sem problema (supondo que eles não usam preterido métodos). Extensões de suporte Joomla! 2,5 e 1,5 no mesmo pacote não iram provavelmente não ira funcionar de imediato, até que os programadores actualizem para Joomla! 3.

Resumido, depende da extensão. O Joomla! Projeto fez o processo relativamente fácil para a maioria das extensões, no entanto, para algumas extensões que vai levar algum trabalho. Para estar certo, diga aos programadores de extensões que você deseja a sua extensão em Joomla 3 e consultar a sua documentação.


Will your 1.0 extensions still work?

Joomla 2.5 and newer Joomla 2.5Joomla 3.x

Extensions written for Joomla 1.0 will not work in Joomla 2.5 and newer. The legacy system used in Joomla 1.5 has been removed.

Joomla 1.5 Joomla 1.5

There is a legacy system in place that will allow extensions that are not 1.5 compatible to continue to operate. However, we strongly recommend that you update to the current version of all extensions prior to migration and that you check each extension's home page for specific recommendations about migration for that extension.

To activate the legacy support, go to the Plugin Manager and enable the legacy plugin.


Wrong date format in profile plugin

If you see % (ampersand) in your date field, which is part of the profile plugin (date of birth field), you can fix it easily with editing the file plugins/user/profile/profile.php.

Line #227 currently (Joomla! 2.5.1) is:

$data['profile']['dob'] = $date->format('%Y-%m-%d');

and should be changed to:

$data['profile']['dob'] = $date->format('Y-m-d');

See also


Articles in Category: Version 2.5 FAQ
Adding images
Adding images/ar
Adding images/da
Adding images/en
Adding images/et
Adding images/fa
Adding images/nl-informal
All HTML markup is stripped when you save an article
Broken-configuration-screen-in-2.5.10
Can I add registration fields?
Can articles be assigned to multiple categories or sections?
Can you remove the "Powered by Joomla!" message?
Cannot-upload-file-in-2.5.10
Control Panel Breaks When Upgrading to 2.5.0
Database Errors When Upgrading to 2.5.0
Disappearing articles after 2.5 upgrade
Editors buttons Issues in FireFox
Empty-$path-issue-in-2.5.10
Enabling user's registration approval by admins
Error notice using search
Fatal error: Call to undefined method JInstaller::parseXMLInstallFile()
Fatal error: Using $this when not in object context in /libraries/joomla/application/base.php on line 87
Ftp-update-not-working
How can you view a live site while developing, but hide it from others?
How do I upgrade to Joomla! 3.x?
How do I upgrade to Joomla! 3.x?/de
How do I upgrade to Joomla! 3.x?/en
How do you find a Joomla! extension?
How do you list your extension in the extensions site?
How do you set global preferences for content?
How do you set parameters for articles and other content items?
How do you use Recaptcha in Joomla?
How do you use Recaptcha in Joomla?/de
How do you use Recaptcha in Joomla?/en
J2.5:How to Disable the EOS Notice Plugin
J2.5:How to Disable the EOS Notice Plugin/en
J2.5:How to add a span element to menu entries
How to check the Joomla version?
How to check the Joomla version?/de
How to check the Joomla version?/en
How to check the Joomla version?/pt-br
Issues with the Contact form and Gmail and GoogleApps
Joomla Update Missing in from Admin Menu
Missing-intro-text-and-images-in 2.5.10
Missing Save buttons on editing an article
Modals Stop Working When Upgrading to 2.5.0
Multilingual-problems-after-updating-to-2.5.11-or-3.1.1
No-updates-shown-in-current-version
Please first make a selection from the list
Should I launch a Joomla! 2.5 site or a 3.x site?
Should I launch a Joomla! 2.5 site or a 3.x site?/en
Should I update from Joomla! 2.5 to 3.x?
Should I update from Joomla! 2.5 to 3.x?/en
Update did not finish successfully
Category:Version 2.5.0 FAQ
Category:Version 2.5.10 FAQ
Category:Version 2.5.11 FAQ
Category:Version 2.5.13 FAQ
Category:Version 2.5.15 FAQ
Category:Version 2.5.1 FAQ
Category:Version 2.5.21 FAQ
Category:Version 2.5.23 FAQ
Category:Version 2.5.26 FAQ
Category:Version 2.5.27 FAQ
Category:Version 2.5.28 FAQ
Category:Version 2.5.2 FAQ
Category:Version 2.5.3 FAQ
Category:Version 2.5.4 FAQ
Category:Version 2.5.5 FAQ
Category:Version 2.5.6 FAQ
Version number is missing in back-end 2.5.0
What are the major differences between Joomla! 2.5 and 3.x?
What are the major differences between Joomla! 2.5 and 3.x?/en
What are the major differences between Joomla! 2.5 and 3.x?/fa
What are the major differences between Joomla! 2.5 and 3.x?/it
What are the major differences between Joomla! 2.5 and 3.x?/pt
What are the major differences between Joomla! 2.5 and 3.x?/ru
What do the locks mean and how do you get rid of them?
J2.5:What does a simple Joomla! installation include?
What if an extension only works on Joomla! 2.5 and not 3.x?
What if an extension only works on Joomla! 2.5 and not 3.x?/en
What is the contact creator?
What is the profile plugin?
What version of Joomla! should you use?
What version of Joomla! should you use?/bg
What version of Joomla! should you use?/de
What version of Joomla! should you use?/en
What version of Joomla! should you use?/et
What version of Joomla! should you use?/id
What version of Joomla! should you use?/it
What version of Joomla! should you use?/pt
What version of Joomla! should you use?/pt-br
What version of Joomla! should you use?/ru
Where are the sections?
Where is the auto update for Joomla?
Why can't a user see anything on the backend?
Why is my Joomla! 2.5 site update manager showing an update to 3.x?
Why is my Joomla! 2.5 site update manager showing an update to 3.x?/en
Will my Joomla! 2.5 extensions work with Joomla! 3.x?
Will my Joomla! 2.5 extensions work with Joomla! 3.x?/en
Will my Joomla! 2.5 extensions work with Joomla! 3.x?/pt
Will your 1.0 extensions still work?
Wrong date format in profile plugin