Joomla! Documentation - User contributions [en]

Translations:Joomla 3.x to 4.x Step by Step Migration/5/zh-tw

2025-01-07T01:14:04Z

Shawnhy: Created page with "== Step by Step == === Set Up a Development Location ==="

== Step by Step ==
=== Set Up a Development Location ===

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:14:01Z

Shawnhy: Created page with "</br>這是Joomla!的核心擴展： * 類別 * 文章 * 選單 * 模組（核心模組 - 不包括第三方模組） * 操作日誌 * 橫幅廣告 * 欄位 * 內容歷史 *..."

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。

無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。}}

本文將一步步的將你的 Joomla 3.10 網站遷移到 4.x。由於實際的應用情境可能有數百種，我們將給你一個最基本的流程可以遵循。大量的第三方擴充套件可能會造成較為複雜的遷移流程，建議你可以聯絡第三方套件的作者詢問相關建議來幫助您遷移這些套件至最新版本。

== Intro ==
從 Joomla! 3.10.x 遷移到 4.x 被視為一次小規模遷移。這是因為 Joomla 核心擴展將通過 Joomla! 後台 (管理員) 中的「更新」元件進行「一鍵式」升級。許多第三方擴展也支持一鍵式升級。有些則不支持。請逐一檢查每個擴展，並確定從 3.10 到 4.x 的升級路徑。如果您還沒有閱讀，請先閱讀 [[S:MyLanguage/Migration Step by Step Self Assessment|自我評估]] 和 [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|規劃 3.10 到 4.x 遷移]]，然後再按照以下步驟操作。
</br>這是Joomla!的核心擴展：

* 類別
* 文章
* 選單
* 模組（核心模組 - 不包括第三方模組）
* 操作日誌
* 橫幅廣告
* 欄位
* 內容歷史
* 聯絡人
* 訊息
* 新聞來源
* 重新導向
* 搜尋（在 4.x 版本中解耦。現有的 3.x 站點仍會遷移它。但是我們建議使用智能搜尋。請參閱「評估每個擴展」下的說明）
* 智能搜尋
* 標籤
* 網站連結（解耦，但您的網站可能正在使用它，並且它將遷移。請參閱「評估每個擴展」下的說明）

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/4/zh-tw

2025-01-07T01:13:54Z

</br>這是Joomla!的核心擴展：

* 類別
* 文章
* 選單
* 模組（核心模組 - 不包括第三方模組）
* 操作日誌
* 橫幅廣告
* 欄位
* 內容歷史
* 聯絡人
* 訊息
* 新聞來源
* 重新導向
* 搜尋（在 4.x 版本中解耦。現有的 3.x 站點仍會遷移它。但是我們建議使用智能搜尋。請參閱「評估每個擴展」下的說明）
* 智能搜尋
* 標籤
* 網站連結（解耦，但您的網站可能正在使用它，並且它將遷移。請參閱「評估每個擴展」下的說明）

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:13:06Z

Shawnhy: Created page with "== Intro == 從 Joomla! 3.10.x 遷移到 4.x 被視為一次小規模遷移。這是因為 Joomla 核心擴展將通過 Joomla! 後台 (管理員) 中的「更新」元件進..."

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。

無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。}}

本文將一步步的將你的 Joomla 3.10 網站遷移到 4.x。由於實際的應用情境可能有數百種，我們將給你一個最基本的流程可以遵循。大量的第三方擴充套件可能會造成較為複雜的遷移流程，建議你可以聯絡第三方套件的作者詢問相關建議來幫助您遷移這些套件至最新版本。

== Intro ==
從 Joomla! 3.10.x 遷移到 4.x 被視為一次小規模遷移。這是因為 Joomla 核心擴展將通過 Joomla! 後台 (管理員) 中的「更新」元件進行「一鍵式」升級。許多第三方擴展也支持一鍵式升級。有些則不支持。請逐一檢查每個擴展，並確定從 3.10 到 4.x 的升級路徑。如果您還沒有閱讀，請先閱讀 [[S:MyLanguage/Migration Step by Step Self Assessment|自我評估]] 和 [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|規劃 3.10 到 4.x 遷移]]，然後再按照以下步驟操作。
</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.)

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/3/zh-tw

2025-01-07T01:12:55Z

== Intro ==
從 Joomla! 3.10.x 遷移到 4.x 被視為一次小規模遷移。這是因為 Joomla 核心擴展將通過 Joomla! 後台 (管理員) 中的「更新」元件進行「一鍵式」升級。許多第三方擴展也支持一鍵式升級。有些則不支持。請逐一檢查每個擴展，並確定從 3.10 到 4.x 的升級路徑。如果您還沒有閱讀，請先閱讀 [[S:MyLanguage/Migration Step by Step Self Assessment|自我評估]] 和 [[S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|規劃 3.10 到 4.x 遷移]]，然後再按照以下步驟操作。

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:12:21Z

Shawnhy: Created page with "本文將一步步的將你的 Joomla 3.10 網站遷移到 4.x。由於實際的應用情境可能有數百種，我們將給你一個最基本的流程可以遵循。大量..."

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。

無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。}}

本文將一步步的將你的 Joomla 3.10 網站遷移到 4.x。由於實際的應用情境可能有數百種，我們將給你一個最基本的流程可以遵循。大量的第三方擴充套件可能會造成較為複雜的遷移流程，建議你可以聯絡第三方套件的作者詢問相關建議來幫助您遷移這些套件至最新版本。

== 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) of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. 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, read 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.
</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.)

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/2/zh-tw

2025-01-07T01:12:20Z

本文將一步步的將你的 Joomla 3.10 網站遷移到 4.x。由於實際的應用情境可能有數百種，我們將給你一個最基本的流程可以遵循。大量的第三方擴充套件可能會造成較為複雜的遷移流程，建議你可以聯絡第三方套件的作者詢問相關建議來幫助您遷移這些套件至最新版本。

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:12:02Z

Shawnhy: Created page with "無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。"

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。

無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。}}

The following are step-by-step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are different scenarios, this will give you the basic procedure to follow. 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 migration path.

== 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) of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. 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, read 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.
</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.)

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/59/zh-tw

2025-01-07T01:11:59Z

Shawnhy: Created page with "無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。"

無需急於一時。請確保所有擴充套件都已準備好支援 Joomla 4.x。Joomla 3.10.x 將支援至 2023 年 8 月 16 日。

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:11:50Z

Shawnhy: Created page with "本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。"

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 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.}}

The following are step-by-step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are different scenarios, this will give you the basic procedure to follow. 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 migration path.

== 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) of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. 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, read 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.
</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.)

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/1/zh-tw

2025-01-07T01:11:39Z

Shawnhy: Created page with "本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。"

本指南假設您從 Joomla 3.10.x 開始。如果您使用的是早期版本，請務必先升級到 Joomla 3.10，然後再升級到 Joomla 4。

Joomla 3.x to 4.x Step by Step Migration/zh-tw

2025-01-07T01:11:09Z

Shawnhy: Created page with "警告！"

<noinclude><languages /></noinclude>
{{version|3.10,4.x}}
{{warning|title=警告！|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.}}

The following are step-by-step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are different scenarios, this will give you the basic procedure to follow. 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 migration path.

== 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) of Joomla. Many third-party extensions are a one-click upgrade too. Some are not. 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, read 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.
</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.)

== Step by Step ==
=== Set Up a Development Location ===
# 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].
# 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:{{-}}[[File:J310-admin-extension-database-fix-en.png|border|800px]]
# Empty trash: Do you have any articles in the trash? Delete them (and any associated media if not in use elsewhere on the site). Articles (categories and menu items too) left in the trash can cause migration issues.
# Test.
# Backup again.

=== Assess Each Extension ===
In your [[S:MyLanguage/Planning_for_Mini-Migration_-_Joomla_3.10.x_to_4.x|planning]], you determined that 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. More details in [[Special:MyLanguage/:Pre-Update_Check|Pre-Update Check]].
# 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.{{-}}[[File:Migration_J3toJ4_update_channel-en.png|border|800px]]{{-}}
# 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.{{-}}[[File:J310-admin-update_to_4-pre_update_check-en.png|border|800px]]{{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
#;* PKG_JOOMLA
#;* Bluestork Administrator Template
#;* Beez_20
#;* Beez5
#;* Atomic
## When it comes to templates, uninstall all core Frontend or Backend templates except Protostar and Beez3 (site 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.
## 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.
# 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.
# '''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''' that 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.
# 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.{{-}}[[File:J310-admin-extension-manage-package-en.png|800px]]{{-}}{{note|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.}}
# 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.{{-}}{{note|'''NOTE!''' You will not be able to uninstall any template that is set as default. Select a Core supported template such as 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.|type=serious}}
# 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.
# 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.
# 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, look at them case by case. They will normally fall into one of the following scenarios:
#* The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
#* 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 simple to uninstall it in 3.10.x and then install it again in 4.x.
#* 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]]

==== 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/.

==== 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].

==== 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''.

=== 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:
# Go to {{rarr|System,Global Configuration,Server tab}} and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.{{-}} [[File:J310-system-global-config-server-tab-en.png|border|500px]]
# 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.{{-}}[[File:J310-component-joomla-update-select-support-en.png|border|500px]]
# 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.{{-}}[[File:J310-to-j4-dev-update-found-en.png|border|800px]]
# If the update is not showing up, go to {{rarr|Extensions,Update}} and select Clear Cache from the toolbar. Now the update to Joomla! 4 should show up.
# Cross your fingers, and make sure you have that backup available in case.
# Click the Install the Update button.
# 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 can take several minutes. There are over 12,000 files comprising 75 megabytes to be extracted. When the update is finished, you might be logged out of the Administrator. Sign in again, if necessary
# If all goes well, you will get to a totally new look to the Backend panel.{{-}}[[File:j4-administrator-overview-en.png|border|800px]]
# Go to {{rarr|System,Maintenance,Database}} and click ''Fix'' if any errors show.
# In {{rarr|System,Install,Discover}} see if there are any extensions to install. (There shouldn't be any!)
# 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]].
# Take a backup.
# Install your new template or other extensions if you have them to install. Back up often.
# Configure them. Back up often.
# Run a broken link checker and fix any broken links.
# Test everything. Back up often.
# If everything works as expected, turn Error Reporting back to System Default ({{rarr|System,Global Configuration,Server tab}}). Make sure to Save & Close.
# Be sure to read the post-installation messages.
=== 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.
# '''If''' you have made security changes to ''.htaccess'' file in the past, you may need to change a line (or lines) in it to update to Joomla 4. Please go to [https://docs.joomla.org/Htaccess_changes_after_joomla4.0.4 Htaccess changes after joomla4.0.4] to determine if you need to change your file.
# 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 and disabled the Frontend of the site.
# 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.

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].

