Actions

Talk

Difference between revisions of "Glossary"

From Joomla! Documentation

(Translation Hints: new section)
m (doubled)
Line 42: Line 42:
 
</DPL>
 
</DPL>
 
<noinclude>[[Category:Landing Pages]]{{cathelp|1.5,2.5,3.0,3.1}}</noinclude>
 
<noinclude>[[Category:Landing Pages]]{{cathelp|1.5,2.5,3.0,3.1}}</noinclude>
 
== Translation Hints ==
 
 
Suggested markup for translations
 
 
Will have to work this out, but it does work and will use the /en coding for English pages once they are all marked for translation.
 
<pre>
 
<DPL>
 
category=Glossary definitions/<lang code>
 
notcategorymatch=%Archived%
 
include=*
 
format=,\n== {{#ifexist:%TITLE%|[[%TITLE%|{{:Translations:%TITLE%/Page_display_title/<lang code>‎}}]]|%TITLE%}} ==\n
 
reset=categories
 
resultsheader=__TOC____NOEDITSECTION__
 
</DPL>
 
</pre>
 
  
 
== Translation Hints ==
 
== Translation Hints ==

Revision as of 14:24, 24 February 2014

Notes on how to write a Glossary entry

Create a page for the term (in its singular form if relevant), but instead of entering the text directly include the term as a documentation chunk. Add the page to the Glossary category and if required (which is the norm) add it to the Landing Pages category too. For example, for the term "extension", create a page called "Extension" (the first letter is automatically capitalised so don't worry about that). In the page enter the following text:

{{Chunk:Extension}}
<noinclude>[[Category:Landing Pages]][[Category:Glossary]]</noinclude>

Save the page, then click on the "Chunk:Extension" link that you will see. Enter your glossary explanation there. At the end of the page, add the following text to make it appear in the Glossary. Make sure there is nothing (not even a newline) between the last character of your text and the following.

<noinclude>[[Category:Glossary definitions|{{PAGENAME}}]]</noinclude>

If the term has a commonly used plural form then you should add a redirect to the singular form. To do this create a page for the plural form and add a #REDIRECT statement to it. If required (which is the norm) add it to the Landing Pages category too. Do not add it to the Glossary category. For example, to add the term "extensions" which will redirect to "extension", create a page called "Extensions" and enter the following text:

#REDIRECT [[Extension]]
[[Category:Landing Pages]]

Updating The Glossary

I've marked this page as needs review as

  1. I feel that having Mambots on the list of extensions is plain unhelpful.
  2. I feel there is no need to have Joomla 1.5 references on this list anymore (references to Legacy mode, Sections etc.)
  3. The upgrade package section needs to be updated ironically to mention the Joomla Updated that shipped in 1.7

Before I make this changes how do people feel about removing anything that isn't still relevant from Joomla 1.5 and earlier

Translation Hints

Suggested markup for translations

Will have to work this out, but it does work and will use the /en coding for English pages once they are all marked for translation.

Contents

!

|

[view] [edit] [history]

Template-info.pngArticle documentation
Template:Glossary/doc

!!/doc

This is an auxiliary template allowing to encode "||" within template and parser function parameters. To get both symbols in final output this template is unnecessary, better use "&#124;&#124;" which is rendered the same. Use this template in parameter values of templates and parser functions of which the result is used in table syntax, since this requires the "real" pipe character.

This template cannot be used for putting thes characters as text in a wiki table; in that case, again, "&#124;&#124;" can be used.

Note that the table syntax code "!" (exclamation mark) can be used directly in parameter values, so for that a template like this is not needed.

See also


!-/doc

This is an auxiliary template allowing to encode "|-" within template and parser function parameters. To get these symbols in final output this template is unnecessary, better use "&#124;-" which is rendered the same. Use this template in parameter values of templates and parser functions of which the result is used in table syntax, since this requires the "real" pipe character.

This template cannot be used for putting these characters as text in a wiki table; in that case, again, "&#124;-" can be used.

See also


!/doc

This is an auxiliary template allowing to encode "|" within template and parser function parameters. To get the symbol in final output this template is unnecessary, better use "&#124;" which is rendered the same. Use this template in parameter values of templates and parser functions of which the result is used in table syntax, since this requires the "real" pipe character. The same applies when a parameter is used literally for an internal link and you want to set a label.

This template cannot be used for putting the character as text in a wiki table; in that case, again, "&#124;" can be used.

Note that the table syntax code "!" (exclamation mark) can be used directly in parameter values, as it's only special at the beginning of a line, so for that a template like this is not needed.

See also


"Save as New" and "Save as Copy" removed from article manager after 3.3.4 Upgrade

After upgrading from Joomla v3.3.3 to v3.3.4 The "Save as Copy" and "Save as New" buttons are no longer available when editing an article. I used a backup to revert back to v3.3.3 and all is well.

Errors reported

N/A

Versions affected

Info non-talk.png
General Information

This pertains only to Joomla! version(s):-   

3.3.4

What is the cause

How to fix

-

template:- (edittalklinkshistory) "clears" both margins; it is often used before a header to make sure that header will be the full width of the page.

/doc

Stop!

If you are viewing this page, you may not be aware of the Joomla! Documentation template documentation pattern. Template documentation subpage should be prefixed by the name of the template. Create the glossary for your template on page: Template:TemplateNameGlossary.

Examples:

bad good
Template:/doc Template:Tl/doc
Template:/doc Template:Non-free media/doc
Template:/doc Template:ArticleHistory/doc

Thank you.

01 template-manager styles.png

02 template-manager editing-styles.png

03 menu-manager edit-menu-item.png

1

[view] [edit] [history]

Template-info.pngArticle documentation
Template:Glossary/doc

1-Extensions-ExtensionManager.png

{{:Translations:1.6.4 Installer Deleted My Files/Page_display_title/<lang code>‎}}

For a small number of implementations, the PHP timeout and hosting conditions are such that the Upgrade Process runs out of time before the Installer has had time to finish. In those cases, the upgrade fails and the site is not properly updated and files are missing. In some cases, nearly all files might be missing. Depending on how far the Upgrade process got, the errors you might experience could vary. Generally speaking, you will see some kind of message about missing files.

Although this is a very concerning problem to have, it can be easily fixed. Simply take a full install package for the release, unzip it, DELETE the installation folder, and copy ALL of the remaining files to your website, replacing the files already there. Doing so will fix the install and your website should work fine.

For the future: a work-around fix was applied to Joomla 1.6.4 to help resolve this problem by resetting the PHP time used to 0 during the unzip process and during the file copy process. This will help prevent time out situations and therefore avoid failed updates for the 1.7 upgrade (or 1.6.5, if that release comes first).

{{:Translations:1.6.4 security alert for layout override files/Page_display_title/<lang code>‎}}

Should this be JfilterOutput::ampReplace instead of JfilterOutput:ampReplace?

{{:Translations:1.6.4 security alert for layout override files/Page_display_title/<lang code>‎}}

In version 1.6.4 a security fix was made to a number of layout files, specifically those for category lists for articles, weblinks, newsfeeds and contacts and the featured contact list. If you are using layout overrides for these you should ensure that you make the same changes are made in your template (if the same issue is present). Overrides are found in the html folder of your template. You may also wish to check layout files for extensions for the same issue since the core layouts are sometimes used as models.

The change made is to replace JfilterOutput::ampReplace with htmlspecialchars. The following files should be changed:

  • components/com_contact/views/category/tmpl/default_items.php
  • components/com_contact/views/featured/tmpl/default_items.php
  • components/com_content/views/category/tmpl/default_articles.php
  • components/com_newsfeeds/views/category/tmpl/default_items.php
  • components/com_weblinks/views/category/tmpl/default_items.php

This change should also be made to the override found in the beez5 template

  • templates/beez5/com_content/category/default_articles.php

{{:Translations:1.7.0 Artisteer Template Errors/Page_display_title/<lang code>‎}}

There are reports for upgrades of sites using Artisteer Templates:

Fatal error: Cannot access protected property ContentViewArticle::$user in /home/xyz/public_html/templates/bpmusic_v1/functions.php on line 561

And others report this: Fatal error: Call to a member function getMessageQueue() on a non-object in /home1/xyz/public_html/templates/otd_white/functions.php on line 165

It is also reported that Artisteer plans to release a Joomla 1.7 compatibility release in the next few days.

http://www.artisteer.com/?post_id=170151&p=forum_post&forum_id=20


According to Artisteer Tech Support Artisteer 2.6 is not compatible with Joomla 1.7. Artisteer Tech Support suggests using Artisteer 3.0

This is the reason for the error: "Fatal error: Call to a member function getMessageQueue() on a non-object in /templates/ functions.php on line 165"

{{:Translations:1.7.0 Flash Upload broken/Page_display_title/<lang code>‎}}

The flash uploader is broken in 1.7.0 because the Flash file is outdated.

Solution: replace in media/system/swf/ with this file:

http://joomlacode.org/gf/download/trackeritem/26603/67164/uploader.swf

{{:Translations:1.7.0 Syndication module broken/Page_display_title/<lang code>‎}}

The Syndication module (mod_syndicate) is broken in 1.7.0.

To solve the issue, edit the file modules/mod_syndicate/helper.php, and replace its content by

<?php
/**
 * @version		$Id: helper.php 21913 2011-07-25 05:21:57Z infograf768 $
 * @package		Joomla.Site
 * @subpackage	mod_syndicate
 * @copyright	Copyright (C) 2005 - 2011 Open Source Matters, Inc. All rights reserved.
 * @license		GNU General Public License version 2 or later; see LICENSE.txt
 */
 
// no direct access
defined('_JEXEC') or die;
 
class modSyndicateHelper
{
	static function getLink(&$params)
	{
		$document = JFactory::getDocument();
 
		foreach($document->_links as $link => $value)
		{
			$value = JArrayHelper::toString($value);
			if (strpos($value, 'application/'.$params->get('format').'+xml')) {
				return $link;
			}
		}
 
	}
}

In trunk, was also updated the beez2 and 5 position.css to prevent display of a border for the livemarks.png image.

img { border: 0 none; }

{{:Translations:1.7.0 Update Collection Could Not Open http:/www.joomla.org/update/core/list.xml/Page_display_title/<lang code>‎}}

The Joomla Updater uses the php fopen command.

Those php configurations without fopen enabled will error with the following messages:

Update: :Collection: Could not update http://www.joomla.org/update/core/list.xml

Update: :Collection: Could not update http://www.joomla.org/update/jed/list.xml

You will not be able to use the Updater without enabling fopen for PHP. This is a web hosting issue.

{{:Translations:1.7.0 Warning: set time limit():/Page_display_title/<lang code>‎}}

During upgrade, some are getting errors like this:

Warning: set_time_limit(): Cannot set time limit in safe mode in /usr/sfw/apache2/http/hhh.hh.com/htdocs/libraries/joomla/filesystem/folder.php on line 548

or

Warning: set_time_limit() has been disabled for security reasons in /home/www/88f713b69e9666e8466e69535bceeda4/web/new/libraries/joomla/filesystem/folder.php on line 548

The first error is when safe mode is enabled on the server. Safe mode must be off as indicated on the first installer screen.

The second error is for hosting setttings which have disabled set_time_limit.

Joomla community member Mackelito offers a work around if your host cannot enable set_time_limit for you.

The change was made to prevent timeouts for some hosts which was causing the install to fail. A fix should be available in future releases to first see if the class is enabled before setting the value.

1.7.3.Featured Article Tool Bar.jpg

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


1.7.3.Featured Block Filter.jpg

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


1.7.3.Featured Filter.jpg

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


1.jpg

1/doc

This template performs a single line feed but without the overhead 'code' of the {{I}}. This is much easier to subst, in particular.

Like {{I}} and other members of the indent family of templates it has some beneficial inheritance attributes within wikimarkup.

Actual code content:
<br />

This is a substable formating utility that duplicates the modified line wrapping behavior of {{I}}, but without the ability to indent.

It is thus far less costly of template pre-expansion and post expansion memory limits, making it more suitable for formatting in articles wherein a lot of templates are used pushing such limits. See: Wikipedia:Template:Indent_family_usage

10080-acl-manager-after-update-en.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


16Events

See discussion on list here: http://groups.google.com/group/joomla-dev-general/browse_thread/thread/4c175ad64f051383/84b86ddb60b15295#84b86ddb60b15295

16breadcrumb-screenshot.png

Summary

Screenshot of the breadcrumb module from the front end in Joomla! 1.6 (default template used)

Licensing

GNU head Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.


16breadcrumbs-advancedoptions.png

Summary

Advanced options tab for the breadcrumbs module in Joomla! 1.6

Licensing

GNU head Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.


16breadcrumbs-basicoptions.png

Summary

screenshots of the basic options tab for the breadcrumbs module in Joomla! 1.6

Licensing

GNU head Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.


16custom htmlmod-basicparams.png

Summary

Screenshot of basic parameters fro the custom_html module in Joomla! 1.6

Licensing

GNU head Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.


1and1joomla10.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla11.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla12.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla13.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla14.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla15.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla2.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla3.png

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

1and1joomla4.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla5.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla6.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla7.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla8.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

1and1joomla9.png

Summary

Screen-shot showing HowTo get joomla working on the web-hosting service called 1and1 with kind permission from 1and1's customer services department. The original first appeared on the page http://faq.1and1.com/web_space__access/ftp_account/14.html

Licensing


Creative Commons License
Creative Commons Attribution iconCreative Commons Share Alike icon
This file is licensed under the Creative Commons Attribution ShareAlike 2.5 License

2

[view] [edit] [history]

Template-info.pngArticle documentation
Template:Glossary/doc

2-Extension-Update.png

{{:Translations:2.5.1 User Notes System/Page_display_title/<lang code>‎}}


Joomla Version 2.5.1 User Note System

This new service allows you to create a one to many relationship with notes about each user in your site.

Each user of your site can have notes created and related to the user table.

Accessing the user manager will give you access to this system.

To access the notes feature look for the document icon next to the user name in the user manager user list or access the system from the sub menu after accessing the user manager menu.

This system also has the standard catagory system like articles to allow you to define unlimited categories to organize your notes under.

The user permission system is also working for this system.

The hover tool tips explain what each box could be used for.

This system is only accessible from the administrator side of Joomla at the current time.

3rd party form tool systems can access the tables and display the notes on the front end if that is desired.

2/doc

This template performs what once known as a double-space, in actual fact a double line feed (2x newlines). This is much easier to subst, in particular.

Like {{I2}} and other members of the indent family of templates it has some beneficial inheritance attributes within wikimarkup.

Actual code content:
<br /><br />

This is a substable formating utility that duplicates the modified line wrapping behavior of {{I2}}, but without the ability to indent.

It is thus far less costly of template pre-expansion and post expansion memory limits, making it more suitable for formatting in articles wherein a lot of templates are used pushing such limits. See: Wikipedia:Template:Indent_family_usage

2010soclogo.jpg

Google Summer of Code 2010 official logo.

219jondn

Jon Neubauer

What I Do in Joomla!

Joomla! World Conference Director
Joomla! Bug Squad Contributor
Joomla! Community Magazine Contributor/Editor
Joomla! Forum Moderator

How You Can Reach Me

E-mail Me! jon.neubauer@community.joomla.org
Twitter: @219jondn

25-Installing-template-install-success.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-Installing-template-navigate.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-Installing-template-upload-package-file.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-Switching-templates-1.png

Summary

Screenshot originally uploaded by User:Wilsonge

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-Switching-templates-assign-menus.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-Template manager access.png

Summary

Screenshot, originally uploaded by User:Wilsonge

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


25-article-edit-header.png

Summary

article header information for Joomla! 2.5

Licensing

GNU head Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.


25custom htmlmod-basicparams.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3-Extension-Manager-Update.png

30-Import content from template.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-install-success-es.png

Summary

Mensaje de instalación de plantilla exitosa.

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-install-success-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-install-success-nl.png

30-Installing-template-install-success.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-navigate-es.png

Summary

Acceso al gestor de plantillas desde el menú superior del backend.

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-navigate-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-navigate-nl.png

30-Installing-template-navigate.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-upload-package-file-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-upload-package-file-es.png

Summary

Instalar paquete de plantilla desde el gestor de extensiones.

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-upload-package-file-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Installing-template-upload-package-file-nl.png

30-Menu-item-template-management-edit-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Menu-item-template-management-edit-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Menu-item-template-management-edit-nl.png

30-Switching-templates-1-en.png

Summary

Screenshot with text added.

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Switching-templates-1-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Switching-templates-1-nl.png

30-Switching-templates-assign-menus-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Switching-templates-assign-menus-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Switching-templates-assign-menus-nl.png

30-Template-manager-select-edit-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-select-edit-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-select-edit-nl.png

30-Template-manager-template-cutomise-view.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-style-view-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-style-view-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-style-view-nl.png

30-Template-manager-template-styles-view-1-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-styles-view-1-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-styles-view-1-nl.png

30-Template-manager-template-styles-view-2-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-styles-view-2-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


30-Template-manager-template-styles-view-2-nl.png

30-Template manager access.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3ndriago

Open Source supporter who very often needs community help, so why not give back a little help to it? IT developer, part time blogger and full time technology passionate!

3x-preview-template-template-manager-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-preview-template-template-manager-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-preview-template-template-manager-nl.png

3x-template-manager-customise-template-create-overrides-component-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-component-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-component-nl.png

3x-template-manager-customise-template-create-overrides-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-file-list-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-file-list-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-file-list-nl.png

3x-template-manager-customise-template-create-overrides-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-message-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-message-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-overrides-message-nl.png

3x-template-manager-customise-template-create-overrides-nl.png

3x-template-manager-customise-template-create-upload-file-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-upload-file-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-upload-file-nl.png

3x-template-manager-customise-template-create-upload-file-types-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-upload-file-types-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-create-upload-file-types-nl.png

3x-template-manager-customise-template-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-file-edit-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-file-edit-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-file-edit-nl.png

3x-template-manager-customise-template-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-manage-folders-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-manage-folders-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-manage-folders-nl.png

3x-template-manager-customise-template-nl.png

3x-template-manager-customise-template-popup-copy-en.png

Summary

screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-popup-copy-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-popup-copy-nl.png

3x-template-manager-customise-template-toolbar-en.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-toolbar-fr.png

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-customise-template-toolbar-nl.png

3x-template-manager-templates-file-link.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


3x-template-manager-templates.png

Summary

Screenshot

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


4-Update-Joomla.png

{{:Translations:404.shtml/Page_display_title/<lang code>‎}}

The requested pagename is invalid!

You should have been redirected to the search page if the requested page does not exist, but if an internal link lead you here, the target page name may either contain invalid characters or the string "index.php", which is known to cause trouble.

Temporary workaround

If you are sure the page exists because you followed a "blue link", change the URL in your browser's address bar from
  http://docs.joomla.org/Page_name_causing_trouble
into
  http://docs.joomla.org/index.php?title=Page_name_causing_trouble

The target page should appear so you can read it.

Permanent fix for existing pages

First of all: don't try to move/redirect the page as this will not necessarily resolve the issue if the original page title is still linked to from someplace else.

Here's how you can fix links pointing to a bogus pagename:

  1. navigate to the bogus page using the workaround explained above
  2. click "What links here" in the sidebar to get a list of all pages that link to it
  3. open each page in a new tab/windows and hit edit
  4. prepend the standard wiki-link [[Page name causing trouble]] with the interwiki prefix "self:" [[self:Page name causing trouble|]]
if the regular link did not feature a link caption, use the "pipe trick" as illustrated

Fix for new pages

If you clicked on a "red link" then the target page does not appear to exist. Here's how you may fix that:

  • think of a better name for the target page that does not include strange characters or the string "index.php" and use that in the source page
  • if that is not possible use the interwiki prefix "self:" as explained in the previous section.

If none of the above helps

Post the issue in the Developer Documentation forum, or if you don't have an account for the Joomla! forums (how comes?) leave a note on the talk page. Please sign your entry by adding four tildes ~~~~ or click the "signature" button in the editor's toolbar.

Thank you

404discovery.png

Summary

Image showing 404 URL discovery in Webmaster Tools

Licensing

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


4b40d77049e1f

Test 1

This is a test of the CodeExamples extension.

Chris Davenport 12:44, 3 January 2010 (EST)

4b40dd2c8bfa4

This is a Text

This is a test comment

Alex 13:08, 3 January 2010 (EST)

4b40de8c16165

Hello again

This is it

Batch1211 13:14, 3 January 2010 (EST)

4b40ded8ec548

Why so serious

function hello(){
 echo $this->greeting;
}
Batch1211 13:15, 3 January 2010 (EST)

4ba65300e4b9c

This is a Test

Let's try this

Batch1211 13:10, 21 March 2010 (EDT) Edit comment

4ba6564a424a0

This is a test

This is a test

Batch1211 13:24, 21 March 2010 (EDT) Edit comment

4ba6641e4cb38

This is a Test

This is a Test

Doxiki 14:23, 21 March 2010 (EDT) Edit comment

4ba801dbc7c03

Tree Structures with JNode

JTree and JNode can be used to create and process simple tree structures. Let's see how this works for JNode with a simple example.

We want represent the family structure of the Smiths. Granny Barbara has two daughters. Stefanie and Aunti Sue. Stefanie has two children, Peter and Stewie. Auntie Sue doesn't have children.

Let's take a look how we can represent this familiy in an object tree.

$barbara = new JNode();
$stefanie = new JNode();
$sue = new JNode();
$peter = new JNode();
$stewie = new JNode();
 
//Granny Barbara has two children, stefanie, and sue
$barbara->addChild($stefanie);
$barbara->addChild($sue);
 
/*
 * Sometimes we want declare parent-child relationships the other way around.
 * We can also do that
 */
 
$peter->setParent($stefanie);
$stewie->setParent($stefanie);
Batch1211 19:48, 22 March 2010 (EDT) Edit comment

4ba802c761837

Tree Structures with JTree and JNote

JTree and JNode can be used to create and process simple tree structures. Let's see how this works for JTree with a simple example.

We want to create the Family Tree of the Smiths. Granny Barbara has two daughters. Stefanie and Aunti Sue. Stefanie has two children, Peter and Stewie. Auntie Sue doesn't have children.

Let's take a look how we can represent this familiy in an object tree.

$barbara = new JNode();
$stefanie = new JNode();
$sue = new JNode();
$peter = new JNode();
$stewie = new JNode();
 
$familyTree = new JTree(); //pointer set to root-node
$familyTree->addChild($barbara, true) //pointer set to barbara
$familyTree->addChild($sue) //$sue added as child to barbara, pointer still on barbara
$familyTree->addChild($stefanie, true) //$stefanie added as child to barbara, pointer on stefanie
$familyTree->addChild($peter, true) //$peter added as child to stefanie, pointer on peter
$familyTree->getParent() // pointer set to parent of peter, which is stefanie
$familyTree->addChild($stewie) //$stewie added as child to stefanie, pointer on stefanie
Batch1211 19:52, 22 March 2010 (EDT) Edit comment

4bcfd994b6e12

A typical example of loading MooTools

// This example depends on mootools
JHTML::_('behavior.mootools');
 
// Do something after page has loaded
$document =& JFactory::getDocument();
$document->addScriptDeclaration("window.addEvent('load', function() { doSomething(); })");
Chris Davenport 01:07, 22 April 2010 (EDT) Edit comment

4c4535a92d52f

getInstance example

 
$row =& JTable::getInstance('review', 'Table');
geomaras 00:35, 20 July 2010 (CDT) Edit comment

4c6c50711caa3

No Title

Example:

$query	= $db->getQuery(true);
$query->insert('#__tableName');
 
$query->set('id=4');
 
$db->setQuery( $query );
$result	= $db->loadResult();
Unhindered 16:28, 18 August 2010 (CDT) Edit comment

4ca07516bb7f7

JPagination on Frontpage

Mariska wrote:

if you want to Jpagination work on front page change Jpagination.php

on this code function _buildDataObject bicause this method use to generate link on front end // add "&limit=".$this->limit to $data->[]->link

   function _buildDataObject() {
       // Initialize variables
       $data = new stdClass();
       $data->all = new JPaginationObject(JText::_('View All'));
       if (!$this->_viewall) {
           $data->all->base = '0';
           $data->all->link = JRoute::_("&limit=".$this->limit."&limitstart="); // <== this  
       }
       // Set the start and previous data objects
       $data->start = new JPaginationObject(JText::_('Start'));
       $data->previous = new JPaginationObject(JText::_('Prev'));
       if ($this->get('pages.current') > 1) {
           $page = ($this->get('pages.current') - 2) * $this->limit;
          $page = $page == 0 ?  : $page; //set the empty for removal from route
           $data->start->base = '0';
           $data->start->link = JRoute::_("&limit=".$this->limit."&limitstart="); //<== this
           $data->previous->base = $page;
           $data->previous->link = JRoute::_("&limit=".$this->limit."&limitstart=" . $page); //<== this
       }
       // Set the next and end data objects
       $data->next = new JPaginationObject(JText::_('Next'));
       $data->end = new JPaginationObject(JText::_('End'));
       if ($this->get('pages.current') < $this->get('pages.total')) {
           $next = $this->get('pages.current') * $this->limit;
           $end = ($this->get('pages.total') - 1) * $this->limit;
           $data->next->base = $next;
           $data->next->link = JRoute::_("&limit=".$this->limit."&limitstart=" . $next); // <== this
           $data->end->base = $end;
           $data->end->link = JRoute::_("&limit=".$this->limit."&limitstart=" . $end); // <== this
       }
       $data->pages = array();
       $stop = $this->get('pages.stop');
       for ($i = $this->get('pages.start'); $i <= $stop; $i++) {
           $offset = ($i - 1) * $this->limit
           $offset = $offset == 0 ?  : $offset;  //set the empty for removal from route
           $data->pages[$i] = new JPaginationObject($i);
           if ($i != $this->get('pages.current') || $this->_viewall) {
               $data->pages[$i]->base = $offset;
               $data->pages[$i]->link = JRoute::_("&limit=".$this->limit."&limitstart=" . $offset); //<== this
           }
       }
       return $data;
   }

Batch1211 05:42, 27 September 2010 (CDT) Edit comment

4cc41287689c8

Example

<?php
/* 
    This program is for adding in Jumi module
    It will show the cooperative account of login user
    which store in CSV  file on the server
 
*/
defined('_JEXEC') OR die("Restricted access"); // Prevent direct Access to the program
$user =& JFactory::getUser(); // get user
if ($user->guest) {
    echo "<h3>Please log in to see your report ! </h3>"; // Show this message if user not yet log in
} else {
        // If user log in 
	$id = strtoupper($user->username);   // Get user and store in $id
	$fd = fopen ("http://btc-intranet.ap.bayer.cnb/coop/COOPBAL.csv", "r"); // Open CSV file
    $found=0; 
	while (!feof ($fd)) {
        $buffer = fgetcsv($fd, 4096);  // Get one record
		if(strtoupper($buffer[1]) == $id){
			$found = 1;  // if $id = login name then set flag $found
			break;  // exit loop
        }
	}
	fclose ($fd);
	if($found){   // Display account detail
		echo "<h3> Report of ".$buffer[4]." For the month".$buffer[5]. "</h3><br/>";	
		echo "<h4> Deposit Account of member no ".$buffer[3]."</h4>";
		echo "<table>";
		echo "<tr><td>Last month :</td><td align=\"right\">".$buffer[6]."</td><td> Baht </td></tr>";
		echo "<tr><td>This month :</td><td align=\"right\">".$buffer[7]."</td><td> Baht </td></tr>";
		echo "<tr><td>Next month :</td><td align=\"right\">".$buffer[8]."</td><td> Baht </td></tr>";
		echo "</table>";
		if(!($buffer[9]=="") || !($buffer[13])){
			echo "<h4>Loan account</h4>";
			echo "<table>";
			echo "<tr><td>Last month :</td><td align=\"right\"> ".$buffer[9]."</td><td> Baht </td></tr>";
			echo "<tr><td>Pay this month :</td><td align=\"right\"> ".$buffer[10]."</td><td> Baht </td></tr>";
			echo "<tr><td>Actual Payment :</td><td align=\"right\"> ".$buffer[11]."</td><td> Baht </td></tr>";
			echo "<tr><td>Interest :</td><td align=\"right\"> ".$buffer[12]."</td><td> Baht </td></tr>";
			echo "<tr><td>Next Month begin :</td><td align=\"right\"> ".$buffer[13]."</td><td> Baht </td></tr>";
			echo "</table>";
		}
                echo "<br/>Please check your account <br/>";
	}else{
                // if check to end of file but not found
		echo "<h3>No Account for you, Please let us know if you are member of the Cooperation fund </h3>";    
	}
}
?>


Jeeradate 06:03, 24 October 2010 (CDT) Edit comment

4cfc9888a45a8

Override Default Headers

From: http://groups.google.com/group/joomla-dev-general/browse_thread/thread/6ef5fe7eba4efc26

How can I override the default joomla headers from within a custom component? I would like to change

Expires: Mon, 1 Jan 2001 00:00:00 GMT 
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre- 
check=0 
Pragma: no-cache

to

Expires: ~in five hours~ 
Cache-Control: public 
Pragma: public

JResponse::allowCache(true) did the trick. If it helps anyone else, here is the code that worked for me.

JResponse::allowCache(true); 
JResponse::setHeader('Pragma', 'public',true); 
JResponse::setHeader('Cache-Control','public',true); 
JResponse::setHeader('Expires', gmdate('D, d M Y H:i:s', time() 
+(60*60*5)) . ' GMT',true);
Elin 02:02, 6 December 2010 (CST) Edit comment

4d0a2b2491399

No Title

 
jimport('joomla.error.log');
$log = &JLog::getInstance();
$log->addEntry(array('LEVEL' => '1','STATUS' => 'SOME ERROR:','COMMENT' =>'some comment'));

4d30818ae30fe

Get the name of the document

demo.xml

<jdoc>
	<doku kategory="Info">Wiki</doku>
</jdoc>
<?php
 
$xml = JFactory::getXML('demo.xml');
 
echo $xml->name();

Output:

jdoc

Elkuku 11:02, 14 January 2011 (CST) Edit comment

4d30846f12c6d

Get the element data

demo.xml

<jdoc>
	<doku kategory="Info">Wiki</doku>
</jdoc>
<?php
 
$xml = JFactory::getXML('demo.xml');
 
echo $xml->doku->data();
 
/* Better: */
echo $xml->doku;

Ausgabe:

Wiki

Elkuku 11:14, 14 January 2011 (CST) Edit comment

4d3084f89e0ff

Get the attribute of an element

demo.xml

<jdoc>
	<doku kategory="Info">Wiki</doku>
</jdoc>
<?php
 
$xml = JFactory::getXML('demo.xml');
 
echo $xml->doku->getAttribute('kategory');
 
/* Better: */
echo $xml->doku->attributes()->kategory;

Output:

Info

Elkuku 11:16, 14 January 2011 (CST) Edit comment

4d30874fd792a

Get the whole XML document or a part of it.

demo.xml

<jdoc>
	<doku kategory="Info">Wiki</doku>
</jdoc>

Get the whole XML document or a part of it.

<?php
 
$xml = JFactory::getXML('demo.xml');
 
echo '<pre>';
echo htmlentities($xml->asFormattedXML());
echo '</pre>';

Output:

<jdoc>
	<doku kategory="Info">Wiki</doku>
</jdoc>

Die "komprimierte" Ausgabe, z.B. zur Verwendung in Streams:

$xml->asFormattedXML(true)

Output:

<jdoc><doku kategory="Info">Wiki</doku></jdoc>

Output only a part of the document:

$xml->doku->asFormattedXML()

Output:

<doku kategory="Info">Wiki</doku>


Elkuku 11:26, 14 January 2011 (CST) Edit comment

4d31659b9455f

Simple text strings

    echo JText::_( 'Welcome' );

see also: http://docs.joomla.org/Tutorial:Template_translations

4d48b240a0d42

No Title

Note: At 20110201, the key=>value pairs which are arguments to function setParam (and function getParam) are stored in table jos_users, column params. This may change in the future.

Spicetrader 19:24, 1 February 2011 (CST) Edit comment

4d6cda382364a

May not always work

addCC may not always work on 1.5 due to an error in the phpmailer class. to forum topic.


E-builds 05:36, 1 March 2011 (CST) Edit comment

4d74e424a7c2b

need more info

hi, I am trying to use this go get all the subcategories of a certain category jimport('joomla.application.categories'); $categories = new JCategories('com_content'); print_r($categories); $subCategories = $categories->get(78); print_r($subCategories);

but this gives: JCategories Object ( [_nodes:protected] => [_checkedCategories:protected] => [_extension:protected] => c [_table:protected] => c [_field:protected] => c [_key:protected] => c [_statefield:protected] => c [_options:protected] => com_jumi ) subs:

So my guess is I can't acces the nessacary data because it is protected... any help?

Djemmers 07:56, 7 March 2011 (CST) Edit comment

4d986a88409e6

This function seem not to exists in joomla 1.6.1

I can't find the getGroups function in Joomla 1.6.1 JForm source code. It seems not to exists.

YannCharlou 07:39, 3 April 2011 (CDT) Edit comment

4da60eb68ca0c

Wrong description

Above syntax is wrong and doesn't work in Joomla 1.6.1.

The correct is:

$this->form->setValue($field, $group , $value);

Bornakke 15:59, 13 April 2011 (CDT) Edit comment

4daab65e66059

Example

$bunny = new JObject;
$bunny->set('animalType', 'hare');
$bunny->set('color', 'white');
$bunny->set('ears', 2);
 
$wolfy = new JObject;
$wolfy->setProperties(
                     array(
                           'animalType'=>'wolf',
                           'color'=>'grey',
                           'teeth'=>42,
                           'stomach'=>null
                           )
                     );
 
 
$wolfy->stomach = $bunny;
 
print_r($wolfy);

would output

JObject Object
(
    [_errors] => Array
        (
        )

    [animalType] => wolf
    [color] => grey
    [teeth] => 42
    [stomach] => JObject Object
        (
            [_errors] => Array
                (
                )

            [animalType] => hare
            [color] => white
            [ears] => 2
        )

)

This example was originally provided by Artyom.


Chris Davenport 04:43, 17 April 2011 (CDT) Edit comment

4daab8c55b7a8

Example

Let's say, we want to integrate Error-Handling in our application, but we don't know yet, if we want the error to be display, logged in a file, stored to the database, or all of the above. Our goal is, to keep the object that raises the error independent of the objects that store the error message.

class MyError extends JObservable {
   public $msg = NULL;
 
   function raiseError($msg){
      $this->msg = $msg;
      //Notify all attached ErrorHandlers of the state change.
      $this->notify();
   }
}
 
//We now implement the Observers, thus the error handlers
class ErrorHandlerDisplay extends JObserver {
   function update(){
      echo $this->subject->msg;
   }
}
class ErrorHandlerFileStorage extends JObserver {
   function update(){
      error_log($this->subject->msg;);
   }
}
class ErrorHandlerDB extends JObserver {
   function update(){
      $db = JFactory::getDBO();
      $sql = "INSERT INTO #__myerrors (message) VALUES (".$db->quote($this->subject->msg).")";
      $db->setQuery($sql);
      $db->query();
   }
}
 
//Now we can use newly implemented MyError class to raise Errors.
$error = new MyError();
 
/* The constructor of the observers automatically attaches the observer to the subject
 * In our example that means that the constructor of the error handler automatically
 * attaches the handler to the MyError Object.
 */
new ErrorHandlerDisplay($error);
new ErrorHandlerFileStorate($error);
new ErrorHandlerDB($error);
 
$error->raiseError('Help!!!');
 
/*
 * Would cause 'Help!!!' to be display, logged in a file, and stored in the database.
 * You can simply add and remove the error handlers as you like
 */

What happened here? We separated the functionality of raising an error of the functionality of handling an error. In the future you can add additional ErrorHandlers, or remove some of the existing handlers, without the need to change any classes at all. Furthermore you can simply change an Errorhandler, without the need to change the MyError class. This greatly increases the reusability of your code.

This example was originally provided by Batch1211.


Chris Davenport 04:54, 17 April 2011 (CDT) Edit comment

4daab98b010e3

Example

Let's say, we want to integrate Error-Handling in our application, but we don't know yet, if we want the error to be display, logged in a file, stored to the database, or all of the above. Our goal is, to keep the object that raises the error independent of the objects that store the error message.

class MyError extends JObservable {
   public $msg = NULL;
 
   function raiseError($msg){
      $this->msg = $msg;
      //Notify all attached ErrorHandlers of the state change.
      $this->notify();
   }
}
 
//We now implement the Observers, thus the error handlers
class ErrorHandlerDisplay extends JObserver {
   function update(){
      echo $this->subject->msg;
   }
}
class ErrorHandlerFileStorage extends JObserver {
   function update(){
      error_log($this->subject->msg;);
   }
}
class ErrorHandlerDB extends JObserver {
   function update(){
      $db = JFactory::getDBO();
      $sql = "INSERT INTO #__myerrors (message) VALUES (".$db->quote($this->subject->msg).")";
      $db->setQuery($sql);
      $db->query();
   }
}
 
//Now we can use newly implemented MyError class to raise Errors.
$error = new MyError();
 
/* The constructor of the observers automatically attaches the observer to the subject
 * In our example that means that the constructor of the error handler automatically
 * attaches the handler to the MyError Object.
 */
new ErrorHandlerDisplay($error);
new ErrorHandlerFileStorate($error);
new ErrorHandlerDB($error);
 
$error->raiseError('Help!!!');
 
/*
 * Would cause 'Help!!!' to be display, logged in a file, and stored in the database.
 * You can simply add and remove the error handlers as you like
 */

What happened here? We separated the functionality of raising an error of the functionality of handling an error. In the future you can add additional ErrorHandlers, or remove some of the existing handlers, without the need to change any classes at all. Furthermore you can simply change an Errorhandler, without the need to change the MyError class. This greatly increases the reusability of your code.

This example was originally contributed by Batch1211.


Chris Davenport 04:57, 17 April 2011 (CDT) Edit comment

4dab1e4e1ba2d

Example

$host = 'joomla.org';
$port = 21;
$options = null;
$user = 'randomUserName';
$pass = 'thisIsDefinatlyNotThePassword';
 
jimport('joomla.client.ftp');
 
/*
 * The JFTP::getInstance() method will connect us to the FTP server and automatically
 * log us in. We could do the same with the connect() and login() methods. Also check 
 * out JClientHelper::getCredentials('ftp');
 */
 
$ftp = JFTP::getInstance($host, $port, $options, $user, $pass);
 
if($ftp->isConnected()){
   //We are connected.
 
   //Let's print the details of the root directory
   echo '<pre>';
   print_r($ftp->listDetails());
   echo '</pre>';
 
   /* Assuming we only have one "Joomla" directory, this would look like this.
   Array
   (
    [0] => Array
        (
            [type] => 1
            [rights] => drwxr-xr-x
            [user] => randomUserName
            [group] => ftpusers
            [size] => 4096
            [date] => 03-15
            [time] => 2008
            [name] => Joomla
        )
   )
   */
   //Let's create a directory
   $ftp->mkdir('test');
 
   //Let's create a file in that new directory
   $ftp->create('test/fairyTale.txt');
 
   //Let's write the first line of our Fairy Tale into our newly created text file
   $ftp->write('test/fairyTale.txt', 'Once upon a time, there was a litte Mermaid, called Arielle');
 
   //Let's read the fairy tale out of the file, and echo it out.
   $fairyTale = '';
   $ftp->read('test/fairyTale.txt', $fairyTale);
   echo $fairyTale;
 
   //Let's think of a name for our fairyTale, and rename the file
   $ftp->rename('test/fairyTale.txt', 'test/Arielle.txt');
 
   //I think you got the idea =)
}

This example was originally contributed by User:Batch1211.


Chris Davenport 12:07, 17 April 2011 (CDT) Edit comment

4dab218c50875

Automatically Generated Properties

From 2.5 As of Joomla 2.5, JTable properties are automatically generated based on the schema of the specified table. When you specify a table in a class that extends JTable, the field names are read from the table and set as properties. When using Joomla 1.5, you must manually declare all table columns as properties of the class that extends JTable.


Chris Davenport 12:21, 17 April 2011 (CDT) Edit comment

4dab21dcdb7a8

Reserved Database Field Names

Some of the optional features of JTable require the existence of specially-named fields in the database table. If you require this additional functionality you should ensure that these named fields are present in the table. These field names should be considered reserved as any attempts to use them for purposes other than those supported by JTable may result in conflict.

Field name Methods using the field name
checked_out checkOut, checkIn, isCheckedOut
checked_out_time checkOut, checkIn, isCheckedOut
hits hit
ordering getNextOrder, reorder, move
published publish


Chris Davenport 12:22, 17 April 2011 (CDT) Edit comment

4dab22169ccc3

Check-in/check-out

Joomla tables implement a simple mechanism for preventing a race condition while editing rows in a database. This depends on the existence of database fields called "checked_out" and "checked_out_time" and if these fields are present JTable will automatically support this mechanism so that it can be easily used in your tables too. In addition to the checkOut and checkIn methods, there is a isCheckedOut method to determine if a given table row is currently checked out by another user.


Chris Davenport 12:23, 17 April 2011 (CDT) Edit comment

4dab224eaef1e

Hit counter

Some Joomla tables contain a field called "hits" which records the number of times that a table row has been accessed. JTable provides a simple method to increment this field: hit.


Chris Davenport 12:24, 17 April 2011 (CDT) Edit comment

4dab24ff969cc

Adding support for new document types

New document types are added by creating a new sub-directory under the /libraries/joomla/document/ directory with the same name as the type. For example, to add a document type called "mytype", you would create the directory /libraries/joomla/document/mytype. In this directory you must then create a file called mytype.php which will contain the class definition for JDocumentMytype which extends JDocument. Look at the code for existing document types to see what needs to be done.


Chris Davenport 12:35, 17 April 2011 (CDT) Edit comment

4dab25ee5b352

Adding support for new document renderers

New renderer types are added by creating a new file in the renderer directory under the document type directory with the same name as the renderer. For example, to add a document renderer type called "myrenderer" for document type "mytype", you would create the file /libraries/joomla/document/mytype/renderer/myrenderer.php. This file will contain the class definition for JDocumentRendererMytype which extends JDocumentRenderer. Look at the code for existing document renderers to see what needs to be done.


Chris Davenport 12:39, 17 April 2011 (CDT) Edit comment

4dab2eb7b2abb

Example of Get and Set Methods

Get and set methods are provided for all the component parts of a URI. The following names of the component parts are used:

     http://fredbloggs:itsasecret@www.example.com:8080/path/to/Joomla/index.php?task=view&id=32#anchorthis
     \__/   \________/ \________/ \_____________/ \__/\_______________________/ \_____________/ \________/
      |          |         |              |        |              |                    |            |
   scheme      user       pass          host      port          path                 query       fragment

The example column in the following table illustrates the result of each of the get methods on the URI above.

Get method Set method Description Example
getFragment setFragment Fragment (everything after the '#'). This is often referred to as an anchor. anchorthis
getHost setHost Hostname or IP address. For example, 'www.joomla.org' or '192.168.2.45'. www.example.com
getPass setPass Password part of the authority. itsasecret
getPath setPath Path string. Note that the path always includes the leading "/" character. /path/to/Joomla/index.php
getPort setPort Port number. Specific schemes (protocols) have their own defaults (for example, 'http' is port 80, 'ftp' is port 21). 8080
getQuery setQuery Query in string format. For example, "foo=bar&x=y". See also buildQuery. task=view&id=32
getScheme setScheme Scheme (protocol). For example, 'http', 'https', 'ftp'. http
getUser setUser Username part of the authority. fredbloggs
getVar setVar An individual query item value from within the query part. See also delVar. 32


Chris Davenport 13:17, 17 April 2011 (CDT) Edit comment

4dab2fe9de3d9

Example

$p = JProfiler::getInstance('Application');
 
$p->mark('Start');
$a = str_repeat("hello world!\n", 100000);
$p->mark('Middle');
unset($a);
$p->mark('Stop');
 
print_r($p->getBuffer());

would output

Array
(
    [0] => Application Start: 0.000 seconds, 0.10 MB
    [1] => Application Middle: 0.005 seconds, 1.34 MB
    [2] => Application Stop: 0.005 seconds, 0.10 MB
)

This example was originally contributed by User:Artyom.


Chris Davenport 13:22, 17 April 2011 (CDT) Edit comment

4dab30df74dba

Example

Let's think of an event, that could affect different parts of your application... To keep it simple, we say that we create an onEmailChange event, that is triggered once the user changes his email address. When he does that, we want to display the change to the screen, but we also want to store it to the database. We also know, that there might be some components out there, who would like to implement their own functionality, once the useer changes his email-address.

/*
 * Let's define our concrete Event Handlers. One for the display, one for 
 * database storage
 *
 * The concrete Event Handlers only have to implement the functionality that should
 * be triggered once the event happens. All underlying functionality is implemented
 * by the abstract JEvent and JObserver classes.
 */
class EventHandlerEcho extends JEvent {
public function onEmailChange($user, $oldEmail, $newEmail){
echo $user->name . 'has changed his or her email address: <br/>';
echo 'OldEmail: '.$oldEmail.'<br/>';
echo 'NewEmail: '.$newEmail;
}
}
class EventHandlerDB extends JEvent {
public function onEmailChange($user, $oldEmail, $newEmail){
$db = JFactory::getDBO();
$sql = "UPDATE #__users SET email = ".$db->quote($newEmail)." " .
"WHERE id = " . $db->quote($user->id);
$db->setQuery($sql);
$db->query();
}
}
 
 
//Let's get the global dispatcher
$dispatcher = JDispatcher::getInstance();
 
/*
 * Let's construct the event handlers
 *
 * Since our Eventhandlers are decendents of JEvent, and JEvent is a decendent of JObserver the constructor
 * automatically attaches the eventhandler object to the dispatcher(which is a JObservable descendant).
 * This means when the Event Handlers are initialized they are automatically added to the observer stack of
 * the dispatcher.
 */
new EventHandlerEcho($dispatcher);
new EventHandlerDB($dispatcher);

After the Event Handlers have been created and added to the dispatcher, the event can be triggered from anywhere in the application. This could be in another module, another component, within the framework or even in another plugin.

 //Access the global dispatcher
 $dispatcher = JDispatcher::getInstance();
 
 /*
  * If we wanted, we could see, that our two Event handlers have been added to
  * observer stack of the dispachter before
  */
 
 var_dump($dispatcher->_observers);
 
 //Instead we want to trigger the event, and see what happens
 $user = JFactory::getUser();
 $oldEmail = 'old@email.com';
 $newEmail = 'new@email.com';
 
 $dispatcher->trigger('onEmailChange', array($user, $oldEmail, $newEmail));
 
 /*
  * Both event handlers have been triggered.
  * The email addresses have been displayed. The new one 
  * has been stored to the database
  */

Other components can now create their own concrete Event Handlers for the onEmailChange event and register it to the dispatcher. They will automatically be triggered once the event occurs anywhere in the application.

This example was originally contributed by User:Batch1211.


Chris Davenport 13:26, 17 April 2011 (CDT) Edit comment

4dab31e600c93

Example

Let's think of an event, that could affect different parts of your application... To keep it simple, we say that we create an onEmailChange event, that is triggered once the user changes his email address. When he does that, we want to display the change to the screen, but we also want to store it to the database. We also know, that there might be some components out there, who would like to implement their own functionality, once the useer changes his email-address.

/*
 * Let's define our concrete Event Handlers. One for the display, one for 
 * database storage
 *
 * The concrete Event Handlers only have to implement the functionality that should
 * be triggered once the event happens. All underlying functionality is implemented
 * by the abstract JEvent and JObserver classes.
 */
class EventHandlerEcho extends JEvent {
public function onEmailChange($user, $oldEmail, $newEmail){
echo $user->name . 'has changed his or her email address: <br/>';
echo 'OldEmail: '.$oldEmail.'<br/>';
echo 'NewEmail: '.$newEmail;
}
}
class EventHandlerDB extends JEvent {
public function onEmailChange($user, $oldEmail, $newEmail){
$db = JFactory::getDBO();
$sql = "UPDATE #__users SET email = ".$db->quote($newEmail)." " .
"WHERE id = " . $db->quote($user->id);
$db->setQuery($sql);
$db->query();
}
}
 
 
//Let's get the global dispatcher
$dispatcher = JDispatcher::getInstance();
 
/*
 * Let's construct the event handlers
 *
 * Since our Eventhandlers are decendents of JEvent, and JEvent is a decendent of JObserver the constructor
 * automatically attaches the eventhandler object to the dispatcher(which is a JObservable descendant).
 * This means when the Event Handlers are initialized they are automatically added to the observer stack of
 * the dispatcher.
 */
new EventHandlerEcho($dispatcher);
new EventHandlerDB($dispatcher);

After the Event Handlers have been created and added to the dispatcher, the event can be triggered from anywhere in the application. This could be in another module, another component, within the framework or even in another plugin.

 //Access the global dispatcher
 $dispatcher = JDispatcher::getInstance();
 
 /*
  * If we wanted, we could see, that our two Event handlers have been added to
  * observer stack of the dispachter before
  */
 
 var_dump($dispatcher->_observers);
 
 //Instead we want to trigger the event, and see what happens
 $user = JFactory::getUser();
 $oldEmail = 'old@email.com';
 $newEmail = 'new@email.com';
 
 $dispatcher->trigger('onEmailChange', array($user, $oldEmail, $newEmail));
 
 /*
  * Both event handlers have been triggered.
  * The email addresses have been displayed. The new one 
  * has been stored to the database
  */

Other components can now create their own concrete Event Handlers for the onEmailChange event and register it to the dispatcher. They will automatically be triggered once the event occurs anywhere in the application.

This example was originally contributed by User:Batch1211.

Chris Davenport 13:31, 17 April 2011 (CDT) Edit comment

4dab33b149953

Pagination like Google

Stop hand nuvola.svg.png
Warning!

This is a core hack. Files you change as described on this page will be overwritten during updates of Joomla!. For more information, see Core hack.

  • edit the libraries/joomla/html/pagination.php
  • In the function __construct see the line $displayedPages = 10;
  • Replace the $this->set( 'pages.start',... with the following lines
  $_remainder = $this->get('pages.current') % $displayedPages;
  if($__remainder == 0){
     $this->set( 'pages.start', (floor( $this->get('pages.current') / $displayedPages)) * $displayedPages -4);  
  }elseif($__remainder == 1 and $this->get('pages.current') > $displayedPages){
     $this->set( 'pages.start', (floor( ($this->get('pages.current')-1) / $displayedPages)) * $displayedPages -4);  
  }else{
    $this->set( 'pages.start', (floor( $this->get('pages.current') / $displayedPages)) * $displayedPages + 1);
  }
  • In the function _buildDataObject find the line
 for ($i = $this->get('pages.start'); $i <= $stop; $i ++)
  • In this for loop, find the line
 if ($i != $this->get('pages.current') || $this->_viewall)
  • Add the elseif statement,
 if ($i != $this->get('pages.current') || $this->_viewall)
 {
   $data->pages[$i]->base = $offset;
   $data->pages[$i]->link = JRoute::_("&limitstart=".$offset);
 }elseif($i == $this->get('pages.current')){
   $data->pages[$i]->text = '<b>' . $i . '</b>';
 }

This example was originally contributed by User:Mahboobkhalid.


Chris Davenport 13:38, 17 April 2011 (CDT) Edit comment

4dab51422cbbd

Create a fresh user

/*
 
I handle this code as if it is a snippet of a method or function!!
 
First set up some variables/objects
*/
// get the ACL
$acl =& JFactory::getACL();
 
/* get the com_user params */
 
jimport('joomla.application.component.helper'); // include libraries/application/component/helper.php
$usersParams = &JComponentHelper::getParams( 'com_users' ); // load the Params
 
// "generate" a new JUser Object
$user = JFactory::getUser(0); // it's important to set the "0" otherwise your admin user information will be loaded
 
$data = array(); // array for all user settings
 
// get the default usertype
$usertype = $usersParams->get( 'new_usertype' );
if (!$usertype) {
    $usertype = 'Registered';
}
 
// set up the "main" user information
 
$data['name'] = $firstname.' '.$lastname; // add first- and lastname
$data['username'] = $username; // add username
$data['email'] = $email; // add email
$data['gid'] = $acl->get_group_id( '', $usertype, 'ARO' );  // generate the gid from the usertype
 
/* no need to add the usertype, it will be generated automaticaly from the gid */
 
$data['password'] = $password; // set the password
$data['password2'] = $password; // confirm the password
$data['sendEmail'] = 1; // should the user receive system mails?
 
/* Now we can decide, if the user will need an activation */
 
$useractivation = $usersParams->get( 'useractivation' ); // in this example, we load the config-setting
if ($useractivation == 1) { // yeah we want an activation
 
    jimport('joomla.user.helper'); // include libraries/user/helper.php
    $data['block'] = 1; // block the User
    $data['activation'] =JUtility::getHash( JUserHelper::genRandomPassword() ); // set activation hash (don't forget to send an activation email)
 
}
else { // no we need no activation
 
    $data['block'] = 0; // don't block the user
 
}
 
if (!$user->bind($data)) { // now bind the data to the JUser Object, if it not works....
 
    JError::raiseWarning('', JText::_( $user->getError())); // ...raise an Warning
    return false; // if you're in a method/function return false
 
}
 
if (!$user->save()) { // if the user is NOT saved...
 
    JError::raiseWarning('', JText::_( $user->getError())); // ...raise an Warning
    return false; // if you're in a method/function return false
 
}
 
return $user; // else return the new JUser object

This example was originally contributed by User:Bembelimen


Chris Davenport 15:44, 17 April 2011 (CDT) Edit comment

4dade689c06c7

Example

This method is most often used to get a reference to the global application object, in which case it can be called with no arguments. In this example, the application object is obtained so that a test can be made to see if the code is running on the front-end (client is 'site') or the back-end (client is 'administrator').

$app =& JFactory::getApplication();
if ($app->isSite())  echo 'Client is site';
if ($app->isAdmin()) echo 'Client is administrator';
Chris Davenport 14:46, 19 April 2011 (CDT) Edit comment

6-Final.png

A2Ggeir

Geir Thomas Jakobsen is a webdeveloper at A2G Grafisk AS in Bergen, Norway. He has worked with component development and hacks for Joomla for about 2 years.

Now working on: Learning the new 1.6 ish, woot!

ACHRAF

PAGINA EN CONSTRUCCION

ACL Action Access Component

  • Access Component. Open the component manger screens (User Manager, Menu Manager, Article Manager, and so on).

ACL Action Admin Login

  • Admin Login. Login to the back end of the site.

ACL Action Configure

  • Configure. Access the Options screen for a component.

ACL Action Create

  • Create. Create an object in the component (for example, create a user, article, contact, and so on).

ACL Action Delete

  • Delete. Delete an object in the component (for example, delete a user, article, contact, and so on).

ACL Action Edit

  • Edit. Edit an object in the component (for example, edit a user, article, contact, and so on).

ACL Action Edit Own

  • Edit Own. Edit component objects created by you. This is the same as the Edit action except that it only applies to objects created by the current user.

ACL Action Edit State

  • Edit State. Change the published state of an object in the component. Normal states include Published, Unpublished, Archived, and Trashed.

ACL Action Site Login

  • Site Login. Login to the front end of the site.

ACL Action Super Admin

  • Super Admin. Grants the user "super user" status. Users with this permission can do anything on the site. Only users with this permission can change Global Configuration settings (this screen). These permissions cannot be restricted. It is important to understand that, if a user is a member of a Super Admin group, any other permissions assigned to this user are irrelevant. The user can do anything action on the site. However, Access Levels can still be assigned to control what this group sees on the site. (Obviously, a Super Admin user can change Access Levels if they want to, so Access Levels do not totally restrict what a Super Admin user can see.)

ACL Calculated Settings

Important Note: The Calculated Settings column is only updated after you press the Save button. If you make changes to the permissions settings, press the Save button to see the updated Calculated settings.

The following values may be shown in the Calculated Settings column.

  • Allowed. Help16-ACL-Allowed.pngThis action is allowed for this group. This is because the action has been allowed at this level or at a higher level in the component/group hierarchy.
  • Not Allowed. Help16-ACL-Not-Allowed.pngThis action is not allowed for this group. This is because the action has not been allowed anywhere in the component/group hierarchy. This setting can be overridden.
  • Not Allowed (Locked). Help16-ACL-Not-Allowed-Locked.pngThis action is not allowed for this group. This is because the action has been denied at this level or a higher level in the component/group hierarchy. This setting can not be overridden at this level or for any lower level in the component/group hierarchy.

ACL Groups

  • Groups. Permissions are set for one group at a time. Click on the desired group to open the slider for that group.

ACL Help Screens

Access Control List or ACL is according to the Wikipedia definition, “...ACL specifies which users or system processes are granted access to objects, as well as what operations are allowed to be performed on given objects.” In the case of Joomla there are two separate aspects to its Access Control List which site administrators can control:

  • Which users can gain access to what parts of the website? For example, will a given menu choice be visible for a given user? A registered user can view, but the public at large cannot. Perhaps the menu choice is hidden from all except an Editor user and higher.
  • What operations (or actions) can a user perform on any given object? For example, can a user listed as an "Editor" submit an article or only edit an existing article. The ACL settings could allow submitting and editing, or allow a change an article's category, add tags or any combination.

The implementation of ACL in Joomla was substantially changed in the Joomla! 2.5 series which allowed for more flexibility in groups and permissions.



You are viewing a list of Help Screen pages under the category called Glossary.

ACL Help Screens/ca

Llista de Control d'accés o ACL està d'acord amb la [de la Wiquipedia], "...ACL especifica que els usuaris o sistema són els processos de permetre l'accés a objectes, així com quines operacions es poden realitzar a objectes donats." En el cas de Joomla hi ha separat en dues aspectes de la seva Llista de Control d'Accés que els administradors del web pot controlar:

  • Què usuaris poden accedir a quines parts del lloc web? Per exemple, tindran una opció de menú determinat de ser visible per a un usuari determinat? Un usuari registrat ho pot veure, però el públic en general no pot. Potser l'opció de menú està oculta a tots, excepte un usuari Editor i superior.
  • Quines operacions (o accions) pot realitzar un usuari en un objecte donat? Per exemple, un usuari pot figurar com "Editor" Enviar un article o només editar un article existent. Els paràmetres de l'ACL podrien permetre la submissió i l'edició, o permetre fer un canvi de categoria d'un article, afegir etiquetes o qualsevol combinació.

La implementació d'ACL a Joomla es va canviar substancialment a les series de Joomla! 2.5, que va permetre una major flexibilitat en els grups i permisos.



Estàs veient una llista de pàgines d'ajuda en pantalla sota la categoria anomenada "'Glossary"'.

ACL Help Screens/da

Access Control List or ACL is according to the Wikipedia definition, “...ACL specifies which users or system processes are granted access to objects, as well as what operations are allowed to be performed on given objects.” In the case of Joomla there are two separate aspects to its Access Control List which site administrators can control:

  • Which users can gain access to what parts of the website? For example, will a given menu choice be visible for a given user? A registered user can view, but the public at large cannot. Perhaps the menu choice is hidden from all except an Editor user and higher.
  • What operations (or actions) can a user perform on any given object? For example, can a user listed as an "Editor" submit an article or only edit an existing article. The ACL settings could allow submitting and editing, or allow a change an article's category, add tags or any combination.

The implementation of ACL in Joomla was substantially changed in the Joomla! 2.5 series which allowed for more flexibility in groups and permissions.



Du ser en liste over hjælpe skærmsider under kategorien kaldet Glossary.

ACL Help Screens/en

Access Control List or ACL is according to the Wikipedia definition, “...ACL specifies which users or system processes are granted access to objects, as well as what operations are allowed to be performed on given objects.” In the case of Joomla there are two separate aspects to its Access Control List which site administrators can control:

  • Which users can gain access to what parts of the website? For example, will a given menu choice be visible for a given user? A registered user can view, but the public at large cannot. Perhaps the menu choice is hidden from all except an Editor user and higher.
  • What operations (or actions) can a user perform on any given object? For example, can a user listed as an "Editor" submit an article or only edit an existing article. The ACL settings could allow submitting and editing, or allow a change an article's category, add tags or any combination.

The implementation of ACL in Joomla was substantially changed in the Joomla! 2.5 series which allowed for more flexibility in groups and permissions.



You are viewing a list of Help Screen pages under the category called Glossary.

ACL Help Screens/es

Una Lista de Control de Acceso o ACL (Access Control List) es, de acuerdo con su definición de Wikipedia, “...una forma de determinar los permisos de acceso apropiados a un determinado objeto”, así como qué operaciones pueden realizarse sobre un objeto dado. En el caso de Joomla, hay dos aspectos diferentes relativos a la Lista de Control de Acceso que los administradores del sitio pueden controlar:

  • ¿Qué usuarios pueden conseguir acceso a qué partes del sitio? Por ejemplo, ¿podrá una opción de menú determinada ser visible para un usuario concreto? Un usuario registrado puede verla, pero el público en general no. Quizás la opción de menú está oculta para todos excepto para un usuario Editor o superior.
  • ¿Qué operaciones (o acciones) puede llevar a cabo un usuario sobre un objeto determinado? Por ejemplo, ¿puede un usuario listado como "Editor" enviar un artículo o sólo editar uno existente? Las opciones de ACL podrían permitir enviar y editar, o permitir un cambio de categoría del artículo, añadir etiquetas o cualquier combinación.

La implementación de la ACL en Joomla! cambió sustancialmente en la versión 2.5, que permitió más flexibilidad en los grupos y permisos.



Está viendo una lista de páginas de Pantallas de Ayuda bajo la categoría Glossary.

ACL Help Screens/fr

La Liste de Contrôle d'Accès ou ACL (Access Control List) est selon la définition de Wikipédia, "...une liste d’Access Control Entry (ACE) ou entrée de contrôle d'accès donnant ou supprimant des droits d'accès à une personne ou un groupe". Dans le cas de Joomla!, deux aspects distincts de cette liste de contrôle d'accès permettent aux administrateurs de sites de contrôler :

  • Quels utilisateurs peuvent accéder à quelles parties du site? Par exemple, est-ce qu'un choix de menu donné sera visible pour un utilisateur donné ? Un utilisateur enregistré peut le voir, mais le grand public ne le pourra pas. Peut-être que le choix de menu est caché pour tous sauf pour un Editeur ou supérieur.
  • Quelles sont les opérations (ou actions) pouvant être réalisées par un utilisateur sur un objet donné ? Par exemple, est-qu'un utilisateur listé en tant qu'"Editeur" peut soumettre un article ou seulement modifier un article existant. Les paramètres d'ACL peuvent autoriser à soumettre et à modifier, ou autoriser un changement de catégorie d'article, ajouter des tags ou toute combinaison.

L'implémentation d'ACL dans Joomla! a été sensiblement modifiée dans les versions Joomla! 2.5 permettant une plus grande flexibilité au niveau des groupes et des permissions.



Vous êtes en train de consulter une liste de pages d'Écran d'aide pour la catégorie Écrans d'aide pour les listes de contrôle d'accès (ACL).

ACL Help Screens/nl

Access Control List of ACL is volgens de Wikipedia definitie, “...ACL bepaalt welke gebruikers of systeemprocessen toegang wordt verleend tot objecten, alsmede welke handelingen mogen worden uitgevoerd op die objecten.” Binnen Joomla zijn er twee aparte aspecten aan de Access Control List die websitebeheerders kunnen instellen:

  • Welke gebruikers hebben toegang tot welke delen van de website? Bijvoorbeeld, is een bepaalde menu-optie zichtbaar voor een bepaalde gebruiker? Een geregistreerde gebruiker kan bekijken, maar het grote publiek niet. Misschien is de menu keuze voor iedereen verborgen behalve voor een gebruiker met auteursrechten en hoger.
  • Welke handelingen (of acties) kan een gebruiker uitvoeren op een bepaald object? Bijvoorbeeld, kan een gebruiker met de rechten "Redacteur" een artikel indienen of alleen een bestaand artikel bewerken. De ACL-instellingen kunnen indienen en bewerken toestaan of het wijzigen van een artikelcategorie, toevoegen van tags of een combinatie daarvan.

De uitvoering van ACL in Joomla is aanzienlijk veranderd in Joomla! 2.5, waardoor het mogelijk is meer flexibiliteit in groepen en rechten toe te passen.



U bekijkt een lijst met Help Screen pagina's onder de categorie genaamd "'Glossary"'.

ACL Help Screens/ru

Согласно определения Википедии, Access Control List [список контроля доступа] или ACL, “...ACL указывает каким пользователям или системным процессам предоставляется доступ к объектам, а также какие операции разрешаются осуществлять над данными объектами.” В случае с [системой] Joomla, существуют два отдельных аспекта ее ACL [списка контроля доступа], которые администраторы веб-сайта могут контролировать:

  • Какие пользователи к какой части веб-сайта получают доступ? Например, будет ли данное выбранное меню видимо данному пользователю? Зарегистрированный пользователь сможет, но общая публика - нет. Возможно, выбор этого меню скрыт ото всех, за исключением пользователей-редакторов и пользователей с высшим [правом доступа].
  • Какие операции (или действия) какой-либо пользователь может осуществлять над любым конкретным объектом? Например, может ли пользователь, показанный как "Editor"[/редактор] создать какой-либо материал или [он может] только редактировать какой-либо существующий материал? Настройки ACL могут разрешить создание и редактирование, или разрешить вносить изменения в категорию данного материала, [или] разрешить добавлять метки, или [разрешить] любую комбинацию [из этого].

Применение ACL [списка контроля доступа] в Joomla было существенно изменено в серии [версий] Joomla! 2.5, что предоставило группам и правам больше гибкости.



Вы просматриваете список веб-страниц с экранами справки для категории под названием Glossary.

ACL Publish.png

ACL Select New Setting

The Select New Setting Options as as follows:

  • Inherited. Inherited from a parent group or a higher level in the component hierarchy. Can result in this action being allowed or not allowed for this group, depending on what permission is set at a higher level in the group/component hierarchy.
  • Allowed. This action is allowed for this group.
  • Allowed - Conflict. Help16-ACL-Conflict.pngThis group is given Allowed permission for this action. However, this permission is overridden by a Denied permission at a higher level in the group/component hierarchy. So this group does not have permission for this action and will show as Not Allowed in the calculated Setting column.
  • Denied. This action is denied for this group. This will also deny this action for any groups or components at a lower level in the group/component hierarchy.

ADFS-ConfigJoomla1.5.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-ConfigJoomla1.6.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.

ADFS-ConfigWindowsLiveID-Joomla1.5.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-ConfigWindowsLiveID-Joomla1.6.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.

ADFS-ConfigWindowsLiveID.png

ADFS-ConfigWindowsLiveIDJoomla.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-1.png

Summary

ADFS-RelyingPartyTrustConfig-1.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-10.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-11.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-12.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-13.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-2.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-3.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-4.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-5.png

ADFS-RelyingPartyTrustConfig-6.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-7.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-8.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


ADFS-RelyingPartyTrustConfig-9.png

Licensing:

Documentation all together tranparent small.png
Joomla Electronic Documentation License

This article is licensed under the Joomla! Electronic Documentation License. It grants you certain rights to use, modify and distribute documentation associated with the Joomla! project. It is designed to foster wide electronic distribution of Joomla! documentation while ensuring that any material added to the documentation by you or others can be taken up and made part of the authoritative documentation distributed by the Joomla! project.


{{:Translations:ADFS 2.0 Relying Party Trust Configuration/Page_display_title/<lang code>‎}}

This document explains how to configure the Relying Party Trust in ADFS 2.0 manually.

Prerequisites

  1. Relying party identifier
  2. Token encryption certificate(.crt file)
  3. WS-Federation Passive redirection URL.

Installation
The below screen captures will show you how to set up the ADFS Relying Party Trust manually.

  1. ADFS 2.0 Management

    Open ADFS 2.0 Management tool from Administrative tools

    AD FS 2.0 Management

  2. Relying Party Trust Wizard

    Relying Party Trust Wizard

  3. Select Data Source

    Select the option ‘Enter data bout the relying party manually’

    Select Data Source

  4. Specify Display Name

    Provide the display name for the relying party. This is the friendly name that can be used to quickly identify the relying party in ADFS 2.0 Management Console.
    For simplicity, we recommend this to be same as the relying party identifier.

    Specify Display Name

  5. Choose Profile

    Select the option ‘ADFS 2.0 profile’

    Choose Profile

  6. Configure Certificate - Optional

    If you need the response encrypted, please choose your certificate file here.

    Configure Certificate - Optional

  7. Configure URL

    Configure the WS Federation Passive protocol URL

    Configure URL

  8. Configure Identifiers

    Configure identifier for relying party

    Configure Identifiers

  9. Choose Issuance Authorization Rules

    Choose Issuance Authorization Rules

  10. Open Claim Rules

    After finishing the configuration, you can choose to open the claim rules dialog directly

    Open Claim Rules

  11. Edit Claim Rules

    Edit Claim Rules

  12. Select Rule Template

    Choose ‘Send LDAP Attributes as Claims’

    Select Rule Template

  13. Edit Rule

    Edit the required claims. You need to provide ‘Name ID’ outgoing claim type as mandatory

    Edit Rule

Known Limitations

  • Current solution is tested for keys with 1024 size. This might show you a warning while configuring the certificate.


References

  • Configure Relying Party Trust Manually
  • Open SSL Commands to create test certificates
    • openssl genrsa -des3 -out adfs-simplesaml.key 1024
    • openssl rsa -in adfs-simplesaml.key -out adfs-simplesaml.pem
    • openssl req -new -key adfs-simplesaml.key -out adfs-simplesaml.csr
    • openssl x509 -req -in adfs-simplesaml.csr -signkey adfs-simplesaml.key -out adfs-simplesaml.crt

{{:Translations:AJAX/Page_display_title/<lang code>‎}}

This category is for documentation on using AJAX in Joomla Extensions.

{{:Translations:AJAX/Page_display_title/<lang code>‎}}

Copyedit.png
This Article Needs Your Help

This article is tagged because it NEEDS IMPROVEMENT. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.


Asynchronous JavaScript and XML or AJAX, is a term for a group of interrelated web development techniques used for creating interactive web applications or commonly known as web 2.0. Ajax allows web applications to retrieve data from the server asynchronously in the background without interfering with the display and behavior of the existing website page. Data is retrieved using the XMLHttpRequest object or through the use of Remote Scripting in browsers that do not support it.

Using AJAX in Joomla

Javascript Resources:

  1. jQuery
  2. MooTools
  3. Prototype
  4. Script.aculo.us
  5. Help I Don’t Know JavaScript Blog

AJAX/bg

Тази категория е предназначена за документация за използване на AJAX в Joomla.

AJAX/ca

Aquesta categoria és per a la documentació sobre l'ús d'AJAX a extensions de Joomla.

AJAX/en

This category is for documentation on using AJAX in Joomla Extensions.

AJAX/es

Esta categoría es para documentación sobre la utilización de AJAX en Extensiones para Joomla.

AJAX/fr

Cette catégorie se rapporte à la documentation pour l'utilisation d'AJAX dans les extensions Joomla.

AJAX/nl

Deze categorie is voor documentatie over het gebruik van AJAX in Joomla extensies.

AJAX/ru

Эта категория предназначена для документации по использованию AJAX в расширениях Joomla.

AJAX and Content History menu items are displaying in the components menu

When a site is upgraded from Joomla 3.1 to 3.2 using FTP or another manual upgrade, a number of extensions show up through the discover install method.

Versions affected

Info non-talk.png
General Information

This pertains only to Joomla! version(s):- 3.2.x


What is the cause

When Discovery Install is used for those extensions, AJAX and Content History show up in Components sub-menu.

How to fix

Create a backup, then delete the "com_ajax" entry in the _menu table (you can search for it in the title column). Afterward, delete the "com_contenthistory" entry in the same table.

You can remove that using phpMyAdmin dropping the row in #__menu that refers to com_ajax.

DELETE FROM `#__menu` WHERE component_id = (SELECT extension_id FROM `#__extensions` WHERE `name` = 'com_ajax')

Replace #_ with your prefix

ANVGC

dckdekfk ffkrfkrfkrfkrfk flgmlennf clelel

{{:Translations:API/Page_display_title/<lang code>‎}}

The Joomla Content Management System (CMS) is built on top of a core of code which presents a standard Application programming interface or API to the applications built on it.

Although Joomla 1.0.x (and its predecessor, Mambo) had a core of code with a defined API, this was not well-structured and did not use modern design practices. The development of Joomla 1.5 presented the opportunity to completely restructure the foundations and resulted in the Joomla Framework which introduced design patterns such as Model-View-Controller (MVC) and Observer to the Joomla codebase. Although it is possible to build web applications on top of the Joomla Framework without involving the Joomla CMS some dependencies still exist and this continues to be true to a lesser degree with Joomla 1.6.

It has long been the plan to distribute the core Framework separately from the CMS, making it easier to build and distribute non-CMS applications without the overhead of having to include some of the CMS code. This plan is finally coming to fruition with the newly-branded Joomla Platform. Currently slated for its first release on 30 April 2011, this will be developed in a separate repository and on a different release cycle to the CMS.

See Also

Aaleksanyants

Հարգելի հայրենակիցներ,

Կոչ եմ անում միանալ Joomla-ի միջերեսի և ուղեցույցի Հայերեն թարգմանության գործընթացին։ Գրանցվե՜ք docs.joomla.org կայքում և տողեք ձեր հաղորդագրությունը User_talk:Aaleksanyants էջում։

--Aaleksanyants (talk) 04:58, 27 June 2015 (CDT)

Aaqqok

thank you ,i very happy,Your blog disger very well.

About


The Joomla! Documentation Wiki contains collaborative community-contributed documentation for the Joomla! project.

Documentation Policies and Guidelines

Documentation Help

JDOC Projects (Helping with documentation)

Our documentation relies on will volunteers to help write and maintain our articles. Please think about helping by joining a documentation project. Check out our listing of all Doc Projects or here are a specific few.

Joomla! Electronic Documentation License

Privacy policy

About/ar


إن جوملا ويكي التوثيق يحتوي مساهمات توثيق مجتمع تعاوني امشروع جوملا!

سياسات والمبادئ التوجيهية للتوثيق

مساعدة التوثيق

مشاريع JDOC (المساعدة بالتوثيق)

التوثيق الخاص بنا يعتمد على مجموعة من المتطوعين لكتابة والمحافظة على مقالاتنا . الرجاء التفكير بالمساعدة من خلال الاشتراك بمشروع توثيق. انظر الى اللائحة الخاصة بنا مشاريع التوثيق أو هنا يوجد البعض

رخصة جوملا! للوثائق الالكترونية

سياسة الخصوصية

About/en


The Joomla! Documentation Wiki contains collaborative community-contributed documentation for the Joomla! project.

Documentation Policies and Guidelines

Documentation Help

JDOC Projects (Helping with documentation)

Our documentation relies on will volunteers to help write and maintain our articles. Please think about helping by joining a documentation project. Check out our listing of all Doc Projects or here are a specific few.

Joomla! Electronic Documentation License

Privacy policy

About/es


La Wiki de documentación de Joomla! contiene documentación colaborativa de la comunidad, para el proyecto Joomla!.

Políticas y Directrices de Documentación

Documentación De Ayuda

Proyectos JDOC (Ayudando con la documentación)

Nuestra documentación se basa en el aporte de voluntarios para ayudar a escribir y mantener nuestros artículos. Por favor, piensa en ayudar al unirte a un proyecto de documentación. Echa un vistazo a nuestro listado de todos los Proyectos de Documentación o este pequeño listado.

Licencia de Documentación Electrónica Jooomla!

Política de privacidad

About/fr


La documentation Wiki de Joomla! est une documentation collaborative élaborée par la communauté pour le Projet Joomla.

Politiques et lignes directrices de la documentation

Aide de la documentation

Projets JDOC (aide à la documentation)

Notre documentation repose sur la bonne volonté des bénévoles à contribuer à l'écriture et la mise à jour de nos articles. Aidez-nous en rejoignant le projet de la documentation. Consultez notre liste de tous les projets de la documentation ou en voici quelques uns :

Joomla! Electronic Documentation License

Politique de confidentialité

About/nl


De Joomla! documentatie Wiki bevat door de community bijgedragen documentatie voor het Joomla! project.

Documentatiebeleid en richtlijnen

Documentatie hulp

JDOC projecten (Helpen met documentatie)

Onze documentatie is gebaseerd op of vrijwilligers willen helpen met schrijven en onderhouden van onze artikelen. Denk aub na over het helpen door aan een documentatie project deel te nemen. Bekijk onze lijst met alle Documentatie projecten of hier staan er een paar.

Joomla! elektronische documentatie licentie

Privacybeleid

{{:Translations:About CSS page layouts/Page_display_title/<lang code>‎}}

Professional websites separate styling from content. There are many reasons for this, the most obvious (to a developer) being the ability to control the appearance of many pages by changing one file. Styling information includes: fonts; backgrounds; images (that recur on every page); position and dimensions of elements on the page. Your HTML file will now be left with: header information; a series of elements; the text of your website. Because you are creating a Joomla! template, you will actually have: some header information; php code to request the rest of the header information; a series of elements; php code to request each module position; php code to request the main content.

Style information is coded in CSS, cascading style sheet, and usually stored in files with the extension .css. A webpage contains a link to the associated .css file so a browser can find the appropriate style information to apply to the page. CSS can also be placed inside a html file between <style type="text/css"></style> tags.

All CSS code is applied to an element of the html/xml page. If you want a style to encompass a whole page, you would probably apply it to the <body> element. You can apply styles to any html element such as <p>, <table> or <div> elements. To style a particular element it needs to have an ID. For example, to apply styles to the <div> containing the title, you would first include an ID in the html - <div ID="title">.

About CSS page layouts/1/de

Professionelle Webseiten trennen Stil von Inhalt. Es gibt viele Gründe dafür, die offensichtlichste (für Entwickler) ist die Fähigkeit zur Steuerung der Darstellung von vielen Seiten durch die Änderung von nur einer Datei. Stilinformationen enthalten: Schriften; Hintergründe; Bilder (die sich auf jeder Seite wiederholen); Positionen und Abmessungen der Elemente auf der Seite. Die HTML-Datei wird nun versehen mit: Header-Informationen, einer Reihe von Elementen, dem Text der Webseite. Da Sie ein Joomla! Template erstellen haben Sie nun: einige Headerinformationen, PHP-Code zum anfordern der Header-Informationen; eine Reihe von Elementen; PHP-Code, um jede Modulposition abzufragen; PHP-Code um den Hauptinhalt anzufordern.

About CSS page layouts/1/en

Professional websites separate styling from content. There are many reasons for this, the most obvious (to a developer) being the ability to control the appearance of many pages by changing one file. Styling information includes: fonts; backgrounds; images (that recur on every page); position and dimensions of elements on the page. Your HTML file will now be left with: header information; a series of elements; the text of your website. Because you are creating a Joomla! template, you will actually have: some header information; php code to request the rest of the header information; a series of elements; php code to request each module position; php code to request the main content.

About CSS page layouts/1/es

Sitios web profesionales separan el estilo del contenido. Hay muchas razones para esto, la más obvia (para un desarrollador) la capacidad de controlar la apariencia de muchas páginas con el cambio de un solo archivo. La información de estilo incluye: tipografías; antecedentes; imágenes (que se repiten en cada página), posición y dimensiones de los elementos en la página. El archivo HTML ahora quedará con: información de la cabecera; una serie de elementos; el texto de tu sitio web. Debido a que estás creando la plantilla de un sitio Joomla!, que en realidad tiene: información del encabezado; código php para solicitar el resto de la información de la cabecera; una serie de elementos; código php para la solicitud de cada posición de los módulo; código php para solicitar el contenido principal.

About CSS page layouts/1/fr

Les professionnels du web on tendance à toujours séparer le style et le contenu. Il existe plusieurs raisons à cela et la plus évidente (pour un développeur) est la capacité à contrôler l'apparence de différentes pages en modifiant un unique fichier. Les informations portant sur le style peuvent comprendre les polices de caractères, les fonds, les images (qui se répètent sur plusieurs pages), les positions et les dimensions des éléments de la page. Votre fichier HTML présentera dès lors des informations pour l'en-tête, une série d'éléments et le texte de votre site web. Pour travailler avec un template Joomla, vous devrez renseigner certaines informations d'en-tête et du code php pour obtenir le reste de l'information d'en-tête, une série d'éléments, du code php pour déterminer chaque position de module et du code php pour appeler le contenu principal.

About CSS page layouts/1/hi

पेशेवर वेबसाइटों की सामग्री में शैली को अलग रखा जाता है। इस के लिए कई कारण हैं, (एक बनानेवाले डेवलपर के लिए) सबसे स्पष्ट, एक फ़ाइल को बदलकर कई पृष्ठों की उपस्थिति नियंत्रित करने की क्षमता मिल जाती है। शैली की जानकारी में जो चीज़े शामिल होती है, वह है: फोंट; पृष्ठभूमि; चित्र (जो हर पेज पर दोबारा हों सकती है); पेज पर स्तिथि और तत्वों के आयाम। आपकी HTML फ़ाइल अब इन के साथ छोड़ दी जाएगी: हेडर सूचना; तत्वों की एक श्रृंखला; अपनी वेबसाइट के पाठ। आप एक जूमला का नमूना (टेम्पलेट) पैदा कर रहे हैं!, आपके पास होगी: कुछ हेडर सूचना; PHP कोड जो बाकि की हेडर सूचना के अनुरोध करने के लिए; तत्वों की एक श्रृंखला; PHP कोड प्रत्येक मॉड्यूल की स्थिति का अनुरोध करने के लिए; PHP कोड मुख्य सामग्री का अनुरोध करने के लिए।

About CSS page layouts/1/it

I siti web professionali separano lo stile dal contenuto. Ci sono molte ragioni, la più evidente (per gli sviluppatori) è la capacità di controllare l'aspetto di molte pagine cambiando un solo file. Le informazioni sullo stile includono: font; sfondi; immagini (che si ripetono in ogni pagina); la posizione e le dimensioni degli elementi della pagina. Il file HTML sarà con: informazioni nell'header; una serie di elementi; il testo del tuo sito web. Stai creando un template di Joomla! dove vi sono: alcune informazioni nell'header; codice php per richiedere il resto delle informazioni dell'header; una serie di elementi di codice php per la richiesta di ogni posizione modulo; codice php per richiedere il contenuto principale.

About CSS page layouts/1/nl

Professionele websites scheiden de vormgeving van de inhoud. Daar zijn verschillende redenen voor; de meest duidelijke (voor ontwikkelaars) is dat je het uiterlijk van veel pagina's kunt regelen door één bestand te veranderen. Styling informatie bevat: lettertypen, achtergronden, afbeeldingen (die op elke pagina terugkomen), positie en dimensies van elementen op de pagina. Uw HTML bestand bevat: header-informatie, een serie elementen en de tekst van uw website. Omdat u een Joomla!-template maakt, zult u het volgende hebben: header-informatie, php-code om de rest van de header-informatie op te vragen, een serie elementen, php-code om de moduleposities op te vragen en php-code om de belangrijkste inhoud op te vragen.

About CSS page layouts/1/ro

Site-urile profesionale separă stilizarea de conținut. Sunt multe motive pentru a face acest lucru, însă, cel mai evident (pentru un programator) este posibilitatea de a controla modul în care arată un număr multiplu de pagini prin schimbarea unui singur fișier. Informațiile referitoare la stil includ: fonturi; fundaluri; imagini (care se repetă pe fiecare pagină); pozițita și dimensiunile elementelor de pe pagină. Fișierul dumneavoastră HTML va conține acum: informații despre header; o serie de elemente; textul site-ului dumneavoastră. Deoarece creați un template Joomla!, veți avea: unele informații din header, cod php care să ceară restul informațiilor din header; o serie de elemente; cod php care să ceară poziția fiecărui modul; cod php care să ceară conținutul principal.

About CSS page layouts/1/ru

В профессиональных сайтах стили представления отделены от содержимого. На это существует много причин. Самая очевидная (для разработчика) это иметь возможность контролировать внешний вид многих страниц путем изменения одного файла. Информация о стиле включает в себя: шрифты; обои; картинки (которые повторяются на каждой странице); положение и размеры элементов на странице. Ваш HTML-файл теперь будет содержать: заголовочную информацию; серию элементов; текст Вашего сайта. Когда Вы создаете Joomla! шаблон, у Вас имеются: некоторые сведения из заголовка; PHP-код для запроса оставшейся информации для заголовка ; ряд элементов; PHP-код для заполнения каждого модуля и позиции; PHP-код с запросом на основное содержание.

About CSS page layouts/2/de

Stilinformationen werden in CSS (Cascading Style Sheet) codiert und in der Regel in Dateien mit der Erweiterung .css gespeichert. Eine Webseite enthält einen Link zu der zugehörigen .css-Datei. So kann ein Browser die entsprechenden Stil-Angaben für die Seite finden. CSS kann auch innerhalb einer HTML-Datei zwischen <style type="text/css"></style> Tags gesetzt werden.

About CSS page layouts/2/en

Style information is coded in CSS, cascading style sheet, and usually stored in files with the extension .css. A webpage contains a link to the associated .css file so a browser can find the appropriate style information to apply to the page. CSS can also be placed inside a html file between <style type="text/css"></style> tags.

About CSS page layouts/2/es

El estilo de la información está codificado en CSS, hojas de estilo en cascada y generalmente se almacenan en archivos con la extensión .css. Una página web contiene un enlace a los archivos asociados .css, por lo que un navegador puede encontrar la información del estilo adecuado para aplicar a la página. CSS también puede ser colocado dentro de un archivo html entre la etiquetas <style type="text/css"></style>.

About CSS page layouts/2/fr

Les informations de style sont codées en CSS, feuille de style en cascade, et généralement stockées dans des fichiers ayant pour extension .css. Une page web contiendra un lien vers le fichier .css associé permettant ainsi au navigateur de trouver les informations de style à appliquer à la page. Les CSS peuvent également être placés à l'intérieur d'un fichier html entre les balises <style type="text/css"></style>.

About CSS page layouts/2/hi

शैली की जानकारी CSS (Cascading Style Sheet) में कोड की जाती है, और आमतौर पर .CSS विस्तार के साथ फाइल में रेखी जाती है। एक वेब पेज में .CSS की फाइल से जोड़े जाने वाले लिंक मौजूद होते है जो पृष्ठ पर लागू करने के लिए उचित शैली के बारे में जानकारी पा सकते हैं| CSS HTML फाइल के शैली टैग <style type="text/css"></style> के भीतर भी रखी जा सकती है|

About CSS page layouts/2/it

Le informazioni sullo stile sono codificate nel CSS, cascading style sheet, e di solito vengono memorizzate nei file con estensione .css. Una pagina web contiene un link al file .css associato, così il browser è in grado di trovare le opportune informazioni di stile da applicare alla pagina. Il CSS può anche essere inserito all'interno di un file html tra i tag <style type="text/css"></style>.

About CSS page layouts/2/nl

Stijl-informatie wordt gecodeerd in CSS (Cascading Style Sheets) en meestal opgeslagen in bestanden met de extensie .css. Een webpagina bevat een link naar het bijbehorende .css-bestand, zodat een browser de juiste stijl-informatie kan vinden om toe te passen op de pagina. CSS kan ook in een HTML-bestand worden opgenomen, tussen <style type="text/css"></style> tags.

About CSS page layouts/2/ro

Informațiile referitoare la stil sunt codate în CSS, listă de stiluri în cascadă, și sunt de obicei stocate în fișiere cu extensia .css. O pagină web conține un link către fișierul .css asociat acesteia, astfel încât un motor de căutare să poată găsi informația referitoare la stilul respectiv și să o aplice paginii. CSS poate fi deasemenea situat în interiorul unui fisier HTML între tagurile <style type="text/css"></style>.

About CSS page layouts/2/ru

Информация о стиле кодируется в CSS, каскадных таблицах стилей, и обычно хранится в файлах с суффиксом .css. Веб-страница содержит ссылку на связанный с ними .css-файл(ы), поэтому браузер может найти соответствующую информацию о стиле, чтобы применить его к странице. CSS может также быть размещена внутри HTML-файла между тегами <style type="text/css"></style>.

About CSS page layouts/3/de

Der gesamte CSS-Code wird auf ein Element der HTML/XML-Seite angewendet. Wenn Sie eine komplette Seite gestalten wollen, würden Sie ihn vermutlich auf das <body>-Element anwenden. Sie können Stile auf jedes HTML-Element wie <p>, <table> oder <div> anwenden. Um ein bestimmtes Element zu gestalten braucht dieses eine ID. Um beispielsweie ein <div> welches, den Titel enthält, zu gestalten, würden Sie diesem zunächst eine ID im HTML-Code zuweisen: <div id="title">.

About CSS page layouts/3/en

All CSS code is applied to an element of the html/xml page. If you want a style to encompass a whole page, you would probably apply it to the <body> element. You can apply styles to any html element such as <p>, <table> or <div> elements. To style a particular element it needs to have an ID. For example, to apply styles to the <div> containing the title, you would first include an ID in the html - <div ID="title">.

About CSS page layouts/3/es

Todo el código CSS se aplica a un elemento de la página html/xml. Si quieres un estilo para abarcar toda la página, probablemente debas aplicar al elemeto <body>. Puedes aplicar estilos a cualquier elemento html como elementos <p>, <table> o <div>. El estilo de un elemento en particular es necesario que disponga de un ID. Por ejemplo, para aplicar estilos a un <div> que contiene el título, primero tendría que incluir un ID en el html <div ID="title">.

About CSS page layouts/3/fr

Le code CSS s'applique à un élément déterminé de la page html/xml. Si vous souhaitez qu'un style s'applique à l'ensemble de la page, il vous sera probablement nécessaire de l'appliquer à l'élément <body>. Vous pouvez appliquer des styles à n'importe quel élément html comme <p>, <table> ou <div>. Pour le style d'un élément particulier, il devra avoir un ID. Par exemple, pour appliquer des styles à la balise <div> contenant le titre, vous devrez d'abord inclure un ID dans le html <div ID="title">.

About CSS page layouts/3/hi

सभी CSS कोड HTML / XML पेज के एक तत्व को लागू किया जाता है। अगर आप एक शैली में एक पूरे पेज की धरना चाहते हैं, तो आप शायद <body> तत्व पर इसे लागू करेंगे। आप इस तरह <p> </ nowiki>, <nowiki> <table> </ nowiki> या <nowiki> <div> </ nowiki> तत्वों के रूप में किसी भी HTML तत्व पर शैलियों को लागू कर सकते हैं। एक विशेष तत्व की शैली के लिए एक ID की जरुरत होती है। उदाहरण के लिए, आप <nowiki> <div> </ nowiki> जिसमें उपाधि है, शैलियों को लागू करने के लिए, आप HTML में इस तरह <Nowiki> <div id = "title"> </ nowiki> - एक आईडी भी शामिल करेंगे। == {{#ifexist:About CSS page layouts/3/it|[[About CSS page layouts/3/it|{{:Translations:About CSS page layouts/3/it/Page_display_title/<lang code>‎}}]]|About CSS page layouts/3/it}} == Tutto il codice CSS è applicato ad un elemento di una pagina html/xml. Se vuoi uno stile che riguardi l'intera pagina, è probabile che si applichi all'elemento <body>. È possibile applicare gli stili a qualsiasi elemento html come gli elementi <nowiki><p>, <table> o <div>. Per applicare lo stile ad uno specifico elemento, è necessario disporre di un ID. Per esempio, per applicare gli stili al <div> contenente il titolo, devi prima includere un ID nel codice html - <div ID="title">.

About CSS page layouts/3/nl

Alle CSS-code wordt toegepast op een element van de HTML/XML-pagina. Als u wilt dat een stijl de hele pagina omvat, zou u het moeten toepassen op het <body> element. U kunt stijlen toepassen op elk HTML-element, zoals <p>, <table> of <div> elementen. Om de stijl van een specifiek element te regelen heeft het een ID nodig. Om bijvoorbeeld stijlen toe te passen op de <div> die de titel bevat, moet u eerst een ID opnemen in de HTML: <div ID="title">.

About CSS page layouts/3/pt

Todo o código CSS é aplicado a um elemento do html/xml página. Se você quer um estilo para abranger toda uma página, provavelmente iria aplicá-lo para o <body> elemento. Pode aplicar estilos a qualquer elemento html, tal como <p>, <table> ou <div>. Ao estilo de um elemento em particular, ele precisa ter um ID. Por exemplo, para aplicar estilos ao <div> contendo o título, seria o primeiro a incluir uma IDENTIFICAÇÃO em html <div ID="title">.

About CSS page layouts/3/ro

Întregul cod CSS este aplicat unui element al paginii html/xml. Dacă doriți ca un stil să fie prezent pe toată pagina, ar trebui să îl aplicați elementului <body>. Puteți aplica stiluri oricărui element html cum ar fi <p>, <table> sau <div>. Pentru a stiliza un anumit element acesta trebuie să aibă un ID. De exemplu, pentru a aplica stiluri elementelor <div> care conțin titlul, mai întâi trebuie să includeți un ID în html - <div ID="title">.

About CSS page layouts/3/ru

Весь код CSS применяется к элементу внутри HTML/XML страницы. Если вы хотите оформить определенным стилем всю страницу, вы, вероятно, примените его к элементу <body>. Вы можете применить стили для элементов HTML, таких как <p>, <table> или <div>. Стиль конкретного элемента должен иметь идентификатор (параметр "id"). Например, чтобы применить стили к <div> содержащий заголовок, Вы должны сначала включить парампетр "id" в HTML вот таким образом - <div ID="title">.

About CSS page layouts/4/de

About CSS page layouts/4/en

About CSS page layouts/4/es

About CSS page layouts/4/fr

About CSS page layouts/4/hi

श्रेणी: नमूने श्रेणी: CSS

About CSS page layouts/4/it

About CSS page layouts/4/nl

About CSS page layouts/4/pt

Categoria:Modelos Categoria:CSS

About CSS page layouts/4/ro

About CSS page layouts/4/ru

About CSS page layouts/Page display title/de

Über CSS Seitenlayouts

About CSS page layouts/Page display title/en

About CSS page layouts

About CSS page layouts/Page display title/es

Sobre diseños de página CSS

About CSS page layouts/Page display title/fr

À propos des mises en page CSS

About CSS page layouts/Page display title/hi

CSS पेज के ख़ाके के बारे में

About CSS page layouts/Page display title/it

I CSS delle pagine

About CSS page layouts/Page display title/nl

Over CSS pagina layouts

About CSS page layouts/Page display title/pt

Sobre CSS, layouts de página

About CSS page layouts/Page display title/ro

Despre layout-uri de pagină CSS

About CSS page layouts/Page display title/ru

О CSS-слоях страниц

{{:Translations:About CSS page layouts/de/Page_display_title/<lang code>‎}}

Professionelle Webseiten trennen Stil von Inhalt. Es gibt viele Gründe dafür, die offensichtlichste (für Entwickler) ist die Fähigkeit zur Steuerung der Darstellung von vielen Seiten durch die Änderung von nur einer Datei. Stilinformationen enthalten: Schriften; Hintergründe; Bilder (die sich auf jeder Seite wiederholen); Positionen und Abmessungen der Elemente auf der Seite. Die HTML-Datei wird nun versehen mit: Header-Informationen, einer Reihe von Elementen, dem Text der Webseite. Da Sie ein Joomla! Template erstellen haben Sie nun: einige Headerinformationen, PHP-Code zum anfordern der Header-Informationen; eine Reihe von Elementen; PHP-Code, um jede Modulposition abzufragen; PHP-Code um den Hauptinhalt anzufordern.

Stilinformationen werden in CSS (Cascading Style Sheet) codiert und in der Regel in Dateien mit der Erweiterung .css gespeichert. Eine Webseite enthält einen Link zu der zugehörigen .css-Datei. So kann ein Browser die entsprechenden Stil-Angaben für die Seite finden. CSS kann auch innerhalb einer HTML-Datei zwischen <style type="text/css"></style> Tags gesetzt werden.

Der gesamte CSS-Code wird auf ein Element der HTML/XML-Seite angewendet. Wenn Sie eine komplette Seite gestalten wollen, würden Sie ihn vermutlich auf das <body>-Element anwenden. Sie können Stile auf jedes HTML-Element wie <p>, <table> oder <div> anwenden. Um ein bestimmtes Element zu gestalten braucht dieses eine ID. Um beispielsweie ein <div> welches, den Titel enthält, zu gestalten, würden Sie diesem zunächst eine ID im HTML-Code zuweisen: <div id="title">.

{{:Translations:About CSS page layouts/en/Page_display_title/<lang code>‎}}

Professional websites separate styling from content. There are many reasons for this, the most obvious (to a developer) being the ability to control the appearance of many pages by changing one file. Styling information includes: fonts; backgrounds; images (that recur on every page); position and dimensions of elements on the page. Your HTML file will now be left with: header information; a series of elements; the text of your website. Because you are creating a Joomla! template, you will actually have: some header information; php code to request the rest of the header information; a series of elements; php code to request each module position; php code to request the main content.

Style information is coded in CSS, cascading style sheet, and usually stored in files with the extension .css. A webpage contains a link to the associated .css file so a browser can find the appropriate style information to apply to the page. CSS can also be placed inside a html file between <style type="text/css"></style> tags.

All CSS code is applied to an element of the html/xml page. If you want a style to encompass a whole page, you would probably apply it to the <body> element. You can apply styles to any html element such as <p>, <table> or <div> elements. To style a particular element it needs to have an ID. For example, to apply styles to the <div> containing the title, you would first include an ID in the html - <div ID="title">.

{{:Translations:About CSS page layouts/es/Page_display_title/<lang code>‎}}

Sitios web profesionales separan el estilo del contenido. Hay muchas razones para esto, la más obvia (para un desarrollador) la capacidad de controlar la apariencia de muchas páginas con el cambio de un solo archivo. La información de estilo incluye: tipografías; antecedentes; imágenes (que se repiten en cada página), posición y dimensiones de los elementos en la página. El archivo HTML ahora quedará con: información de la cabecera; una serie de elementos; el texto de tu sitio web. Debido a que estás creando la plantilla de un sitio Joomla!, que en realidad tiene: información del encabezado; código php para solicitar el resto de la información de la cabecera; una serie de elementos; código php para la solicitud de cada posición de los módulo; código php para solicitar el contenido principal.

El estilo de la información está codificado en CSS, hojas de estilo en cascada y generalmente se almacenan en archivos con la extensión .css. Una página web contiene un enlace a los archivos asociados .css, por lo que un navegador puede encontrar la información del estilo adecuado para aplicar a la página. CSS también puede ser colocado dentro de un archivo html entre la etiquetas <style type="text/css"></style>.

Todo el código CSS se aplica a un elemento de la página html/xml. Si quieres un estilo para abarcar toda la página, probablemente debas aplicar al elemeto <body>. Puedes aplicar estilos a cualquier elemento html como elementos <p>, <table> o <div>. El estilo de un elemento en particular es necesario que disponga de un ID. Por ejemplo, para aplicar estilos a un <div> que contiene el título, primero tendría que incluir un ID en el html <div ID="title">.

{{:Translations:About CSS page layouts/fr/Page_display_title/<lang code>‎}}

Les professionnels du web on tendance à toujours séparer le style et le contenu. Il existe plusieurs raisons à cela et la plus évidente (pour un développeur) est la capacité à contrôler l'apparence de différentes pages en modifiant un unique fichier. Les informations portant sur le style peuvent comprendre les polices de caractères, les fonds, les images (qui se répètent sur plusieurs pages), les positions et les dimensions des éléments de la page. Votre fichier HTML présentera dès lors des informations pour l'en-tête, une série d'éléments et le texte de votre site web. Pour travailler avec un template Joomla, vous devrez renseigner certaines informations d'en-tête et du code php pour obtenir le reste de l'information d'en-tête, une série d'éléments, du code php pour déterminer chaque position de module et du code php pour appeler le contenu principal.

Les informations de style sont codées en CSS, feuille de style en cascade, et généralement stockées dans des fichiers ayant pour extension .css. Une page web contiendra un lien vers le fichier .css associé permettant ainsi au navigateur de trouver les informations de style à appliquer à la page. Les CSS peuvent également être placés à l'intérieur d'un fichier html entre les balises <style type="text/css"></style>.

Le code CSS s'applique à un élément déterminé de la page html/xml. Si vous souhaitez qu'un style s'applique à l'ensemble de la page, il vous sera probablement nécessaire de l'appliquer à l'élément <body>. Vous pouvez appliquer des styles à n'importe quel élément html comme <p>, <table> ou <div>. Pour le style d'un élément particulier, il devra avoir un ID. Par exemple, pour appliquer des styles à la balise <div> contenant le titre, vous devrez d'abord inclure un ID dans le html <div ID="title">.

{{:Translations:About CSS page layouts/hi/Page_display_title/<lang code>‎}}

पेशेवर वेबसाइटों की सामग्री में शैली को अलग रखा जाता है। इस के लिए कई कारण हैं, (एक बनानेवाले डेवलपर के लिए) सबसे स्पष्ट, एक फ़ाइल को बदलकर कई पृष्ठों की उपस्थिति नियंत्रित करने की क्षमता मिल जाती है। शैली की जानकारी में जो चीज़े शामिल होती है, वह है: फोंट; पृष्ठभूमि; चित्र (जो हर पेज पर दोबारा हों सकती है); पेज पर स्तिथि और तत्वों के आयाम। आपकी HTML फ़ाइल अब इन के साथ छोड़ दी जाएगी: हेडर सूचना; तत्वों की एक श्रृंखला; अपनी वेबसाइट के पाठ। आप एक जूमला का नमूना (टेम्पलेट) पैदा कर रहे हैं!, आपके पास होगी: कुछ हेडर सूचना; PHP कोड जो बाकि की हेडर सूचना के अनुरोध करने के लिए; तत्वों की एक श्रृंखला; PHP कोड प्रत्येक मॉड्यूल की स्थिति का अनुरोध करने के लिए; PHP कोड मुख्य सामग्री का अनुरोध करने के लिए।

शैली की जानकारी CSS (Cascading Style Sheet) में कोड की जाती है, और आमतौर पर .CSS विस्तार के साथ फाइल में रेखी जाती है। एक वेब पेज में .CSS की फाइल से जोड़े जाने वाले लिंक मौजूद होते है जो पृष्ठ पर लागू करने के लिए उचित शैली के बारे में जानकारी पा सकते हैं| CSS HTML फाइल के शैली टैग <style type="text/css"></style> के भीतर भी रखी जा सकती है|

सभी CSS कोड HTML / XML पेज के एक तत्व को लागू किया जाता है। अगर आप एक शैली में एक पूरे पेज की धरना चाहते हैं, तो आप शायद <body> तत्व पर इसे लागू करेंगे। आप इस तरह <p> </ nowiki>, <nowiki> <table> </ nowiki> या <nowiki> <div> </ nowiki> तत्वों के रूप में किसी भी HTML तत्व पर शैलियों को लागू कर सकते हैं। एक विशेष तत्व की शैली के लिए एक ID की जरुरत होती है। उदाहरण के लिए, आप <nowiki> <div> </ nowiki> जिसमें उपाधि है, शैलियों को लागू करने के लिए, आप HTML में इस तरह <Nowiki> <div id = "title"> </ nowiki> - एक आईडी भी शामिल करेंगे। <noinclude> [[श्रेणी: नमूने]] [[श्रेणी: CSS]] </noinclude> == {{#ifexist:About CSS page layouts/it|[[About CSS page layouts/it|{{:Translations:About CSS page layouts/it/Page_display_title/<lang code>‎}}]]|About CSS page layouts/it}} == <noinclude><languages /></noinclude> I siti web professionali separano lo stile dal contenuto. Ci sono molte ragioni, la più evidente (per gli sviluppatori) è la capacità di controllare l'aspetto di molte pagine cambiando un solo file. Le informazioni sullo stile includono: font; sfondi; immagini (che si ripetono in ogni pagina); la posizione e le dimensioni degli elementi della pagina. Il file HTML sarà con: informazioni nell'header; una serie di elementi; il testo del tuo sito web. Stai creando un template di Joomla! dove vi sono: alcune informazioni nell'header; codice php per richiedere il resto delle informazioni dell'header; una serie di elementi di codice php per la richiesta di ogni posizione modulo; codice php per richiedere il contenuto principale. Le informazioni sullo stile sono codificate nel CSS, cascading style sheet, e di solito vengono memorizzate nei file con estensione .css. Una pagina web contiene un link al file .css associato, così il browser è in grado di trovare le opportune informazioni di stile da applicare alla pagina. Il CSS può anche essere inserito all'interno di un file html tra i tag <style type="text/css"></style>. Tutto il codice CSS è applicato ad un elemento di una pagina html/xml. Se vuoi uno stile che riguardi l'intera pagina, è probabile che si applichi all'elemento <body>. È possibile applicare gli stili a qualsiasi elemento html come gli elementi <nowiki><p>, <table> o <div>. Per applicare lo stile ad uno specifico elemento, è necessario disporre di un ID. Per esempio, per applicare gli stili al <div> contenente il titolo, devi prima includere un ID nel codice html - <div ID="title">.

{{:Translations:About CSS page layouts/nl/Page_display_title/<lang code>‎}}

Professionele websites scheiden de vormgeving van de inhoud. Daar zijn verschillende redenen voor; de meest duidelijke (voor ontwikkelaars) is dat je het uiterlijk van veel pagina's kunt regelen door één bestand te veranderen. Styling informatie bevat: lettertypen, achtergronden, afbeeldingen (die op elke pagina terugkomen), positie en dimensies van elementen op de pagina. Uw HTML bestand bevat: header-informatie, een serie elementen en de tekst van uw website. Omdat u een Joomla!-template maakt, zult u het volgende hebben: header-informatie, php-code om de rest van de header-informatie op te vragen, een serie elementen, php-code om de moduleposities op te vragen en php-code om de belangrijkste inhoud op te vragen.

Stijl-informatie wordt gecodeerd in CSS (Cascading Style Sheets) en meestal opgeslagen in bestanden met de extensie .css. Een webpagina bevat een link naar het bijbehorende .css-bestand, zodat een browser de juiste stijl-informatie kan vinden om toe te passen op de pagina. CSS kan ook in een HTML-bestand worden opgenomen, tussen <style type="text/css"></style> tags.

Alle CSS-code wordt toegepast op een element van de HTML/XML-pagina. Als u wilt dat een stijl de hele pagina omvat, zou u het moeten toepassen op het <body> element. U kunt stijlen toepassen op elk HTML-element, zoals <p>, <table> of <div> elementen. Om de stijl van een specifiek element te regelen heeft het een ID nodig. Om bijvoorbeeld stijlen toe te passen op de <div> die de titel bevat, moet u eerst een ID opnemen in de HTML: <div ID="title">.

{{:Translations:About CSS page layouts/pt/Page_display_title/<lang code>‎}}

Professional websites separate styling from content. There are many reasons for this, the most obvious (to a developer) being the ability to control the appearance of many pages by changing one file. Styling information includes: fonts; backgrounds; images (that recur on every page); position and dimensions of elements on the page. Your HTML file will now be left with: header information; a series of elements; the text of your website. Because you are creating a Joomla! template, you will actually have: some header information; php code to request the rest of the header information; a series of elements; php code to request each module position; php code to request the main content.

Style information is coded in CSS, cascading style sheet, and usually stored in files with the extension .css. A webpage contains a link to the associated .css file so a browser can find the appropriate style information to apply to the page. CSS can also be placed inside a html file between <style type="text/css"></style> tags.

Todo o código CSS é aplicado a um elemento do html/xml página. Se você quer um estilo para abranger toda uma página, provavelmente iria aplicá-lo para o <body> elemento. Pode aplicar estilos a qualquer elemento html, tal como <p>, <table> ou <div>. Ao estilo de um elemento em particular, ele precisa ter um ID. Por exemplo, para aplicar estilos ao <div> contendo o título, seria o primeiro a incluir uma IDENTIFICAÇÃO em html <div ID="title">.


Categoria:Modelos Categoria:CSS

{{:Translations:About CSS page layouts/ro/Page_display_title/<lang code>‎}}

Site-urile profesionale separă stilizarea de conținut. Sunt multe motive pentru a face acest lucru, însă, cel mai evident (pentru un programator) este posibilitatea de a controla modul în care arată un număr multiplu de pagini prin schimbarea unui singur fișier. Informațiile referitoare la stil includ: fonturi; fundaluri; imagini (care se repetă pe fiecare pagină); pozițita și dimensiunile elementelor de pe pagină. Fișierul dumneavoastră HTML va conține acum: informații despre header; o serie de elemente; textul site-ului dumneavoastră. Deoarece creați un template Joomla!, veți avea: unele informații din header, cod php care să ceară restul informațiilor din header; o serie de elemente; cod php care să ceară poziția fiecărui modul; cod php care să ceară conținutul principal.

Informațiile referitoare la stil sunt codate în CSS, listă de stiluri în cascadă, și sunt de obicei stocate în fișiere cu extensia .css. O pagină web conține un link către fișierul .css asociat acesteia, astfel încât un motor de căutare să poată găsi informația referitoare la stilul respectiv și să o aplice paginii. CSS poate fi deasemenea situat în interiorul unui fisier HTML între tagurile <style type="text/css"></style>.

Întregul cod CSS este aplicat unui element al paginii html/xml. Dacă doriți ca un stil să fie prezent pe toată pagina, ar trebui să îl aplicați elementului <body>. Puteți aplica stiluri oricărui element html cum ar fi <p>, <table> sau <div>. Pentru a stiliza un anumit element acesta trebuie să aibă un ID. De exemplu, pentru a aplica stiluri elementelor <div> care conțin titlul, mai întâi trebuie să includeți un ID în html - <div ID="title">.

{{:Translations:About CSS page layouts/ru/Page_display_title/<lang code>‎}}

В профессиональных сайтах стили представления отделены от содержимого. На это существует много причин. Самая очевидная (для разработчика) это иметь возможность контролировать внешний вид многих страниц путем изменения одного файла. Информация о стиле включает в себя: шрифты; обои; картинки (которые повторяются на каждой странице); положение и размеры элементов на странице. Ваш HTML-файл теперь будет содержать: заголовочную информацию; серию элементов; текст Вашего сайта. Когда Вы создаете Joomla! шаблон, у Вас имеются: некоторые сведения из заголовка; PHP-код для запроса оставшейся информации для заголовка ; ряд элементов; PHP-код для заполнения каждого модуля и позиции; PHP-код с запросом на основное содержание.

Информация о стиле кодируется в CSS, каскадных таблицах стилей, и обычно хранится в файлах с суффиксом .css. Веб-страница содержит ссылку на связанный с ними .css-файл(ы), поэтому браузер может найти соответствующую информацию о стиле, чтобы применить его к странице. CSS может также быть размещена внутри HTML-файла между тегами <style type="text/css"></style>.

Весь код CSS применяется к элементу внутри HTML/XML страницы. Если вы хотите оформить определенным стилем всю страницу, вы, вероятно, примените его к элементу <body>. Вы можете применить стили для элементов HTML, таких как <p>, <table> или <div>. Стиль конкретного элемента должен иметь идентификатор (параметр "id"). Например, чтобы применить стили к <div> содержащий заголовок, Вы должны сначала включить парампетр "id" в HTML вот таким образом - <div ID="title">.

About Joomla

{{:Translations:Absolute Basics of How a Component Functions/Page_display_title/<lang code>‎}}

This article is designed for Joomlaǃ beginners; it is designed to explain what a Joomlaǃ component is, and how it functions. When a specific component example will benefit the tutorial, this article will refer to an example component named Hello Worldǃ.

What is a Joomlaǃ 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. Created by a component, content is 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 of your site when they are requested by your site visitors 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

In the Joomla! framework, components can be designed using a flat model (returns HTML code for the requested page) or Model-View-Controller (herein referred to as MVC) pattern.

Introduction to MVC

MVC is a software design pattern that can be used to organize code in such a way that the business logic and data presentation are seperate. The premise behind this approach is that if the business logic is grouped into one section, then the interface and user interaction that surrounds the data can be revised and customized without having to reprogram the business logic. MVC was originally developed to map the traditional input, processing, output roles into a logical GUI architecture.

Model

The model is the part of the component that encapsulates the application's data. It will often provide routines to manage and manipulate this data in a meaningful way in addition to routines that retrieve the data from the model. In general, the underlying data access technique should be encapsulated in the model. In this way, if an application is to be moved from a system that utilizes a flat file to store its information to a system that uses a database, the model is the only element that needs to be changed, not the view or the controller.

View

The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the user. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays the data received from the model.

Controller

The controller is responsible for responding to user actions. In the case of a web application, a user action is generally a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.

Joomla! Component Framework Explained

Model

In the Joomla framework, models are responsible for managing the data. The first function that has to be written for a model is a get function. It returns data to the caller. For this example, the caller will be the HelloWorldViewHelloWorld view. By default, the model named HelloWorldModelHelloWorld residing in site/models/helloworld.php is the main model associated to this view.

So let's have a quick look at the naming conventions with an example, since the naming convention are the actual magic, that make everything work:

The class HelloWorldViewHelloWorld resides in site/views/helloworld/view.html.php and will make use of the class HelloWorldModelHelloWorld in the file site/models/helloworld.php

Do let's just assume we want to use an imaginary view fluffy, you would have to have:

The class HelloWorldViewFluffy which resides in site/views/fluffy/view.html.php. The view will make use of HelloWorldModelFluffy in the file site/models/fluffy.php. Note: the actual screen of the view: site/views/fluffy/tmpl/default.php is required as well to make this example work.

Breaking any of these bold conventions will lead to errors or a blank page.

Accessing a Joomlaǃ Component

First we need to access the Joomla! platform, which is always accessed through a single point of entry. Using your preferred web browser, navigate to the following URL:

1 user access <yoursite>/joomla/index.php
2 administrator access <yoursite>/joomla/administrator/index.php

Hello World! example: localhost/joomla/index.php

You can use the URL of the component, or a Menu in order to navigate to the component. In this article we will discuss using the URL.

1 user access <yoursite>/joomla/index.php?option=com_<component_name>
2 administrator access <yoursite>/joomla/administrator/index.php?option=com_<component_name>

Hello World! example: localhost/joomla/index.php?option=com_helloworld

MVC Basic Directory Structure

Components are stored in a directory within your Joomla! installation, specifically at:

  • htdocs/<path_to_joomla>/components/com_<component_name>/ .

The Hello World! component would be stored in htdocs/<path_to_joomla>/components/com_helloworld/.

A basic component will contain the following files within its directoryː

  • A html file that is just a security file with a background colorː index.html
  • A php file that represents the controller itselfː controller.php
  • A php file that loads the controller classː <component_name>.php
  • A php file that represents the model itselfː models/<component_name>.php
  • Another html file for background controlː models/index.html
  • A php file containing the default viewː views/<component_name>/tmpl/default.php
  • A xml file for adding a menu item typeː views/<component_name>/tmpl/default.xml
  • Another html file for background controlː views/<component_name>/tmpl/index.html
  • Another html file for background controlː views/<component_name>/index.html
  • A php file for displaying the viewː views/<component_name>/view.html.php


JEXEC

The following line is commonly found at the start of Joomla! PHP files:

<?php
    defined('_JEXEC') or die('Restricted Access');

This enables for a secure entry point into the Joomla! platform. JEXEC contains a detailed explanation.

Tutorials on Designing a MVC Component

To learn how to design your own MVC Component, please complete the tutorial for your Joomla! version.

{{:Translations:Absolute Basics of How a Component Functions/Page_display_title/<lang code>‎}}

Just want to say this is a great topic and an article from which I learnt a lot. Perhaps it should feature more prominently.

Over recent weeks I've been struggling with understanding how it all hangs together grabbing snippets all over the place, reading through loads of the php source, slow & difficult progress.

I have no doubt it would have taken me several more days to workout that the 'task' was defaulting to display and that I could name my own controller methods (like jump) and have them activated by a URL parameter. (The sort of stuff I imagine every PHP developer coming to Joomla would want to know).

The article may also be a bit dated now with 1.7 I see the demo Hello World MVC component involves 4 files ?? (Basefile + M+V+C) ? Anyway, well done great article and lots of gems of knowledge about how Joomla works. Thanks

Missing in Instructions

//Hi, I have tried to follow these instructions, and found a few missing things.
Setting up my controller.php was missing the following statement in the display class:
 
return parent::display();
 
//Without this, the instructions don't work.

Cwurtz (talk) 03:07, 14 December 2013 (CST)

Feel free to correct it. Tom Hutchison (talk) 10:57, 14 December 2013 (CST)

Updated article:

Hello all,

I am a new Joomla! student, I am going through and updating several of the tutorials, those that are geared towards beginners, with current information. My main focus is to update Developing a Model-View-Controller Component/3.x, so that it is geared toward beginners.

This article itself seemed designed originally for Joomla 1.5. For this article, I removed the sections that displayed specific code; this was due to the code differences between 1.5, 2.5, and 3.x. To compensate for this change, I added the links to the specific tutorials for those versions. I also added new sections with information that I have found dispersed throughout the Joomla! documentation.

If you can think of any other additions or revisions that I can make to this article, please let me know.

Warm Regards,

Kevinkabatra (talk) 08:18, 17 September 2015 (CDT)

Absolute Basics of How a Component Functions/1/de

Dieser Artikel ist für Joomla! Anfänger entworfen worden; er ist entworfen worden um zu erklären, was eine Joomla! Komponente ist und wie sie funktioniert. Falls das Tutorial von einem bestimmten Komponenten Beispiel profitiert wird dieser Artikel auf eine Beispiel-Komponente namens "Hello World!" verweisen.

Absolute Basics of How a Component Functions/1/en

This article is designed for Joomlaǃ beginners; it is designed to explain what a Joomlaǃ component is, and how it functions. When a specific component example will benefit the tutorial, this article will refer to an example component named Hello Worldǃ.

Absolute Basics of How a Component Functions/1/es

Este artículo está pensado para principiantes en Joomlaǃ; está diseñado para explicar que es un componente en Joomlaǃ y cómo funciona. Como un componente específico de ejemplo beneficiará el tutorial, este artículo se refiere al ejemplo del componente llamado Hello Worldǃ.

Absolute Basics of How a Component Functions/1/fr

Cet article est destiné aux débutants sur Joomla. Il a pour objectif d'expliquer ce qu'est un composant Joomlaǃ comment il fonctionne. Puisqu'il est toujours interessant de se référer à des exemples, cet article va parfois se référer à un composant d'exemple nommé "Hello World!" (Bonjour à tous !).

Absolute Basics of How a Component Functions/1/it

Questo articolo è per principianti di Joomlaǃ; è progettato per spiegare cos'è un componente di Joomlaǃ e come funziona. Questo articolo farà riferimento ad un esempio di componente denominato Hello Worldǃ.

Absolute Basics of How a Component Functions/1/nl

Dit artikel is voor Joomla! beginners; het legt uit wat een component is en hoe het functioneert. Wanneer een voorbeeld van een component ter sprake komt, dan wordt er gerefereerd naar het voorbeeld component met de naam "Hello World!".

Absolute Basics of How a Component Functions/1/ro

Acest articol este destinat începătorilor Joomla!; scopul său este de a explica ce este o componentă Joomla! și cum funcționează. În momentul în care un exemplu specific de componentă va fi prezentat în tutorial, acest articol se va referi la componenta exemplu numită Hello World!.

Absolute Basics of How a Component Functions/1/ru

Этот документ написан для начинающих [пользователей системы] Joomla!; его назначение - объяснить что такое компоненты Joomla! и как они функционируют. Когда пример с каким-либо определенным компонентом может быть полезным, то этот документ будет ссылаться на компонент-образец под названием 'Hello World!'.

Absolute Basics of How a Component Functions/10/de

View

Absolute Basics of How a Component Functions/10/en

View

Absolute Basics of How a Component Functions/10/es

Vista

Absolute Basics of How a Component Functions/10/fr

View (vue)

Absolute Basics of How a Component Functions/10/it

View

Absolute Basics of How a Component Functions/10/nl

View

Absolute Basics of How a Component Functions/10/ru

Представление

Absolute Basics of How a Component Functions/11/en

The view is the part of the component that is used to render the data from the model in a manner that is suitable for interaction. For a web-based application, the view would generally be an HTML page that is returned to the user. The view pulls data from the model (which is passed to it from the controller) and feeds the data into a template which is populated and presented to the user. The view does not cause the data to be modified in any way, it only displays the data received from the model.

Absolute Basics of How a Component Functions/11/es

La vista es la parte del componente que se utiliza para presentar los datos a partir del modelo de una manera que sea adecuada para la interacción. Para una aplicación basada en la web, la vista general sería una página HTML que se devuelve al usuario. La vista extrae los datos del modelo (que se pasan desde el controlador) y alimenta los datos en una plantilla que se rellena y se presentan al usuario. La vista no provoca que los datos sean modificados de ninguna manera, sólo se muestran los datos recibidos del modelo.

Absolute Basics of How a Component Functions/11/fr

La vue (view) est la partie du composant qui est utilisée pour le rendu des données reçues à partir du modèle, de manière à les rendre convenable pour l'interaction. Pour une application basée web, la vue sera généralement une page HTML qui est renvoyée à l'utilisateur. La vue extrait des données à partir du modèle (qui passeront par le contrôleur) et les organiseront via un template qui permettra la présentation à l'utilisateur. La vue n'impose pas une modifications des données, elle se contente de permettre l'affichage des données reçues du modèle.

Absolute Basics of How a Component Functions/11/nl

De view is het stuk van het component wat wordt gebruikt om de gegevens van het model aan te voeren zodat het gereed is voor interactie. Voor een web gebaseerde toepassing zal de view normaliter een HTML pagina zijn die wordt gepresenteerd aan de gebruiker. De view haalt de gegevens van het model (welke hij aangeleverd van de controller) en zet deze gegeven in een template welke wordt gevuld en gepresenteerd aan de gebruikt. De view wijzigt op geen enkele manier de gegevens, het toont alleen de gegevens van het model.

Absolute Basics of How a Component Functions/12/de

Steuerung

Absolute Basics of How a Component Functions/12/en

Controller

Absolute Basics of How a Component Functions/12/es

Controlador

Absolute Basics of How a Component Functions/12/fr

Controller (contrôleur)

Absolute Basics of How a Component Functions/12/nl

Controller

Absolute Basics of How a Component Functions/13/en

The controller is responsible for responding to user actions. In the case of a web application, a user action is generally a page request. The controller will determine what request is being made by the user and respond appropriately by triggering the model to manipulate the data appropriately and passing the model into the view. The controller does not display the data in the model, it only triggers methods in the model which modify the data, and then pass the model into the view which displays the data.

Absolute Basics of How a Component Functions/13/es

El controlador es responsable de responder a las acciones del usuario. En el caso de una aplicación web, una acción del usuario es generalmente una solicitud de página. El controlador determinará qué solicitud ha sido realizada por el usuario y responderá de forma adecuada mediante la activación del modelo para manipular los datos de forma adecuada y pasar el modelo a la vista. El controlador no mostrará los datos en el modelo, sólo activa los métodos del modelo que modifican los datos y, a continuación, pasan del modelo a la vista que muestra los datos.

Absolute Basics of How a Component Functions/13/fr

Le contrôleur (controller) est chargé de répondre aux actions de l'utilisateur. Dans le cas d'une application web, l'action de l'utilisateur est généralement une demande de page. Le contrôleur devra déterminer quelle est la demande de l'utilisateur et va répondre de façon appropriée par le déclenchement du modèle qui va manipuler les données de façon appropriée et en passant le modèle dans la vue. Le contrôleur n'affiche pas les données dans le modèle, il déclenche les méthodes du modèle qui va modifier les données puis passer le modèle dans la vue qui affichera les données.

Absolute Basics of How a Component Functions/13/nl

De controller is verantwoordelijk voor het reageren op acties van de gebruiker. In het geval van een web-applicatie, is de actie van een gebruiker meestal een pagina opvragen. De controller zal bepalen welk verzoek wordt gedaan door de gebruiker en zal er adequaat op reageren, namelijk het activeren van het model dat de gegevens op de juiste manier manipuleert en het model doorgeven aan de view. De controller zorgt niet voor de weergave van de gegevens in het model, het zal enkele methoden in het model uitvoeren om gegevens te wijzigen, om dan het model door te geven naar de view die de gegevens weergeeft.

Absolute Basics of How a Component Functions/14/de

Joomla! Das Komponenten-Framework, erklärt

Absolute Basics of How a Component Functions/14/en

Joomla! Component Framework Explained

Absolute Basics of How a Component Functions/14/es

Explicación sobre el componente en el Framework de Joomla!

Absolute Basics of How a Component Functions/14/fr

Le framework pour composants Joomla! expliqué

Absolute Basics of How a Component Functions/14/nl

Joomla! Component Framework Uitgelegd

Absolute Basics of How a Component Functions/15/de

Model

Absolute Basics of How a Component Functions/15/en

Model

Absolute Basics of How a Component Functions/15/es

Modelo

Absolute Basics of How a Component Functions/15/fr

Model (modèle)

Absolute Basics of How a Component Functions/15/nl

Model

Absolute Basics of How a Component Functions/16/de

Im Joomlaframework sind die Models verantwortlich für die Datenverwaltung. Die erste Funktion, die für ein Model geschrieben werden muss, ist die "get-Funktion". Sie gibt Daten zurück an den Aufrufer. Für dieses Beispiel der Aufrufer ist die "HelloWorldViewHelloWorld" Ansicht. Standardmäßig ist das Model "HelloWorldModelHelloWorld", welches unter site/models/helloworld.php zu finden ist, das wichtigste Model für diese Ansicht.

Absolute Basics of How a Component Functions/16/en

In the Joomla framework, models are responsible for managing the data. The first function that has to be written for a model is a get function. It returns data to the caller. For this example, the caller will be the HelloWorldViewHelloWorld view. By default, the model named HelloWorldModelHelloWorld residing in site/models/helloworld.php is the main model associated to this view.

Absolute Basics of How a Component Functions/16/es

En el framework Joomla, los modelos son responsables de la gestión de los datos. La primera función que se debe escribir en un modelo es una función get. Esta devuelve los datos a quien la llame. En nuestro caso, el que llama será la vista HelloWorldViewHelloWorld. De forma predeterminada, el modelo denominado HelloWorldModelHelloWorld que reside en site/models/helloworld.php es el modelo principal asociado a esta vista.

Absolute Basics of How a Component Functions/16/fr

Dans le framework Joomla, les modèles gèrent les données. La première fonction à écrire pour un modèle est la fonction get. Elle permet de renvoyer les données à l'appelant. Dans notre cas, l'appelant sera la vue HelloWorldViewHelloWorld. Par défaut, le modèle nommé HelloWorldModelHelloWorld, situé dans site/models/helloworld.php est le modèle principal associé à cette vue.

Absolute Basics of How a Component Functions/16/nl

In het Joomla framework, zijn modellen verantwoordelijk voor het beheer van de gegevens. De eerste functie die voor een model geschreven moet worden, is een 'get'-functie. Deze levert de gegevens aan de oproepende. In ons voorbeeld, is de oproeper de 'view' HelloWorldViewHelloWorld. Het model dat hier standaard bijhoort heeft een naam als HelloWorldModelHelloWorld en is te vinden in site/models/helloworld.php.

Absolute Basics of How a Component Functions/17/en

So let's have a quick look at the naming conventions with an example, since the naming convention are the actual magic, that make everything work:

Absolute Basics of How a Component Functions/17/es

Así que vamos a echar un vistazo rápido a las convenciones de nomenclatura con un ejemplo, ya que la convención de nomenclatura es la magia, que hace todo el trabajo:

Absolute Basics of How a Component Functions/17/fr

Regardons rapidement les conventions de nommage à l'aide d'un exemple. Les conventions de nommage ont un côté magique, permettant de faire tout le travail :

Absolute Basics of How a Component Functions/17/nl

Het belang van de naamgeving zal duidelijk blijken uit ons voorbeeld.

Absolute Basics of How a Component Functions/18/en

The class HelloWorldViewHelloWorld resides in site/views/helloworld/view.html.php and will make use of the class HelloWorldModelHelloWorld in the file site/models/helloworld.php

Absolute Basics of How a Component Functions/18/es

La clase HelloWorldViewHelloWorld reside en site/views/helloworld/view.html.php y hará uso de la clase HelloWorldModelHelloWorld en el archivo site/models/helloworld.php

Absolute Basics of How a Component Functions/18/fr

La classe HelloWorldViewHelloWorld se situe dans site/views/helloworld/view.html.php et utilisera la classe HelloWorldModelHelloWorld du fichier site/models/helloworld.php

Absolute Basics of How a Component Functions/18/nl

De klasse HelloWorldViewHelloWorld bevindt zich in site/views/helloworld/view.html.php en maakt gebruik van de klasse HelloWorldModelHelloWorld in het bestand site/modellen/helloworld.php

Absolute Basics of How a Component Functions/19/en

Do let's just assume we want to use an imaginary view fluffy, you would have to have:

Absolute Basics of How a Component Functions/19/es

Así que vamos a suponer que queremos utilizar una vista imaginaria fluffy', tendría que tener:

Absolute Basics of How a Component Functions/19/fr

Supposons que nous voulons utiliser la vue fictive fluffy, vous devriez avoir :

Absolute Basics of How a Component Functions/19/nl

In de veronderstelling dat we een ingebeelde view fluffy willen gebruiken, dan zouden we komen tot:

Absolute Basics of How a Component Functions/2/de

Was ist ein Joomlaǃ Komponente

Absolute Basics of How a Component Functions/2/en

What is a Joomlaǃ Component

Absolute Basics of How a Component Functions/2/es

¿Qué es un Componente de Joomla!?

Absolute Basics of How a Component Functions/2/fr

Qu'est-ce qu'un composant Joomla! ?

Absolute Basics of How a Component Functions/2/it

Cos'è un Componente di Joomlaǃ

Absolute Basics of How a Component Functions/2/nl

Wat is een Joomlaǃ component

Absolute Basics of How a Component Functions/2/ro

Ce este o Componentă Joomlaǃ

Absolute Basics of How a Component Functions/2/ru

Что такое компонент Joomlaǃ

Absolute Basics of How a Component Functions/20/en

The class HelloWorldViewFluffy which resides in site/views/fluffy/view.html.php. The view will make use of HelloWorldModelFluffy in the file site/models/fluffy.php. Note: the actual screen of the view: site/views/fluffy/tmpl/default.php is required as well to make this example work.

Absolute Basics of How a Component Functions/20/es

La clase HelloWorldViewFluffy, que reside en site/views/fluffy/view.html.php. La vista va a hacer uso de HelloWorldModelFluffy en el archivo site/models/fluffy.php. Nota: la pantalla de la vista: site/views/fluffy/tmpl/default.php es necesaria para que este ejemplo funcione.

Absolute Basics of How a Component Functions/20/fr

La classe HelloWorldViewFluffy qui se trouve dans site/views/fluffy/view.html.php. La vue va utiliser HelloWorldModelFluffy du fichier site/models/fluffy.php. Remarque : l'écran de la vue site/views/fluffy/tmpl/default.php est requise pour que cet exemple puisse fonctionner.

Absolute Basics of How a Component Functions/20/nl

De klasse HelloWorldViewFluffy die zich bevindt in site/views/fluffy/view.html.php. Deze 'view' zal gebruik maken van HelloWorldModelFluffy in het bestand site/modellen/fluffy.php. Opmerking: om dit voorbeeld te doen werken moet het scherm bestaan voor de weergave van die 'view': site/views/fluffy/tmpl/default.php.

Absolute Basics of How a Component Functions/21/de

Brechen mit dieser Konventionen führt zu Fehlern oder einer leere Seite.

Absolute Basics of How a Component Functions/21/en

Breaking any of these bold conventions will lead to errors or a blank page.

Absolute Basics of How a Component Functions/21/es

Romper cualquiera de estas convenciones en negrita dará lugar a errores o una página en blanco.

Absolute Basics of How a Component Functions/21/fr

Le non respect de l'une des conventions en gras va engendrer des erreurs ou une page blanche.

Absolute Basics of How a Component Functions/21/nl

Volg je deze strikte regels niet dan krijg je foutmeldingen of een blanko pagina.

Absolute Basics of How a Component Functions/22/de

Zugriff auf eine Joomlaǃ Komponente

Absolute Basics of How a Component Functions/22/en

Accessing a Joomlaǃ Component

Absolute Basics of How a Component Functions/22/es

Acceso a un Componente Joomlaǃ

Absolute Basics of How a Component Functions/22/fr

Accéder à un composant Joomla!

Absolute Basics of How a Component Functions/22/nl

Toegang tot een Joomlaǃ Component

Absolute Basics of How a Component Functions/23/en

First we need to access the Joomla! platform, which is always accessed through a single point of entry. Using your preferred web browser, navigate to the following URL:

Absolute Basics of How a Component Functions/23/es

En primer lugar, debemos acceder a la plataforma de Joomla!, a la que siempre se accede a través de un único punto de entrada. Utilizando tu navegador web preferido, ve a la siguiente URL:

Absolute Basics of How a Component Functions/23/fr

Il nous faut en premier lieu accéder à la plateforme Joomla! qui n'est accessible que par le biais d'un point d'entrée unique. À l'aide de votre navigateur web préféré, accédez à l'URL suivante :

Absolute Basics of How a Component Functions/23/nl

Eerste moeten we in het Joomla! platform gaan, dat altijd toegankelijk is via volgende volgende URL (open in je browser):

Absolute Basics of How a Component Functions/24/de

Benutzer Zugang

Absolute Basics of How a Component Functions/24/en

user access

Absolute Basics of How a Component Functions/24/es

acceso de usuario

Absolute Basics of How a Component Functions/24/fr

accès utilisateur

Absolute Basics of How a Component Functions/24/nl

gebruikerstoegang

Absolute Basics of How a Component Functions/25/de

<deineDomain>/joomla/index.php

Absolute Basics of How a Component Functions/25/en

<yoursite>/joomla/index.php

Absolute Basics of How a Component Functions/25/es

<tusitio>/joomla/index.php

Absolute Basics of How a Component Functions/25/fr

<votresite>/joomla/index.php

Absolute Basics of How a Component Functions/25/nl

<uwsite>/joomla/index.php

Absolute Basics of How a Component Functions/26/de

Administrator-Zugang

Absolute Basics of How a Component Functions/26/en

administrator access

Absolute Basics of How a Component Functions/26/es

acceso de administrador

Absolute Basics of How a Component Functions/26/fr

accès administration

Absolute Basics of How a Component Functions/26/nl

beheerderstoegang

Absolute Basics of How a Component Functions/27/de

<deinedomain>/joomla/administrator/index.php

Absolute Basics of How a Component Functions/27/en

<yoursite>/joomla/administrator/index.php

Absolute Basics of How a Component Functions/27/es

<tusitio>/joomla/administrator/index.php

Absolute Basics of How a Component Functions/27/fr

<votresite>/joomla/administrator/index.php

Absolute Basics of How a Component Functions/27/nl

<uwsite>/joomla/administrator/index.php

Absolute Basics of How a Component Functions/28/de

"Hallo Welt!"- Beispiel:

Absolute Basics of How a Component Functions/28/en

Hello World! example:

Absolute Basics of How a Component Functions/28/es

Ejemplo Hola Mundo!:

Absolute Basics of How a Component Functions/28/fr

Exemple Hello World! :

Absolute Basics of How a Component Functions/28/nl

Hallo Wereld! voorbeeld:

Absolute Basics of How a Component Functions/29/de

Sie können die Url der Komponente, oder eine Menu nutzen, um zur Komponente zu navigieren. In diesem Artikel werden wir die Möglichkeit der Url besprechen.

Absolute Basics of How a Component Functions/29/en

You can use the URL of the component, or a Menu in order to navigate to the component. In this article we will discuss using the URL.

Absolute Basics of How a Component Functions/29/es

Puedes utilizar la dirección URL del componente, o un Menú con el fin de navegar al componente. En este artículo vamos a discutir el uso de la dirección URL.

Absolute Basics of How a Component Functions/29/fr

Vous pouvez utiliser l'URL du composant ou un Menu pour naviguer vers le composant. Dans cet article, nous utiliserons l'URL.

Absolute Basics of How a Component Functions/29/nl

U kunt gebruik maken van de URL van het component, of een Menu , om te navigeren naar het onderdeel. In dit artikel bespreken we het gebruik van de URL.

Absolute Basics of How a Component Functions/3/en

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. Created by a component, content is usually displayed in the center of the main content area of a template (depending on the template).

Absolute Basics of How a Component Functions/3/es

Un componente es un tipo de extensión de Joomla! . Los componentes son las principales unidades funcionales de Joomla!; pueden verse como mini-aplicaciones. Una analogía fácil sería considerar que Joomla! es el sistema operativo y los componentes son las aplicaciones de escritorio. Lo creado por un componente, se muestra en el centro del área de contenido principal de una plantilla (dependiendo de la plantilla).

Absolute Basics of How a Component Functions/30/de

Benutzer Zugang

Absolute Basics of How a Component Functions/30/en

user access

Absolute Basics of How a Component Functions/30/es

acceso de usuario

Absolute Basics of How a Component Functions/30/fr

accès utilisateur

Absolute Basics of How a Component Functions/30/nl

gebruikerstoegang

Absolute Basics of How a Component Functions/31/de

<deine Seite>/joomla/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/31/en

<yoursite>/joomla/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/31/es

<tusitio>/joomla/index.php?option=com_<nombre_componente>

Absolute Basics of How a Component Functions/31/fr

<votresite>/joomla/index.php?option=com_<nom_du_composant>

Absolute Basics of How a Component Functions/31/nl

<uwsite>/joomla/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/32/de

administrator Zugriff

Absolute Basics of How a Component Functions/32/en

administrator access

Absolute Basics of How a Component Functions/32/es

acceso de administrador

Absolute Basics of How a Component Functions/32/fr

accès administration

Absolute Basics of How a Component Functions/32/nl

beheerderstoegang

Absolute Basics of How a Component Functions/33/de

<deine Seite>/joomla/administrator/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/33/en

<yoursite>/joomla/administrator/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/33/es

<tusitio>/joomla/administrator/index.php?option=com_<nombre_componente>

Absolute Basics of How a Component Functions/33/fr

<votresite>/joomla/administrator/index.php?option=com_<nom_du_composant>

Absolute Basics of How a Component Functions/33/nl

<uwsite>/joomla/administrator/index.php?option=com_<component_name>

Absolute Basics of How a Component Functions/34/de

Hallo Welt! Beispiel:

Absolute Basics of How a Component Functions/34/en

Hello World! example:

Absolute Basics of How a Component Functions/34/es

Ejemplo Hola Mundo!:

Absolute Basics of How a Component Functions/34/fr

Exemple Hello World! :

Absolute Basics of How a Component Functions/34/nl

Hallo Wereld! voorbeeld:

Absolute Basics of How a Component Functions/35/de

MVC-Basis Verzeichnis Struktur

Absolute Basics of How a Component Functions/35/en

MVC Basic Directory Structure

Absolute Basics of How a Component Functions/35/es

MVC Estructura Básica de Directorios

Absolute Basics of How a Component Functions/35/fr

Structure de base d'un dossier MVC

Absolute Basics of How a Component Functions/35/nl

MVC Basis Directory-Structuur

Absolute Basics of How a Component Functions/36/de

Komponenten liegen in einem Verzeichnis Ihrer Joomla-Installation. Genau gesagt in htdocs/<PfadzuJoomla>/komponenten/com_<komponenten_name>/

Absolute Basics of How a Component Functions/36/en

Components are stored in a directory within your Joomla! installation, specifically at:

  • htdocs/<path_to_joomla>/components/com_<component_name>/ .

Absolute Basics of How a Component Functions/36/es

Los componentes se almacenan en un directorio dentro de la instalación de tu sitio Joomla!, específicamente en:

  • htdocs/<ruta_a_joomla>/components/com_<nombre_componente>/ .

Absolute Basics of How a Component Functions/36/fr

Les composants sont stockés dans un dossier de votre installation Joomla! et plus précisément dans :

  • htdocs/<chemin_vers_joomla>/components/com_<nom_du_composant>/.

Absolute Basics of How a Component Functions/36/nl

Onderdelen worden opgeslagen in een map in uw Joomla! installatie, specifiek op:

  • htdocs/<pad_naar_joomla>/components/com_<component_naam>/ .

Absolute Basics of How a Component Functions/37/de

Die Hallo Welt! Komponente wurde gespeichert in htdocs/<path_to_joomla>/Komponenten/com_helloworld/.

Absolute Basics of How a Component Functions/37/en

The Hello World! component would be stored in htdocs/<path_to_joomla>/components/com_helloworld/.

Absolute Basics of How a Component Functions/37/es

El componente Hello World! debe ser almacenado en htdocs/<ruta_a_joomla>/components/com_helloworld/.

Absolute Basics of How a Component Functions/37/fr

Le composant Hello World! est stocké dans htdocs/<chemin_vers_joomla>/components/com_helloworld/.

Absolute Basics of How a Component Functions/37/nl

Het Hallo World! component zou worden opgeslagen in htdocs/<pad_naar_joomla>/components/com_helloworld/.

Absolute Basics of How a Component Functions/38/de

Eine Grundkomponente enthält die folgenden Dateien in ihrem Verzeichnis:

Absolute Basics of How a Component Functions/38/en

A basic component will contain the following files within its directoryː

Absolute Basics of How a Component Functions/38/es

Un componente básico contendrá los siguientes archivos dentro de su directorioː

Absolute Basics of How a Component Functions/38/fr

Un composant de base contiendra les fichiers suivants dans son propre dossier ː

Absolute Basics of How a Component Functions/38/nl

Een basis component zal de volgende bestanden in zijn bestandsmap bevatten ː

Absolute Basics of How a Component Functions/39/en

  • A html file that is just a security file with a background colorː index.html

Absolute Basics of How a Component Functions/39/es

  • Un archivo html que es sólo un archivo de seguridad con un color de fondo: index.html

Absolute Basics of How a Component Functions/39/fr

  • Un fichier html de sécurité avec une couleur d'arrière-plan ː index.html

Absolute Basics of How a Component Functions/39/nl

  • Ter beveiliging een html-bestand met enkel een achtergrond kleurː index.html

Absolute Basics of How a Component Functions/4/en

Most components have two main parts: an administrator part and a site part. The site part is what is used to render pages of your site when they are requested by your site visitors 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.

Absolute Basics of How a Component Functions/4/es

La mayoría de los componentes tienen dos partes principales: la parte de administración y la parte del sitio o interfaz pública. La parte del sitio es lo que se usa para generar las páginas de su sitio web cuando lo solicitan los visitantes, durante una operación normal del sitio web. La parte de administración es la que proporciona una interfaz para configurar y gestionar los distintos aspectos del componente y es accesible a través de la aplicación de administración de Joomla!.

Absolute Basics of How a Component Functions/40/en

  • A php file that represents the controller itselfː controller.php

Absolute Basics of How a Component Functions/40/es

  • Un archivo php que representa el controlador en si mismo: controller.php

Absolute Basics of How a Component Functions/40/fr

  • Un fichier php qui est le contrôleur ː controller.php

Absolute Basics of How a Component Functions/40/nl

  • Een php-bestand dat overeenkomt met de controller zelf ː controller.php

Absolute Basics of How a Component Functions/41/en

  • A php file that loads the controller classː <component_name>.php

Absolute Basics of How a Component Functions/41/es

  • Un archivo php que carga la clase del controladorː <nombre_componente>.php

Absolute Basics of How a Component Functions/41/fr

  • Un fichier php qui va charger les classes du contrôleur ː <nom_du_composant>.php

Absolute Basics of How a Component Functions/41/nl

  • Een php-bestand dat de controller klasse oplaadtː <component_name>.php

Absolute Basics of How a Component Functions/42/en

  • A php file that represents the model itselfː models/<component_name>.php

Absolute Basics of How a Component Functions/42/es

  • Un archivo php que representa al modelo itselfː models/<nombre_componente>.php

Absolute Basics of How a Component Functions/42/fr

  • Un fichier php qui est le modèle ː models/<nom_du_composant>.php

Absolute Basics of How a Component Functions/42/nl

  • Een php-bestand dat overeenkomt met het model zelf: models/<component_naam>.php

Absolute Basics of How a Component Functions/43/en

  • Another html file for background controlː models/index.html

Absolute Basics of How a Component Functions/43/es

  • Otro archivo html para el control del acceso directo: models/index.html

Absolute Basics of How a Component Functions/43/fr

  • Un autre fichier html pour le contrôle de la couleur de fond ː models/index.html

Absolute Basics of How a Component Functions/43/nl

  • Een andere html-bestand voor de achtergrond controlː models/index.html

Absolute Basics of How a Component Functions/44/en

  • A php file containing the default viewː views/<component_name>/tmpl/default.php

Absolute Basics of How a Component Functions/44/es

  • Un archivo php que contiene la vista predeterminada: views/<nombre_componente>/tmpl/default.php

Absolute Basics of How a Component Functions/44/fr

  • Un fichier php contenant la vue par défaut ː views/<nom_du_composant>/tmpl/default.php

Absolute Basics of How a Component Functions/44/nl

  • Een php-bestand met de standaard viewː views/<component_naam>/tmpl/default.php

Absolute Basics of How a Component Functions/45/en

  • A xml file for adding a menu item typeː views/<component_name>/tmpl/default.xml

Absolute Basics of How a Component Functions/45/es

  • Un archivo xml para agregar los ítems del menú tipo: views/<nombre_componente>/tmpl/default.xml

Absolute Basics of How a Component Functions/45/fr

  • Un fichier xml pour ajouter un type d'élément de menu ː views/<nom_du_composant>/tmpl/default.xml

Absolute Basics of How a Component Functions/45/nl

  • Een xml-bestand voor het toevoegen van een menu-item typeː views/<component_naam>/tmpl/default.xml

Absolute Basics of How a Component Functions/46/en

  • Another html file for background controlː views/<component_name>/tmpl/index.html

Absolute Basics of How a Component Functions/46/es

  • Otro archivo html para el control del acceso directo: views/<nombre_componente>/tmpl/index.html

Absolute Basics of How a Component Functions/46/fr

  • Un autre fichier html pour le contrôle de couleur de fond de la vue ː views/<nom_du_comosant>/tmpl/index.html

Absolute Basics of How a Component Functions/46/nl

  • Een ander html-bestand voor de achtergrond controlː views/<component_naam>/tmpl/index.html

Translation Hints

Suggested markup for translations

Will have to work this out, but it does work and will use the /en coding for English pages once they are all marked for translation.

DPL Call between tags
category=Glossary definitions/<lang code>
notcategorymatch=%Archived%
include=*
format=,\n== {{#ifexist:%TITLE%|[[%TITLE%|{{:Translations:%TITLE%/Page_display_title/<lang code>‎}}]]|%TITLE%}} ==\n
reset=categories
resultsheader=__TOC____NOEDITSECTION__
...end DPL call