Joomla! Documentation - User contributions [en]

Talk:Online Poker Strategi-3 Golden Rules Untuk Winning Online Poker

2020-07-31T19:40:20Z

Efduggan: Created page with "Is there a better way to keep this type of spam from appearing. This is the 4th page I’ve “revised” in the week.!"

Is there a better way to keep this type of spam from appearing. This is the 4th page I’ve “revised” in the week.!

Talk:Dengan Cara Apa Turnamen Poker Freeroll Merupakan Pilihan Ideal Untuk Berlagak Poker Online Gratis

2020-07-29T16:26:39Z

Efduggan: Created page with "Spam! - delete please."

Spam! - delete please.

Talk:Buletin Tentang Balkon Poker Online

2020-07-24T02:08:46Z

Efduggan: Created page with "seems to be spam!"

seems to be spam!

Range form field type

2020-02-19T18:10:14Z

Efduggan: Fixed description of the example to cover the full range and explains the initial/default value

The ‘''range''' form field type provides a horizontal slider for numeric input. While the default value can be set, there is no indication of the actual value being chosen, just the position of the slider’s thumb. Available from {{JVer|3.2}}

* '''type''' (mandatory) must be ''range''.

* '''name''' (mandatory) is the unique name of the field.

* '''label''' (optional) (translatable) is the descriptive title of the field, and will appear in the pop-up when hovering over label as well.

* '''description''' (optional) (translatable) is text that will be shown as a tooltip when the user moves the mouse over the label.

* '''default''' (optional) (translatable) is the initial default value.

* '''class''' (optional) is a CSS class name for the HTML form field.

* '''min''' (optional) this value is the lowest that can be chosen.

* '''max''' (optional) this value is the highest that can be chosen.

* '''step''' (optional) if user click up/down arrow current value will change by this attribute (this attribute value will be added or subtracted to current field value).

* '''required''' (optional) should the user be required to enter data in this field?

Example XML field definition which would create a slider having the initial value of 0, with possibility to choose values between -0.5 and 0.5. The slider’s value changes by 0.1 as the slider is moved left or right.
<source lang="xml"><field name="myrange" type="range" default="0" label="Range from -0.5 to 0.5 step 0.1" description="" min="-0.5" max="0.5" step="0.1" /></source>

=== See also ===

<noinclude>
[[Category:Standard form field types]]
</noinclude>

JDOC talk:Joomla 4 Tutorials Project

2020-01-23T23:56:49Z

Efduggan:

[[User:GregJPreece|GregJPreece]] ([[User talk:GregJPreece|talk]]) 21:01, 3 January 2020 (CST) MVC Component Tutorial

I've been considering rewriting the component tutorial for Joomla 3.x, as many elements of it need modernising, and I really don't like the way it still uses legacy class names. If J4 is on the way and needs a similar tutorial, it seems sensible to start there.

---

Yes, please do. I’ve been holding off working my way through it as it seamed dated to a degree.

If you want a reviewer for the changes, I’d be up for it.

---

Cool, thank you. I'll get started soon. My first component is making its way into the JED right now, so I'll be working on J4 compatibility for that in the next release. I'll write the docs here as I go.

---
Great - I look forward to helping out!

JDOC talk:Joomla 4 Tutorials Project

2020-01-05T19:45:12Z

Efduggan:

User talk:GregJPreece

2019-10-24T18:46:03Z

Efduggan: Created page with "The last code example looks to be off in that it suggests the toSQL function would return a Unix second string. I’m assuming it’s a small typo. Unfortunately I don’t cur..."

The last code example looks to be off in that it suggests the toSQL function would return a Unix second string. I’m assuming it’s a small typo. Unfortunately I don’t currently have the ability to fix it yet, and hopefully this entry is a reasonable way of addressing the issue.

=== Outputting Dates as Unix Timestamps ===

A Unix timestamp is expressed as the number of seconds that have passed since the Unix Epoch (the first second of Jan 1st 1970).

<source lang="php">

$date = new Date('20121201T152000Z');

$date->toSQL(); // 1354375200

</source>

from https://docs.joomla.org/index.php?title=How_to_use_JDate&diff=640698&oldid=635076

[[User:Efduggan|Efduggan]] ([[User talk:Efduggan|talk]]) 13:46, 24 October 2019 (CDT)

User:Efduggan

2019-01-19T19:30:29Z

Efduggan: Brief personal statement about Joomla and me.

Joomla’s open source philosophy appeals to me; that’s why I use it, promote it and support it :-)
I’ve helped out with EventList (now JEM) https://extensions.joomla.org/extensions/extension/calendars-a-events/events/jem/ in the past, and do contribute OSModul https://extensions.joomla.org/extension/osmodul/

As I move into development with Joomla, my aim is to help improve the documentation for beginners like myself with this task.

Range form field type

2019-01-13T19:56:43Z

Efduggan: added a brief description with options for this field.

The ‘''range''' form field type provides a horizontal slider for numeric input. While the default value can be set, there is no indication of the actual value being chosen, just the position of the slider’s thumb. Available from {{JVer|3.2}}

* '''type''' (mandatory) must be ''range''.

* '''name''' (mandatory) is the unique name of the field.

* '''label''' (optional) (translatable) is the descriptive title of the field, and will appear in the pop-up when hovering over label as well.

* '''description''' (optional) (translatable) is text that will be shown as a tooltip when the user moves the mouse over the label.

* '''default''' (optional) (translatable) is the initial default value.

* '''class''' (optional) is a CSS class name for the HTML form field.

* '''min''' (optional) this value is the lowest that can be chosen.

* '''max''' (optional) this value is the highest that can be chosen.

* '''step''' (optional) if user click up/down arrow current value will change by this attribute (this attribute value will be added or subtracted to current field value).

* '''required''' (optional) should the user be required to enter data in this field?

Example XML field definition which would create a slider with possibility to choose values between 0 and 0.5 and change current value by 0.1 as the slider is moved left or right.
<source lang="xml"><field name=“myrange" type="range" default=“0" label="Range from -0.5 to 0.5 step 0.1" description="" min=“-0.5" max=“0.5" step="0.1" /></source>

=== See also ===

Category:Standard form field types

Accessing the current user object

2019-01-06T23:45:30Z

Efduggan: /* External Links */ - URL updated - old target has ben deleted

{{version/tutor|2.5,3.x}}
== Basics ==