== Suggested Tools ==
* [http://extensions.joomla.org/extensions/access-a-security/site-security/backup/1606 Akeeba Backup] is popular for backup and restore. See more [https://extensions.joomla.org/tags/backup/ backup tools].
==Related information==
[[Special:MyLanguage/:Pre-Update_Check|Pre-Update_Check]]
<noinclude>
[[Category:Migration{{#translation:}}]]
[[Category:Tutorials{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]</noinclude>

Translations:Joomla 3.x to 4.x Step by Step Migration/34/zh-tw

2025-01-07T01:11:08Z

Shawnhy: Created page with "警告！"

警告！

Planning for Mini-Migration - Joomla 3.10.x to 4.x/zh-tw

2025-01-04T06:45:51Z

Shawnhy: Created page with "#如果您重新設計或更改網站設計或導航，是否會有過時的頁面需要重定向？如果是，請記錄它們。電子表格有助於記錄需要更改的鏈..."

<noinclude><languages /></noinclude>
從Joomla 3.10.x 移植到 {{JVer|4.x}} 4.x 算做是迷你移轉或是小規模移轉。這代表說Joomla 核心擴充套件可以用「一鍵升級」的方式來完成，但是第三方擴充套件就不能一概而論，需要逐一檢視。

== 導覽 ==
移轉是重新整理大好時機，可以清除不需要的內容，並開發您網站需要的新功能或是元素。儘可能妥善地發展想法並規劃，讓成果發揮到極致。謹記規劃、規劃、再規劃。良好的規劃有助於執行。

<div class="mw-translate-fuzzy">
規劃的初步，先讓自己回答以下的問題，或是執行下列的任務。依據您網站的複雜程度，您可能會需要有更多需要在規劃階段考慮的項目。不幸的是，我們無法羅列出所有可能的情境。到時候我們會架設一個論壇，專門給 Joomla 4.x 移轉用，類似於之前我們為每一個主要版本 Joomla 所規劃的。
</div>

== 3.10.x 橋接 ==
{{JVer|3.10}}.x 版本是作為Joomla 3 以及 {{JVer|4}} 產品生命週期之前的橋樑。{{JVer|3.10}}.x 版本發佈主要是為了包含Joomla 4.x更改的 API 向後移植(backports) 開發分支，以協助並減輕社群夥伴們開發下一個主要版本用。
{{JVer|3.10}}.x 有個優異的新功能， Joomla! Update 元件，可以協助您檢查您的迷你搬移程序 : [[S:MyLanguage/Pre-Update Check|升級前檢查事項]]
一旦您的網站升級到3.10，更新前檢查可以協助您確認您的PHP以及SQL選項、設定、以及您使用中的擴充套件相容於Joomla 4.0，使用目標平台(targetplatform) 標記。更多細節請見 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 文件。

== 規劃要採取的行動 ==
下文假設您已經將您的 Joomla 3.x 網站升級到 3.10.x。這會讓您可以使用升級前檢查，有助於您執行規劃。
#確認您的網站正執行 3.10.x 版本
#確認您原本的網站目標。移轉是一個好機會，可以重新對焦您的網站目標，或是設定新的方向。
#您的伺服器是否符合Joomla! 4 的最低水準 [https://www.joomla.org/about-joomla/technical-requirements.html 技術需求] ？如果沒有，您會需要更換主機。再也沒有比這更好的機會做這件事情了。
#您將會使用什麼環境來開發？是在您的本機進行開發嗎？是在您的伺服器上設置子網域來進行開發嗎？是否有符合需求的伺服器/主機帳號？
<div class="mw-translate-fuzzy">
#列下正在使用的第三方擴充套件，包含元件、模組、插件、語言以及佈景主題。您可以使用 [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf 第三方擴充套件庫存清查] 或是複製/貼上到文件來當做參考，要用筆紙來手寫筆記也是可以的啦！可以的話順便記錄下，這些套件使用的頻率，重度使用、中度，沒什麼用，還是根本沒用過？
</div>
#確認您依賴的第三方擴充套件是否已準備好遷移到您要遷移的 Joomla 版本。在 Joomla 更新元件中選擇「Joomla 下一步」選項（一旦運行 Joomla 3.10.x），並檢查它們是否顯示與 Joomla 4 的相容性。不要運行更新到 4.x，只需在 Joomla 更新選項中選擇「Joomla 下一步」，以便顯示「更新前檢查器」。這將幫助您獲得正在使用的擴充套件及其相容性的摘要視圖。它不能替代仍然需要使用「擴充套件」→「管理」。有關更多信息，請參閱分步指南和 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 元件的文件。這只是為了準備哪些第三方擴充套件將保留、刪除或替換。
#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？
#檢視您的分類和文章。有沒有需要清理文章內容的地方？不需要的內容就不用移轉了。
#您的佈景主題如何呢？假如您從第三方購買佈景主題，他們是否有發佈相容 4.x 的版本？那你有想要繼續使用這個佈景主題嗎？開發者是否有發佈更新路徑？新版本是否具備響應式？您使用的是客製化佈景嗎？或是您使用的，是重度客製了第三方佈景主題？ Joomla 核心佈景主題'''Protostar 並不相容於 Joomla 4'''。經過移轉後他會消失。您可以考慮使用 Joomla 4.x 的核心佈景主題 Cassiopeia. For an expansion of Template based considerations，請見 [[S:MyLanguage/Template_Considerations_During_Migration|移轉時佈景主題需要考慮的項目]]。
#如果您要替換模板，是否需要任何新圖像？例如，如果您的當前網站具有白色背景，並且您的徽標或其他圖像為具有白色背景的 .jpg 檔案，那麼在具有米白色或彩色背景的新模板下，它們的外觀將不會很好。
#如果您重新設計或更改網站設計或導航，是否會有過時的頁面需要重定向？如果是，請記錄它們。電子表格有助於記錄需要更改的鏈接。

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|一步步將 Joomla 3.10 遷移（Migration）至 4.x|class=expand}}

<noinclude>
[[Category:Migration/zh-tw]]
[[Category:Tutorials/zh-tw]]
</noinclude>

Translations:Planning for Mini-Migration - Joomla 3.10.x to 4.x/21/zh-tw

2025-01-04T06:45:50Z

#如果您重新設計或更改網站設計或導航，是否會有過時的頁面需要重定向？如果是，請記錄它們。電子表格有助於記錄需要更改的鏈接。

Planning for Mini-Migration - Joomla 3.10.x to 4.x/zh-tw

2025-01-04T06:45:39Z

Shawnhy:

<noinclude><languages /></noinclude>
從Joomla 3.10.x 移植到 {{JVer|4.x}} 4.x 算做是迷你移轉或是小規模移轉。這代表說Joomla 核心擴充套件可以用「一鍵升級」的方式來完成，但是第三方擴充套件就不能一概而論，需要逐一檢視。

== 導覽 ==
移轉是重新整理大好時機，可以清除不需要的內容，並開發您網站需要的新功能或是元素。儘可能妥善地發展想法並規劃，讓成果發揮到極致。謹記規劃、規劃、再規劃。良好的規劃有助於執行。

<div class="mw-translate-fuzzy">
規劃的初步，先讓自己回答以下的問題，或是執行下列的任務。依據您網站的複雜程度，您可能會需要有更多需要在規劃階段考慮的項目。不幸的是，我們無法羅列出所有可能的情境。到時候我們會架設一個論壇，專門給 Joomla 4.x 移轉用，類似於之前我們為每一個主要版本 Joomla 所規劃的。
</div>

== 3.10.x 橋接 ==
{{JVer|3.10}}.x 版本是作為Joomla 3 以及 {{JVer|4}} 產品生命週期之前的橋樑。{{JVer|3.10}}.x 版本發佈主要是為了包含Joomla 4.x更改的 API 向後移植(backports) 開發分支，以協助並減輕社群夥伴們開發下一個主要版本用。
{{JVer|3.10}}.x 有個優異的新功能， Joomla! Update 元件，可以協助您檢查您的迷你搬移程序 : [[S:MyLanguage/Pre-Update Check|升級前檢查事項]]
一旦您的網站升級到3.10，更新前檢查可以協助您確認您的PHP以及SQL選項、設定、以及您使用中的擴充套件相容於Joomla 4.0，使用目標平台(targetplatform) 標記。更多細節請見 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 文件。

== 規劃要採取的行動 ==
下文假設您已經將您的 Joomla 3.x 網站升級到 3.10.x。這會讓您可以使用升級前檢查，有助於您執行規劃。
#確認您的網站正執行 3.10.x 版本
#確認您原本的網站目標。移轉是一個好機會，可以重新對焦您的網站目標，或是設定新的方向。
#您的伺服器是否符合Joomla! 4 的最低水準 [https://www.joomla.org/about-joomla/technical-requirements.html 技術需求] ？如果沒有，您會需要更換主機。再也沒有比這更好的機會做這件事情了。
#您將會使用什麼環境來開發？是在您的本機進行開發嗎？是在您的伺服器上設置子網域來進行開發嗎？是否有符合需求的伺服器/主機帳號？
<div class="mw-translate-fuzzy">
#列下正在使用的第三方擴充套件，包含元件、模組、插件、語言以及佈景主題。您可以使用 [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf 第三方擴充套件庫存清查] 或是複製/貼上到文件來當做參考，要用筆紙來手寫筆記也是可以的啦！可以的話順便記錄下，這些套件使用的頻率，重度使用、中度，沒什麼用，還是根本沒用過？
</div>
#確認您依賴的第三方擴充套件是否已準備好遷移到您要遷移的 Joomla 版本。在 Joomla 更新元件中選擇「Joomla 下一步」選項（一旦運行 Joomla 3.10.x），並檢查它們是否顯示與 Joomla 4 的相容性。不要運行更新到 4.x，只需在 Joomla 更新選項中選擇「Joomla 下一步」，以便顯示「更新前檢查器」。這將幫助您獲得正在使用的擴充套件及其相容性的摘要視圖。它不能替代仍然需要使用「擴充套件」→「管理」。有關更多信息，請參閱分步指南和 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 元件的文件。這只是為了準備哪些第三方擴充套件將保留、刪除或替換。
#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？
#檢視您的分類和文章。有沒有需要清理文章內容的地方？不需要的內容就不用移轉了。
#您的佈景主題如何呢？假如您從第三方購買佈景主題，他們是否有發佈相容 4.x 的版本？那你有想要繼續使用這個佈景主題嗎？開發者是否有發佈更新路徑？新版本是否具備響應式？您使用的是客製化佈景嗎？或是您使用的，是重度客製了第三方佈景主題？ Joomla 核心佈景主題'''Protostar 並不相容於 Joomla 4'''。經過移轉後他會消失。您可以考慮使用 Joomla 4.x 的核心佈景主題 Cassiopeia. For an expansion of Template based considerations，請見 [[S:MyLanguage/Template_Considerations_During_Migration|移轉時佈景主題需要考慮的項目]]。
#如果您要替換模板，是否需要任何新圖像？例如，如果您的當前網站具有白色背景，並且您的徽標或其他圖像為具有白色背景的 .jpg 檔案，那麼在具有米白色或彩色背景的新模板下，它們的外觀將不會很好。
#If you redesign or make changes to your site design or navigation, will you have obsolete pages that will require a redirect? If so, document them. A spreadsheet is helpful for documenting links that will need to change.

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|一步步將 Joomla 3.10 遷移（Migration）至 4.x|class=expand}}

<noinclude>
[[Category:Migration/zh-tw]]
[[Category:Tutorials/zh-tw]]
</noinclude>

Translations:Planning for Mini-Migration - Joomla 3.10.x to 4.x/20/zh-tw

2025-01-04T06:45:34Z

Shawnhy:

#如果您要替換模板，是否需要任何新圖像？例如，如果您的當前網站具有白色背景，並且您的徽標或其他圖像為具有白色背景的 .jpg 檔案，那麼在具有米白色或彩色背景的新模板下，它們的外觀將不會很好。

Planning for Mini-Migration - Joomla 3.10.x to 4.x/zh-tw

2025-01-04T06:45:01Z

Shawnhy: Created page with "#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？"

<noinclude><languages /></noinclude>
從Joomla 3.10.x 移植到 {{JVer|4.x}} 4.x 算做是迷你移轉或是小規模移轉。這代表說Joomla 核心擴充套件可以用「一鍵升級」的方式來完成，但是第三方擴充套件就不能一概而論，需要逐一檢視。

== 導覽 ==
移轉是重新整理大好時機，可以清除不需要的內容，並開發您網站需要的新功能或是元素。儘可能妥善地發展想法並規劃，讓成果發揮到極致。謹記規劃、規劃、再規劃。良好的規劃有助於執行。

<div class="mw-translate-fuzzy">
規劃的初步，先讓自己回答以下的問題，或是執行下列的任務。依據您網站的複雜程度，您可能會需要有更多需要在規劃階段考慮的項目。不幸的是，我們無法羅列出所有可能的情境。到時候我們會架設一個論壇，專門給 Joomla 4.x 移轉用，類似於之前我們為每一個主要版本 Joomla 所規劃的。
</div>

== 3.10.x 橋接 ==
{{JVer|3.10}}.x 版本是作為Joomla 3 以及 {{JVer|4}} 產品生命週期之前的橋樑。{{JVer|3.10}}.x 版本發佈主要是為了包含Joomla 4.x更改的 API 向後移植(backports) 開發分支，以協助並減輕社群夥伴們開發下一個主要版本用。
{{JVer|3.10}}.x 有個優異的新功能， Joomla! Update 元件，可以協助您檢查您的迷你搬移程序 : [[S:MyLanguage/Pre-Update Check|升級前檢查事項]]
一旦您的網站升級到3.10，更新前檢查可以協助您確認您的PHP以及SQL選項、設定、以及您使用中的擴充套件相容於Joomla 4.0，使用目標平台(targetplatform) 標記。更多細節請見 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 文件。

== 規劃要採取的行動 ==
下文假設您已經將您的 Joomla 3.x 網站升級到 3.10.x。這會讓您可以使用升級前檢查，有助於您執行規劃。
#確認您的網站正執行 3.10.x 版本
#確認您原本的網站目標。移轉是一個好機會，可以重新對焦您的網站目標，或是設定新的方向。
#您的伺服器是否符合Joomla! 4 的最低水準 [https://www.joomla.org/about-joomla/technical-requirements.html 技術需求] ？如果沒有，您會需要更換主機。再也沒有比這更好的機會做這件事情了。
#您將會使用什麼環境來開發？是在您的本機進行開發嗎？是在您的伺服器上設置子網域來進行開發嗎？是否有符合需求的伺服器/主機帳號？
<div class="mw-translate-fuzzy">
#列下正在使用的第三方擴充套件，包含元件、模組、插件、語言以及佈景主題。您可以使用 [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf 第三方擴充套件庫存清查] 或是複製/貼上到文件來當做參考，要用筆紙來手寫筆記也是可以的啦！可以的話順便記錄下，這些套件使用的頻率，重度使用、中度，沒什麼用，還是根本沒用過？
</div>
#確認您依賴的第三方擴充套件是否已準備好遷移到您要遷移的 Joomla 版本。在 Joomla 更新元件中選擇「Joomla 下一步」選項（一旦運行 Joomla 3.10.x），並檢查它們是否顯示與 Joomla 4 的相容性。不要運行更新到 4.x，只需在 Joomla 更新選項中選擇「Joomla 下一步」，以便顯示「更新前檢查器」。這將幫助您獲得正在使用的擴充套件及其相容性的摘要視圖。它不能替代仍然需要使用「擴充套件」→「管理」。有關更多信息，請參閱分步指南和 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 元件的文件。這只是為了準備哪些第三方擴充套件將保留、刪除或替換。
#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？
#檢視您的分類和文章。有沒有需要清理文章內容的地方？不需要的內容就不用移轉了。
#您的佈景主題如何呢？假如您從第三方購買佈景主題，他們是否有發佈相容 4.x 的版本？那你有想要繼續使用這個佈景主題嗎？開發者是否有發佈更新路徑？新版本是否具備響應式？您使用的是客製化佈景嗎？或是您使用的，是重度客製了第三方佈景主題？ Joomla 核心佈景主題'''Protostar 並不相容於 Joomla 4'''。經過移轉後他會消失。您可以考慮使用 Joomla 4.x 的核心佈景主題 Cassiopeia. For an expansion of Template based considerations，請見 [[S:MyLanguage/Template_Considerations_During_Migration|移轉時佈景主題需要考慮的項目]]。
#If you are changing out your template for a new one, will it require any new images? For example, if your current site has a white background and your logo or other images are .jpg images with a white background it won’t look very nice against a new template with an off-white or coloured background.
#If you redesign or make changes to your site design or navigation, will you have obsolete pages that will require a redirect? If so, document them. A spreadsheet is helpful for documenting links that will need to change.

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|一步步將 Joomla 3.10 遷移（Migration）至 4.x|class=expand}}

<noinclude>
[[Category:Migration/zh-tw]]
[[Category:Tutorials/zh-tw]]
</noinclude>

Translations:Planning for Mini-Migration - Joomla 3.10.x to 4.x/17/zh-tw

2025-01-04T06:45:00Z

Shawnhy: Created page with "#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？"

#評估您是否真的需要所有正在使用的擴充套件。Joomla 4 是否內建了可以取代第三方擴充套件的功能？

Planning for Mini-Migration - Joomla 3.10.x to 4.x/zh-tw

2025-01-04T06:44:19Z

Shawnhy: Created page with "#確認您依賴的第三方擴充套件是否已準備好遷移到您要遷移的 Joomla 版本。在 Joomla 更新元件中選擇「Joomla 下一步」選項（一旦運行..."

<noinclude><languages /></noinclude>
從Joomla 3.10.x 移植到 {{JVer|4.x}} 4.x 算做是迷你移轉或是小規模移轉。這代表說Joomla 核心擴充套件可以用「一鍵升級」的方式來完成，但是第三方擴充套件就不能一概而論，需要逐一檢視。

== 導覽 ==
移轉是重新整理大好時機，可以清除不需要的內容，並開發您網站需要的新功能或是元素。儘可能妥善地發展想法並規劃，讓成果發揮到極致。謹記規劃、規劃、再規劃。良好的規劃有助於執行。

<div class="mw-translate-fuzzy">
規劃的初步，先讓自己回答以下的問題，或是執行下列的任務。依據您網站的複雜程度，您可能會需要有更多需要在規劃階段考慮的項目。不幸的是，我們無法羅列出所有可能的情境。到時候我們會架設一個論壇，專門給 Joomla 4.x 移轉用，類似於之前我們為每一個主要版本 Joomla 所規劃的。
</div>

== 3.10.x 橋接 ==
{{JVer|3.10}}.x 版本是作為Joomla 3 以及 {{JVer|4}} 產品生命週期之前的橋樑。{{JVer|3.10}}.x 版本發佈主要是為了包含Joomla 4.x更改的 API 向後移植(backports) 開發分支，以協助並減輕社群夥伴們開發下一個主要版本用。
{{JVer|3.10}}.x 有個優異的新功能， Joomla! Update 元件，可以協助您檢查您的迷你搬移程序 : [[S:MyLanguage/Pre-Update Check|升級前檢查事項]]
一旦您的網站升級到3.10，更新前檢查可以協助您確認您的PHP以及SQL選項、設定、以及您使用中的擴充套件相容於Joomla 4.0，使用目標平台(targetplatform) 標記。更多細節請見 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 文件。

== 規劃要採取的行動 ==
下文假設您已經將您的 Joomla 3.x 網站升級到 3.10.x。這會讓您可以使用升級前檢查，有助於您執行規劃。
#確認您的網站正執行 3.10.x 版本
#確認您原本的網站目標。移轉是一個好機會，可以重新對焦您的網站目標，或是設定新的方向。
#您的伺服器是否符合Joomla! 4 的最低水準 [https://www.joomla.org/about-joomla/technical-requirements.html 技術需求] ？如果沒有，您會需要更換主機。再也沒有比這更好的機會做這件事情了。
#您將會使用什麼環境來開發？是在您的本機進行開發嗎？是在您的伺服器上設置子網域來進行開發嗎？是否有符合需求的伺服器/主機帳號？
<div class="mw-translate-fuzzy">
#列下正在使用的第三方擴充套件，包含元件、模組、插件、語言以及佈景主題。您可以使用 [https://docs.joomla.org/images/7/7a/3to4-Third-Party_Extension_Checklist_Inventory_Sheet.pdf 第三方擴充套件庫存清查] 或是複製/貼上到文件來當做參考，要用筆紙來手寫筆記也是可以的啦！可以的話順便記錄下，這些套件使用的頻率，重度使用、中度，沒什麼用，還是根本沒用過？
</div>
#確認您依賴的第三方擴充套件是否已準備好遷移到您要遷移的 Joomla 版本。在 Joomla 更新元件中選擇「Joomla 下一步」選項（一旦運行 Joomla 3.10.x），並檢查它們是否顯示與 Joomla 4 的相容性。不要運行更新到 4.x，只需在 Joomla 更新選項中選擇「Joomla 下一步」，以便顯示「更新前檢查器」。這將幫助您獲得正在使用的擴充套件及其相容性的摘要視圖。它不能替代仍然需要使用「擴充套件」→「管理」。有關更多信息，請參閱分步指南和 [[S:MyLanguage/Pre-Update Check|Pre-Update Check]] 元件的文件。這只是為了準備哪些第三方擴充套件將保留、刪除或替換。
#Determine if you really need all the extensions you are using. Could it be that Joomla 4 has built in features that could eliminate the use of a third-party extension?
#檢視您的分類和文章。有沒有需要清理文章內容的地方？不需要的內容就不用移轉了。
#您的佈景主題如何呢？假如您從第三方購買佈景主題，他們是否有發佈相容 4.x 的版本？那你有想要繼續使用這個佈景主題嗎？開發者是否有發佈更新路徑？新版本是否具備響應式？您使用的是客製化佈景嗎？或是您使用的，是重度客製了第三方佈景主題？ Joomla 核心佈景主題'''Protostar 並不相容於 Joomla 4'''。經過移轉後他會消失。您可以考慮使用 Joomla 4.x 的核心佈景主題 Cassiopeia. For an expansion of Template based considerations，請見 [[S:MyLanguage/Template_Considerations_During_Migration|移轉時佈景主題需要考慮的項目]]。
#If you are changing out your template for a new one, will it require any new images? For example, if your current site has a white background and your logo or other images are .jpg images with a white background it won’t look very nice against a new template with an off-white or coloured background.
#If you redesign or make changes to your site design or navigation, will you have obsolete pages that will require a redirect? If so, document them. A spreadsheet is helpful for documenting links that will need to change.

{{Basic button|S:MyLanguage/Joomla 3.x to 4.x Step by Step Migration|一步步將 Joomla 3.10 遷移（Migration）至 4.x|class=expand}}

<noinclude>
[[Category:Migration/zh-tw]]
[[Category:Tutorials/zh-tw]]
</noinclude>

Planning for Migration/zh-hant

2025-01-04T06:37:44Z

Shawnhy: Created page with "一些簡短的澄清"

<noinclude><languages /></noinclude>
<div class="mw-translate-fuzzy">
無論規模大或小，搬遷作業的第一步就是計畫，假如計畫要花上一週或是四週，那麼也得花。計畫會讓整個搬遷過程更順利。
</div>

一些簡短的澄清
<div class="mw-translate-fuzzy">
=== Joomla 1.5 到 3.10.x 或 4.x 是大更新 ===
Joomla核心底層結構有大幅度的改變，所有的資料庫，包含核心內容、第三方擴充套件以及佈景主題都需要從 1.5 搬遷到 4.x.
</div>
<div class="mw-translate-fuzzy">
=== Joomla 2.5 到 3.10.x；以及 3.10.x 到 Joomla 4.x 算是小升級 (或是稱作迷你升級) ===
迷你升級的意思是說，Joomla 核心擴充套件 (文章、選單、模組、分類、Weblinks、聯絡人、新聞聯播、搜尋)都可以執行一鍵升級，所有的第三方擴充套件，包含佈景主題則需要逐一檢視。
</div>

=== Joomla 2.5 to 4.x is Two Minor Migrations (or two mini-migrations) ===
If you are currently running Joomla 2.5 and want to migrate to Joomla 4.x, you will be doing two mini-migrations. The first will be from 2.5 to 3.10.x. The second will be 3.10.x to 4.x. See [[Planning for Mini-Migration - Joomla 2.5 to 4.x]] for the links and the best course of action.

=== Joomla 4.4.x to 5.x is an Upgrade, not a migration ===
Thankfully, Joomla 4.4.x to 5.x is an upgrade, not a migration. Head over to the [[Joomla_4.4.x_to_5.x_Planning_and_Upgrade_Step_by_Step|Joomla 4.4.x to 5.x Planning and Upgrade Step by Step]] documentation.

<div class="mw-translate-fuzzy">
=== 需求 ===
您的伺服器必須符合 [https://downloads.joomla.org/technical-requirements Technical Requirements] Joomla 3 以及/或是 Joomla 4 ，以在相同伺服器上執行搬遷作業。
</div>
<div class="mw-translate-fuzzy">
=== 第三方擴充套件 ===
Joomla 核心算是容易的部份，第三方套件，包含佈景主題，在搬遷作業中是充滿困難性的部分。
</div>
<div class="mw-translate-fuzzy">
=== 最後的想法和考量 ===
不論是大型搬遷或是小型搬遷，都有一些需要考量的評估項目。如果您已經執行過從1.5到2.5 的搬遷，以及/或是 2.5 到 3.10.x ，那你幹得真好，因為要從2.5 到 3.10sx 以及從3.10x 到 4，要容易得多。如果您正在執行1.5的版本，打算要搬遷到 4，請提起勇氣，因為你一躍跳過中間兩個版本。一個適當的計畫可以讓您正常執行Joomla 4，並將意外狀況縮小到最低程度。
</div>

<div class="row">
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 3.10.x to 4.x|Planning for Mini-Migration - Joomla 3.10.x to 4.x|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning for Mini-Migration - Joomla 2.5 to 4.x|小搬遷計畫 - Joomla 2.5 到 4.x|class=expand}}</div>
<div class="large-4 columns">{{Basic button|S:MyLanguage/Planning Migration - Joomla 1.5 to 4|搬遷計畫 - Joomla 1.5 到 4.x|class=expand success}}</div>
</div>

