Joomla! Documentation - User contributions [en]

J4.x:Adding a menu link in an article/ja

2018-08-16T18:09:40Z

Nori: Created page with "''新規''をクリックして新しい''コンテンツ''を作成 {{rarr}} ''記事''-ページでコンテンツを入力後''保存''します。保存していない場..."

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

記事編集時に直接メニューアイテムを追加する手順

# 記事編集画面へ
#* ''記事''へ画面へ移動し {{rarr}} 既存の''記事''をクリックして編集 '''するか'''
#* ''新規''をクリックして新しい''コンテンツ''を作成 {{rarr}} ''記事''-ページでコンテンツを入力後''保存''します。保存していない場合は、ボタンが表示されません
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/6/ja

2018-08-16T18:09:39Z

''新規''をクリックして新しい''コンテンツ''を作成 {{rarr}} ''記事''-ページでコンテンツを入力後''保存''します。保存していない場合は、ボタンが表示されません

J4.x:Adding a menu link in an article/ja

2018-08-16T18:05:12Z

Nori:

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

記事編集時に直接メニューアイテムを追加する手順

# 記事編集画面へ
#* ''記事''へ画面へ移動し {{rarr}} 既存の''記事''をクリックして編集 '''するか'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/5/ja

2018-08-16T18:05:12Z

Nori:

''記事''へ画面へ移動し {{rarr}} 既存の''記事''をクリックして編集 '''するか'''

J4.x:Adding a menu link in an article/ja

2018-08-16T18:02:44Z

Nori: Created page with "''記事''へ画面へ {{rarr}} 既存の''記事''をクリックして編集 '''又は'''"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

記事編集時に直接メニューアイテムを追加する手順

# 記事編集画面へ
#* ''記事''へ画面へ {{rarr}} 既存の''記事''をクリックして編集 '''又は'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/5/ja

2018-08-16T18:02:44Z

Nori: Created page with "''記事''へ画面へ {{rarr}} 既存の''記事''をクリックして編集 '''又は'''"

''記事''へ画面へ {{rarr}} 既存の''記事''をクリックして編集 '''又は'''

J4.x:Adding a menu link in an article/ja

2018-08-16T17:56:48Z

Nori: Created page with "記事編集画面へ"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

記事編集時に直接メニューアイテムを追加する手順

# 記事編集画面へ
#* Going to ''Content'' {{rarr}} ''Articles'' and click on an existing one to edit it '''or'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/4/ja

2018-08-16T17:56:47Z

Nori: Created page with "記事編集画面へ"

記事編集画面へ

J4.x:Adding a menu link in an article/ja

2018-08-16T17:55:43Z

Nori: Created page with "記事編集時に直接メニューアイテムを追加する手順"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

記事編集時に直接メニューアイテムを追加する手順

# Edit an article by either
#* Going to ''Content'' {{rarr}} ''Articles'' and click on an existing one to edit it '''or'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/3/ja

2018-08-16T17:55:43Z

Nori: Created page with "記事編集時に直接メニューアイテムを追加する手順"

記事編集時に直接メニューアイテムを追加する手順

J4.x:Adding a menu link in an article/ja

2018-08-16T17:52:04Z

Nori: Created page with "記事からメニューアイテムの追加方法"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
記事からメニューアイテムの追加方法}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

Steps to add a menu item directly when an article is edited:

# Edit an article by either
#* Going to ''Content'' {{rarr}} ''Articles'' and click on an existing one to edit it '''or'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/2/ja

2018-08-16T17:52:03Z

Nori: Created page with "記事からメニューアイテムの追加方法"

記事からメニューアイテムの追加方法

J4.x:Adding a menu link in an article/ja

2018-08-16T17:50:43Z

Nori: Created page with "チュートリアル"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=チュートリアル 
How to add a Menu Item from an Article}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

Steps to add a menu item directly when an article is edited:

# Edit an article by either
#* Going to ''Content'' {{rarr}} ''Articles'' and click on an existing one to edit it '''or'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/1/ja

2018-08-16T17:50:43Z

Nori: Created page with "チュートリアル"

チュートリアル

J4.x:Adding a menu link in an article/ja

2018-08-16T17:50:28Z