For every request in Joomla!, there is one user. Information about this user is readily available through the Joomla! framework in the form of an object. To get this object for the current user, use the following member function of JFactory:

<source lang="php">
$user = JFactory::getUser();
</source>

Or, to get information about any other registered user you can call the function with a user 'id', e.g. for user '99';

<source lang="php">
$user = JFactory::getUser(99);
</source>

Getting a reference through getUser() ensures that only one user object is created during any one Joomla! request, saving on memory and processing time. Most of the information about the user is available through public member variables of the user object. This code displays the current user's name, email, user name and user type:

<source lang="php">
echo "<p>Your name is {$user->name}, your email is {$user->email}, and your username is {$user->username}</p>";
</source>
'''Note:''' Since version 1.6 Joomla has a flexible ACL system, which makes $user->usertype deprecated!

The usertype field in #__users will only contain values for users that have been migrated from Joomla 1.5, but for new created users the field will be empty.

Use $user->groups to retrieve an array with all the IDs that refer to the groups (from #__usergroups table) of a user.

== Object Member Variables and Parameters ==

These are the relevant member variables automatically generated on a call to getUser():
* id - The unique, numerical user id. Use this when referencing the user record in other database tables.
* name - The name of the user. (e.g. Vint Cerf)
* username - The login/screen name of the user. (e.g. shmuffin1979)
* email - The email address of the user. (e.g. crashoverride@hackers.com)
* password - The encrypted version of the user's password
* password_clear - Set to the user's password only when it is being changed. Otherwise, remains blank.
* usertype - <strike>The role of the user within Joomla!. (Super Administrator, Editor, etc...)</strike> Has been deprecated since Joomla 1.6. Use $user->groups to retrieve an array with all the roles of a user.
* groups - Set to the user's group ids.
* block - Set to '1' when the user is set to 'blocked' in Joomla!.
* registerDate - Set to the date when the user was first registered.
* lastvisitDate - Set to the date the user last visited the site.
* guest - If the user is not logged in, this variable will be set to '1'. The other variables will be unset or default values.
* lastResetTime - Set to the last time the password was reset.
* resetCount - Counts the number of password resets.

In addition to the member variables (which are stored in the database in columns), there are parameters for the user that hold preferences. To get one of these parameters, call the getParam() member function of the user object, passing in the name of the parameter you want along with a default value in case it is blank.

<source lang="php">
$user = JFactory::getUser();
$language = $user->getParam('language', 'the default');

echo "<p>Your language is set to {$language}.</p>";
</source>

== Determining Status ==

Frequently, you will just want to make sure the user is logged in before continuing. The 'guest' property will be set to '1' when the current user is not logged in. When the user is authenticated, 'guest' will be set to '0'.

<source lang="php">
$user = JFactory::getUser();

if ($user->guest) {
echo "<p>You must login to see the content. I want your email address.</p>";
} else {

<h1>Impromptu leftovers salad that goes well with fish</h1>
<ul>
<li>1/2 cup chopped celery</li>
<li>1/4 cup raisins</li>
<li>1 teaspoon Extra Virgin Olive Oil</li>
<li>2 tablespoons of faux Thai lemongrass marinade</li>
<li>1/4 cup shredded fresh basil</li>
<li>Sprinkling of dill weed</li>
<li>Big pinch of kosher salt</li>
<li>Several lettuce leaves</li>
</ul>

<p>Wash the lettuce and basil and place in a salad bowl.
Get out a much smaller bowl and swish around all of the remaining ingredients.
Pour this over the greens and toss.
Serves two.</p>

}
</source>

== Privileges ==
Not all users are given equal rights. For instance, a Super Administrator may be able to edit anyone's content, while a Publisher may only be able to edit their own. The authorise() member function can be used to determine if the current user has permission to do a certain task. The first parameter is used to identify which task we wish to check being allowed. The second represents the component we wish to retrieve the ACL information from.

<source lang="php">
$user = JFactory::getUser();

if ($user->authorise('core.edit', 'com_content'))
{
echo "<p>You may edit all content.</p>";
}
else
{
echo "<p>You may not edit all content.</p>";
}

if ($user->authorise('core.edit.own', 'com_content'))
{
echo "<p>You may edit your own content.</p>";
}
else
{
echo "<p>You may not edit your own content.</p>";
}
</source>

== Summary ==

Information about the current user is readily available in any part of your Joomla! extension. You need only fetch the object and access the member variables. You can authorise the user against the core permissions set, or create your own to suit your needs.

== External Links ==

[https://api.joomla.org/cms-3/classes/Joomla.CMS.Factory.html#method_getUser Joomla 3.9 API reference]
[[Category:Development]]
[[Category:Tutorials]][[Category:Framework]]
[[Category:Module Development]]
[[Category:Plugin Development]][[Category:Component Development]]

How do you list your extension in the extensions site?

2019-01-06T23:30:15Z

Efduggan: Fixed broken link to hopefully point at correct page

{{version|2.5,3.x}}Information on how to list extensions in the extensions site is available here:
https://extensions.joomla.org/support/knowledgebase/item/submitting-an-extension/

Before submitting an extension to JED you should read the 4 steps checklist process
* [[JED_Entries_Submission_Checklist|Submission Checklist]]

<noinclude>[[Category:FAQ]]
[[Category:Getting Started FAQ]]
[[Category:Version 3.x FAQ]]
[[Category:Version 2.5 FAQ]]
[[Category:JED]]
[[Category:Template Development]]
[[Category:Module Development]]
[[Category:Plugin Development]]
[[Category:Component Development]]
[[Category:Language Development]]</noinclude>

Register globals

2011-11-14T18:00:12Z

Efduggan: /* How do I find the state of register_globals on my Joomla! install? */

{{review}}

== What is it? ==

<tt>register_globals</tt> is a PHP environment setting that has been the subject of controversy for sometime. Older versions of PHP often have this variable set to on and that setting is known to leave a site vulnerable to hacking. Further information is available at [http://us.php.net/register_globals the PHP website]. Current Joomla! releases do not require this setting to be on, and best practices dictate that it should be changed to off. (Joomla! 1.0.x releases also have a related emulator for this setting, which was implemented for backward compatibility with older components and extensions. ''It is generally preferred not to enable this capability''.) If you have a component that requires this setting, you should look for an update, or find an alternative component.

== How do I find the state of register_globals on my Joomla! install? ==
J 1.5 Log in to Joomla! administration, go to Help -> System Info, click on the PHP Settings tab, and look for the Register Globals entry.

J1.6+ Log in to Joomla! administration, go to Site -> System Information, click on the PHP Settings tab, and look for the Register Globals entry.

== Can I change it? ==
Yes, maybe. Depending on how much control you have over your server, there are several approaches to addressing this setting.

If you have complete control of your server, then you probably want to make sure that your main PHP configuration file (which is typically found in /usr/local/lib/php.ini) has the directive ''register_globals'' set to 0(zero).

If you're in a shared web environment, most likely your hosting provider will not let you modify the global php.ini file. You have a couple of options in this case.

== Where do I change it? ==
Possibly the easiest thing to do is to ask your hosting provider to make this change for your domain. (Often this is accomplished by logging a technical support request.) But not all providers will make this change for you. So you may not be so lucky. The good news is that there are likely other options available to you, and here are some of them.

'''Local php configuration file:'''
If you have access to your web site's root directory, you should be able to include your own copy of a php.ini file. Your copy only needs to include the settings that you want to alter from the global settings.

'''Change to .htaccess:'''
Another option is to introduce the preferred setting by making an entry in the .htaccess file at the root directory of your web site. In this case, you should add the following line to .htaccess
: '''Important''': This method is only suitable for the Apache PHP ''module'' and will not work if PHP runs in CGI-mode.
php_flag register_globals off

'''Joomla's Global Register Emulator:'''
In the case where you have an extension that absolutely needs to have register_globals on, Joomla! 1.0.x provides an alternative approach that does not require a change to your global settings. The ''globals.php'' file in your site's root directory has an entry that lets Joomla! emulate a change to the register_globals site setting. You will find a line that looks as such:

define( 'RG_EMULATION', 0 );

You can change the zero to a one, if you want Joomla to emulate ''register_globals = on''.
[[Category:Landing Pages]]

Register globals

2011-11-14T17:58:56Z

Efduggan: /* How do I find the state of register_globals on my Joomla! install? */

{{review}}

== What is it? ==

<tt>register_globals</tt> is a PHP environment setting that has been the subject of controversy for sometime. Older versions of PHP often have this variable set to on and that setting is known to leave a site vulnerable to hacking. Further information is available at [http://us.php.net/register_globals the PHP website]. Current Joomla! releases do not require this setting to be on, and best practices dictate that it should be changed to off. (Joomla! 1.0.x releases also have a related emulator for this setting, which was implemented for backward compatibility with older components and extensions. ''It is generally preferred not to enable this capability''.) If you have a component that requires this setting, you should look for an update, or find an alternative component.

== How do I find the state of register_globals on my Joomla! install? ==
J 1.5 Log in to Joomla! administration, go to Help -> System Info, click on the PHP Settings tab, and look for the Register Globals entry.
J1.6+ Log in to Joomla! administration, go to Site -> System Information, click on the PHP Settings tab, and look for the Register Globals entry.

== Can I change it? ==
Yes, maybe. Depending on how much control you have over your server, there are several approaches to addressing this setting.

If you have complete control of your server, then you probably want to make sure that your main PHP configuration file (which is typically found in /usr/local/lib/php.ini) has the directive ''register_globals'' set to 0(zero).

If you're in a shared web environment, most likely your hosting provider will not let you modify the global php.ini file. You have a couple of options in this case.

== Where do I change it? ==
Possibly the easiest thing to do is to ask your hosting provider to make this change for your domain. (Often this is accomplished by logging a technical support request.) But not all providers will make this change for you. So you may not be so lucky. The good news is that there are likely other options available to you, and here are some of them.

'''Local php configuration file:'''
If you have access to your web site's root directory, you should be able to include your own copy of a php.ini file. Your copy only needs to include the settings that you want to alter from the global settings.

'''Change to .htaccess:'''
Another option is to introduce the preferred setting by making an entry in the .htaccess file at the root directory of your web site. In this case, you should add the following line to .htaccess
: '''Important''': This method is only suitable for the Apache PHP ''module'' and will not work if PHP runs in CGI-mode.
php_flag register_globals off

'''Joomla's Global Register Emulator:'''
In the case where you have an extension that absolutely needs to have register_globals on, Joomla! 1.0.x provides an alternative approach that does not require a change to your global settings. The ''globals.php'' file in your site's root directory has an entry that lets Joomla! emulate a change to the register_globals site setting. You will find a line that looks as such:

define( 'RG_EMULATION', 0 );

You can change the zero to a one, if you want Joomla to emulate ''register_globals = on''.
[[Category:Landing Pages]]

J1.5:Creating a CSS Drop down Menu

2011-02-20T06:04:50Z

Efduggan: got rid of duplicate paragraph.

To emphasize W3C valid code and lean pages, neither Flash nor JavaScript are generally considered to be favourable. Many (drop down) menu solutions make use of one of these two. There are a number of techniques one can use to get more visually attractive (drop down) menus, almost solely using cascading style sheet (CSS) and limiting the use of Javascript.

All use unordered lists (ul) to create the menu. An often-used solution is the drop down menus called “Suckerfish” or "Son of Suckerfish." It's pure CSS, very lean, hack free and employs just 12 lines of JavaScript to fix some problems with Microsoft Internet Explorer 6 and earlier. You can see a [http://www.htmldog.com/articles/suckerfish/dropdowns/example/ demo] of what can be created with Suckerfish. More detailed guides about the Suckerfish technique can be found at [http://www.htmldog.com/articles/suckerfish/dropdowns/ htmldog.com] and [http://www.alistapart.com/articles/dropdowns/ alistapart.com].

__toc__

__toc__
==Suckerfish Combined with the Extended Menu Module==
In order to let Suckerfish function well, you need your menu in the form of a good clean list. It just so happens that there is a module out there to do this. It's called Extended Menu (Module Type: mod_exmenu-j15). You can find it [http://extensions.joomla.org/extensions/163/details Extended menu] and in the [http://extensions.joomla.org JED].

Download and install the module. Now let’s set it up:

In the main Joomla interface, open the '''Extensions''' menu and choose the '''''Module Manager'''''.

Select your newly added Extended Menu Module by clicking on its name - it'll probably be fairly close to the bottom of the list.

• Assign a '''Menu suffix''' and a '''Module class suffix''' of "mainnav" (unless you change the CSS, below)

• Set '''Menu style''': Tree List

• Set '''Expand Menu''': Yes (don't worry about the tooltip description here - the CSS code takes care of hiding and showing the sub-menus, so they need to always be visible.)

• You can leave the other settings here at their defaults.

In order to see it in action, you will likely want to select a set of menus for it to display.

===The Cascading Style Sheet===
You can either add these CSS selectors to your existing template.css or create a new CSS file. If you create a new file be sure to include a reference to it inside the <head>..</head> section of your template's index.php file.

<source lang="css">
#twocols{ /* The columns that gets dropped down over yours might be different. */
z-index:20;
}

#leftcol{ /* The columns that gets dropped down over yours might be different. */
z-index:10;
}

.moduletablemainnav { /* I have absolutely positioned the module, you might have a different scheme. */
position:absolute;
top:187px;
left:20px;
z-index:100;
font:0.9em Verdana, Arial, Helvetica, sans-serif;
margin:0;
padding:0;
}

#mainlevelmainnav,#mainlevelmainnav ul {
float:left;
list-style:none;
line-height:1em;
background:transparent;
font-weight:700;
margin:0;
padding:0;
}

#mainlevelmainnav a {
display:block;
color:#f90;
text-decoration:none;
margin-right:15px;
padding:0.3em;
}

#mainlevelmainnav li {
float:left;
padding:0;
}

#mainlevelmainnav li ul {
position:absolute;
left:-999em;
height:auto;
width:11em;
font-weight:400;
background:#36f;
border:#00C 1px solid;
margin:0;
}

#mainlevelmainnav li li {
width:11em;
}

#mainlevelmainnav li ul a {
width:11em;
color:#fff;
font-size:0.9em;
line-height:1em;
font-weight:400;
}

#mainlevelmainnav li:hover ul ul,#mainlevelmainnav li:hover ul ul ul,#mainlevelmainnav li.sfhover ul ul,#mainlevelmainnav li.sfhover ul ul ul{
left:-999em;
}

#mainlevelmainnav li:hover ul,#mainlevelmainnav li li:hover ul,#mainlevelmainnav li li li:hover ul,#mainlevelmainnav li.sfhover
ul,#mainlevelmainnav li li.sfhover ul,#mainlevelmainnav li li li.sfhover ul {
left:auto;
z-index:6000;
}

#mainlevelmainnav li li:hover,#mainlevelmainnav li li.sfhover {
background:#039 url(../images/soccerball.gif) 98% 50% no-repeat;
}
</source>

Make sure you have the z-indexes set up properly. Also remember, in order to have a z-index, the element needs some sort of positioning. If not absolute, then relative.

===The JavaScript File===
You need to insert a reference to the JavaScript file for early versions of Microsoft Internet Explorer into the head of your template's index.php file.