<div class="mw-translate-fuzzy">
[[Category:Migration/zh-tw]]
[[Category:Tutorials/zh-tw]]
</div>

Translations:Planning for Migration/13/zh-hant

2025-01-04T06:37:43Z

Shawnhy: Created page with "一些簡短的澄清"

一些簡短的澄清

Selecting data using JDatabase/zh-tw

2023-11-02T03:35:23Z

Shawnhy: Created page with "==在查詢語法中使用 OR =="

Translations:Selecting data using JDatabase/141/zh-tw

2023-11-02T03:35:23Z

Shawnhy: Created page with "要在查詢語法中，使用多重的 WHERE 叢集，它們要被當成 AND 看待"

要在查詢語法中，使用多重的 WHERE 叢集，它們要被當成 AND 看待

Translations:Selecting data using JDatabase/140/zh-tw

2023-11-02T03:35:21Z

Shawnhy: Created page with "==在查詢語法中使用 OR =="

==在查詢語法中使用 OR ==

Selecting data using JDatabase/zh-tw

2023-11-02T03:16:37Z

Shawnhy: Created page with "請注意，很多網路上的範例會使用 <code>$db->query()</code> ，而非<code>$db->execute()</code>。前者是使用在 Joomla 1.5 以及 2.5 的舊method，在 Jo..."

