Glossary
出典: Joomla! ドキュメンテーション
Article
In Joomla! an Article is a piece of content consisting of text (HTML), possibly with links to other resources (for example, images). Articles are the basic units of information in the content system and the bottom level in the content hierarchy. Since Joomla! 1.6
, each Article is in exactly one Category, and Categories can be in other Categories. It is also possible to have Uncategorised Articles that exist without being associated with any Category.
In Joomla! 1.5
and earlier versions, an Article was the third level in the hierarchy Sections -> Categories -> Articles.
Articles are maintained using the Article Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Article Manager menu item.
Article/ja
In Joomla! an Article is a piece of content consisting of text (HTML), possibly with links to other resources (for example, images). Articles are the basic units of information in the content system and the bottom level in the content hierarchy. Since Joomla! 1.6
, each Article is in exactly one Category, and Categories can be in other Categories. It is also possible to have Uncategorised Articles that exist without being associated with any Category.
In Joomla! 1.5
and earlier versions, an Article was the third level in the hierarchy Sections -> Categories -> Articles.
Articles are maintained using the Article Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Article Manager menu item.
Category
In Joomla! a Category is a collection of Articles. In Joomla! versions up to and including
, is the middle level in the hierarchy Sections -> Categories -> Articles. For example, a website might have Sections called "Animals" and "Plants". Within the "Animals" Section, the website might have Categories such as "Birds" and "Mammals". Within the "Birds" Category, the website might have Articles such as "Parrots" and "Sparrows". In Joomla! versions
and up, Categories can contain other Categories. The example above could be created using an "Animal" category, the Categories "Birds" and "Mammals" that are in that category, and the "Parrots" and "Sparrows" Articles in the "Birds" category.
Categories are maintained using the Category Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Category Manager menu item.
Category/ja
In Joomla! a Category is a collection of Articles. In Joomla! versions up to and including
, is the middle level in the hierarchy Sections -> Categories -> Articles. For example, a website might have Sections called "Animals" and "Plants". Within the "Animals" Section, the website might have Categories such as "Birds" and "Mammals". Within the "Birds" Category, the website might have Articles such as "Parrots" and "Sparrows". In Joomla! versions
and up, Categories can contain other Categories. The example above could be created using an "Animal" category, the Categories "Birds" and "Mammals" that are in that category, and the "Parrots" and "Sparrows" Articles in the "Birds" category.
Categories are maintained using the Category Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Category Manager menu item.
Component
A component is a kind of Joomla! extension. Components are the main functional units of Joomla!; they can be seen as mini-applications. An easy analogy would be that Joomla! is the operating system and the components are desktop applications. They are usually displayed in the center of the main content area of a template (depending on the template).
Most components have two main parts: an administrator part and a site part. The site part is what is used to render pages when being called during normal site operation. The administrator part provides an interface to configure and manage different aspects of the component and is accessible through the Joomla! administrator application.
Joomla! comes with a number of core components, like the content management system, contact forms and Web Links.
See also: Module, Plugin, Template
Component/ja
A component is a kind of Joomla! extension. Components are the main functional units of Joomla!; they can be seen as mini-applications. An easy analogy would be that Joomla! is the operating system and the components are desktop applications. They are usually displayed in the center of the main content area of a template (depending on the template).
Most components have two main parts: an administrator part and a site part. The site part is what is used to render pages when being called during normal site operation. The administrator part provides an interface to configure and manage different aspects of the component and is accessible through the Joomla! administrator application.
Joomla! comes with a number of core components, like the content management system, contact forms and Web Links.
See also: Module, Plugin, Template
Database Table Prefix
The database table prefix is a string (a few characters long) prepended to the name of Joomla!'s tables. Using a prefix enables you to run multiple installations of Joomla! using a single database.
The database table prefix can be set during installation. Changing it later is possible, but requires access to the database through a non-Joomla medium and will cause some downtime.
Extension developers need to use the string #__ to represent the prefix. This will be replaced by the real prefix during runtime by Joomla.
Database Table Prefix/ja
The database table prefix is a string (a few characters long) prepended to the name of Joomla!'s tables. Using a prefix enables you to run multiple installations of Joomla! using a single database.
The database table prefix can be set during installation. Changing it later is possible, but requires access to the database through a non-Joomla medium and will cause some downtime.
Extension developers need to use the string #__ to represent the prefix. This will be replaced by the real prefix during runtime by Joomla.
Extension
An extension is a software package that extends your Joomla! installation in some way. A small selection of extensions is included with the default Joomla! installation but many more are available from the Joomla! Extensions Directory.
The term extension is generic and the following specific extension types are available (listed alphabetically):
- Component (since
ファイル:Compat icon 1 0.png) – adds custom functions to your site that can be selected from menus
- Language (since
ファイル:Compat icon 1 0.png) – defines an additional language for your site
- Library (since
) – provides functions to be used by other extensions
- Mambot (in
ファイル:Compat icon 1 0.png) – modifies content in articles
- Module (since
ファイル:Compat icon 1 0.png) – shows nonessential data in a side box, possibly on multiple pages
- Package (since
) – bundles related extensions
- Plugin (since
) – modifies content in articles or provides functions to extend other extensions
- Template (since
ファイル:Compat icon 1 0.png) – define the look, feel, and navigation capabilities of your site
For an overview of the most important extension types and the functionality they provide, see Extension types (general definitions).
Extension/ja
An extension is a software package that extends your Joomla! installation in some way. A small selection of extensions is included with the default Joomla! installation but many more are available from the Joomla! Extensions Directory.
The term extension is generic and the following specific extension types are available (listed alphabetically):
- Component (since
ファイル:Compat icon 1 0.png) – adds custom functions to your site that can be selected from menus
- Language (since
ファイル:Compat icon 1 0.png) – defines an additional language for your site
- Library (since
) – provides functions to be used by other extensions
- Mambot (in
ファイル:Compat icon 1 0.png) – modifies content in articles
- Module (since
ファイル:Compat icon 1 0.png) – shows nonessential data in a side box, possibly on multiple pages
- Package (since
) – bundles related extensions
- Plugin (since
) – modifies content in articles or provides functions to extend other extensions
- Template (since
ファイル:Compat icon 1 0.png) – define the look, feel, and navigation capabilities of your site
For an overview of the most important extension types and the functionality they provide, see Extension types (general definitions).
LDAP
LDAP, or lightweight directory access protocol, is a protocol designed to access directory systems over TCP/IP. Because of this various databases provide an LDAP interface such as Microsoft's Active Directory, Novell's eDirectory, as well as more dedicated LDAP solutions such as OpenLDAP.
With the release of Joomla! 1.5, Joomla! has a native LDAP library (joomla.client.ldap) and a native LDAP authentication plugin. This allows Joomla! 1.5 to authenticate against LDAP systems out of the box.
In Joomla! 1.0, there was no native LDAP library or authentication plugin. The JAuthTools project provides a Joomla! 1.0 solution for authentication without hacks as well as configuration resources for both Joomla! 1.0 and 1.5 LDAP authentication solutions.
You can also read a tutorial on getting started from scratch with LDAP.
LDAP/ja
LDAP, or lightweight directory access protocol, is a protocol designed to access directory systems over TCP/IP. Because of this various databases provide an LDAP interface such as Microsoft's Active Directory, Novell's eDirectory, as well as more dedicated LDAP solutions such as OpenLDAP.
With the release of Joomla! 1.5, Joomla! has a native LDAP library (joomla.client.ldap) and a native LDAP authentication plugin. This allows Joomla! 1.5 to authenticate against LDAP systems out of the box.
In Joomla! 1.0, there was no native LDAP library or authentication plugin. The JAuthTools project provides a Joomla! 1.0 solution for authentication without hacks as well as configuration resources for both Joomla! 1.0 and 1.5 LDAP authentication solutions.
You can also read a tutorial on getting started from scratch with LDAP.
Language
Languages are perhaps the most basic and critical extension type. Languages are packaged as either a core language pack or an extension language pack. These packages consist of INI files which contain key/value pairs. These key/value pairs provide the translation of static text strings within Joomla! source code. This allows both the Joomla! core and third party components and modules to be internaionalised. Core language packs also include an XML meta file describing the language and providing information about the fonts to use for PDF content generation.
Language/ja
Languages are perhaps the most basic and critical extension type. Languages are packaged as either a core language pack or an extension language pack. These packages consist of INI files which contain key/value pairs. These key/value pairs provide the translation of static text strings within Joomla! source code. This allows both the Joomla! core and third party components and modules to be internaionalised. Core language packs also include an XML meta file describing the language and providing information about the fonts to use for PDF content generation.
Menu
In Joomla!, a Menu is a set of menu items. Each menu item defines an URL to a page on your site, and settings that control the contents and style of that page. Additionally, each menu item has an alias that will be used to create human-readable URLs when Search Engine Friendly URLs are on. Menu items can have any number of subitems.
A Menu isn't automatically shown on any page. You need to create a menu module to show the menu on all or some pages. Each menu can be shown by one or more modules (making it possible to show the same menu in different positions). It is also possible to create Split menus.
A Menu that isn't shown by any module is usually called a hidden menu. Hidden menus can be used to create URLs that are not visible on any page.
Menu/ja
In Joomla!, a Menu is a set of menu items. Each menu item defines an URL to a page on your site, and settings that control the contents and style of that page. Additionally, each menu item has an alias that will be used to create human-readable URLs when Search Engine Friendly URLs are on. Menu items can have any number of subitems.
A Menu isn't automatically shown on any page. You need to create a menu module to show the menu on all or some pages. Each menu can be shown by one or more modules (making it possible to show the same menu in different positions). It is also possible to create Split menus.
A Menu that isn't shown by any module is usually called a hidden menu. Hidden menus can be used to create URLs that are not visible on any page.
Model-View-Controller
Joomla makes extensive use of the Model-View-Controller design pattern.
When Joomla is started to process a request from a user, such as a GET for a particular page, or a POST containing form data, one of the first things that Joomla does is to analyse the URL to determine which component will be responsible for processing the request, and hand control over to that component.
If the component has been designed according to the MVC pattern, it will pass control to the controller. The controller is responsible for analysing the request and determining which model(s) will be needed to satisfy the request, and which view should be used to return the results back to the user.
The model encapsulates the data used by the component. In most cases this data will come from a database, either the Joomla database, or some external database, but it is also possible for the model to obtain data from other sources, such as via a web services API running on another server. The model is also responsible for updating the database where appropriate. The purpose of the model is to isolate the controller and view from the details of how data is obtained or amended.
The view is responsible for generating the output that gets sent to the browser by the component. It calls on the model for any information it needs and formats it appropriately. For example, a list of data items pulled from the model could be wrapped into an HTML table by the view.
Since Joomla is designed to be highly modular, the output from the component is generally only part of the complete web page that the user will ultimately see. Once the view has generated the output the component hands control back to the Joomla framework which then loads and executes the template. The template combines the output from the component, and any modules that are active on the current page, so that it can be delivered to the browser as a single page.
To provide additional power and flexibility to web designers, who may only be concerned with creating new designs rather than manipulating the underlying code, Joomla splits the traditional view into a separate view and layout. The view pulls data from the model, as in a traditional MVC pattern, but then simply makes that data available to the layout, which is responsible for formatting the data for presentation to the user. The advantage of having this split is that the Joomla template system provides a simple mechanism for layouts to be overridden in the template. These layout overrides (often called "template overrides" because they form part of the template, although actually it is the layout that is being overridden) are bundled with the template and give the template designer complete control over all the output from the Joomla core and any installed third-party extensions that comply with the MVC design pattern.
See also:
- Developing a Model-View-Controller Component - Part 1
- Developing a Model-View-Controller Component - Part 2 - Adding a Model
- Developing a Model-View-Controller Component - Part 3 - Using the Database
- Developing a Model-View-Controller Component - Part 4 - Creating an Administrator Interface
- Understanding Output Overrides
- Developers
- JModel
- JView
- JController
Model-View-Controller/ja
Joomla makes extensive use of the Model-View-Controller design pattern.
When Joomla is started to process a request from a user, such as a GET for a particular page, or a POST containing form data, one of the first things that Joomla does is to analyse the URL to determine which component will be responsible for processing the request, and hand control over to that component.
If the component has been designed according to the MVC pattern, it will pass control to the controller. The controller is responsible for analysing the request and determining which model(s) will be needed to satisfy the request, and which view should be used to return the results back to the user.
The model encapsulates the data used by the component. In most cases this data will come from a database, either the Joomla database, or some external database, but it is also possible for the model to obtain data from other sources, such as via a web services API running on another server. The model is also responsible for updating the database where appropriate. The purpose of the model is to isolate the controller and view from the details of how data is obtained or amended.
The view is responsible for generating the output that gets sent to the browser by the component. It calls on the model for any information it needs and formats it appropriately. For example, a list of data items pulled from the model could be wrapped into an HTML table by the view.
Since Joomla is designed to be highly modular, the output from the component is generally only part of the complete web page that the user will ultimately see. Once the view has generated the output the component hands control back to the Joomla framework which then loads and executes the template. The template combines the output from the component, and any modules that are active on the current page, so that it can be delivered to the browser as a single page.
To provide additional power and flexibility to web designers, who may only be concerned with creating new designs rather than manipulating the underlying code, Joomla splits the traditional view into a separate view and layout. The view pulls data from the model, as in a traditional MVC pattern, but then simply makes that data available to the layout, which is responsible for formatting the data for presentation to the user. The advantage of having this split is that the Joomla template system provides a simple mechanism for layouts to be overridden in the template. These layout overrides (often called "template overrides" because they form part of the template, although actually it is the layout that is being overridden) are bundled with the template and give the template designer complete control over all the output from the Joomla core and any installed third-party extensions that comply with the MVC design pattern.
See also:
- Developing a Model-View-Controller Component - Part 1
- Developing a Model-View-Controller Component - Part 2 - Adding a Model
- Developing a Model-View-Controller Component - Part 3 - Using the Database
- Developing a Model-View-Controller Component - Part 4 - Creating an Administrator Interface
- Understanding Output Overrides
- Developers
- JModel
- JView
- JController
Module
Modules are lightweight and flexible extensions used for page rendering. These modules are often “boxes” arranged around a component on a typical page. A well-known example is the login module. Modules are assigned per menu item, so you can decide to show or hide (for example) the login module depending on which page (menu item) the user is currently on. Some modules are linked to components: the “latest news” module, for example, links to the content component (com_content) and displays links to the newest content items. However, modules do not need to be linked to components; they don't even need to be linked to anything and can be just static HTML or text.
Modules are managed in the Administrator by the Module Manager (help screen).
See also: Component, Plugin, Template
Module Position
Module positions are placeholders in a template. They identify positions within the template and tell the Joomla! application where to place output from modules assigned to a particular position. The template designer has complete control over module positions, creating variations between templates and the respective Joomla! default positions assigned to modules in the installation sample data.
For example, the module position Left could be defined to be on the left side of the template to display a site navigation menu. So if a module is assigned the Left position, it will be displayed wherever the designer puts that Left module position - not necessarily the left side of the page.
Module Position/ja
Module positions are placeholders in a template where you can place modules. See Module positions for more information.
Module/ja
Modules are lightweight and flexible extensions used for page rendering. Sometimes modules are linked to components such as the “latest news” module which links to the content component (com_content) and displays links to the newest content items. These modules are mostly visible as the “boxes” that are arranged around a component on a typical page, for example, the login module. Modules are assigned per menu item, so, for example, you can decide to show or hide the logon module depending on which component (menu item) is used. However, modules do not need to be linked to components; they don't even need to be linked to anything and can be just static HTML or text.
Modules are managed in the Administrator by the Module Manager (help screen).
See also: Component, Plugin, Template
PHP
PHP is a computer scripting language designed for creating dynamic web pages. PHP is widely-used for web development and can be embedded into HTML. It generally runs on a web server, taking PHP code as its input and creating web pages as output. Joomla! is primarily written using the PHP language. For more information, see Where can you learn about PHP?
PHP/ja
PHP is a computer scripting language designed for creating dynamic web pages. PHP is widely-used for web development and can be embedded into HTML. It generally runs on a web server, taking PHP code as its input and creating web pages as output. Joomla! is primarily written using the PHP language. For more information, see Where can you learn about PHP?
Patch
The term patch file is used for two different file types. The term patch file is sometimes used to refer to archive files that allow you to upgrade from one Joomla! version to another (for example, from version 1.0.0 to version 1.0.7). These upgrade files are also referred to as upgrade packages.
The other meaning for a patch file is a file created by source code version control software -- for example, Subversion or SVN, which is used for the Joomla! source code. This type of patch file contains instructions for changing the contents of one or more source code files. The SVN software reads the patch file and then can automatically change the source code of the files being patched.
Patch files are used by the Bug Squad to test proposed bug fixes. They can also be used to contribute proposed new features to the version under development. For more information about the structure of SVN patch files, read Learn more about patch files.
Patch/ja
The term patch file is used for two different file types. The term patch file is sometimes used to refer to archive files that allow you to upgrade from one Joomla! version to another (for example, from version 1.0.0 to version 1.0.7). These upgrade files are also referred to as upgrade packages.
The other meaning for a patch file is a file created by source code version control software -- for example, Subversion or SVN, which is used for the Joomla! source code. This type of patch file contains instructions for changing the contents of one or more source code files. The SVN software reads the patch file and then can automatically change the source code of the files being patched.
Patch files are used by the Bug Squad to test proposed bug fixes. They can also be used to contribute proposed new features to the version under development. For more information about the structure of SVN patch files, read Learn more about patch files.
Plugin
A plugin is a kind of Joomla! extension. Plugins provide functions which are associated with trigger events. Joomla provides a set of core plugin events, but any extension can fire (custom) events. When a particular event occurs, all plugin functions of the type associated with the event are executed in sequence. This is a powerful way of extending the functionality of the Joomla! Framework. It also offers extension developers a way to allow other extensions to respond to their actions, making extensions extensible.
The Joomla! plugin architecture follows the Observer design pattern. The JPlugin class is derived from JObserver and provides the means to register custom plugin code with core or custom events. The JEventDispatcher class, derived from JObservable, is an event handler which calls all plugins registered for a particular event, when that event is triggered.
Prior to Joomla! 1.5 plugins were known as mambots. Mambots were able to change content only and were based on certain signal words. Since then their scope has been stretched and extended to such an extent that to enhance the meaning of the new functionality the developers decided to change the name from mambots to plugins. Joomla! 1.5 includes legacy support for Joomla! 1.0 mambots.
See also: Component, Module, Template
Plugin/ja
A plugin is a kind of Joomla! extension. Plugins provide functions which are associated with trigger events. Joomla provides a set of core plugin events, but any extension can fire (custom) events. When a particular event occurs, all plugin functions of the type associated with the event are executed in sequence. This is a powerful way of extending the functionality of the Joomla! Framework. It also offers extension developers a way to allow other extensions to respond to their actions, making extensions extensible.
The Joomla! plugin architecture follows the Observer design pattern. The JPlugin class is derived from JObserver and provides the means to register custom plugin code with core or custom events. The JEventDispatcher class, derived from JObservable, is an event handler which calls all plugins registered for a particular event, when that event is triggered.
Prior to Joomla! 1.5 plugins were known as mambots. Mambots were able to change content only and were based on certain signal words. Since then their scope has been stretched and extended to such an extent that to enhance the meaning of the new functionality the developers decided to change the name from mambots to plugins. Joomla! 1.5 includes legacy support for Joomla! 1.0 mambots.
See also: Component, Module, Template
Section
In Joomla! versions up to and including
, a Section is a collection of Categories. It is the top level in the hierarchy Sections -> Categories -> Articles. For example, a website might have Sections called "Animals" and "Plants". Within the "Animals" Section, the website might have Categories such as "Birds" and "Mammals".
Sections are maintained using the Section Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Section Manager menu item.
Section/ja
In Joomla! versions up to and including
, a Section is a collection of Categories. It is the top level in the hierarchy Sections -> Categories -> Articles. For example, a website might have Sections called "Animals" and "Plants". Within the "Animals" Section, the website might have Categories such as "Birds" and "Mammals".
Sections are maintained using the Section Manager (help screen) which can be reached in the Administrator (Back-end) by clicking on the Content menu, then the Section Manager menu item.
Split menus
A split menu is where different levels of a single menu are displayed in two or more locations on a single web page.
For example, a common requirement is for a menu of top-level items to appear at the top of the page. When one of the items is clicked the user is taken to a page where a secondary menu, say on the left of the page, shows second-level items within the scope of the top-level item.
The menus appear in separate locations on the page, but are related because one shows only top-level items while the other shows second-level items. This idea can be extended to include menus for third-level items and beyond.
This can be implemented in Joomla using a single multi-level menu then creating more than one menu module each referring to a different level.
See also: Menu
Split menus/ja
A split menu is where different levels of a single menu are displayed in two or more locations on a single web page.
For example, a common requirement is for a menu of top-level items to appear at the top of the page. When one of the items is clicked the user is taken to a page where a secondary menu, say on the left of the page, shows second-level items within the scope of the top-level item.
The menus appear in separate locations on the page, but are related because one shows only top-level items while the other shows second-level items. This idea can be extended to include menus for third-level items and beyond.
This can be implemented in Joomla using a single multi-level menu then creating more than one menu module each referring to a different level.
See also: Menu
Template
A template is the type of Joomla! extension that changes the way your site looks. There are two types of templates: Front-end Templates and Back-end Templates.
See also: Component, Module, Plugin
Template/ja
A template is the type of Joomla! extension that changes the way your site looks. There are two types of templates: Front-end Templates and Back-end Templates.
See also: Component, Module, Plugin
Upgrade Package
An Upgrade Package in Joomla! is an archive of files that contain the files that have changed between Joomla! versions. When this archive is unpacked, it replaces the old version of the modified files with the new version. For example, if 50 files were changed between version 1.x.1 and 1.x.2, the upgrade package from 1.x..1 to 1.5.2 would contain these 50 files and, when unpacked, would replace these 50 files and upgrade the installed version from 1.x.1 to 1.x.2.
Upgrade Packages are also sometimes referred to as patch files. Before installing an Upgrade Package, read the release notes and the Upgrade Instructions relating to the Upgrade Package.
Upgrade Package/ja
An Upgrade Package in Joomla! is an archive of files that contain the files that have changed between Joomla! versions. When this archive is unpacked, it replaces the old version of the modified files with the new version. For example, if 50 files were changed between version 1.x.1 and 1.x.2, the upgrade package from 1.x..1 to 1.5.2 would contain these 50 files and, when unpacked, would replace these 50 files and upgrade the installed version from 1.x.1 to 1.x.2.
Upgrade Packages are also sometimes referred to as patch files. Before installing an Upgrade Package, read the release notes and the Upgrade Instructions relating to the Upgrade Package.
Version Control Software
Version Control Software is software that automates the process of revising software. The Joomla! project uses a popular open-source version control program called Subversion or SVN. This makes it easy to track each change to each program file and to test and undo changes as needed. See the Wikipedia article for more information on Subversion.
Version Control Software/ja
Version Control Software is software that automates the process of revising software. The Joomla! project uses a popular open-source version control program called Subversion or SVN. This makes it easy to track each change to each program file and to test and undo changes as needed. See the Wikipedia article for more information on Subversion.