<source lang="javascript">
<script type="text/javascript"><![CDATA[//><!]]></script>
</source>

==Suckerfish Combined with the Default Joomla! Menu Module==
The second approach is to implement a Drop Down menu using the mod_mainmenu module that comes with Joomal 1.5. I've played around with the “suckerfish” and CSS to make this work. This work perfectly in IE 7 as well as Netscape.

1. Create your Menu with the following Hierarchy:

Menu 1.

– Menu 1 Sub Menu 1.

– Menu 1 Sub Menu 2.

– Menu 1 Sub Menu 3.

2. Make sure the parameters are set to:

• Menu Style is set to List.

• Always show sub-menu Items is set to Yes.

• Menu Class Suffix is set to <b>san</b> - you can pick you own, but then make sure you change it in CSS & JS files.

3. Insert this piece of JS in your template index.php <head> tag, or in Javascript file that’s called from index.php

<source lang="javascript">
/* ********* drop down menu Java script code - start **********/
<script type=”text/javascript”><!–//–><![CDATA[//><!– // don’t need this line if using .JS file
sfHover = function()
{
var sfEls = document.menusan.getElementsByTagName(”LI”);

for (var j=0; j<sfEls.length; j++)
{
sfEls[j].onmouseover=function()
{
this.className+=” sfhover”;
}
sfEls[j].onmouseout=function()
{
this.className=this.className.replace(new RegExp(” sfhover\\b”), “”);
}
}
}
if (window.attachEvent) window.attachEvent(”onload”, sfHover);
//–><!]]></script> // don’t need this line if using .JS file

/* ********* drop down menu Java script code – end **********/
</source>

4. Here's the corresponding CSS

Either add these CSS selectors to your template's existing template.css file or create a new CSS file, name it and include it between the <head>...</head> section of the index.php.

<source lang="css">
/****************** Dropdown Menu styling starts here **************/
.menusan
{
/* Use these parameters to positions your menu. */
position: relative;
left: 10px;
}

.menusan, .menusan li, .menusan li ul { /* all lists */
padding: 0;
margin: 0;
list-style: none;
}

.menusan li a {
display: block;
width: 10em;
color:#FFFFFF ;
background-color:#BC031F;
border:2px solid #BC031F;
text-decoration:none;
}

.menusan li { /* all list items */
float: left;
width: 10em; /* The width is needed by the Opera browser. */
border-bottom:1px solid #ccc;
}

.menusan li ul { /* second-level lists */
position: absolute;
width: 10em;
left: -98%; /* Use left instead of display to hide menus; display: none isn’t read by screen readers. */
}

.menusan li a:hover {
border:2px solid #8C7AD6;
background-color:#8C7AD6;
color:#fff;
}

.menusan li:hover ul, .menusan li.sfhover ul { /* lists nested under hovered list items */
left: auto; /* change is to 10px, 20px, etc for indenting the sub menu */
}
/* **************** Dropdown Menu styling end here ***************/
</source>

5. Save all.

===Hint===
You can use a single menu to create multiple drop downs menus. Just create the menu in the following hierarchy and you’ll have 2 drop down menus, Menu 1 & Menu 2.

Menu 1.

– Menu 1 Sub Menu 1.

– Menu 1 Sub Menu 2.

– Menu 1 Sub Menu 3.

Menu 2.

– Menu 2 Sub Menu 1.

– Menu 2 Sub Menu 2.

– Menu 2 Sub Menu 3.

You might have to play with CSS a bit to work out the positions of the second menu etc. (Note: This did not work on the Chrome Browser 5.0.)

[[Category:Tips and tricks]]
[[Category:Tips and tricks 1.0]]
[[Category:Tips and tricks 1.5]]
[[Category:Tutorials]][[Category:Templates]]

==Suckerfish Combined with the Default Joomla! Menu Module==
The second approach is to implement a Drop Down menu using the mod_mainmenu module that comes with Joomal 1.5. I've played around with the “suckerfish” and CSS to make this work. This work perfectly in IE 7 as well as Netscape.

1. Create your Menu with the following Hierarchy:

Menu 1.

– Menu 1 Sub Menu 1.

– Menu 1 Sub Menu 2.

– Menu 1 Sub Menu 3.

2. Make sure the parameters are set to:

• Menu Style is set to List.

• Always show sub-menu Items is set to Yes.

• Menu Class Suffix is set to <b>san</b> - you can pick you own, but then make sure you change it in CSS & JS files.

3. Insert this piece of JS in your template index.php <head> tag, or in Javascript file that’s called from index.php

<source lang="javascript">
/* ********* drop down menu Java script code - start **********/
<script type=”text/javascript”><!–//–><![CDATA[//><!– // don’t need this line if using .JS file
sfHover = function()
{
var sfEls = document.menusan.getElementsByTagName(”LI”);

for (var j=0; j<sfEls.length; j++)
{
sfEls[j].onmouseover=function()
{
this.className+=” sfhover”;
}
sfEls[j].onmouseout=function()
{
this.className=this.className.replace(new RegExp(” sfhover\\b”), “”);
}
}
}
if (window.attachEvent) window.attachEvent(”onload”, sfHover);
//–><!]]></script> // don’t need this line if using .JS file

/* ********* drop down menu Java script code – end **********/
</source>

4. Here's the corresponding CSS

Either add these CSS selectors to your template's existing template.css file or create a new CSS file, name it and include it between the <head>...</head> section of the index.php.

<source lang="css">
/****************** Dropdown Menu styling starts here **************/
.menusan
{
/* Use these parameters to positions your menu. */
position: relative;
left: 10px;
}

.menusan, .menusan li, .menusan li ul { /* all lists */
padding: 0;
margin: 0;
list-style: none;
}

.menusan li a {
display: block;
width: 10em;
color:#FFFFFF ;
background-color:#BC031F;
border:2px solid #BC031F;
text-decoration:none;
}

.menusan li { /* all list items */
float: left;
width: 10em; /* The width is needed by the Opera browser. */
border-bottom:1px solid #ccc;
}

.menusan li ul { /* second-level lists */
position: absolute;
width: 10em;
left: -98%; /* Use left instead of display to hide menus; display: none isn’t read by screen readers. */
}

.menusan li a:hover {
border:2px solid #8C7AD6;
background-color:#8C7AD6;
color:#fff;
}

.menusan li:hover ul, .menusan li.sfhover ul { /* lists nested under hovered list items */
left: auto; /* change is to 10px, 20px, etc for indenting the sub menu */
}
/* **************** Dropdown Menu styling end here ***************/
</source>

5. Save all.

===Hint===
You can use a single menu to create multiple drop downs menus. Just create the menu in the following hierarchy and you’ll have 2 drop down menus, Menu 1 & Menu 2.

Menu 1.

– Menu 1 Sub Menu 1.

– Menu 1 Sub Menu 2.

– Menu 1 Sub Menu 3.

Menu 2.

– Menu 2 Sub Menu 1.

– Menu 2 Sub Menu 2.

– Menu 2 Sub Menu 3.

You might have to play with CSS a bit to work out the positions of the second menu etc. (Note: This did not work on the Chrome Browser 5.0.)

[[Category:Tips and tricks]]
[[Category:Tips and tricks 1.0]]
[[Category:Tips and tricks 1.5]]
[[Category:Tutorials]][[Category:Templates]]

J2.5:What's new in Joomla 2.5

2010-11-30T02:07:06Z

Efduggan: Added Beta 15 release date

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareFormData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010
*Beta 15: 29 November 2010

[[Category:Joomla! 1.6]]

J2.5:What's new in Joomla 2.5

2010-11-18T20:58:23Z

Efduggan: Added beta release dates for beta 11 - 14

The principal changes introduced in Joomla 1.6 are:-

* '''New Access Control System''' - Allows site administrators control over who can view and manage content.
* '''Unlimited Depth Organizational Model''' - Gives site administrators and content creators user-defined category levels that allow for the creation of a category tree with as many or as few levels for organizing articles and other content as needed.
* '''One-Click Extension Updates''' - Allows users to keep sites secure and controlled by simplifying the process of updating extensions.
* '''Semantic XHTML Layouts''' - Provides a better baseline for content presentation.

The following is a more complete list of changes.
==Administrators==
===Introduction===
*Consistent UI
*Consistent Features
*Richer sample data
*IE 7+, Firefox 3.x, Safari 4.x
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)

===Administrator===
*Menu Changes
*Submenu consistency

====Toolbar Features====
*Save
*Save & Close
*Save & New
*Save as Copy
*Expired session will return to the page you were on then you got logged out (can be hit and miss)
*Most search filters allow you to search for a record id via [ id:123 ]
*"Parameters" are now referred to as "Options"
*Template Styles
*Integrated Trash Management
*Consistent archive support for most content
*Extension Installer Improvements

===Module Enhancements===
*Publish up and down
*Add option to display on all pages "except" selected
*Expanded Category System
*404 Page Redirection
*Better Menu Management
*Alternative layouts for content, modules and menus (taken from the home template)

===New Templates===
*Atomic
*Beez2
*(Administrator) Bluestork (replaces Khephri)
*(Administrator) Hathor
*Legacy layer in Milkyway
*Backend supports layout overrides
*New Modules
*New Plugins
*Content Languages
*User Login Permissions
*Activate selected users from the user list now (and filter)
*Administrator registration approval
*Polls component removed
*New codemirror editor

===SEO Improvements===
*Meta decription and keywords for categories
*Articles can change the page title and page header separately

===Global Configuration===
*Add site name to titles
*Default Access Level
*Set Metadata Language (buggy)
*Unicode Aliases
*Cookie domain and path
*User Setting moved to User Manager -> Options
*Media Settings moved to Media Manager -> Options
*Debug Modules - allows you to enabled to disable the tp=1 feature
*Server Timezone now a location, not an integer offset
*New Global Permissions tab

===User Manager===
*Can activate a user from the list now
*User can be assigned to multiple groups
*Manage user groups
*Manager content access levels

===Media Manager===
*Flash uploader fixed

===Menu Manager===
====Menus List====
*Rebuild button to press when you brick the menu
*Clicking the menu name brings up the menu items list rather than going into Edit Menu. To edit the menu, click on the check box next to the name and click on the Edit icon in the toolbar.

====Items List====
*Menus support the language filter
*Default now called Home
*Home is now clickable in the menu item list
*A separate home can be set for different languages

=====New batch operations=====
*Set access level
*Copy or move to another part of this or another menu

====Edit Item====
*Improved "Type" selector with human readable view and layout names
*Note field added
*New window target
*New Language assignment
*New Template style
*Ability to add & edit Module assignments from this page

=====New options for the menu links and pages themselves=====
*Link title attribute
*Link CSS style
*Menu image is changed to a modal selector
*CSS class for page heading
*Page meta description
*Page meta keywords
*Robots options

===Articles Manager===
*Frontpage is now referred to as Featured
*Article manager uses submenu to quickly skip between articles , categories and featured
*Sections and categories are now merged.

====Articles List====
*''"Missing move and copy; filter by author"''
*New column to show language
*Filtering by language available

====Article Edit====
*Created by user now selected by modal popup
*New ability to set the page title from the article
*Define create, delete, edit and publishing permissions

====Archived Articles====
*In 1.5, Archived Articles had to first be changed to Published or Unpublished before update.
*In 1.6, an Article with an Archived Status *can* be changed without changing the State first.

===Categories===
====Category List====
*Nested view
*Filtering on language

====Edit Category====
*New note field
*Section replaced with ability to assign a parent category
*Ability to assign content language

=====New Options (not previously available in 1.5)=====
*Assign alternate layout
*Define create, delete, edit and publishing permissions
*Meta description
*Meta keywords
*Alternative page title
*Meta author
*Meta robots

===Banners===
====Banners list====
* Missing copy toolbar button
*New archive toolbar button
*New columns to show meta keywords, purchase type and language
*New filtering by client and language

====Edit Banner====
*New type toggle for Image or Custom (dynamically changes the available form fields)
*New alt text field for image
*New language field

=====New Options=====
*Ability to set the created date
*Ability to set start and finish publishing times
*Ability to set the purchase type
*Ability to track impressions
*Ability to track clicks
*Use own prefix ?
*Tags renamed to meta
*Contacts
*Messaging
*Newsfeeds
*Search
*Weblinks
*Redirect

===Extensions Manager===
====Discover====
*Module mgr
*Plugin Mgr
*Template Mgr
*Language mgr

===Misc===
*Auto create linked contact when creating new user ??

==Access Controls==
*Introduction
*User Groups
*Access Levels
*Permission Layers
*How Permissions are Inherited
*How to debrick your site

==Developers==
===Introduction===
*PHP 5.2.4+
*MySQL 5.0.4 (allows for wide varchars)
*IE7+, Firefox 3+, Safari 4+
*Focus on code consistency
*Focus on code reduction

Usage of PHP Native Functions where possible, for example:
*[[JXMLElement]] extends the native [http://php.net/manual/en/book.simplexml.php SimpleXML] class
*[[JDate]] extends the [http://www.php.net/manual/en/class.datetime.php DateTime] class
*Native INI parser to load languages

===Removed features===
*ADODB compatibility methods in database classes
*DOMIT (unsupported XML library)
*Legacy mode (includes global $mainframe, etc)
*JTemplate (based on patTemplate)
*patTemplate (templating engine)
*PDF support
*PEAR libraries (due to license incompatibilities)
*phpgacl
*PHP 4.0 and 5.0 compatibility files
*XStandard Editor

===Deprecated Features===
*JController::_acoSection
*JController::_acoSectionValue
*JController::authorize()
*JController::setAccessControl()
*JDatabase::stderr()
*JDate::offest
*JDate::setOffset()
*JDate::toFormat() - use JDate::format() instead
*JException::toString()
*JFactory::getXMLParser()
*JHtmlGird::access()
*JHtmlImage::administrator - use JHtml::image instead
*JHtmlImage::site - use JHtml::image instead
*JHtmlList::accesslevel()
*JHtmlList::specificordering() - use JHtml::_('list.ordering')
*JHtmlList::category()
*JHtmlSelect::optgroup() - see JHtmlSelect::groupedList()
*JLanguage::_parseLanguageFiles - renamed to parseLanguageFiles
*JLanguage::_parseXMLLanguageFile - renamed to parseXMLLanguageFile
*JLanguage::_parseXMLLanguageFiles - renamed to parseXMLLanguageFiles
*JObject::toString - replaced with magic method
*JRegistry::getNameSpaces()
*JRegistry::getValue()
*JRegistry::makeNameSpace()
*JRegistry::setValue()
*JPane - See JHtmlSliders
*JParameter - replaced by JForm
*JSimpleXML, JSimpleXMLElement - Use JXMLElement instead, based on the native SimpleXMLElement
*JTable::canDelete() - models or controllers should be doing the access checks
*JTable::toXML()
*JToolbarHelper customX(), addNewX(), editListX(), editHtmlX(), editCssX(), deleteListX()
*JUser::authorize() - Use JUser::authorise()
*JUtility::dump()
*JUtility::array_unshift_ref() - Not needed in PHP 5
*JUtility::getHash() - Use JApplication::getHash()
*JUtility::getToken() - Use JFactory::getSession()->getFormToken()
*JUtility::isWinOS() - Use JApplication::isWinOS()
*JUtility::return_bytes() - See InstallerModelWarnings::return_bytes()
*JUtility::sendMail() - Use JFactory::getMailer()->sendMail()
*JUtility::sendAdminMail() - Use JFactory::getMailer()->sendMail()
*JXMLElement::data() - Provided for backward compatibility
*JXMLElement::getAttribute() - Provided for backward compatibility

===Database===
*JTable now automatically looks up the fields from the database schema
*New JDatabaseQuery - A chained CRUD query builder
*New JDatabase::getNextRow
*New JDatabase::getNextObject
*JDatabase::loadAssocList - Now takes a second argument to just return the value of a column
*JDatabase::setQuery - Added chaining support

====Important Schema Changes====
*New jos_extensions table to list all extensions
*Components table information moved and split between jos_extensions and jos_menu (special menu called _adminmenu)

The old phpgacl (jos_core_acl*) and jos_groups tables have been reworked into:
*jos_assets
*jos_user_usergroup_map
*jos_usergroups
*jos_viewlevels
*Archived state changed from a value of -1 to +2

===Improved MVC===
====Models====
*JModelList
*JModelForm
*JModelAdmin
*Format handling (eg JSON)
*Sub-controller handling

====Controllers====
*JControllerForm
*JControllerAdmin
*JController::setMessage takes second arg to set the message type
*JController can set the default view
*Added chaining support to several JController methods

====Views====
*Semantic core output
*Milkyway legacy layouts
*The old component parameters are not automatically added to the menu anymore. You need to explicitly put them in the layout XML files.
*The menu manager will now detect additional layouts for a given view in the default template.

===Form API===
====Event manipulation====
*onContentPrepareForm
*onContentPrepareFormData

===Translation and Language Support===
*Support for unicode slugs, eg, SEF URL's with Greek characters
*3-letter languages now supported, xxx-XX
*All existing language keys have been refactored

====INI files must validate====
*Upper case key with no spaces, alphanumeric characters and underscores
*Quoted values
*Double quotes within literal strings must use _QQ_ in the form KEY="<a href="_QQ_"index.php"_QQ_">Click</a>"

====Javascript translation layer====
*See the flash uploader script for an example
Local extension language files

====Language file API====
*Pluralisation support
*Transliteration support for ASCII or Unicode slugs
*Ignore Search Words
*Minimum search word length
*Custom language overrides
*System language file to support administrator menu and installation (.sys.ini)

====Language switcher====
*Language Filter plugin enables language switching
*Sets the automatic filtering via JFactory::getApplication()->setLanguageFilter(true)
*A frontend component with language support would test JFactory::getApplication()->getLanguageFilter(), which returns the selected language code from the Languages Module
*The language field can be a language code for a single language, or "*" to be displayed for all languages
*Community extension for language maintenance com_localise

===Extension management===
====New installation types====
=====Libraries=====
*Must include an XML manifest where type="library"
*Can only be installed into a sub-folder of /libraries/
*Can extend parts of an existing library, eg /libraries/joomla/database/database/oracle.php

=====Packages multi-installer=====
*Must include an XML manifest where type="package"
*A package is a zip of zip's

New install script can be provided with 5 methods:
=====preflight=====
*Runs before anything is run and while the extracted files are in the uploaded temp folder

======Could allow for:======
*secondary extraction of custom zip's
*version checks to be performed
*halting the installer on an error

=====install / update=====
*Runs after the database scripts are executed
*If the extension is new, the install method is run
*If the extension exists then update method is run if method="upgrade", otherwise assumes that the extension is not meant to be upgradable

=====postflight=====
*Runs after the extension is registered in the database
*Is not run for the uninstall process (nothing left to do obviously)

====Discover====
*Does not do any file copying, only works with what it finds
*Performs preflight, install and postflight
*Developer of installer has two language files??

====Update site====
*Can publish an XML manifest on your site that can include individual extensions and extension sets.

====XML Manifest Changes====
*<install> is deprecated - use <extension>
*New <update> tag. Takes a <schemas> tag which can define <schemapath>
*<params> and <param> tags are deprecated, use <fields>, <fieldsets> and <field> instead

====File changes====
*Installation manifest must be the same name as the extension, eg com_foobar/foobar.xml This helps with discovery (otherwise the function has to go through all the files in the extension folder
*Plugins are now in folders like modules and components
*See SVN/tests/_data/installer_packages/ for complete examples of all extensions and manifests.
*The method="upgrade" will compare individual files in the original and incoming manifests and will remove files as appropriate. However, it will not remove differences in the <folder> tags.
*Future support for rollback

===Events===
====New Events====
*onBeforeRender
*onContentBeforeDelete
*onContentAfterDelete
*onContentChangeState
*onContentPrepareForm
*onContentPrepareFormData
*onExtensionBeforeInstall
*onExtensionBeforeUpdate
*onExtensionBeforeUninstall
*onExtensionAfterInstall
*onExtensionAfterUpdate
*onExtensionAfterUninstall

====Renamed Events====
*onContentAfterSave
*onContentAfterTitle
*onContentAfterDisplay
*onContentBeforeDisplay
*onContentBeforeSave
*onContentSearch
*onContentSearchAreas
*onUserAuthenticate
*onUserAfterDelete
*onUserAfterSave
*onUserBeforeDelete
*onUserBeforeSave
*onUserLogin
*onUserLogout
*All content events (except for search and search areas) now pass a 'context' as the first argument to alert the plugin as to what type of content is being passed. The plugin event may or may not heed this context.

===Categories===
*Component can provide custom options for its own categories via optional category.xml
*Supported via JTableNested

===Access Controls===
*A thing that can be controlled by permissions is registered in the assets table
*JTable handles this transparently via asset_id field
*For view permissions, support is as simple as adding
:::$user = JFactory::getUser();
:::$groups = implode(',', $user->authorisedLevels());
:::$query->where('a.access IN (' . $groups . ')');

For action permissions, same format as in 1.5:
$user->authorise($actionName, $assetName)
*OpenID library moved to plugin folder
*Geshi library moved to plugin folder
*JRegistry notes defaults to JSON (new format), dynamically converting existing data in INI format
*New JStream
*New JApplicationHelper::getComponentName
*Core icons moved to /media/
*Backward incompatible change to JEditor::display
*Added chaining support to JMail
*JFilterInput can no longer be called statically
*JHtml::image now supports relative paths
*All system images are overridable in the default template
*New JHtmlString
*Added wincache session handler for IIS
*New JFilterOutput::stripImages
*JPath::check takes second arg for separator (to pass to JPath::clean)
*Expanded configuration support through config.xml (multiple tabs)

====Core actions====
*core.login.site
*core.login.admin
*core.admin
*core.manage
*core.create
*core.edit
*core.edit.state
*core.delete
*Miscellaneous changes

===Debug Plugin===
*More tools for assisting with translation

===Mootools 1.2/1.3===
*Need to use document.id instead of $

==Cache changes ==
===API changes relevant to 3rd party developers===
====Component view cache====

Component view cache now takes an array of url parameters and their types to create Cacheid. This is a replacement for a previous unsafe way which took the whole URL for this and so opened the doors for DOS attacks via random url parameters added to request URL's.

Com_contact example:

<pre>
$safeurlparams = array(
'id'=>'INT',
'catid'=>'INT', 'limit'=>'INT',
'limitstart'=>'INT',
'filter_order'=>'CMD',
'filter_order_Dir'=>'CMD'
);

parent::display($cachable,$safeurlparams);
</pre>

Old cacheid created from URL was retained for backwards compatibility and takes effect if there are no $safeurlparams.

====Module cache====
This has been completly reconceptualized. Module cache now has 5 different modes of operation, 3 of them are to be set from module XML file, while 2 are meant to be used from within the module itself. Default is backwards compatible oldstatic mode that requires no changes to a module.

Modes to be set in XML:
*'''static''' - one cache file for all pages with the same module parameters
*'''oldstatic''' - 1.5. definition of module caching, one cache file for all pages with the same module id and user aid. Default for backwards compatibility
*'''itemid''' - changes on itemid change

In addition to cache field that was required in 1.5 there is now another hidden field called cachemode that sets any of the above modes.

<pre>
<field name="cachemode" type="hidden" label="" default="static">
<option value="static"></option>
</pre>

Modes to be called from inside the module:
*'''safeuri''' - id is created from $cacheparams->modeparams array, the same as in component view cache
*'''id''' - module sets own cache id's

To use this modes one must rename cache field in xml to owncache field and call JModuleHelper::ModuleCache from within the module's main php file. This is actually a shortcut to cache callback to avoid code duplication in every module.

An example that uses safeuri mode and replaces uncached
$list = modRelatedItemsHelper::getList($params) :

<pre>
$cacheparams = new stdClass;
$cacheparams->cachemode = 'safeuri';
$cacheparams->class = 'modRelatedItemsHelper';
$cacheparams->method = 'getList';
$cacheparams->methodparams = $params;
$cacheparams->modeparams = array('id'=>'int','Itemid'=>'int');
$list = JModuleHelper::ModuleCache ($module, $params, $cacheparams);
</pre>

====Functional changes====
'''Cache administration (Clean cache, Purge cache) now works with all drivers''', not only with file cache.
'''New standalone garbage collect script''' that is to be called from crontab has been added. It can be found in libraries/joomla/utilities/garbagecron.php . For safety reasons it is recommended that it is renamed to something unique.

====CMS and framework level functional changes====
'''Caching is implemented in all components and modules''' that can potentially gain from cache.
Caching has also been added to some most expensive and frequent framework calls JComponentHelper::_load(), JModuleHelper::_load(),JMenuSite::load();

====Cache library changes====
Cache library has been completely refactored.
*Cache '''handlers have been renamed to controllers''' to better reflect their role and avoid confusion with cache storage handlers (referred to as drivers in following text).
*'''New JCacheController''' parent class has been added and inheritance has been changed to prevent bugs occurring from controller's and storage handler's get method clashes.

====JCache====
*'''getAll()''' method was added to JCache, JCacheStorage and all drivers, and it returns all cached items (this was previously possible only with file driver and hardcoded in administration)
*New '''lock and unlock''' methods were added to JCache, JCacheStorage and drivers. They enable cache item locking and unlocking to prevent errors on parallel accesses and double saves. This functionally was also implemented in controllers.
*Workarounds are now consolidated in new '''JCache getWorkarounds and setWorkarounds''' methods, are now used by all controllers and their use has been made optional.
*New makeId() method in JCache that creates cache id from registered url parameters set by components and system plugins

====JCacheController====
New parent class to Controllers that also functions as an intermediate to JCache. There is no JObject inheritance as otherwise magic __call doesn't work.
Change was needed to prevent bugs occurring from controller's and storage handler's get method clashes. They could be renamed but this would break backwards compatibility.

====JCacheStorage====
*_getCacheId method was moved from drivers to their parent JCacheStorage and all drives now use the same method by default
*CacheItem was moved from cache admin to framework JCacheStorageHelper, it is used by getAll
*There are new cachelite and wincache drivers. All other drivers have been fixed with missing functions (gc, clean) added, their code cleaned and tested they should be now working properly.
*Replaced separate _expire files in filecache driver with timestamps (this should amount to cca. 40% speed gain). The same in all drivers that had this.
*Numerous bugfixes on all levels, most important is proper use of options defaulting to configuration parameters settings and correctly passing from level to level.

====Other framework level changes====
*Safe url parameters registration added to JControler view method.
*New ModuleCache method in JModuleHelper that performs the above described module cache (in 5 modes) for both, modules and module renderer.
*JFactory::getFeedParser has been changed to use Joomla caching instead of simplepie's.

==Performance==
===Eliminate the usage of JTable for general browsing on the frontend===
*Session drops the usage of JTable
*Item views use a dedicated question, not JTable->load

==Known Issues==
*Still Mootools 1.2. Will be upgrading to 1.3 during the beta process.
*Scaling issues to address

==Notes==
===Releases===
*Alpha 1: 22 June 2009
*Alpha 2: 25 October 2009
*Beta 01: 18 May 2010
*Beta 02: 31 May 2010
*Beta 03: 14 June 2010
*Beta 04: 28 June 2010
*Beta 05: 12 July 2010
*Beta 06: 26 July 2010
*Beta 07: 09 August 2010
*Beta 08: 23 August 2010
*Beta 09: 06 September 2010
*Beta 10: 20 September 2010
*Beta 11: 03 October 2010
*Beta 12: 17 October 2010
*Beta 13: 31 October 2010
*Beta 14: 14 November 2010

[[Category:Joomla! 1.6]]

Talk:Main Page

2010-11-18T20:51:00Z

Efduggan:

Hi,
you've found the main page for Joomla! documentation.

If you cannot find the answer you are looking for, consider asking on the Joomla! forum at http://forum.joomla.org/[http://forum.joomla.org/]

Thanks!

Talk:Main Page

2010-11-18T20:50:25Z

Efduggan: Removed call for help - put link into Joomla forums

Hi,
you've found the main page for Joomla! documentation.

If you cannot find the answer you are looking for, consider asking on the Joomla! forum at [http://forum.joomla.org/]Thanks!