Translations:Selecting data using JDatabase/1/zh-tw

2023-11-02T03:16:34Z

請注意，很多網路上的範例會使用 <code>$db->query()</code> ，而非<code>$db->execute()</code>。前者是使用在 Joomla 1.5 以及 2.5 的舊method，在 Joomla 3.0+會回傳 deprecated notice。

Secure coding guidelines/zh-tw

2023-02-09T03:03:08Z

Shawnhy:

<noinclude><languages /></noinclude>
Joomla 包含了很多特色，可以協助在其上開發應用和擴充套件時的安全性。您應該要盡可能地一直使用這些特色功能，因為它們是已經被開發社群嘗試過、檢查過；而且可能還會在未來需要被更新。以下是關於使用 Joomla API最佳實踐的描述，確保您的擴充套件是盡可能安全的。

==使用 request 來獲取資料==
{{JVer|3.x}} 從Joomla 3.0 版本開始，應該停止使用<code>[https://api.joomla.org/cms-3/classes/JRequest.html JRequest]</code>，改成使用<code>[[Retrieving_request_data_using_JInput|JInput]]</code>

所有來自使用者發起的輸入都必須要被視為具有潛在危險的，並且必須要在使用前先做過清理。您應該總是使用 Joomla [[Retrieving_request_data_using_JInput|JInput]] class 來從請求擷取資料，而不是赤裸裸的 <code>$_GET</code>, <code>$_POST</code> 或是 <code>$_REQUEST</code> 變項，因為 <code> JInput </code> method 預設會過濾用戶的輸入。<code> JInput </code> 會處理所有方面的用戶請求，讓它獨立於使用的 request method。<code> JInput </code> 也可以用於獲取 cookie資料，甚至是伺服器和環境變數。然而，非常重要的是，使用正確的[[Retrieving_request_data_using_JInput|JInput]] method，來確保最大的安全性。使用<code> [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code> method ，輔以預設參數是十分容易的，儘管在很多案例中，還可以對使用者的輸入套用更加嚴格的規範。

非常重要的是，要了解 <code> [[Retrieving_request_data_using_JInput|JInput]] </code>方法並非 SQL-aware，而且需要額外作業來防範 SQL Injection。如果沒有在呼叫 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] 當中指定預設，並沒有預設的值會被取回。假如沒有指定預設的話，而且沒有在請求變數當中顯示 argument，就會取回未定義(undefined)。

使用 [[Retrieving_request_data_using_JInput|JInput]] 也可以消除您需要留意 <code>magic_quotes_gpc </code> 設定的麻煩。無論您的 <code>magic_quotes_gpc </code> 有沒有打開，[[Retrieving_request_data_using_JInput|JInput]] 都恪盡職守。請查閱[http://php.net/manual/en/security.magicquotes.php security.magicquotes.php] 以獲得更多資訊。

考慮到用戶的輸入內容，您需要思考關於您要獲取的資料類型，並套用最嚴謹的 <code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput]] </code>類型，依照每個不同的案例來應用。特定地說，避免使用像是<code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code>的懶惰蟲手段，因為它會取回陣列，當中可能包含您不想要顯示的。儘管這些內容會被清理，它們經常在某些個別 argument 中，被額外的過濾器找到。例如，get 方法會把所有的 arguments 當成字串(string) 來處理，然而它們是可以被限制為整數之類的。

JInput 方法中頭三個參數 (parameter) 是相同的，只有頭一項 parameter 是強制的。一般而言，格式是
<source lang="php">
JFactory::getApplication->input-><data-source>->get<type>( <name>, <default> )
</source>
其中

{| class="wikitable" border="1"
| <type> || 可以獲取的資料類型 (在底下查可以使用的類型)。
|-
| <name> || 要獲取的變數(variable)的名稱(name) (例如，在 URL 當中 argument 的名稱name).
|-
| <default> || 預設的值
|-
| <data-source> || 指定變數要從何處來獲取 (見底下).
|}

支援底下的 <data-source> 值:

{| class="wikitable" border="1"
| get || 由 URL 中 query 的部分送出的資料
|-
| post || 從欄位 (field) 送出的資料。
|-
| method || The same as either GET or POST depending on how the request was made.
|-
| cookie || 在 cookies 中送出的資料。
|-
| request || 所有的 GET, POST 以及 COOKIE 合併資料。這是預設的。
|-
| files || 關於 POST request 檔案上傳的資訊
|-
| env || 環境變數 (platform-specific)
|-
| server || 網站伺服器變數 (platform-specific)
|}

請注意預設會使用 REQUEST，其中包含了 cookie 資料。

以下的段落深入解釋每種資料類型。

===整數===
以下會接受整數。整數型可以包含一個前導的負號(<code> - </code>)，但正號(<code> + </code>)是不允許的。
<source lang="php">
$integer = JFactory::getApplication->input->getInt( 'id' );
</source>
會從 request 回傳 "id" argument 的值from the request (預設包含所有的 GET, POST and COOKIE data)。預設值是零
<source lang="php">
$integer = JFactory::getApplication->input->cookie->getInt( 'myId', 12 );
</source>
會從 cookie 回傳 "myId" 變數的值，預設值是12

===浮點數===
浮點數型可以包含一個前導的負號(<code> - </code>)，但正號(<code> + </code>)是不允許的。如果數字包含了千分位號，那千分位號前頭必須要至少有一個數字。例如，
<source lang="php">
$float = JFactory::getApplication->input->getFloat( 'price' );
</source>
會回傳請求的 'price' 參數，預設的值是 "0.0"
<source lang="php">
$float = JFactory::getApplication->input->post->getFloat( 'total', 100.00 );
</source>
會從 POST (而非 GET) 請求回傳 'total' 值。預設的值是 100.00

===布林值===
所有「非零」的值都會被視為 'true'。零是 'false'
<source lang="php">
$boolean = JFactory::getApplication->input->getBool( 'show' );
</source>
如果請求 'show' 參數的值是零，上面的程式會回傳 false；而如果是其他的參數，會回傳 1 (true)。預設的值是 false. 請注意任何字串都會造成回傳 true，所以使用URL包含"?show=false" 來呼叫上述的程式，事實上會回傳 true!
<source lang="php">
$boolean = JFactory::getApplication->input->get->getBool( 'hide', true );
</source>
會從 GET 請求 (而非 POST) 回傳 'hide' 參數的值。預設的值是 true.

===Word===
Word 的定義是指使用A到Z組成的字段。在 word 中使用部分小寫的字母是允許的。
<source lang="php">
$word = JFactory::getApplication->input->cookie->getWord( 'search-word' );
</source>
會獲取由request送出的 'search-word' 的值。預設是空白字串。
<source lang="php">
$word = JFactory::getApplication->input->cookie->getWord( 'keyword', '' );
</source>
會獲取 cookie 中 'keyword' 變數的值。預設是空白字串。

===指令(Command)===
指令(Command) 類似 word 但是允許的字元是更廣泛的。允許的字元包含：all alphanumeric characters, dot, dash (hyphen) and underscore.
<source lang="php">
$command = JFactory::getApplication->input->getCmd( 'option' );
</source>
會獲取由 request 請求回傳的 "option" 值。預設值是空字串。
<source lang="php">
$command = JFactory::getApplication->input->post->getCmd( 'controller', 'view' );
</source>
會獲取由 POST 請求(而非 GET) "controller" 參數的值。預設值是 'view'

===字串===
字串型允許更廣泛的字元輸入 It also takes an optional fourth argument specifying some additional mask options. 請查看 [[#Filter options]] for information on the available masks.
<source lang="php">
$string = JFactory::getApplication->input->getString( 'description' );
</source>
會獲取從 request 回傳 "description" 參數的值。預設的值是空字串。輸入的值會清除前後的空白，以及 HTML 標籤。
<source lang="php">
$string = JFactory::getApplication->input->getString( 'text', '' );
</source>
會獲取從 request 回傳 "text" 參數的值。預設的值是空字串。
<source lang="php">
$string = JFactory::getApplication->input->getString( 'template', '<html />' );
</source>
會從 request 回傳"template"參數的值。預設的值是 '<html />'.

===JSON 字串===
<source lang="php">
$json = JFactory::getApplication->input->json->get( 'var_name' );
</source>

===通用及其他資料類型===
如果上述的 methods 您要使用的，還有一些額外的過濾類型，可以直接呼叫 <code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code> method 。語法是：
<source lang="php">
JFactory::getApplication->input->get( <name>, <default>, <type> );
</source>
其中的：

{| class="wikitable" border="1"
| <name> || the name of the variable to be retrieved (for example, the name of an argument in a URL).
|-
| <default> || 預設值。如果沒有在[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] 呼叫中指定預設值，則沒有預設值會被回傳。
|-
| <type> || 指定的預期資料類型 (見底下)
|}

The first three arguments are the same as for the more specific methods described earlier. Only the first argument is mandatory.

允許的 <type> 值，大小寫有分別，如底下：

{| class="wikitable" border="1"
| INT, INTEGER || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getInt]].
|-
| UINT || Get an unsigned integer. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getUint]].
|-
| FLOAT, DOUBLE || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getFloat]].
|-
| BOOL, BOOLEAN || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getBool]].
|-
| WORD || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getWord]].
|-
| ALNUM || 僅允許 alphanumeric 字元 (a-z, A-Z, 0-9). 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getAlnum]].
|-
| CMD || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getCmd]].
|-
| BASE64 || 僅允許可以被呈現於base64編碼的字元 (也就是 a-z, A-Z, 0-9, /, + 和 =)。相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getBase64]].
|-
| STRING || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getString]].
|-
| ARRAY || Source is not filtered but is cast to array type. When using this type you should use JFilterInput directly to filter the values in your data array.
|-
| HTML || 經過安全處理的字串，相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getHtml]].
|-
| PATH || Valid pathname regex that filters out common attacks. 例如，any path beginning with a "/" will return an empty string. Simliarly, any path containing "/./" or "/../" will return an empty string. Dots within filenames are okay though. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getPath]].
|-
| USERNAME || 移除 control 字元 (0x00 - 0x1F), 0x7F, <, >, ", ', % and &. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getUsername]].
|}

===過濾選項===
所有的輸入值都應該要用<code> JFilterInput->clean </code>來過濾

過濾值矩陣
<source lang="php">
$data = JFactory::getApplication()->input->post->get('data', array(), 'array');
$filter = JFilterInput::getInstance();

foreach ($data as $value)
{
$array[] = $filter->clean($value, 'string');
}
</source>
要看更多的過濾類型，請看 [https://github.com/joomla/joomla-cms/blob/master/libraries/joomla/filter/input.php#L115 JFilterInput source].

底下列出的選項是過時的 [[JRequest]] library.
允許的 <options> 值羅列如下 (預設並不會套用任何一項)：

{| class="wikitable" border="1"
| JREQUEST_NOTRIM || 並不會移除字串前後的空白
|-
| JREQUEST_ALLOWRAW || 不會套用任何的過濾條件，請絕對謹慎使用！
|-
| JREQUEST_ALLOWHTML || 不會移除字串中的 HTML
|}

Masks can be combined by logically OR'ing them. 如果沒有指定過濾選項，那麼預設會移除空白，並且HTML會被移除。

===上傳檔案===
關於檔案上傳的安全性，網站伺服器已經提供了不錯的想法，然而，還是需要有些額外的手續，來確保檔案名稱以及路徑不會被濫用。一個簡化過的請求上傳檔案表單看起來像這樣：
<source lang="html4strict">
<form action="index.php?option=com_mycomponent/form_handler.php" method="post" enctype="multipart/form-data">
<input type="file" name="Filedata" />
<input type="submit" />
</form>
</source>
按下送出按鈕後，瀏覽器將會使用POST請求來上傳檔案，呼叫 Joomla! 的 <code> "components/com_mycomponent/form_handler.php" </code> 來傳送控制項目這包含了像是以下的程式碼。變項 $somepath 必須要被設定到路徑中，讓網頁伺服器有權限可以建立檔案。
<source lang="php">
// Check to ensure this file is included in Joomla!
defined('_JEXEC') or die( 'Restricted access' );

// 從 request 獲得檔案資料矩陣
$file = JFactory::getApplication->input->get( 'Filedata', '', 'files', 'array' );

// 讓檔案名稱安全無害
jimport('joomla.filesystem.file');
$file['name'] = JFile::makeSafe($file['name']);

// 將上傳的檔案移動到常駐位置
if (isset( $file['name'] )) {

// Make sure that the full file path is safe.
$filepath = JPath::clean( $somepath.'/'.strtolower( $file['name'] ) );

// 移動上傳的檔案
JFile::upload( $file['tmp_name'], $filepath );
}
</source>

===Saving a request variable into user state===
Because setting a user state variable from a variable in the request is such a common operation, there is an API method to make the task easier. This is generally safe to use because it calls [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] to obtain the input from the request, but remember that none of the input filtering calls will protect against SQL injection attempts.
<source lang="php">
$app = JFactory::getApplication();
$app->getUserStateFromRequest( <key>, <name>, <default>, <type> );
</source>
where
{| class="wikitable" border="1"
| <key> || the name of the variable in the user state.
|-
| <name> || the name of the request variable (same as the first argument of a [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] call).
|-
| <default> || the default value to be assigned to the user state variable if the request variable is absent. The default is null.
|-
| <type> || 預期的變數型別
|}

例如，getting an integer variable called 'id' from the request with a default value of 0, then saving it into a session variable called 'myid' can be done like this:
<source lang="php">
$app = JFactory::getApplication();
$app->getUserStateFromRequest( 'myid', 'id, 0, 'int' );
</source>
instead of something like this:
<source lang="php">
$app = JFactory::getApplication();
$app->setUserState( 'myid', $app->input->getInt( 'id', 0 ) );
</source>

==慎重結構 SQL queries==
SQL Injection 是常見的網站攻擊類型之一，攻擊者會對輸入值管控不良的資料庫，修改資料庫請求的語法來破壞資料庫。攻擊結果會造成資料庫內容被破壞，或是隱私資料外洩。因此，確保SQL語法結構被送出時，能夠被正確地使用 escape 以及 quote 過濾，是很重要的，這樣惡意輸入才不會構成惡意的 SQL 語法。您將不能倚靠[[Retrieving_request_data_using_JInput|JInput]] 方法來完成這件事，因為它並非 SQL-aware。

===強化整數以及其他數字值的安全===
在 MySQL 資料庫中，數字欄位不應該被 quote，因此，將它們做類型轉換是很重要的。若是沒有這樣處理，您的程式碼會暴露於風險之下，讓駭客在 SQL 資料中存放字串。

依照其類型，數值類型看起來像這樣：
<source lang="php">
// For SQL data types: INT, INTEGER, TINYINT, SMALLINT, MEDIUMINT, BIGINT, YEAR
$query = 'SELECT * FROM #__table WHERE `id`=' . (int) $id;

// For SQL data types: FLOAT, DOUBLE
$query = 'SELECT * FROM #__table WHERE `id`=' . (float) $id;
</source>
總是對使用 <cdoe> JInput->getInt</code>獲得的變數進行整數型別轉換，絕對是個好習慣。關於 SQL 注入攻擊更進一步的資訊，可以在 http://php.net/manual/en/security.database.sql-injection.php 以及 [[Retrieving_request_data_using_JInput#Getting_Values]] 找到。

===強化字串安全===
在一個遵循規範的範例中，會假定<code> $db </code> 是joomla!資料庫物件的 instance 。這可以確保從[https://docs.joomla.org/Using_the_JFactory_class JFactory] 取用，使用
<source lang="php">
$db = JFactory::getDBO();
</source>
字串在使用於 SQL 語法之前，一定要先進行清理。這事實上是相當容易的，因為 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_quote JDatabase->quote] method 已經為您清理所有的可疑內容了。您也可以直接使用 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_escape JDatabase->escape] method。相當於底下的語法：
<source lang="php">
$query = 'SELECT * FROM #__table WHERE `field` = ' . $db->quote( $db->escape( $field ), false );

$query = 'SELECT * FROM #__table WHERE `field` = ' . $db->quote( $field );
</source>

===強化搜尋安全===
請特別留意使用 LIKE 的句法，它會包含 % 萬用字元(wildcard character)做出特別的逃逸，為了要避免可能發生的DoS阻斷攻擊。LIKE 句法可以如此來處理：
<source lang="php">
// 用逃逸user-supplied string來結構搜尋字詞，並且如果有必要的話，手動加入 % 萬用字元.
$search = '%' . $db->escape( $search, true ) . '%';

// Construct the SQL query, being careful to suppress the default behaviour of Quote so as to prevent double-escaping.
$query = 'SELECT * FROM #__table WHERE `field` LIKE ' . $db->quote( $search, false );
</source>

===強固資料安全===
If data is to be entered into a datetime column then you can use the Joomla API to ensure a valid date format:
<source lang="php">
$date = JFactory::getDate( $mydate );
$query = 'UPDATE #__table SET `date` = ' . $db->quote( $date->toMySQL(), false );
</source>
Note that it is necessary to suppress database escaping as legitimate dates may contain characters that should not be escaped.

===強固欄位名稱(field name)安全===
In the comparatively rare case where a field name is a variable, that should also be quoted using an API call:
<source lang="php">
$query = 'SELECT * FROM #__table WHERE ' . $db->quoteName( $field->name ) . '=' . $db->quote( $field->value );
</source>

===強固整數陣列安全===
When you have an array of ids, typically used for IN() queries, you have to sanitise it also with <code> JArrayHelper::toInteger($cid); </code> before imploding:

<source lang="php">
...
$catId = JArrayHelper::toInteger($catId);
$query->where($db->quoteName('x.category_id') . ' IN (' . implode(',', $catId) . ')');
</source>

=== Quote 以及 QuoteName 的短別名===
Shorter alternatives to the quote methods may also be used。的語法是相同意思的：
<source lang="php">
$query = 'SELECT * FROM #__table WHERE ' . $db->quoteName( $field->name ) . '=' . $db->quote( $field->value );
$query = 'SELECT * FROM #__table WHERE ' . $db->qn( $field->name ) . '=' . $db->q( $field->value );
</source>

==強固表單安全==
Apart from cleaning input variables as described above, you can also implement a simple technique which makes it more difficult for a cross-site request forgery attack (CSRF) to succeed. This involves adding a randomly-generated unique token to the form which is checked against a copy of the token held in the user's session. By checking that the submitted token matches the one contained in the stored session, it is possible to tie a rendered form to the request variables presented.

In POST forms you should add a hidden token field using:
<source lang="php">
echo JHTML::_( 'form.token' );
</source>
This outputs the token as a hidden form field looking like this:
<source lang="html4strict">
<input type="hidden" name="8cb24ae69ffd7828ccecbcf06056e6fc" value="1" />
</source>
and places a copy of the token into the user's session, for later checking.

If you need to add the token to a URL rather than a form then you can use something like this:
<source lang="php">
echo JRoute::_( 'index.php?option=com_mycomponent&' . JSession::getFormToken() . '=1' );
</source>

In the most common scenario, you will want to check the token following a POST to the form handler. This can be done by adding this line of code to form handler:
<source lang="php">
JSession::checkToken() or die( JText::_( 'Invalid Token' ) );
</source>
If you need to pass the token in a GET request then you can check it like this:
<source lang="php">
JSession::checkToken( 'get' ) or die( JText::_( 'Invalid Token' ) );
</source>

In both cases the code will die if the token is omitted from the request, or the submitted token does not match the session token. If the token is correct but has expired, then [[JSession/checkToken|JSession::checkToken]] will automatically redirect to the site front page.

==清理檔案的系統路徑==
If there is any possibility that a filesystem path might be constructed using data that originated from user input, then the path must be cleaned and checked before being used. 只要像這樣做，很容易就可以：
<source lang="php">
JPath::check( $path );
</source>
This will raise an error and terminate Joomla if the path contains a ".." or leads to a location outside the Joomla root directory. If you want to deal with the error yourself without terminating the application, then you can use code like this:
<source lang="php">
$path = JPath::clean( $path );
if (strpos( $path, JPath::clean( JPATH_ROOT ) ) !== 0) {
// Handle the error here.
}
</source>
<code> [[JPath:clean]] </code> method 也可以使用於您的程式碼。它僅僅是移除首尾的空白字元，以 double slash (<code>--</code>) 代替；以標準的路徑分隔符號代替double slashes(<code>//</code>)

==清理檔案路徑檔案名稱==
As with filesystem paths, if there is any possibility that a file name might be constructed using user-originated data, then the file name must be cleaned and checked before use. 像這樣做就可以完成：
<source lang="php">
jimport('joomla.filesystem.file');
$clean = JFile::makeSafe( $unclean );
</source>
這個 method 會移除內容中的"." 或是多個"." 字元，以及其他非 alphabetic, numeric 或是dot, dash 或是 underscore 字元。如果字串起頭是"."，也會被移除。
[[Category:Development/zh-tw]][[Category:Security/zh-tw]]

Translations:Secure coding guidelines/45/zh-tw

2023-02-09T03:02:57Z

Shawnhy:

===強化搜尋安全===
請特別留意使用 LIKE 的句法，它會包含 % 萬用字元(wildcard character)做出特別的逃逸，為了要避免可能發生的DoS阻斷攻擊。LIKE 句法可以如此來處理：
<source lang="php">
// 用逃逸user-supplied string來結構搜尋字詞，並且如果有必要的話，手動加入 % 萬用字元.
$search = '%' . $db->escape( $search, true ) . '%';

Secure coding guidelines/zh-tw

2023-02-09T02:57:09Z

Shawnhy:

<noinclude><languages /></noinclude>
Joomla 包含了很多特色，可以協助在其上開發應用和擴充套件時的安全性。您應該要盡可能地一直使用這些特色功能，因為它們是已經被開發社群嘗試過、檢查過；而且可能還會在未來需要被更新。以下是關於使用 Joomla API最佳實踐的描述，確保您的擴充套件是盡可能安全的。

==使用 request 來獲取資料==
{{JVer|3.x}} 從Joomla 3.0 版本開始，應該停止使用<code>[https://api.joomla.org/cms-3/classes/JRequest.html JRequest]</code>，改成使用<code>[[Retrieving_request_data_using_JInput|JInput]]</code>

所有來自使用者發起的輸入都必須要被視為具有潛在危險的，並且必須要在使用前先做過清理。您應該總是使用 Joomla [[Retrieving_request_data_using_JInput|JInput]] class 來從請求擷取資料，而不是赤裸裸的 <code>$_GET</code>, <code>$_POST</code> 或是 <code>$_REQUEST</code> 變項，因為 <code> JInput </code> method 預設會過濾用戶的輸入。<code> JInput </code> 會處理所有方面的用戶請求，讓它獨立於使用的 request method。<code> JInput </code> 也可以用於獲取 cookie資料，甚至是伺服器和環境變數。然而，非常重要的是，使用正確的[[Retrieving_request_data_using_JInput|JInput]] method，來確保最大的安全性。使用<code> [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code> method ，輔以預設參數是十分容易的，儘管在很多案例中，還可以對使用者的輸入套用更加嚴格的規範。

非常重要的是，要了解 <code> [[Retrieving_request_data_using_JInput|JInput]] </code>方法並非 SQL-aware，而且需要額外作業來防範 SQL Injection。如果沒有在呼叫 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] 當中指定預設，並沒有預設的值會被取回。假如沒有指定預設的話，而且沒有在請求變數當中顯示 argument，就會取回未定義(undefined)。

使用 [[Retrieving_request_data_using_JInput|JInput]] 也可以消除您需要留意 <code>magic_quotes_gpc </code> 設定的麻煩。無論您的 <code>magic_quotes_gpc </code> 有沒有打開，[[Retrieving_request_data_using_JInput|JInput]] 都恪盡職守。請查閱[http://php.net/manual/en/security.magicquotes.php security.magicquotes.php] 以獲得更多資訊。

考慮到用戶的輸入內容，您需要思考關於您要獲取的資料類型，並套用最嚴謹的 <code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput]] </code>類型，依照每個不同的案例來應用。特定地說，避免使用像是<code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code>的懶惰蟲手段，因為它會取回陣列，當中可能包含您不想要顯示的。儘管這些內容會被清理，它們經常在某些個別 argument 中，被額外的過濾器找到。例如，get 方法會把所有的 arguments 當成字串(string) 來處理，然而它們是可以被限制為整數之類的。

JInput 方法中頭三個參數 (parameter) 是相同的，只有頭一項 parameter 是強制的。一般而言，格式是
<source lang="php">
JFactory::getApplication->input-><data-source>->get<type>( <name>, <default> )
</source>
其中

{| class="wikitable" border="1"
| <type> || 可以獲取的資料類型 (在底下查可以使用的類型)。
|-
| <name> || 要獲取的變數(variable)的名稱(name) (例如，在 URL 當中 argument 的名稱name).
|-
| <default> || 預設的值
|-
| <data-source> || 指定變數要從何處來獲取 (見底下).
|}

支援底下的 <data-source> 值:

{| class="wikitable" border="1"
| get || 由 URL 中 query 的部分送出的資料
|-
| post || 從欄位 (field) 送出的資料。
|-
| method || The same as either GET or POST depending on how the request was made.
|-
| cookie || 在 cookies 中送出的資料。
|-
| request || 所有的 GET, POST 以及 COOKIE 合併資料。這是預設的。
|-
| files || 關於 POST request 檔案上傳的資訊
|-
| env || 環境變數 (platform-specific)
|-
| server || 網站伺服器變數 (platform-specific)
|}

請注意預設會使用 REQUEST，其中包含了 cookie 資料。

以下的段落深入解釋每種資料類型。

===整數===
以下會接受整數。整數型可以包含一個前導的負號(<code> - </code>)，但正號(<code> + </code>)是不允許的。
<source lang="php">
$integer = JFactory::getApplication->input->getInt( 'id' );
</source>
會從 request 回傳 "id" argument 的值from the request (預設包含所有的 GET, POST and COOKIE data)。預設值是零
<source lang="php">
$integer = JFactory::getApplication->input->cookie->getInt( 'myId', 12 );
</source>
會從 cookie 回傳 "myId" 變數的值，預設值是12

===浮點數===
浮點數型可以包含一個前導的負號(<code> - </code>)，但正號(<code> + </code>)是不允許的。如果數字包含了千分位號，那千分位號前頭必須要至少有一個數字。例如，
<source lang="php">
$float = JFactory::getApplication->input->getFloat( 'price' );
</source>
會回傳請求的 'price' 參數，預設的值是 "0.0"
<source lang="php">
$float = JFactory::getApplication->input->post->getFloat( 'total', 100.00 );
</source>
會從 POST (而非 GET) 請求回傳 'total' 值。預設的值是 100.00

===布林值===
所有「非零」的值都會被視為 'true'。零是 'false'
<source lang="php">
$boolean = JFactory::getApplication->input->getBool( 'show' );
</source>
如果請求 'show' 參數的值是零，上面的程式會回傳 false；而如果是其他的參數，會回傳 1 (true)。預設的值是 false. 請注意任何字串都會造成回傳 true，所以使用URL包含"?show=false" 來呼叫上述的程式，事實上會回傳 true!
<source lang="php">
$boolean = JFactory::getApplication->input->get->getBool( 'hide', true );
</source>
會從 GET 請求 (而非 POST) 回傳 'hide' 參數的值。預設的值是 true.

===Word===
Word 的定義是指使用A到Z組成的字段。在 word 中使用部分小寫的字母是允許的。
<source lang="php">
$word = JFactory::getApplication->input->cookie->getWord( 'search-word' );
</source>
會獲取由request送出的 'search-word' 的值。預設是空白字串。
<source lang="php">
$word = JFactory::getApplication->input->cookie->getWord( 'keyword', '' );
</source>
會獲取 cookie 中 'keyword' 變數的值。預設是空白字串。

===指令(Command)===
指令(Command) 類似 word 但是允許的字元是更廣泛的。允許的字元包含：all alphanumeric characters, dot, dash (hyphen) and underscore.
<source lang="php">
$command = JFactory::getApplication->input->getCmd( 'option' );
</source>
會獲取由 request 請求回傳的 "option" 值。預設值是空字串。
<source lang="php">
$command = JFactory::getApplication->input->post->getCmd( 'controller', 'view' );
</source>
會獲取由 POST 請求(而非 GET) "controller" 參數的值。預設值是 'view'

===字串===
字串型允許更廣泛的字元輸入 It also takes an optional fourth argument specifying some additional mask options. 請查看 [[#Filter options]] for information on the available masks.
<source lang="php">
$string = JFactory::getApplication->input->getString( 'description' );
</source>
會獲取從 request 回傳 "description" 參數的值。預設的值是空字串。輸入的值會清除前後的空白，以及 HTML 標籤。
<source lang="php">
$string = JFactory::getApplication->input->getString( 'text', '' );
</source>
會獲取從 request 回傳 "text" 參數的值。預設的值是空字串。
<source lang="php">
$string = JFactory::getApplication->input->getString( 'template', '<html />' );
</source>
會從 request 回傳"template"參數的值。預設的值是 '<html />'.

===JSON 字串===
<source lang="php">
$json = JFactory::getApplication->input->json->get( 'var_name' );
</source>

===通用及其他資料類型===
如果上述的 methods 您要使用的，還有一些額外的過濾類型，可以直接呼叫 <code>[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] </code> method 。語法是：
<source lang="php">
JFactory::getApplication->input->get( <name>, <default>, <type> );
</source>
其中的：

{| class="wikitable" border="1"
| <name> || the name of the variable to be retrieved (for example, the name of an argument in a URL).
|-
| <default> || 預設值。如果沒有在[[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] 呼叫中指定預設值，則沒有預設值會被回傳。
|-
| <type> || 指定的預期資料類型 (見底下)
|}

The first three arguments are the same as for the more specific methods described earlier. Only the first argument is mandatory.

允許的 <type> 值，大小寫有分別，如底下：

{| class="wikitable" border="1"
| INT, INTEGER || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getInt]].
|-
| UINT || Get an unsigned integer. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getUint]].
|-
| FLOAT, DOUBLE || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getFloat]].
|-
| BOOL, BOOLEAN || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getBool]].
|-
| WORD || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getWord]].
|-
| ALNUM || 僅允許 alphanumeric 字元 (a-z, A-Z, 0-9). 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getAlnum]].
|-
| CMD || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getCmd]].
|-
| BASE64 || 僅允許可以被呈現於base64編碼的字元 (也就是 a-z, A-Z, 0-9, /, + 和 =)。相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getBase64]].
|-
| STRING || 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getString]].
|-
| ARRAY || Source is not filtered but is cast to array type. When using this type you should use JFilterInput directly to filter the values in your data array.
|-
| HTML || 經過安全處理的字串，相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getHtml]].
|-
| PATH || Valid pathname regex that filters out common attacks. 例如，any path beginning with a "/" will return an empty string. Simliarly, any path containing "/./" or "/../" will return an empty string. Dots within filenames are okay though. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getPath]].
|-
| USERNAME || 移除 control 字元 (0x00 - 0x1F), 0x7F, <, >, ", ', % and &. 相當於 [[Retrieving_request_data_using_JInput#Getting_Values|JInput->getUsername]].
|}