Nori: Created page with "J4.x:記事にメニューリンクを追加"

<noinclude><languages /></noinclude>
{{Top portal heading|color=white-bkgd|icon=magic|icon-color=#5091cd|size=3x|text-color=#333|title=Tutorial 
How to add a Menu Item from an Article}}
<noinclude>{{Joomla version|version=4.0}}</noinclude>
{{-}}

Steps to add a menu item directly when an article is edited:

# Edit an article by either
#* Going to ''Content'' {{rarr}} ''Articles'' and click on an existing one to edit it '''or'''
#* Create a new one by clicking on ''New'' on the ''Content'' {{rarr}} ''Article''-Page and click on ''Save'' after filling out the form. The Button will not appear if the article is not saved
# On the ''Article: Edit'' page you can click on ''New Menu Item'' to open the depending modal popup {{-}}[[File:Article Edit page-en.png|800px|center]]
# Fill in the ''Menu Title'', as ''Menu Item Type'' choose ''Single Article'' and select the newly created article. Remember to choose the correct ''Menu'' on the right where the link should appear. '''Note:''' You can select a single article but also multiple ones, e.g. by category {{-}} [[File:Fill in the form for a new menu item-en.png|800px|center]]
# Click ''Save&Close'' and head to ''Menus'' {{rarr}} ''[The Menu with the new Item]''. You should now see the new item in the list {{-}}[[File:Menu Item Created-en.png|800px|center]]

