Joomla! Documentation - User contributions [en]

J3.x:Joomla 3.10.12 Release FAQ

2023-07-04T15:17:54Z

Zero24: Created page with "== Joomla 3.10.12 Release FAQ == === What is this release about === This is a planned release of Joomla 3.10 that ensures the certificate files bundled within the core (`cac..."

== Joomla 3.10.12 Release FAQ ==

=== What is this release about ===

This is a planned release of Joomla 3.10 that ensures the certificate files bundled within the core (`cacert.pem`) used on some sites to verify SSL connections are up-to-date and not significantly out of date by the EOS of Joomla 3.10. Additionally, the version of the CMS will be bumped to 3.10.12.

=== Why do we have this release now? ===

The expected EOS date of 3.10 is 17.08.2023, and the planned 4.3.4 release is on 22.08., which is after the EOS of 3.10. To avoid confusion and maintain the tradition of releasing 3.10 alongside the corresponding 4.x release, we have decided to do this release together with 4.3.3.

=== What are the changes included in this release ===

As mentioned above, there are only two changes included in this release:

* Updating the `cacert.pem` files to the latest version available at the time of the release. [https://github.com/joomla/joomla-cms/pull/39116 #39116]
* Bumping the CMS version to 3.10.12

=== What will happen until the EOS of 3.10 ===

As we have done in the past together with the JSST, we will monitor the security issues reported to us, and they will be checked against 3.10 too. When something is reported that applies to 3.10 as well, there will be a coordinated release of 3.10 and 4.x.

=== What should I do when I'm still on 3.10 now ===

When you are still on 3.10, please be aware that 17.08.2023 is just 38 days from the stable release at 11.07. We are aware and don't expect that 3.10 will be insecure by day one after this date, but after that date, 3.10 will be out of security support by the Joomla! Project.
So please check the Joomla 3.10 to 4.x step by step docs available with the Joomla Documentation: [[Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration – Joomla! Documentation]]

=== How can I update my Joomla installation to version 3.10.12? ===

The update will be provided by the Joomla Update server and will be the new base release to go to 4.x.

=== Will there be any compatibility issues with existing extensions or templates when upgrading to Joomla 3.10.12? ===

We don't expect any compatibility issues other than the pre-existing issues that the 3.x core or 3rd party extensions might have with higher PHP versions.

=== Can I continue using Joomla 3.10 after the EOS date without security support? ===

Sure, just be aware that there will be no security support from the project after that date.

=== What are the consequences of not updating to Joomla 3.10.12? ===

It will be a requirement to upgrade to 3.10.12 before moving to 4.x, but other than an outdated cacert.pem file used on some hosts, there will be no consequences.

=== Are there any other changes or enhancements in Joomla 3.10.12, apart from the SSL certificate update and version bump? ===

No.

=== Will there be any further releases or updates for Joomla 3.10 after version 3.10.12? ===

There are no plans to release another version of 3.10, but there will be one if any security issues are found before the EOS date.

=== What should I do if I encounter any issues or need support during the update process? ===

Please reach out to the Joomla Support forum or other Joomla support channels. As this is a regular release, it is usually a one-click release from the Joomla 3.10 backend. Just make sure you have the "Default" Update server selected to stay within your major.

=== How to upgrade from 3.10 to Joomla 4 ===

Please check the Joomla 3.10 to 4.x step by step docs available with the Joomla Documentation: [[Joomla 3.x to 4.x Step by Step Migration|Joomla 3.x to 4.x Step by Step Migration – Joomla! Documentation]]

<noinclude>
[[Category:Version 3.10.12 FAQ{{#translation:}}]]
[[Category:Joomla! 3.10{{#translation:}}]]
</noinclude>

Category:Version 3.10.12 FAQ

2023-07-03T21:52:22Z

Zero24: Created page with "<noinclude><languages /></noinclude> {{Joomla version|version=3.10.12|}} <translate>  These FAQs are specific to the Joomla! 3.10.12 release. Only issues that are sp..."

<noinclude><languages /></noinclude>
{{Joomla version|version=3.10.12|}}
<translate>

These FAQs are specific to the Joomla! 3.10.12 release. Only issues that are specific to this release will be listed here, together with suggested resolutions. Please add information to this resource. The Joomla! Bug Squad will watch over this page to ensure any new bugs are added to the tracker and resolved. Continue to use the '''[[jforum:705|Joomla! Forums for support requests]]''' as this is not a substitute for posting there, but rather a common location for the community to gather common release issues. </translate>

{{<translate> Note|To appear in this category, this text is required at the foot of the page</translate>:<br />
<nowiki>[[Category:Version 3.10.12 FAQ{{#translation:}}]]</nowiki>|reminder}}

{{TT|CreateFAQ}}
<noinclude>
[[Category:Version 3.10 FAQ{{#translation:}}]]
[[Category:Joomla! 3.10{{#translation:}}]]
</noinclude>

J3.x:4.2.0 Class not found

2022-08-16T20:55:02Z

Zero24: Replaced content with "to be deleted"

to be deleted

J3.x:After going to 4.1,1 or 3.10.7 some users can't login anymore

2022-03-29T20:51:17Z

Zero24:

==Errors reported== 

Some users can't login after they have been able to login without entering a PW right after the update to 4.1.1 or 3.10.7.

==Versions affected== 
{{tip|This pertains only to Joomla! version(s): '''4.1.1 & 3.10.7'''|title=General Information}} 

==What is the cause== 

After the update the Joomla Core binds the user on login to the authentication provider. But when your first login is with an none primarly update provider like the Cookie (Remember Me) after logging out the user can login again.

==How to fix== 

When you still have an SuperUser and can login into the backend, please go to: Users -> Manage -> "Username" -> Authentication Method -> Set to "None"

When you don't have an Super User that can login into the backend please go to the #__users table for the user and clear the value thats set in the "authprovider" column.

There will also be a 3.10.8 and 4.1.2 update that will apply the fix on all affected users and protect against the issue in the first place.

__NOTOC__

J3.x:After going to 4.1,1 or 3.10.7 some users can't login anymore

2022-03-29T20:48:17Z

Zero24: Created page with " ==Errors reported==  Some users can't login after they have been able to login without entering a PW r..."

File:Help-4x-Extensions-Plugin-Manager-Edit-http-headers-screen-en.png

2021-09-14T22:42:38Z

Zero24: Zero24 uploaded a new version of File:Help-4x-Extensions-Plugin-Manager-Edit-http-headers-screen-en.png

== Licensing ==
{{JEDL}}

Chunk4x:Extensions Plugin Manager Edit System Group

2021-09-14T22:39:26Z

Zero24:

With 3.10.0 we have added a bug that will show a required checkbox when you update to 3.10.1, that checkbox should not show up at all for patch releases and does not have any impact for 3.10.0 to 3.10.1 updates, so please check this checkbox to proceed with the update.

==Errors reported== 

On the update from 3.10.0 to 3.10.1 you will notice an message reading:

<code>Do you wish to ignore the warnings about potentially incompatible plugins and to proceed with the upgrade?</code>

[[File:3100 to 3101 update checkbox.png|border|800px]]

==Versions affected== 
{{tip|This pertains only to Joomla! version(s): '''3.10.0'''|title=General Information}} 

==What is the cause== 

With 3.10.0 we have added a bug that will show a required checkbox when you update to 3.10.1, that checkbox should not show up at all for patch releases in the first place and does not have any impact for 3.10.0 to 3.10.1 updates.

==How to fix== 

Please check that checkbox to procced with the update.

__NOTOC__


<noinclude>
[[Category:Joomla! 3.x]]
[[Category:Version 3.10.1 FAQ{{#translation:}}]]
[[Category:Version 3.10 FAQ{{#translation:}}]]
[[Category:Joomla! 3.10{{#translation:}}]]
</noinclude>

J3.x:Upgrades from 3.10.0 to 3.10.1 requires to tick an checkbox

2021-08-23T20:14:21Z

Zero24:

Deploying an Update Server

2021-08-23T19:01:29Z

Zero24:

<noinclude><languages /></noinclude>
<noinclude>{{Joomla version|version=2.5|status=eos}}{{Joomla version|version=3.x|}}{{Joomla version|version=4.x|}}</noinclude>

<translate>
== Introduction == 
</translate>
__TOC__
<translate>
This tutorial is designed to teach developers how to create an update server for integration with the update system introduced in Joomla!. By adding an update server listing to your extension's manifest, developers enable users to update their extensions via the Extension Manager's Update (see [[S:MyLanguage/Help31:Extensions Extension Manager Update|Joomla 3.x]] helpscreen) view with only a few clicks.</translate>
<translate>
== Defining an update server == 
</translate>
<translate>
In order to use this feature, an update server must be defined in your extension's manifest. This definition can be used in all Joomla! 2.5 and newer compatible extensions but is not available for templates. You can use two options for your server type: collection or extension. These will be explained in detail shortly. This code should be added to the extension manifest file, within the root ''extension'' element. The update server is defined as follows for each type:</translate>

<source lang="xml">
<extension>
<...>
<updateservers>
<server type="collection">https://example.com/list.xml</server>
<server type="extension" priority="2" name="My Extension's Updates">http://example.com/extension.xml</server>
</updateservers>
</extension>
</source>
<translate>
Multiple servers can be defined within the <tt><updateservers></tt> tag. If you have more than one update server, you can set a different priority for each. In that way you can control the order in which the update servers are checked.</translate>

<translate>
== Server types == 
</translate>
<translate>
=== Collection === 
</translate>
<translate>
The <tt>"collection"</tt> server type allows developers to define an extension's manifest to pull updates from a collection. This type of server can be used if the developer wants to define all of their extension's updates in a single file (not recommended) or if their extension has multiple sub-extensions which are not distributed or updated at the same time (such as a package extension type). The below example is the <tt>"collection"</tt> definition used by the updater when processing core Joomla! updates:</translate>

<source lang="xml">
<extensionset name="Joomla Core" description="Joomla! Core">
<extension name="Joomla" element="joomla" type="file" version="1.7.0" detailsurl="https://update.joomla.org/core/extension.xml"/>
</extensionset>
</source>

<translate>
All definitions must be defined between <extensionset> tags in your collection manifest. The <extensionset> tag has two optional parameters; name and description. For each extension that this collection references, a separate <extension> tag is required. The <extension> tag has the following parameters, all of which are required for updates to properly process:</translate>

<translate>
* '''name''' – The name of the extension</translate>
<translate>
* '''element''' – The untranslated extension name i.e. mod_custom</translate>
<translate>
* '''type''' – The extension type (component, module, plugin, etc.)</translate>
<translate>
* '''version''' – The latest version of the extension</translate>
<translate>
* '''detailsurl''' – The URL of the XML file which contains that extension's individual update definitions</translate>
<translate>
=== Extension === 
</translate>
<translate>
The <tt>"extension"</tt> server type allows developers to define an extension's manifest to pull updates from a single extension's manifest. All collection manifests eventually point to this XML file. All updates in this file must be defined after an <tt><updates></tt> tag at the beginning of the file. The below example is the update definition for the Joomla! 3.9.6 release:</translate>

<source lang="xml">
<updates>
<update>
<name>Joomla! 3.9</name>
<description>Joomla! 3.9 CMS</description>
<element>joomla</element>
<type>file</type>
<version>3.9.6</version>
<infourl title="Joomla!">https://www.joomla.org/announcements/release-news/5765-joomla-3-9-6-release.html</infourl>
<downloads>
<downloadurl type="full" format="zip">https://downloads.joomla.org/cms/joomla3/3-9-6/Joomla_3.9.6-Stable-Update_Package.zip</downloadurl>
<downloadsource type="full" format="zip">https://github.com/joomla/joomla-cms/releases/download/3.9.6/Joomla_3.9.6-Stable-Update_Package.zip</downloadsource>
<downloadsource type="full" format="zip">https://update.joomla.org/releases/3.9.6/Joomla_3.9.6-Stable-Update_Package.zip</downloadsource>
</downloads>
<tags>
<tag>stable</tag>
</tags>
<sha256>05157273aadd3045564ee44373ea3643b437fa5321d17993a3119b38b04578e2</sha256>
<sha384>ebd9b0666fbe84e20a420a4bcd6c10d306fc4dee4edbbe8e2133c85f0fb84e59be5a50aa97cb38c068b77f77f6bbc091</sha384>
<sha512>a4c47644ceeaeec28944e0c74160203cf12037e0ea1439022e95055dfb6716de172667ce6d9164f12bb519d9cfcf1fdc728abea00f853b41debc7d2740f2b711</sha512>
<maintainer>Joomla! Production Department</maintainer>
<maintainerurl>https://www.joomla.org</maintainerurl>
<section>STS</section>
<targetplatform name="joomla" version="3.[789]" />
<php_minimum>5.3.10</php_minimum>
</update>
</updates>
</source>

<translate>
The following section describes the elements of a single update entity.</translate>

<translate>
* '''name''' – The name of the extension, this name will appear in the Name column of the Extension Manager's Update view (required)</translate>
<translate>
* '''description''' – A short description of the extension (optional) — if you choose to use <![CDATA[]]>, double-quotes will break the HTML formatting. Use single quotes with your HTML entities.</translate>
<translate>
* '''element''' – The installed name of the extension (required). For plugins, this needs to be same as plugin attribute value for main file in plugin manifest. For <filename plugin="pluginname">pluginname.php</filename>, element value should be '''pluginname'''.</translate>
<translate>
* '''type''' – The type of extension (component, module, plugin, etc.) (required)</translate>
<translate>
* '''folder''' – Specific to plugins, this tag describes the type of plugin being updated (content, system, etc.) (required for plugins)</translate>
<translate>
* '''client''' – Required for modules and templates as of 3.2.0. – The client ID of the extension, which can be found by looking inside the #_extensions table. To date, use 0 for "site" and 1 for "administrator". '''Warning!''' Plugins and front-end modules are automatically installed with a client of 0 (site), but you will need to specify the client in an update or it will default to 1 (administrator) and then found update would not be shown because it would not match any extension. Components are automatically installed with a client of 1, which is currently the default.</translate>
<translate>
** ''Warning'': The tag name is <'''client'''> for Joomla! 2.5 and <'''client_id'''> for 1.6 and 1.7. If you use <client_id> (rather than <client>) on a 2.5 site, it will be ignored.</translate>
<translate>
* '''version''' – The version of the release (required)</translate>
<translate>
* '''infourl''' – A URL to point users to containing information about the update (optional) (In CMS 2.5, if set, this URL will be displayed in the update view)</translate>
<translate>
* '''downloads''' – The section which lists all download locations</translate>
<translate>
** '''downloadurl''' – The URL to download the extension from; the <downloadurl> tag has two required parameters:</translate>
<translate>
*** '''type''' – The type of package (full or upgrade)</translate>
<translate>
*** '''format''' – The format of the package (zip, tar, etc.)</translate>
<translate>

** '''downloadsource''' – Optional. Since Joomla 3.8.3. Alternative URL to download the extension from when the connection to <downloadurl> fails. Multiple <downloadsource> tags are allowed. The <downloadsource> tag has two required parameters:</translate>
<translate>

*** '''type''' – The type of package (full or upgrade)</translate>
<translate>

*** '''format''' – The format of the package (zip, tar, etc.)</translate>
<translate>
** '''NB''' – there must be no newline before or after the URL; it needs to all be on one line or you will get Error connecting to the server: malformed when the update is run</translate>
<translate>
* '''changelogurl''' - A link to an xml file holding the changelog. Joomla 4.0 and later will allow you to show a button for the changelog in the extension updater page. More details in how to use it can be found here: [[Adding changelog to your manifest file]]
* '''tags''' – A list of tags relevant to this version. Joomla! 3.4 and later uses this to determine the stability level of the update. The valid tags are:</translate>
<translate>
** ''dev'': Development versions, very unstable and pre-alpha (e.g. nightly builds)</translate>
<translate>
** ''alpha'': Alpha quality software (features not implemented, show-stopper bugs)</translate>
<translate>
** ''beta'': Beta quality software (all features implemented, show-stopper bugs possible, minor bugs almost certain)</translate>
<translate>
** ''rc'': Release Candidate quality software (no show-stopper bugs, minor bugs may still be present)</translate>
<translate>
** ''stable'': Production quality software All other tags are currently ignored. If you provide more than one tag containing one of the aforementioned stability keywords only the LAST tag will be taken into account. If you do not provide any tags Joomla! will assume it is a stable version</translate>.
<translate>
* '''maintainer''' – The name of the extension maintainer (similar to the <author> tag in a manifest) (optional)</translate>
<translate>
* '''maintainerurl''' – The website of the extension maintainer (similar to the <authorUrl> tag in a manifest) (optional)</translate>
<translate>
* '''section''' – Optional (unknown use)</translate>
<translate>
* '''targetplatform''' – A tag to define platform requirements (from {{ JVer| 3.10 }} this is also used to detect extension compatibility for the Joomla Update component), requires the following elementsː</translate>
<translate>
** '''name''' – The name of the platform dependency; as of this writing, it should ONLY be "joomla"</translate>
<translate>
** '''version''' – The version of Joomla! the extension supports</translate>
<translate>
** '''min_dev_level''' and '''max_dev_level''' – These attributes were added in 3.0.1 to allow you to select a target platform based on the developer level ("z" in x.y.z). They are optional. You can specify either one or both. If omitted, all developer levels are matched. For example, the following matches versions 4.0.0 and 4.0.1. <code><targetplatform name="joomla" version="4.0" min_dev_level="0" max_dev_level="1"/></code></translate>
<translate>
*** '''Note:''' If your extension is Joomla! 2.5 and/or 3.1 compatible, you will be required to have separate <update> definitions for each version due to the manner in which the updater checks the version if you specify a number. However to show your extension on all Joomla versions that support automatic updates (and thus mark as compatible with all future unreleased versions of Joomla in Joomla Update) add <code><targetplatform name="joomla" version=".*"/></code>. If you want your extension to show on all {{JVer|3.x}} versions then rather than specifying a version in the version tag add in <code><targetplatform name="joomla" version="3.[012345]"/></code>. This will show the update to all 3.x versions from version 3.0 to 3.5. If you want to include version 3.10 you can use an <code>|</code> like this: <code><targetplatform name="joomla" version="3.[012345]|10"/></code>. If you want to show the updates for all 3.8.x versions and all 3.10.x versions you can use <code><targetplatform name="joomla" version="3.(8|10)"/></code></translate>
<translate>
* '''php_minimum''' – Beginning with 3.2.2, a minimum supported PHP version can be supplied in the update stream. If the server does not meet the minimum, a message is displayed to the user advising that an update is available but cannot be installed due to unsupported requirements.</translate>
<translate>
* '''supported_databases''' – Beginning with 3.7, a minimum supported databases + version check can be supplied in the update stream. When the server does not meet the minimum, a message is displayed to the user advising that an update is available but cannot be installed due to unsupported requirements. Note: [https://github.com/joomla/joomla-cms/pull/26079 As of 3.9.12] there is also a special case for mariadb so you can set a specific minimum version for that too now.</translate>
<translate>
** An example could look like this:</translate> <code><supported_databases mysql="5.5.3" mariadb="10.1" postgresql="9.2" mssql="10.50.1600.1" /></code>
<translate>

* '''sha256''', '''sha384''', '''sha512''' – Optional. Since Joomla 3.9.0 you can add file checksums in these hash formats. Be aware that in Joomla 3 only a notice is shown on '''updates''' if a checksum is not correct. That's all. The update doesn't stop then. In Joomla 4 updates and installations will stop if a provided checksum doesn't match.</translate>

<translate>
A separate <update> definition will be required for each version of your extension you release.</translate>

<translate>
The values of '''element''', '''type''', '''client_id''' and '''folder''' should match those in the table #_extensions.</translate>

<translate>
'''Important for plugins:''' Plugins have to include <folder> and <client> elements to work properly</translate>
<translate>
== Troubleshooting == 
</translate>
<translate>
* '''SQL update script is not executed during update.'''</translate>
<translate>
:If the SQL update script (for example, in the folder <code>sql/updates/mysql</code>) does not get executed during the update process, it could be because there is no version number in the <code>#_schemas</code> table for this extension ''prior to the update''. This value is determined by the last script name in the SQL updates folder. If this value is blank, no SQL scripts will be executed during that update cycle. To make sure this value is set correctly, make sure you have a SQL script in this folder with its name as the version number (for example, 1.2.3.sql if the version is 1.2.3). The file can be empty or just have a SQL comment line. This should be done in the old version — the one before the update. Alternatively, you can add this value to the <code>#_schemas</code> using a SQL query.</translate>

<translate>
== Supporting Tools == 
</translate>

<noinclude><translate>
[[Category:Development]]</translate></noinclude>

2021-03-30T22:05:15Z

Zero24:

== Licensing ==
{{JEDL}}

File:Pre upgrade checker ok-en.png

2021-03-30T21:58:30Z

Zero24:

== Licensing ==
{{JEDL}}

File:Pre upgrade checker warning-en.png

2021-03-30T21:58:13Z

Zero24:

== Licensing ==
{{JEDL}}