===過濾選項===
所有的輸入值都應該要用<code> JFilterInput->clean </code>來過濾

過濾值矩陣
<source lang="php">
$data = JFactory::getApplication()->input->post->get('data', array(), 'array');
$filter = JFilterInput::getInstance();

foreach ($data as $value)
{
$array[] = $filter->clean($value, 'string');
}
</source>
要看更多的過濾類型，請看 [https://github.com/joomla/joomla-cms/blob/master/libraries/joomla/filter/input.php#L115 JFilterInput source].

底下列出的選項是過時的 [[JRequest]] library.
允許的 <options> 值羅列如下 (預設並不會套用任何一項)：

{| class="wikitable" border="1"
| JREQUEST_NOTRIM || 並不會移除字串前後的空白
|-
| JREQUEST_ALLOWRAW || 不會套用任何的過濾條件，請絕對謹慎使用！
|-
| JREQUEST_ALLOWHTML || 不會移除字串中的 HTML
|}

Masks can be combined by logically OR'ing them. 如果沒有指定過濾選項，那麼預設會移除空白，並且HTML會被移除。

===上傳檔案===
關於檔案上傳的安全性，網站伺服器已經提供了不錯的想法，然而，還是需要有些額外的手續，來確保檔案名稱以及路徑不會被濫用。一個簡化過的請求上傳檔案表單看起來像這樣：
<source lang="html4strict">
<form action="index.php?option=com_mycomponent/form_handler.php" method="post" enctype="multipart/form-data">
<input type="file" name="Filedata" />
<input type="submit" />
</form>
</source>
按下送出按鈕後，瀏覽器將會使用POST請求來上傳檔案，呼叫 Joomla! 的 <code> "components/com_mycomponent/form_handler.php" </code> 來傳送控制項目這包含了像是以下的程式碼。變項 $somepath 必須要被設定到路徑中，讓網頁伺服器有權限可以建立檔案。
<source lang="php">
// Check to ensure this file is included in Joomla!
defined('_JEXEC') or die( 'Restricted access' );

// 從 request 獲得檔案資料矩陣
$file = JFactory::getApplication->input->get( 'Filedata', '', 'files', 'array' );

// 讓檔案名稱安全無害
jimport('joomla.filesystem.file');
$file['name'] = JFile::makeSafe($file['name']);

// 將上傳的檔案移動到常駐位置
if (isset( $file['name'] )) {

// Make sure that the full file path is safe.
$filepath = JPath::clean( $somepath.'/'.strtolower( $file['name'] ) );

// 移動上傳的檔案
JFile::upload( $file['tmp_name'], $filepath );
}
</source>

===Saving a request variable into user state===
Because setting a user state variable from a variable in the request is such a common operation, there is an API method to make the task easier. This is generally safe to use because it calls [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] to obtain the input from the request, but remember that none of the input filtering calls will protect against SQL injection attempts.
<source lang="php">
$app = JFactory::getApplication();
$app->getUserStateFromRequest( <key>, <name>, <default>, <type> );
</source>
where
{| class="wikitable" border="1"
| <key> || the name of the variable in the user state.
|-
| <name> || the name of the request variable (same as the first argument of a [[Retrieving_request_data_using_JInput#Getting_Values|JInput->get]] call).
|-
| <default> || the default value to be assigned to the user state variable if the request variable is absent. The default is null.
|-
| <type> || 預期的變數型別
|}

例如，getting an integer variable called 'id' from the request with a default value of 0, then saving it into a session variable called 'myid' can be done like this:
<source lang="php">
$app = JFactory::getApplication();
$app->getUserStateFromRequest( 'myid', 'id, 0, 'int' );
</source>
instead of something like this:
<source lang="php">
$app = JFactory::getApplication();
$app->setUserState( 'myid', $app->input->getInt( 'id', 0 ) );
</source>

==慎重結構 SQL queries==
SQL Injection 是常見的網站攻擊類型之一，攻擊者會對輸入值管控不良的資料庫，修改資料庫請求的語法來破壞資料庫。攻擊結果會造成資料庫內容被破壞，或是隱私資料外洩。因此，確保SQL語法結構被送出時，能夠被正確地使用 escape 以及 quote 過濾，是很重要的，這樣惡意輸入才不會構成惡意的 SQL 語法。您將不能倚靠[[Retrieving_request_data_using_JInput|JInput]] 方法來完成這件事，因為它並非 SQL-aware。

===強化整數以及其他數字值的安全===
在 MySQL 資料庫中，數字欄位不應該被 quote，因此，將它們做類型轉換是很重要的。若是沒有這樣處理，您的程式碼會暴露於風險之下，讓駭客在 SQL 資料中存放字串。

依照其類型，數值類型看起來像這樣：
<source lang="php">
// For SQL data types: INT, INTEGER, TINYINT, SMALLINT, MEDIUMINT, BIGINT, YEAR
$query = 'SELECT * FROM #__table WHERE `id`=' . (int) $id;

// For SQL data types: FLOAT, DOUBLE
$query = 'SELECT * FROM #__table WHERE `id`=' . (float) $id;
</source>
總是對使用 <cdoe> JInput->getInt</code>獲得的變數進行整數型別轉換，絕對是個好習慣。關於 SQL 注入攻擊更進一步的資訊，可以在 http://php.net/manual/en/security.database.sql-injection.php 以及 [[Retrieving_request_data_using_JInput#Getting_Values]] 找到。

===強化字串安全===
在一個遵循規範的範例中，會假定<code> $db </code> 是joomla!資料庫物件的 instance 。這可以確保從[https://docs.joomla.org/Using_the_JFactory_class JFactory] 取用，使用
<source lang="php">
$db = JFactory::getDBO();
</source>
字串在使用於 SQL 語法之前，一定要先進行清理。這事實上是相當容易的，因為 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_quote JDatabase->quote] method 已經為您清理所有的可疑內容了。您也可以直接使用 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_escape JDatabase->escape] method。相當於底下的語法：
<source lang="php">
$query = 'SELECT * FROM #__table WHERE `field` = ' . $db->quote( $db->escape( $field ), false );

$query = 'SELECT * FROM #__table WHERE `field` = ' . $db->quote( $field );
</source>

===強化搜尋安全===
Special attention should be paid to LIKE clauses which contain the % wildcard character as these require special escaping in order to avoid possible denial of service attacks. LIKE clauses can be handled like this:
<source lang="php">
// Construct the search term by escaping the user-supplied string and, if required, adding the % wildcard characters manually.
$search = '%' . $db->escape( $search, true ) . '%';

// Construct the SQL query, being careful to suppress the default behaviour of Quote so as to prevent double-escaping.
$query = 'SELECT * FROM #__table WHERE `field` LIKE ' . $db->quote( $search, false );
</source>

===強固資料安全===
If data is to be entered into a datetime column then you can use the Joomla API to ensure a valid date format:
<source lang="php">
$date = JFactory::getDate( $mydate );
$query = 'UPDATE #__table SET `date` = ' . $db->quote( $date->toMySQL(), false );
</source>
Note that it is necessary to suppress database escaping as legitimate dates may contain characters that should not be escaped.

===強固欄位名稱(field name)安全===
In the comparatively rare case where a field name is a variable, that should also be quoted using an API call:
<source lang="php">
$query = 'SELECT * FROM #__table WHERE ' . $db->quoteName( $field->name ) . '=' . $db->quote( $field->value );
</source>

===強固整數陣列安全===
When you have an array of ids, typically used for IN() queries, you have to sanitise it also with <code> JArrayHelper::toInteger($cid); </code> before imploding:

<source lang="php">
...
$catId = JArrayHelper::toInteger($catId);
$query->where($db->quoteName('x.category_id') . ' IN (' . implode(',', $catId) . ')');
</source>

=== Quote 以及 QuoteName 的短別名===
Shorter alternatives to the quote methods may also be used。的語法是相同意思的：
<source lang="php">
$query = 'SELECT * FROM #__table WHERE ' . $db->quoteName( $field->name ) . '=' . $db->quote( $field->value );
$query = 'SELECT * FROM #__table WHERE ' . $db->qn( $field->name ) . '=' . $db->q( $field->value );
</source>

==強固表單安全==
Apart from cleaning input variables as described above, you can also implement a simple technique which makes it more difficult for a cross-site request forgery attack (CSRF) to succeed. This involves adding a randomly-generated unique token to the form which is checked against a copy of the token held in the user's session. By checking that the submitted token matches the one contained in the stored session, it is possible to tie a rendered form to the request variables presented.

In POST forms you should add a hidden token field using:
<source lang="php">
echo JHTML::_( 'form.token' );
</source>
This outputs the token as a hidden form field looking like this:
<source lang="html4strict">
<input type="hidden" name="8cb24ae69ffd7828ccecbcf06056e6fc" value="1" />
</source>
and places a copy of the token into the user's session, for later checking.

If you need to add the token to a URL rather than a form then you can use something like this:
<source lang="php">
echo JRoute::_( 'index.php?option=com_mycomponent&' . JSession::getFormToken() . '=1' );
</source>

In the most common scenario, you will want to check the token following a POST to the form handler. This can be done by adding this line of code to form handler:
<source lang="php">
JSession::checkToken() or die( JText::_( 'Invalid Token' ) );
</source>
If you need to pass the token in a GET request then you can check it like this:
<source lang="php">
JSession::checkToken( 'get' ) or die( JText::_( 'Invalid Token' ) );
</source>

In both cases the code will die if the token is omitted from the request, or the submitted token does not match the session token. If the token is correct but has expired, then [[JSession/checkToken|JSession::checkToken]] will automatically redirect to the site front page.

==清理檔案的系統路徑==
If there is any possibility that a filesystem path might be constructed using data that originated from user input, then the path must be cleaned and checked before being used. 只要像這樣做，很容易就可以：
<source lang="php">
JPath::check( $path );
</source>
This will raise an error and terminate Joomla if the path contains a ".." or leads to a location outside the Joomla root directory. If you want to deal with the error yourself without terminating the application, then you can use code like this:
<source lang="php">
$path = JPath::clean( $path );
if (strpos( $path, JPath::clean( JPATH_ROOT ) ) !== 0) {
// Handle the error here.
}
</source>
<code> [[JPath:clean]] </code> method 也可以使用於您的程式碼。它僅僅是移除首尾的空白字元，以 double slash (<code>--</code>) 代替；以標準的路徑分隔符號代替double slashes(<code>//</code>)

==清理檔案路徑檔案名稱==
As with filesystem paths, if there is any possibility that a file name might be constructed using user-originated data, then the file name must be cleaned and checked before use. 像這樣做就可以完成：
<source lang="php">
jimport('joomla.filesystem.file');
$clean = JFile::makeSafe( $unclean );
</source>
這個 method 會移除內容中的"." 或是多個"." 字元，以及其他非 alphabetic, numeric 或是dot, dash 或是 underscore 字元。如果字串起頭是"."，也會被移除。
[[Category:Development/zh-tw]][[Category:Security/zh-tw]]

Translations:Secure coding guidelines/43/zh-tw

2023-02-09T02:56:59Z

Shawnhy:

===強化字串安全===
在一個遵循規範的範例中，會假定<code> $db </code> 是joomla!資料庫物件的 instance 。這可以確保從[https://docs.joomla.org/Using_the_JFactory_class JFactory] 取用，使用
<source lang="php">
$db = JFactory::getDBO();
</source>
字串在使用於 SQL 語法之前，一定要先進行清理。這事實上是相當容易的，因為 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_quote JDatabase->quote] method 已經為您清理所有的可疑內容了。您也可以直接使用 [https://api.joomla.org/cms-3/classes/JDatabaseQuery.html#method_escape JDatabase->escape] method。相當於底下的語法：
<source lang="php">
$query = 'SELECT * FROM #__table WHERE `field` = ' . $db->quote( $db->escape( $field ), false );

What version of Joomla! should you use?/zh-tw

2023-02-04T07:20:25Z

Shawnhy: Created page with "zh-tw"

<noinclude><languages /></noinclude>
首先，您應該會想要檢查一下您的網站 [[S:MyLanguage/How to check the Joomla version?|正在執行的 Joomla! 版本]]是哪一個。
{{:Joomla! CMS versions/en}}

==包含的外部函示庫==
{{:External Libraries in Joomla/zh-tw}}

==Joomla! 版本差異說明==
{{:Release_and_support_cycle/zh-tw}}

==參考及註記==
<references/>
__NOTOC__
<noinclude>
[[Category:FAQ/zh-tw]]
[[Category:Version 1.0 FAQ/zh-tw]]
[[Category:Version 1.5 FAQ/zh-tw]]
[[Category:Version 1.6 FAQ/zh-tw]]
[[Category:Version 1.7 FAQ/zh-tw]]
[[Category:Version 2.5 FAQ/zh-tw]]
[[Category:Version 3.0 FAQ/zh-tw]]
[[Category:Version 3.1 FAQ/zh-tw]]
[[Category:Version 3.2 FAQ/zh-tw]]
[[Category:Version 3.3 FAQ/zh-tw]]
[[Category:Version 3.4 FAQ/zh-tw]]
[[Category:Version 3.5 FAQ/zh-tw]]
[[Category:Version 3.6 FAQ/zh-tw]]
[[Category:Version 3.7 FAQ/zh-tw]]
[[Category:Version 3.8 FAQ/zh-tw]]
[[Category:Getting Started FAQ/zh-tw]]
[[Category:Joomla! versions/zh-tw]]
</noinclude>