Joomla! Documentation - User contributions [en]

Pizza Bugs and Fun 2024/Contributors List

2024-02-24T15:43:23Z

Mfleeson: /* Kenyia */

<noinclude><languages /></noinclude>

[[Image:Banner_pbf24_1100px.png|center]]

Back to [[https://www.pizza-bugs-fun.com/en/ Pizza, Bugs & Fun]]

<translate>
''Edit the page and add your name to have your contribution to PBF2024 recorded.''

== These awesome Joomlers contributed to Pizza, Bugs & Fun 2024 ==

====Austria====
* Harald Leithner
* Sigrid Gramlinger
* Christine Walk
* Florian Bauer
* Kurt W.

====France====
* Catherine Mollet
* Emmanuel Lemor
* Gilles Nédélec
* Cyrille Poussin
* Serge Billon
* Jean-Charles Antoine
* Sebastien Lhuillier
* Yann Gomiero

====Germany====
* Martina Scholz
* Christiane Maier-Stadtherr
* Nadja Lamisch
* Benjamin Trenkle (JUG Munich)
* Dieter Ziller (max123kl)

====Greece====
* Dimitris Trikkas
* Bill Kotsias

====Italy====
* Pierantonio Borga
* Gioacchino Cipriano
* Walter Consoli
* Nicola Galgano
* Roberto Longo
* Alessandro Lumaca
* Davide Messia
* Luigi Morgantini
* Fausto Nenci
* Luca Racchetti
* Luca Sacchi Ricciardi

====Kenya====
* James Gichuru
* Dominic Maina
* Charles Kiruru
* Esther Nyambura

====Netherlands====
* Peter Martin
* Anja de Crom
* Tom van der Laan
* Nico van de Kamp
* Steven Trooster

====Spain====

====Switzerland====
* Martin Kopp
* Christof Rimle
* Heinz Riedener
* Rahel Schierbaum
* Lea Kemper
* Doris Dreher
* Manuel Häusler
* Roger Abt
* Peter Guntern
* Vreni Angst
* Ruedi Knutti

====Uganda====

====UK====
* Mark Fleeson

====USA====
* Laura Gordon
* Olivier Buisard
* Eddie Konczel
* Sarah Berryman
* SD Williams

====Vietnam====
* Tuan Pham Ngoc

</translate>

[[Category:Volunteer Engagement{{#translation:}}]]
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]

Pizza Bugs and Fun 2024/Contributors List

2024-02-24T15:19:32Z

Mfleeson: /* Kenyia */

<noinclude><languages /></noinclude>

[[Image:Banner_pbf24_1100px.png|center]]

Back to [[https://www.pizza-bugs-fun.com/en/ Pizza, Bugs & Fun]]

<translate>
''Edit the page and add your name to have your contribution to PBF2024 recorded.''

== These awesome Joomlers contributed to Pizza, Bugs & Fun 2024 ==

====Austria====
* Harald Leithner
* Sigrid Gramlinger
* Christine Walk
* Florian Bauer
* Kurt W.

====France====
* Catherine Mollet
* Emmanuel Lemor
* Cyrille Poussin
* Serge Billon
* Jean-Charles Antoine
* Sebastien Lhuillier
* Yann Gomiero

====Germany====
* Benjamin Trenkle (JUG Munich)
* Dieter Ziller (max123kl)

====Greece====
* Dimitris Trikkas
* Bill Kotsias

====Italy====
* Pierantonio Borga
* Gioacchino Cipriano
* Walter Consoli
* Nicola Galgano
* Roberto Longo
* Alessandro Lumaca
* Davide Messia
* Luigi Morgantini
* Fausto Nenci
* Luca Racchetti
* Luca Sacchi Ricciardi

====Kenyia====
* James Gichuru
* Dominic Maina
* Charles Kiruru
* Esther Nyambura

====Netherlands====
* Peter Martin
* Anja de Crom
* Tom van der Laan
* Nico van de Kamp
* Steven Trooster

====Spain====

====Switzerland====
* Martin Kopp
* Christof Rimle
* Heinz Riedener
* Rahel Schierbaum
* Lea Kemper
* Doris Dreher
* Manuel Häusler
* Roger Abt
* Peter Guntern
* Vreni Angst
* Ruedi Knutti

====Uganda====

====UK====
* Mark Fleeson

====USA====
* Laura Gordon
* Olivier Buisard
* Eddie Konczel
* Sarah Berryman
* SD Williams

====Vietnam====
* Tuan Pham Ngoc

</translate>

[[Category:Volunteer Engagement{{#translation:}}]]
[[Category:Pizza_Bugs_and_Fun{{#translation:}}]]

Pizza Bugs and Fun 2024/Contributors List

2024-02-24T11:52:37Z

Mfleeson: /* UK */

Joomla 3.x to 4.x Step by Step Migration

2021-08-17T22:08:15Z

Mfleeson: Removing section 12 of Joomla 4 as per request of Jenn Gress.

<noinclude><languages /></noinclude>
{{warning|title=<translate>

Warning!</translate>|<translate>

This guide assumes you are starting on Joomla 3.10.x. If you are on a earlier version make sure you upgrade to Joomla 3.10 first before moving to Joomla 4.


There is no rush. Make sure all your extensions are ready for Joomla 4.x. Joomla 3.10.x will be supported until 16 August 2023.</translate>}}

<translate>

The following are step by step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are hundreds of different scenarios, this will give you the basic procedure to follow. Very complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested path to migrate their extensions.
</translate>

<translate>
== Intro == 
The migration from Joomla! 3.10.x to 4.x is considered a mini-migration. This is because the Joomla core extensions will upgrade with a “one-click” upgrade via the Joomla! Update component in the backend administrator side of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. You need to look at each one and determine what path the extension needs to follow to get from 3.10 to 4.x. If you haven't already, you might be interested in reading the [[S:MyLanguage/Migration Step by Step Self Assessment|Self Assessment]] and [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for 3.10 to 4.x Migration]] prior to following the steps below.</translate>
<translate>

</br>Joomla! Core Extensions are:
* Categories
* Articles
* Menus
* Modules (core modules - not third-party)
* Action Logs
* Banners
* Fields
* Content History
* Contacts
* Messaging
* Newsfeeds
* Redirect
* Search (decoupled in 4.x. Existing 3.x sites will still migrate it. However we recommend using Smart Search going forward. See Notes under Assess Each Extension)
* Smart Search
* Tags
* Weblinks (decoupled but your site may be using it and it will migrate. See Notes under Assess Each Extension)
</translate>

<translate>
== Step by Step == 
=== Set up a Development Location ===
</translate>
<translate>

# Make sure you are running the latest Joomla 3.10.x version before proceeding.
# Take a backup of your live 3.10.x site. You can use a suggested tool (see the ''Suggested Tools'' at the bottom of page) or you can do this manually.
#*[[S:MyLanguage/Backup_Basics_for_a_Joomla!_Web_Site|Backup Basics for a Joomla! Web Site]]
#*[[S:MyLanguage/What_are_the_best_practices_for_site_backups%3F|What are the best practices for site backups?]]
# Make sure your environment meets the [https://downloads.joomla.org/technical-requirements technical requirements for Joomla 4] before proceeding.
# Create a new database and new user to restore your 3.10.x site to.
# Create a testing site or build area to work in and restore the backup copy of your 3.10.x site in one of the following places:
#* A subdomain.
#* A subdirectory.
#* A local device. Joomla has a detailed tutorial on installing [https://sourceforge.net/projects/xampp/ XAMPP] at [[XAMPP]]. However [https://www.wampserver.com/en/ WAMP], [https://www.mamp.info/en/windows/ MAMP], [https://sourceforge.net/projects/lampas/ LAMP] are all suitable alternatives.
#* A new hosting account on a temporary domain in the root. (If you would like to change hosts in the process of migration.)
#** Restoring a site on a local device. See [[S:MyLanguage/Installing Joomla locally|Installing Joomla locally]] and [[S:MyLanguage/Setting up your workstation for Joomla development|Setting up your workstation for Joomla development]].
#** Restoring a site with a tool listed at the bottom of the page. (Read the developer documentation.)
# In your test location, update your Joomla! 3.10.x instance to the latest maintenance release.
# Make sure you have the latest database schema updated to the latest version 3.10.x version by going to {{rarr|Extension Manager,Database}} tab. If your schema is not up to date as in the following image, click the '''Fix''' button:</translate>{{-}}[[File:J310-admin-extension-database-fix-<translate>

en</translate>.png|border|800px]]
<translate>

# Empty trash: Do you have any articles in the trash? If so, delete them (and any applicable media that may be associated with them if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause issues in having a migration to complete without errors.
# Test.
# Backup again.
</translate>

<translate>
=== Assess Each Extension === 
</translate>
<translate>

In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in {{rarr|Components,Joomla! Update}} and {{rarr|Extensions,Manage,Manage}}. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled.</translate>
<translate>

# Using the '''Pre-Update Check''': in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:Migration_J3toJ4_update_channel-<translate> en</translate>.png|border|800px]]{{-}}
<translate>
# Click Save & Close
# You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-admin-update_to_4-pre_update_check-<translate> en</translate>.png|border|800px]]<translate>

{{amboxNew|image=notice|style=notice|title={{{title|Important Notice}}}|text='''Do NOT update to Joomla! 4 right now. This is only to prepare your third-party extensions and get the site compatible with Joomla! 4.'''}}
# Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
# If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
#;* plg_content_geshi
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic</translate>
<translate> ## When it comes to templates, uninstall all core frontend or backend templates except Protostar and Beez3 (frontend templates) and Isis or Hathor (administrator templates). '''NOTE: Protostar is NOT compatible with Joomla 4'''. Upon migration it will disappear. You'll need to have one template selected as "default" and you can use Protostar or Beez3. Protostar will disappear upon migration to Joomla 4.x.</translate>
<translate> ## If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.</translate>
<translate> # You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.</translate>
<translate> # '''Update Extensions''': update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to {{rarr|Extension Manager,Update tab}} and click '''Find Updates''' which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.</translate>
<translate>
# Investigate and Uninstall Extensions Extensions: go to {{rarr|Extension Manager,Manage}}
# Click the Button ''Search Tools'' to show the filter options
# Select Package from the ''Select Type'' drop-down.</translate>{{-}}[[File:J310-admin-extension-manage-package-<translate>

en</translate>.png|800px]]{{-}}{{note|<translate>

Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.</translate>}}
<translate>

# Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
# Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.</translate>{{-}}{{note|<translate>

'''NOTE!''' You will not be able to uninstall any template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so. <br />''Another reminder:'' '''Protostar is not compatible with Joomla 4.x'''. Upon migration it will disappear. Selecting it as default simply gets you to Joomla 4.x.</translate>|type=serious}}
<translate>

# Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can copy/paste them into a document for reference.</translate>
<translate> # For any extensions you are keeping but don't use the Extension Manager to one-click update ({{rarr|Extensions,Manage,Update}}) update all extensions to the latest versions.</translate>
<translate> # Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:</translate>
<translate> #* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.</translate>
<translate> #* The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.</translate>
<translate> #* See [[S:MyLanguage/Template_Considerations_During_Migration|Template Considerations]] for more specific information on templates and [[S:MyLanguage/J3.x:Converting_A_Previous_Joomla!_Version_Template|Converting a previous Joomla! Version template]]</translate>

<translate>
==== Notes on Search (com_search) ==== 
Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.</translate>

<translate>
==== Notes on Weblinks ==== 
Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at [https://extensions.joomla.org/category/official-extensions/ Official Extensions].</translate>

==== Notes on Legacy Routing ====
Legacy routing will not be available in Joomla 4.x. Only Modern will be available. When you do the migration, if you are using Legacy routing, the system will automatically change them to Modern routing. You will want to run a broken link checker on your site after migrating to Joomla 4.x and ''before you go live''.

<translate>

=== Going to Joomla! 4.x === 
Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:
</translate>
<translate>

# Go to {{rarr|Site,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.</translate>{{-}} [[File:J310-system-global-config-server-tab-<translate>

en</translate>.png|border|500px]]
<translate>

# Take another backup.
# Go to {{rarr|Components,Joomla Update}}. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
# Select ''Joomla Next'' from the drop-down for Update Channel.</translate>{{-}}[[File:J310-component-joomla-update-select-support-<translate>

en</translate>.png|border|500px]]
<translate>

# Click Save & Close.
# You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.</translate>{{-}}[[File:J310-to-j4-dev-update-found-<translate>

en</translate>.png|border|800px]]
<translate>

# If the update is not showing up, go to {{rarr|Extension manager,Update}} and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.</translate>
<translate> # Cross your fingers, and make sure you have that backup available in case.</translate>
<translate> # Click the Install the Update button.</translate>
<translate> # Make tea whilst the status bar loads to fully green. The amount of time this takes is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.</translate>
<translate> # If all goes well, you will get to a totally new look to the backend administrator panel.</translate>{{-}}[[File:j4-administrator-overview-<translate>

en</translate>.png|border|800px]]
<translate> # Go to {{rarr|Extensions,Manage,Database}} and click ''Fix'' if any errors show.</translate>
<translate> # In the Extension Manager, go to Discover and see if there are any extensions to install. (There shouldn't be any!)</translate>
<translate> # Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see [[S:MyLanguage/Joomla 3.10 to 4.x Common Migration Errors|common errors during migration]].</translate>
<translate> # Take a backup.</translate>
<translate> # Install your new template or other extensions if you have them to install. Back up often.</translate>
<translate> # Configure them. Back up often.</translate>
# Run a broken link checker and fix any broken links.
<translate> # Test everything. Back up often.</translate>
<translate>
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
</translate>

<translate>

=== Going Live with your Joomla! 4.x Site === 
# When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
# Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
# Test again.
# Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your ''robots.txt'' file to block the search engine spiders.
# Remove all development sites you have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server. </translate>

<translate>

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a [https://extensions.joomla.org/category/migration-a-conversion/data-import-a-export%20transfer%20tool/third-party%20extension/ third party extension].
</translate>

<translate>
== Suggested Tools == 
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is very popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
</translate>
<noinclude>
<translate>

[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
</translate></noinclude>
<noinclude>[[Category:Needs to be marked for translation]]</noinclude>

User:Mfleeson

2021-05-20T11:39:51Z

Mfleeson:

My name is Mark, from the UK. I've used Joomla since Mambo days and have written extensions for over 10 years. I'm currently helping on the Joomla Extension Directory 4 Team and generally helping out where I think I can help. If you want to get in touch with me, post on my '''[[User_talk:{{PAGENAME}}|talk page]]'''.

Joomla and MySQL 8

2021-05-20T11:32:38Z

Mfleeson: Update to rephrase, it is possible to connect, it's not a work-around just a configuration change in MySQL 8.

<noinclude><languages /></noinclude>
<translate>
==MySQL default authentication plugin issue== 
</translate>
<translate> It is possible to connect to a MySQL 8 Database using Joomla {{JVer|3.x}}, however it requires a customisation on the MySQL 8 installation configuration. The reason is that MySQL 8 has a lot of low-level changes including the default authentication plugin changing to <tt>sha256_password</tt> from <tt>mysql_native_password</tt>. The native PHP MySQL-Driver doesn't currently support MySQL 8 with this plugin. [https://github.com/php/php-src/commit/d6e81f0bfd0cb90586dd83d4fd47a4302605261a PHP 7.3 (alpha)] is supporting MySQL 8 though.</translate>

<translate>
==MySQL configuration change to get Joomla working with MySQL 8== 
</translate>
<translate>
If you edit the configuration file for MySQL 8, you can change the default authentication plugin for MySQL to use the older mysql_native_password.
Open your configuration file <tt>sudo nano /etc/my.cnf</tt> (Please note that your file may be under a different directory) and add the following configuration:</translate>
<source lang="ini">
[mysqld]
default-authentication-plugin=mysql_native_password
</source>
<translate> If you don't have access to your config file then you can update your user as follows:</translate>
<source lang="mysql">
ALTER USER 'username'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password';
</source>
<translate> Replace username with the name of the user account and password with the password belonging to the account. Restart MySQL and you are done ...well, only if you have Joomla 3.8 or 3.9 installed.</translate>

<translate>
==How MySQL default authentication plugin works== 
</translate>
<translate> The advantage of <tt>mysql_native_password</tt> is that it supports the challenge-response mechanism which is very quick and does not require encrypted connection. However, <tt>mysql_native_password</tt> relies on SHA1 algorithm and NIST has recommended to stop using it.</translate>

<translate> Further, if two user accounts use the same password, <tt>mysql_native_password</tt> transformation is the same in the mysql.user table. Although the hash does not expose information about the actual password, it still tells which two users use the same password. To avoid that, a salt should be used. A salt is basically a random number that is used as one of the parameters to cryptographic hash functions used to transform user passwords. Since a salt is random and different for each execution, even if two users use the same passwords, the end result of transformation would look very different.</translate>
<translate>

Since MySQL 5.6, sha256_password authentication plugin is supported. It uses multiple rounds of SHA256 hash on a salted password to make sure that the hash transformation is more secure. However, it requires either encrypted connections or support for an RSA key pair. So, while password security is stronger, secure connections and multiple rounds of hash transformations require more time in the authentication process.</translate>

<translate> caching_sha2_password tries to combine the best of both worlds.</translate> <ref>https://mysqlserverteam.com/mysql-8-0-4-new-default-authentication-plugin-caching_sha2_password/</ref>

<noinclude>
[[Category:Server configurations{{#translation:}}]]
[[Category:Installation{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
</noinclude>

User:Mfleeson

2021-05-20T11:00:22Z

Mfleeson: This is my user page

My name is Mfleeson and if you want to get in touch with me, post on my '''[[User_talk:{{PAGENAME}}|talk page]]'''.

==My testing subpages==
<splist/>