<noinclude>
[[Category:Tutorials{{#translation:}}]]
[[Category:Article Management{{#translation:}}]]
[[Category:Beginners{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Joomla! 4.0{{#translation:}}]]
</noinclude>

Translations:J4.x:Adding a menu link in an article/Page display title/ja

2018-08-16T17:50:28Z

Nori: Created page with "J4.x:記事にメニューリンクを追加"

J4.x:記事にメニューリンクを追加

Search Engine Friendly URLs/ja

2014-03-08T20:51:19Z

Nori: Created page with "=== ルートフォーマット ==="

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

== ルートフォーマットとルーティングの仕組み ==

''このセクションではJoomla!コア(内蔵)のルーティングの仕組みを説明します。ルーティングエクステンションはシステムで作成するルートを変更する事があります。''

=== ルートフォーマット ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/24/ja

2014-03-08T20:51:18Z

Nori: Created page with "=== ルートフォーマット ==="

=== ルートフォーマット ===

Search Engine Friendly URLs/ja

2014-03-08T20:51:02Z

Nori: Created page with "''このセクションではJoomla!コア(内蔵)のルーティングの仕組みを説明します。ルーティングエクステンションはシステムで作成す..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

== ルートフォーマットとルーティングの仕組み ==

''このセクションではJoomla!コア(内蔵)のルーティングの仕組みを説明します。ルーティングエクステンションはシステムで作成するルートを変更する事があります。''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/23/ja

2014-03-08T20:51:01Z

''このセクションではJoomla!コア(内蔵)のルーティングの仕組みを説明します。ルーティングエクステンションはシステムで作成するルートを変更する事があります。''

Search Engine Friendly URLs/ja

2014-03-08T20:45:53Z

Nori: Created page with "== ルートフォーマットとルーティングの仕組み =="

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

== ルートフォーマットとルーティングの仕組み ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/22/ja

2014-03-08T20:45:52Z

Nori: Created page with "== ルートフォーマットとルーティングの仕組み =="

== ルートフォーマットとルーティングの仕組み ==

Search Engine Friendly URLs/ja

2014-03-08T10:37:56Z

Nori:

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/11/ja

2014-03-08T10:37:56Z

Nori:

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです)

Search Engine Friendly URLs/ja

2014-03-08T10:35:48Z

Nori: Created page with "=== SEF URLの数字をなくすには？ === SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定した..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/21/ja

2014-03-08T10:35:47Z

=== SEF URLの数字をなくすには？ ===
SEF URLの数字はサイトトラフィック制御するJoomla!ルータが必要です。ルータロジックが安定したらサードパーティ製のシステムプラグインを選択しルータの機能を強化できるでしょう。その時にURLから数字は削除されます。

Search Engine Friendly URLs/ja

2014-03-08T10:29:18Z

Nori: Created page with "完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>"

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/20/ja

2014-03-08T10:29:17Z

Nori: Created page with "完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>"

完成したURL: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

Search Engine Friendly URLs/ja

2014-03-08T10:29:01Z

Nori: Created page with "* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;"

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/19/ja

2014-03-08T10:29:01Z

Nori: Created page with "* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;"

* 記事のプライマリーキーと記事のエイリアスを追加 - 1-apple;

Search Engine Friendly URLs/ja

2014-03-08T10:28:55Z

Nori:

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/18/ja

2014-03-08T10:28:55Z

Nori:

* カテゴリのプライマリーキーとカテゴリのエイリアスを追加 - 32-fruit;

Search Engine Friendly URLs/ja

2014-03-08T10:27:50Z

Nori: Created page with "* カテゴリのプライマリーキーとカテゴリエイリアスを追加 - 32-fruit;"

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* カテゴリのプライマリーキーとカテゴリエイリアスを追加 - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/18/ja

2014-03-08T10:27:50Z

Nori: Created page with "* カテゴリのプライマリーキーとカテゴリエイリアスを追加 - 32-fruit;"

* カテゴリのプライマリーキーとカテゴリエイリアスを追加 - 32-fruit;

Search Engine Friendly URLs/ja

2014-03-08T10:25:31Z

Nori: Created page with "* メニューアイテムのURL - example.com/products;"

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* メニューアイテムのURL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/17/ja

2014-03-08T10:25:31Z

Nori: Created page with "* メニューアイテムのURL - example.com/products;"

* メニューアイテムのURL - example.com/products;

Search Engine Friendly URLs/ja

2014-03-08T10:25:01Z

Nori: Created page with "Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテ..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/16/ja

2014-03-08T10:25:00Z

Joomla!のルータが正しいページに移動する為、URL内のプライマリーキーを使用しています。上記例のメニューアイテムの種類がカテゴリブログの場合、記事タイトルや続きを読むリンクの3個のパーツ:

Search Engine Friendly URLs/ja

2014-03-08T10:16:57Z

Nori: Created page with "=== エイリアスはURLのどの部分に使用されますか？ === メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFの..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Joomla! also uses the primary key values of data within the URL to help the router navigate to the correct page. Continuing with the previous example, if your products menu item was for an Article/Category Blog, the link for the Article Title and/or Read More link would have three parts:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/15/ja

2014-03-08T10:16:56Z

=== エイリアスはURLのどの部分に使用されますか？ ===
メニューアイテムではJoomla!はURLプラグとしてエイリアスを使用します。SEFのオプションを二つとも有効に設定しているとしてProductsというタイトルのメニューアイテムを作った場合のURLはexample.com/productsになります。

Search Engine Friendly URLs/ja

2014-03-08T10:09:59Z

Nori: Created page with "=== エイリアスを自分で作成したい === Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

=== How is Alias used in a URL? ===
For a menu item, Joomla! uses the alias as the URL plug. Assume that you use the first two SEF URL options and you create a menu item called Products. Your URL would be example.com/products.

Joomla! also uses the primary key values of data within the URL to help the router navigate to the correct page. Continuing with the previous example, if your products menu item was for an Article/Category Blog, the link for the Article Title and/or Read More link would have three parts:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/14/ja

2014-03-08T10:09:59Z

=== エイリアスを自分で作成したい ===
Joomla!が作成するエイリアスが気に入らない場合、エイリアスフィールドに好きな値を入れる事ができます。大抵の場合URL内に効果的なキーワードを使用するとSEO対策となるでしょう。記事のタイトルにこれらのキーワードを含みJoomla!で作成したり独自のエイリアスを作る事ができます。

Search Engine Friendly URLs/ja

2014-03-08T10:02:00Z

Nori: Created page with "=== エイリアスとは？またどの様に作成されますか？ === エイリアスは記事、カテゴリ、セクション、メニューア..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

=== I want to specify my own value for Alias. ===
If you do not like the alias provided by Joomla!, you can enter a value of your choosing into that field. Many believe using good keywords in your URL helps search engine optimization. You can do so by including those keywords in your title, and allowing Joomla! to create the alias, or by creating the alias yourself.

=== How is Alias used in a URL? ===
For a menu item, Joomla! uses the alias as the URL plug. Assume that you use the first two SEF URL options and you create a menu item called Products. Your URL would be example.com/products.

Joomla! also uses the primary key values of data within the URL to help the router navigate to the correct page. Continuing with the previous example, if your products menu item was for an Article/Category Blog, the link for the Article Title and/or Read More link would have three parts:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/13/ja

2014-03-08T10:02:00Z

Nori: Created page with "=== エイリアスとは？またどの様に作成されますか？ === エイリアスは記事、カテゴリ、セクション、メニューア..."

=== [[S:MyLanguage/Alias|エイリアス]]とは？またどの様に作成されますか？ ===
エイリアスは記事、カテゴリ、セクション、メニューアイテム等のタイトルフィールドの下に表示されています。Joomla!は自動的にエイリアスを作成でき自動作成されたエイリアスはタイトルから始まりすべて小文字に変換されます。スペースやURLで使用できない文字はダッシュに変換されます。

Search Engine Friendly URLs/ja

2014-03-08T09:50:05Z

Nori: Created page with "=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ === 削除してはいけませんURLには<code>index.php</code>が..."

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

=== What is the [[Alias]] value? And how does it get created? ===
Alias is listed beneath the Title field in Articles, Categories, Sections and Menu Items. Joomla! can automatically create the alias for you. An automatic alias begins with the title. All upper case letters are changed to lower case. Spaces and special characters not allowed in a URL; they are changed to dashes.

=== I want to specify my own value for Alias. ===
If you do not like the alias provided by Joomla!, you can enter a value of your choosing into that field. Many believe using good keywords in your URL helps search engine optimization. You can do so by including those keywords in your title, and allowing Joomla! to create the alias, or by creating the alias yourself.

=== How is Alias used in a URL? ===
For a menu item, Joomla! uses the alias as the URL plug. Assume that you use the first two SEF URL options and you create a menu item called Products. Your URL would be example.com/products.

Joomla! also uses the primary key values of data within the URL to help the router navigate to the correct page. Continuing with the previous example, if your products menu item was for an Article/Category Blog, the link for the Article Title and/or Read More link would have three parts:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/12/ja

2014-03-08T09:50:04Z

=== URLには <code>index.php</code> がありませんこのファイルは削除していいですか？ ===
削除してはいけませんURLには<code>index.php</code>が含まれていませんが内部的にmod_rewriteが表示しないで元のパスへリダイレクトしているためです。

Translations:Search Engine Friendly URLs/11/ja

2014-03-08T09:46:43Z

Nori: Created page with "これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリ..."

これらの数字は、Joomla!が必要とするパラメータでURLから取得し表示したいページを探します。 (この場合、最初の数字1はカテゴリーのID、二つ目の数字1は、記事のIDです）

Translations:Search Engine Friendly URLs/10/ja

2014-03-08T09:43:55Z

Nori: Created page with "<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>"

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

Search Engine Friendly URLs/ja

2014-03-08T09:43:54Z

Nori: Created page with "新しいURLでは:"

<noinclude><languages /></noinclude>
<onlyinclude>
'''検索エンジンフレンドリーURL''','''人が読みとれる'''や[[wikipedia:Clean_URL|clean URLs]]は特定ページへのパスを人と検索エンジン両方に理解できるURLです。Joomla! バージョン1.5以降ではSEF URLを含む全フォーマットでもURLを作成し解析できます。Joomla!の場合、WebサーバのURL書換えに依存しない為、Joomla!はmod_rewriteモジュールを使用しているApache以外のサーバでも作動します。SEF URLは特定の固有パターンがありますがユーザはURL毎に短い説明(エイリアス)を含める事ができます。

内部的にSEF URL(ドメイン名以降)のパスは'''ルート'''と呼ばれています。SEF URLの作成と解析処理は'''ルーティング'''と呼ばれ関連するコードは'''ルータ'''と呼ばれています。
</onlyinclude>
ルーティングのよい例がサンプルデータ内の記事"Joomla!へようこそ"です。

* SEF URLが無効のURL <code><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></code>
* SEF URLが有効でmod_rewriteは無効 <code><nowiki>http://www.example.com/index.php/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>
* SEF URL,mod_rewrite両方有効 <code><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></code>

検索エンジンフレンドリーURLは'''グローバル設定'''内の'''検索エンジンフレンドリーURL'''で設定できますこのオプションはJoomla!1.6からデフォルトで有効になっています。詳細は[[S:MyLanguage/Enabling Search Engine Friendly (SEF) URLs|検索エンジンフレンドリーURLを有効化]]を参照して下さい。

== FAQs ==

=== URL内の数字はなんですか？ ===
古いURLと新しいURLの数字を比較してみましょう古いURLでは

<pre><nowiki>http://www.example.com/index.php?option=com_content&view=article&id=1:welcome-to-joomla&catid=1:latest-news&Itemid=50</nowiki></pre>

新しいURLでは:

<pre><nowiki>http://www.example.com/the-news/1-latest-news/1-welcome-to-joomla</nowiki></pre>

These numbers are the parameters that are needed by Joomla! to get the internal URL and show the page you want to see. (In this case, the first numeral one is the ID of the category, the second numeral one is the ID of the article.)

=== There is no <code>index.php</code> in the URL anymore. Can I delete the file now? ===
No! The URL may doesn't contain the <code>index.php</code> anymore, but internally the mod_rewrite will only redirect to the original path without showing it to you.

=== What is the [[Alias]] value? And how does it get created? ===
Alias is listed beneath the Title field in Articles, Categories, Sections and Menu Items. Joomla! can automatically create the alias for you. An automatic alias begins with the title. All upper case letters are changed to lower case. Spaces and special characters not allowed in a URL; they are changed to dashes.

=== I want to specify my own value for Alias. ===
If you do not like the alias provided by Joomla!, you can enter a value of your choosing into that field. Many believe using good keywords in your URL helps search engine optimization. You can do so by including those keywords in your title, and allowing Joomla! to create the alias, or by creating the alias yourself.

=== How is Alias used in a URL? ===
For a menu item, Joomla! uses the alias as the URL plug. Assume that you use the first two SEF URL options and you create a menu item called Products. Your URL would be example.com/products.

Joomla! also uses the primary key values of data within the URL to help the router navigate to the correct page. Continuing with the previous example, if your products menu item was for an Article/Category Blog, the link for the Article Title and/or Read More link would have three parts:

* The menu item URL - example.com/products;

* Plus, the primary key for the Category and the Category alias - 32-fruit;

* Plus, the primary key for the Article and the Article alias - 1-apple;

The complete URL is: <code><nowiki>http://example.com/products/32-fruit/1-apple</nowiki></code>

=== How can I get rid of the numbers in the SEF URLs? ===
The numbers in the SEF URL are needed by Joomla!'s router to know how to direct site traffic. Once the router logic stabilizes, simple third party system plugins can be developed to augment the router capabilities by allowing more choice. At that time, numbers will likely be removed from the URL.

== Route Formats and the Routing Mechanism ==

''This section describes Joomla!'s core (built-in) routing mechanism. Routing extensions may change the way routes are created on your system.''

=== Route Formats ===

To describe the Joomla! routing mechanism in more detail, we first need to pin down what we refer to as a '''route'''. Suppose that Joomla! has been installed in <code><nowiki>http://example.com/sites/first/</nowiki></code>. The installation path is generally referred to as the '''base URL'''. A possible example URL is <code><nowiki>http://example.com/sites/first/products/32-fruit/1-apple</nowiki></code>. The first part of this URL is the aforementioned base URL, and neither Joomla! nor any component router can create URLs with a different first part. The second part, <code>products/32-fruit/1-apple</code>, is a '''route''', consisting of three '''segment'''s.

The first segment of a route is, for regular URLs, the alias of a menu item. The SEF URL is said to be '''routed through''' that menu item. The other segments are determined entirely by the router of the component that provides the type of the menu item. The ''Category - Blog'' menu item type, for example, is provided by the [[Content]] component, and therefore that component's router is responsible for building and parsing the remaining segments.

It is also possible (for extensions) to ask the system to create a route without supplying a menu item to route through. In that case, the system will usually decide to create a special route that has the word <code>component</code> as the first segment. These routes are created using a fixed format: the name of the component (without the leading <code>com_</code>) is selected as the second segment and any parameters as the other segments.

=== Limitations ===

It is important to note creating a menu item is the ''only'' way for a Joomla! user to define a route that leads to a specific component. It is, however, possible to create a route without showing it on the site (in a menu). An often-applied method is to create a menu item in a menu that isn't displayed anywhere. Such a menu is usually called a [[Menu|hidden menu]].

The previous paragraph implies that it is not possible to make one component responsible for handling all routes. For example, it is not possible to specify that the URL <code><nowiki>http://example.com/thealias</nowiki></code> should display the Content item with the alias <code>thealias</code>, where <code>thealias</code> could be any word. If this needs to be done for a small number of articles, menu items can be created manually for these. Else a routing extension is necessary.

This routing mechanism is therefore not as flexible as users sometimes require. On the other hand, it has one large advantage: it reduces the chance of ambiguous routes (routes that could lead to two different pages). Since the first segment of a route is always a menu item alias, the system immediately knows which component's router must be used to parse it.

== Implementation Details ==
=== Handling Routes ===

''This section describes the routing implementation. If you are a component developer, see [[Supporting SEF URLs in your component]].''

Joomla routes are created and resolved by [[JRouter|the JRouter class]]. This class looks in the component root of the currently active component (specified in the <code>option</code> parameter in the query string) and includes the <code>router.php</code> file in that component's root directory. It then calls one of two functions: one for creating the SEF URL and one for interpreting the SEF URL.

The JRouter class is overridden by the Joomla CMS in <code>/includes/router.php</code>. In this file the build and parse functions are overridden to properly build and parse the URLs for the Joomla CMS.

The <code>router.php</code> file in each component (for example, <code>/components/com_content/router.php</code>) should contain the following two functions:
* ContentBuildRoute - this builds the SEF URL
** Parameters
*** $query - this is a named array containing the querystring variables
** Returns: an array of segments where each segment is separated by a '/' when later combined to create the actual URL (the items in the array should not contain '/' characters)
* ContentParseRoute - this interprets an SEF URL
** Parameters
*** $segments - this is an array that contains the segments of the URL requested.
** Returns: a name => value array of the querystring variables that the link maps to

=== The SEF Plugin ===
The Joomla ''System - SEF'' plugin inherits <code>JPlugin</code> and implements the <code>onAfterRender()</code> function. In this function the body of the response that will be sent to the browser is retrieved using <code>JResponse::getBody()</code>. The body of the response is then searched for links containing <code>/index.php...</code> and replaces them with a correct SEF URL by calling <code>JRoute::_(''url'')</code>.

JRoute builds SEF URLs by instantiating a <code>JRouter</code> object and requesting that it build the correct link from the passed in URL.

=== Handling SEF URLs ===
By default the SEF URLs are handled by the <code>JRouterSite</code> object (from <code>/includes/router.php</code>) and is called by a call to <code>JApplication::route()</code> in index.php. This call is made on the <code>$app</code> variable which is actually an instance of <code>JSite</code> (from <code>/includes/application.php</code>).

<code>JApplication::route()</code> has a non-destructive result on the <code>$_GET</code> array. That is, <code>JApplication::route()</code> sets variables in <code>$_GET</code> by calling <code>JRequest::set()</code> with the overwrite flag set to false. Thus if a variable name is returned from <code>JRouter::route()</code> that is already in <code>$_GET</code>, it will not put that value into <code>$_GET</code>. This allows for custom routing.

=== Custom Routing ===
Joomla allows you to create your own routing mechanism. In order to create this mechanism you must have a plugin that overrides the <code>JPlugin::onAfterInitialise()</code> function. This function then parses the URL and creates the needed variables in <code>$_GET</code> before the standard Joomla routing is done.

''See [[Creating a System Plugin to augment JRouter]] for an example.''

[[Category:Search Engine Friendly URLs| ]]

Translations:Search Engine Friendly URLs/9/ja

2014-03-08T09:43:54Z

Nori: Created page with "新しいURLでは:"

新しいURLでは: