Joomla! Documentation - User contributions [en]

Portal:Template Development/Reading list

2013-04-12T16:07:53Z

Lemings:

* [[Accessibility]]
* [[Beez]] - an accessible default template
* [[Creating clickable background images using CSS]]
* The [[Joomla! 1.5 Template Tutorial]] is a work in progress. If you would like to help out with it, please take a look at the [[JDOC:Joomla! 1.5 Template Tutorials Project|main project page]] and the [[JDOC:Joomla! 1.5 Template Tutorials Project/Outline|Outline for Template Tutorials]].
* Jim Yuzwalk has contributed a useful [http://help.joomla.org/files/JJYs_Joomla_Template_Design_Tutorial-2010_08_26.pdf introduction to Joomla templates] (download the example template from [http://help.joomla.org/files/JJYs_Example_Joomla_Template_2010_05_07.zip here]).
* [[Changing the site favicon]]
* [[Using Class Suffixes]]
* [[Using Firebug With Your Joomla Website]] {{JVer/multi|1.0,1.5,1.6,1.7,2.5}}
* [[Understanding Output Overrides]] {{JVer/multi|1.5,2.5,3.0}}
* [[Layout Overrides in Joomla 2.5]] {{JVer/multi|1.6,2.5,3.0}}
* [[Creating custom template parameter types]] {{JVer/multi|1.5}}
* [[How are templates executed?]]
* [[How to determine if the user is viewing the front page]]
* [[Template parameters]] {{JVer/multi|1.5}}
* [[jdoc statements]]
* [[Objects methods and properties available from your template]] - what you can do with <code>$this</code>
* [[How to cloak email addresses]] {{JVer/multi|1.6,1.7,2.5,3.0}}
<noinclude>[[Category:Landing subpages|{{PAGENAME}}]]</noinclude>

Talk:Creating a profile plugin

2011-03-21T20:52:42Z

Lemings: /* profile to profile5 */ new section

[[User:Jcasal|Jcasal]] 13:17, 28 December 2010 (UTC)

The examples uses the language model for I18N of the plugin, but does not show how this elements are added to the plugin the language directories.

Looking at ''profile5.xml'' it indicates that the language files are to be found in:

<languages>
<language tag="en-GB">en-GB.plg_user_profile.ini</language>
<language tag="en-GB">en-GB.plg_user_profile.sys.ini</language>
</languages>

But these are the language files for the ''User:Profile'' plugin. So basically, the language translations would need to be done on another plugin's language files?

Should this tutorial show the plugin containing its own language files? For example:

<languages>
<language tag="en-GB">en-GB.plg_user_profile5.ini</language>
<language tag="en-GB">en-GB.plg_user_profile5.sys.ini</language>
</languages>

and examples of how these files would look like...

[[User:Jcasal|Jcasal]] 21:00, 28 December 2010 (UTC)

Actually, after lots of trial and error, I have found a few other things that needed to be updated, so the changes are now published. Hope they work for others and save you some time doing your first user profile extension plugin.

== profile to profile5 ==

I made the changes for plug-in to work as expected.

As before it was not running onUserAfterSave functon, because profile5 property in $data array was not set.

If profile keys stay the same in database, profile plugin wipes out profile5 keys and vice versa.

Creating a profile plugin

2011-03-21T20:49:17Z

Lemings: Changed 'profile' with 'profile5' to make plugin work.

Profile plugin is a new extension in Joomla! 1.6. It allows the addition of supplemental fields in the registration and profile forms of the com_user front end and in the user create/edit form in the back end.

A simple example plugin is included in the basic Joomla! installation as a proof of concept. Much more complex plugins are possible.

The example plugin takes advantage of on the onContentPrepareForm and onUserAfterSave events.

Multiple profile plugins may be included and will be rendered in sequence.

There are four separate places where profiles forms are used in core extensions, and each of these four can be manipulated separately if that is desired. The two locations in the front end are the user registration form and the user profile edit form. In the back end the locations are the edit screen for users in the user manager and the My Profile view found in the Admin menu.

This page shows an example of a second plugin, named profile5. It adds a single field called something.

This is the file structure

profile5.php
profile5.xml
en-GB.plg_user_profile5.ini
en-GB.plg_user_profile5.sys.ini
/profiles/profile.xml

The supplemental fields are created with xml file in the profiles folder.

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<form>
<fields name="profile5">
<fieldset name="profile5"
label="PLG_USER_PROFILE5_SLIDER_LABEL"
>
<field
name="something"
type="text"
id="something"
description="PLG_USER_PROFILE5_FIELD_SOMETHING_DESC"
filter="string"
label="PLG_USER_PROFILE5_FIELD_SOMETHING_LABEL"
message="PLG_USER_PROFILE5_FIELD_SOMETHING_MESSAGE"
size="30"
/>

</fieldset>
</fields>
</form>
</source>

profile5.php

<source lang="PHP">
<?php
/**
* @version $Id: profile.php 17685 2010-06-14 21:46:46Z dextercowley $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

defined('JPATH_BASE') or die;

/**
* An example custom profile plugin.
*
* @package Joomla.Plugins
* @subpackage user.profile
* @version 1.6
*/
class plgUserProfile5 extends JPlugin
{
/**
* @param string The context for the data
* @param int The user id
* @param object
* @return boolean
* @since 1.6
*/
function onContentPrepareData($context, $data)
{
// Check we are manipulating a valid form.
if (!in_array($context, array('com_users.profile', 'com_users.registration'))) {
return true;
}

$userId = isset($data->id) ? $data->id : 0;

// Load the profile data from the database.
$db = &JFactory::getDbo();
$db->setQuery(
'SELECT profile_key, profile_value FROM #__user_profiles' .
' WHERE user_id = '.(int) $userId .
' AND profile_key LIKE \'profile5.%\'' .
' ORDER BY ordering'
);
$results = $db->loadRowList();

// Check for a database error.
if ($db->getErrorNum()) {
$this->_subject->setError($db->getErrorMsg());
return false;
}

// Merge the profile data.
$data->profile5 = array();
foreach ($results as $v) {
$k = str_replace('profile5.', '', $v[0]);
$data->profile[$k] = $v[1];
}

return true;
}

/**
* @param JForm The form to be altered.
* @param array The associated data for the form.
* @return boolean
* @since 1.6
*/
function onContentPrepareForm($form, $data)
{
// Load user_profile plugin language
$lang = JFactory::getLanguage();
$lang->load('plg_user_profile5', JPATH_ADMINISTRATOR);

if (!($form instanceof JForm)) {
$this->_subject->setError('JERROR_NOT_A_FORM');
return false;
}
// Check we are manipulating a valid form.
if (!in_array($form->getName(), array('com_users.profile', 'com_users.registration','com_users.user','com_admin.profile'))) {
return true;
}
if ($form->getName()=='com_users.profile')
{
// Add the profile fields to the form.
JForm::addFormPath(dirname(__FILE__).'/profiles');
$form->loadFile('profile', false);

// Toggle whether the something field is required.
if ($this->params->get('profile-require_something', 1) > 0) {
$form->setFieldAttribute('something', 'required', $this->params->get('profile-require_something') == 2, 'profile');
} else {
$form->removeField('something', 'profile');
}
}

//In this example, we treat the frontend registration and the back end user create or edit as the same.
elseif ($form->getName()=='com_users.registration' || $form->getName()=='com_users.user' )
{
// Add the registration fields to the form.
JForm::addFormPath(dirname(__FILE__).'/profiles');
$form->loadFile('profile', false);

// Toggle whether the something field is required.
if ($this->params->get('register-require_something', 1) > 0) {
$form->setFieldAttribute('something', 'required', $this->params->get('register-require_something') == 2, 'profile');
} else {
$form->removeField('something', 'profile');
}
}
}

function onUserAfterSave($data, $isNew, $result, $error)
{
$userId = JArrayHelper::getValue($data, 'id', 0, 'int');

if ($userId && $result && isset($data['profile5']) && (count($data['profile5'])))
{
try
{
$db = &JFactory::getDbo();
$db->setQuery('DELETE FROM #__user_profiles WHERE user_id = '.$userId.' AND profile_key LIKE \'profile5.%\'');
if (!$db->query()) {
throw new Exception($db->getErrorMsg());
}

$tuples = array();
$order = 1;
foreach ($data['profile5'] as $k => $v) {
$tuples[] = '('.$userId.', '.$db->quote('profile5.'.$k).', '.$db->quote($v).', '.$order++.')';
}

$db->setQuery('INSERT INTO #__user_profiles VALUES '.implode(', ', $tuples));
if (!$db->query()) {
throw new Exception($db->getErrorMsg());
}
}
catch (JException $e) {
$this->_subject->setError($e->getMessage());
return false;
}
}

return true;
}
}
</source>

Profile5.xml controls whether the field is required, disabled or optional in the forms. Since profile5.php says to treat backend create/edit the same as registration only two sets of options are required, register and profile.

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>

<extension version="1.6" type="plugin" group="user">
<name>plg_user_profile5</name>
<author>Joomla! Project</author>
<creationDate>January 2008</creationDate>
<copyright>(C) 2005 - 2010 Open Source Matters. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<authorEmail>admin@joomla.org</authorEmail>
<authorUrl>www.joomla.org</authorUrl>
<version>1.6.0</version>
<description>PLG_USER_PROFILE5_XML_DESCRIPTION</description>

<files>
<filename plugin="profile5">profile5.php</filename>
<filename>index.html</filename>
<folder>profiles</folder>
</files>

<languages>
<language tag="en-GB">en-GB.plg_user_profile5.ini</language>
<language tag="en-GB">en-GB.plg_user_profile5.sys.ini</language>
</languages>

<config>
<fields name="params">

<fieldset name="basic">
<field name="register-require-user" type="spacer"
label="PLG_USER_PROFILE5_FIELD_NAME_REGISTER_REQUIRE_USER"
/>

<field name="register-something" type="list"
description="PLG_USER_PROFILE5_FIELD_SOMETHING_DESC"
label="PLG_USER_PROFILE5_FIELD_SOMETHING_LABEL"
>
<option value="2">JOPTION_REQUIRED</option>
<option value="1">JOPTION_OPTIONAL</option>
<option value="0">JDISABLED</option>
</field>

<field name="profile-require-user" type="spacer"
label="PLG_USER_PROFILE5_FIELD_NAME_PROFILE_REQUIRE_USER"
/>

<field name="profile-require_something" type="list"
description="PLG_USER_PROFILE5_FIELD_SOMETHING_DESC"
label="PLG_USER_PROFILE5_FIELD_SOMETHING_LABEL"
>
<option value="2">JOPTION_REQUIRED</option>
<option value="1">JOPTION_OPTIONAL</option>
<option value="0">JDISABLED</option>
</field>

</fieldset>

</fields>
</config>
</extension>
</source>

en-GB.plg_user_profile5.ini

; $Id: en-GB.plg_user_profile.ini 19353 2010-11-05 07:57:29Z infograf768 $
; Joomla! Project
; Copyright (C) 2005 - 2010 Open Source Matters. All rights reserved.
; License http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL, see LICENSE.php
; Note : All ini files need to be saved as UTF-8

PLG_USER_PROFILE5_XML_DESCRIPTION="User Profile 5 Plug-in"
PLG_USER_PROFILE5="User - Profile 5"
PLG_USER_PROFILE5_SLIDER_LABEL="User Profile 5"
PLG_USER_PROFILE5_FIELD_NAME_REGISTER_REQUIRE_USER="User profile fields for registration and administrator user profile 5 forms"
PLG_USER_PROFILE5_FIELD_NAME_PROFILE_REQUIRE_USER="User profile fields for profile 5 edit form"
PLG_USER_PROFILE5_FIELD_SOMETHING_DESC="Choose an option for the something filed"
PLG_USER_PROFILE5_FIELD_SOMETHING_LABEL="Something!"
PLG_USER_PROFILE5_FIELD_SOMETHING_MESSAGE="A Message for something!"
PLG_USER_PROFILE5_XML_DESCRIPTION="User Profile 5 Plug-in"

en-GB.plg_user_profile5.sys.ini

; $Id: en-GB.plg_user_profile.sys.ini 17052 2010-05-14 14:05:58Z infograf768 $
; Joomla! Project
; Copyright (C) 2005 - 2010 Open Source Matters. All rights reserved.
; License http://www.gnu.org/licenses/gpl-2.0.html GNU/GPL, see LICENSE.php
; Note : All ini files need to be saved as UTF-8

PLG_USER_PROFILE5="User - Profile 5 "
PLG_USER_PROFILE5_XML_DESCRIPTION="User Profile 5 Plug-in"

By installing profile5 you can add new fields in addition to the ones in profile. You can also control which view levels see those fields.
Alternatively, you can write a more complex common plugin with varying controls for different groups.

[[Category:Tutorials]][[Category:Plugin Development]]

Joomla info page/lv-LV

2010-09-01T08:31:35Z

Lemings:

{{RightTOC}}
= Latviešu=

== Kas ir Joomla? ==
Joomla ir informācijas pārvaldības sistēma (CMS), ar kā palīdzību iespējams izveidot interneta vietnes un dažāda tiešsaites aplikācijas. Joomla ir saņēmusi vairākas balvas dažādās nominācijās, kas apliecina tās kvalitāti. Lietošanas ērtuma un vieglas paplašināšanas iespēju, kas arī citu iemeslu dēl Joomla ir kļuvusi par populārāko vietņu sistēmu pasaulē. Vēl jo vairāk, Joomla ir atvērtā koda produkts, un ikvienam ir tiesības to lietot bez maksas. Galvenās Joomla! pozitīvās iezīmes ir:

* Viegla instalācija
* Vienkārša vietnes uzturēšana
* Augstākā līmeņa drošības un stabilitātes filozofija
* Jaudīgi bezmaksas un maksas paplašinājumi
* Milzīgs skaits viedņu, ar kā palīdzību vienkārši var mainīt vietnes izskatu

== Kur var atrast Joomla? ==
* Ielādēt Joomla pakotni: http://www.joomla.org/download.html
* Ielādēt Joomla tulkojuma pakotnes Latviešu valodā (lv-LV): http://extensions.joomla.org/extensions/languages/translations-for-joomla/5341

== Kur var atrast paplašinājumus? ==
* Ielādēt paplašinājumus: http://extensions.joomla.org/
* Ielādēt paplašinājumu tulkojumus latviešu valodā: http://www.joomlalv.org/forums/viewforum.php?f=52/

== Kur var atrast pamācības Joomla lietošanā? ==
* Dokumentācijas angļu valodā: http://docs.joomla.org/
* Dokumentācija latviešu valodā: http://www.joomlalv.org/

== Kur meklēt palīdzību saistībā ar Joomla lietošanu? ==
* Bezmaksas palīdzības forums angļu valodā: http://forum.joomla.org/
* Bezmaksas palīdzības forums latviešu valodā: http://forum.joomla.org/viewforum.php?f=358
* Bezmaksas palīdzības forums latviešu valodā: http://www.joomlalv.org/forums

== Vietējie pasākumi / Joomla dienas ==
Joomla lietotāji visā pasaulē organizē Joomla dienas. Joomla diena ir pasākums, kas paredzēts vietējiem Joomla lietotājiem, lai demonstrētu sistēmas iespējas, dažādus projektus un risinātu kopīgas problēmas. Vairāk informācijas atrodams šeit: http://community.joomla.org/events/joomla-days.html

== Joomla lietotāju grupas (JUG) ==
Joomla lietotāju grupas (JUG) ir lielisks veids, kā satikt jaunus cilvēkus un savstarpēji sadarboties, iegūt jaunas iemaņas un dalīties ar tām ar citiem lietotājiem. Joomla lietotāji ir atrodami gandrīz visur. Iespējams arī Jūsu pilsētā. Ja nav, tad Jums ir iespēja izveidot jaunu grupu.

* Latvijā nav reģistrētu lietotāju grupu
* Visas lietotāju grupas :http://community.joomla.org/user-groups/

* Bieži uzdotie jautāji par Joomla lietotāju grupām: http://community.joomla.org/user-groups/jug-faq.html

== Kā piedalīties Joomla attīstībā? ==
* Atbildēt jebkurā atbalsta forumā (link to: Where to get support for Joomla?)
* Tulkot vai rakstīt dokumentāciju vai pamācības (link to: Where to get documentation for Joomla?)
* Izstrādāta paplašinājumus vai veidnes
* Testēt un komentēt un pievienot jaunus ierakstus kļūdu reģistrā: http://docs.joomla.org/How_do_you_report_a_bug%3F
* Pievienoties Joomla! darba grupām
* Piedalīties ar Joomla! saistītos notikumos
* Palīdzēt arī citādi, skatiet http://contribute.joomla.org/

Joomla info page/lv-LV

2010-09-01T08:21:53Z

Lemings: New page: {{RightTOC}} = Latviešu= == Kas ir Joomla? == Joomla ir informācijas pārvaldības sistēma (CMS), ar kā palīdzību iespējams izveidot interneta vietnes un dažāda tiešsaites aplik...

{{RightTOC}}
= Latviešu=

== Kas ir Joomla? ==
Joomla ir informācijas pārvaldības sistēma (CMS), ar kā palīdzību iespējams izveidot interneta vietnes un dažāda tiešsaites aplikācijas. Joomla ir saņēmusi vairākas balvas dažādās nominācijās, kas apliecina tās kvalitāti. Lietošanas ērtuma un vieglas paplašināšanas iespēju, kas arī citu iemeslu dēl Joomla ir kļuvusi par populārāko vietņu sistēmu pasaulē. Vēl jo vairāk, Joomla ir atvērtā koda produkts, un ikvienam ir tiesības to lietot bez maksas. Galvenās Joomla! pozitīvās iezīmes ir:

* Viegla instalācija
* Vienkārša vietnes uzturēšana
* Augstākā līmeņa drošības un stabilitātes filozofija
* Jaudīgi bezmaksas un maksas paplašinājumi
* Milzīgs skaits viedņu, ar kā palīdzību vienkārši var mainīt vietnes izskatu

== Kur var atrast Joomla? ==
* Ielādēt Joomla pakotni: http://www.joomla.org/download.html
* Ielādēt Joomla tulkojuma pakotnes Latviešu valodā (lv-LV): http://extensions.joomla.org/extensions/languages/translations-for-joomla/5341

== Kur var atrast paplašinājumus? ==
* Ielādēt paplašinājumus: http://extensions.joomla.org/
* Ielādēt paplašinājumu tulkojumus latviešu valodā: {http://www.joomlalv.org/forums/viewforum.php?f=52/}

== Kur var atrast pamācības Joomla lietošanā? ==
* Dokumentācijas angļu valodā: http://docs.joomla.org/
* Dokumentācija latviešu valodā: {http://www.joomlalv.org/}

== Kur meklēt palīdzību saistībā ar Joomla lietošanu? ==
* Bezmaksas palīdzības forums angļu valodā: http://forum.joomla.org/
* Bezmaksas palīdzības forums latviešu valodā: http://forum.joomla.org/viewforum.php?f=358
* Bezmaksas palīdzības forums latviešu valodā: http://www.joomlalv.org/forums

== Vietējie pasākumi / Joomla dienas ==
Joomla lietotāji visā pasaulē organizē Joomla dienas. Joomla diena ir pasākums, kas paredzēts vietējiem Joomla lietotājiem, lai demonstrētu sistēmas iespējas, dažādus projektus un risinātu kopīgas problēmas. Vairāk informācijas atrodams šeit: http://community.joomla.org/events/joomla-days.html

== Joomla User Groups (JUG) ==
Local Joomla User Groups (JUG) are a great way to meet new people, get help with a project, or share your own knowledge with other Joomla users. Joomla is everywhere so check to see if there's already a JUG in your area. If not, you might want to consider forming one.

{ Please put here the JUGs organized in the countries where this language is spoken, e.g. for English that would be:
* JUGs in the United Kingdom: http://community.joomla.org/user-groups/europe/united-kingdom.html
* JUGs in The United States: http://community.joomla.org/user-groups/north-america/united-states.html
* JUGs in Canada: http://community.joomla.org/user-groups/north-america/canada.html
* JUGs in Australia: http://community.joomla.org/user-groups/asia-pacific/australia.html
}

* JUG FAQ: http://community.joomla.org/user-groups/jug-faq.html

== How to contribute to Joomla? ==
* Answer Questions in any Joomla! Forum (link to: Where to get support for Joomla?)
* Write or Translate a Tutorial or Documentation (link to: Where to get documentation for Joomla?)
* Develop an Extension or Template
* Test or Add a Comment to an Issue Report: http://docs.joomla.org/How_do_you_report_a_bug%3F
* Join a Joomla! Working Group
* Help Out at a Joomla! Event
* Contribute in Other Ways, see http://contribute.joomla.org/

Running Automated Tests for the Joomla CMS

2010-02-25T18:04:31Z

Lemings: /* Install Selenium RC */

== Introduction ==
As of February 2010, a tests folder has been added to the Joomla! SVN download. This folder contains a growing library of unit and functional tests. The unit tests use PHPUnit and the functional tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium functional tests actually run Joomla! from a browser and test it as a user would.

Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run the functional tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

Windows users not using WAMP / XAMP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

Ubuntu users would use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

More detailed instructions can be found here: [http://www.phpunit.de/manual/3.0/en/installation.html http://www.phpunit.de/manual/3.0/en/installation.html].

== Install Selenium RC ==
Selenium RC is the package that allows you to run Selenium tests from PHP or other programming languages. To install it, just go to the Selenium site [http://seleniumhq.org/projects/remote-control http://seleniumhq.org/projects/remote-control] and download the package. Then unzip the file into a folder.

For example, in Windows if you create a folder called <code>C:\selenium</code> and unzip this file there, it will create a folder called selenium-server-1.0.1. In that folder, create a Windows bat file (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:

<code>c:\program files (x86)\Java\jre6\bin\java.exe" -jar selenium-server.jar -browserSessionReuse</code>

Note the argument <code>browserSessionReuse</code> is used to allow you to run multiple tests without closing and re-opening the browser each time. Save this file so you can easily find and execute it when needed.

This program needs to be running in the background before you can run any Selenium functional tests.

If You are using Firefox 3.6.x you will run in problems with this configuration. Check out this link: http://www.qaautomation.net/?p=15 how to get it working on Firefox 3.6.x.

== Create a Selenium Configuration File ==
To run the Selenium tests, we have to tell Selenium how to navigate and login to your local Joomla! installation. This is done by creating a PHP file called <code>configdef.php</code>. The Joomla! download includes a file called <code>tests/system/servers/config-def.php-dist</code>. This is a sample file that you can use to create the real file. Copy this file to a file called <code>tests/system/servers/configdef.php</code> and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.

== Run the Test Suite ==
At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium RC process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium RC. This will continue to run until you cancel it.

Once Selenium RC is running, you need to execute the functional tests. There are several ways you can do this.

To run all tests from the command line in Windows, change to the <code>tests/system</code> folder and run the following command (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

This will run all of the tests in the TestSuite.php file. You should see a series of messages display in the console telling you what tests are being run and what the tests are doing. You should also see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run.

The tests will run for a few minutes, depending on the speed of your system. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show.

An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected.

== Tips ==
* Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state.
* If you find errors or failures when you run the tests, you can run the tests against the Joomla! trunk to see if the problems are in trunk or just in your branch.
* If you maintain more than one local Joomla! project (for example, one for trunk, another for a branch), you will need to make sure to have a configdef.php file for each that has the right path and login information. You can watch the browser window while the tests are running to make sure you are testing the URL that you expect.

== Eclipse Users ==
You can use the External Tools Configurations option, found under the Run -> External Tools menu, to create launch configurations to run the tests.

* For example, to create a launch configuration to run the Test Suite of the currently-selected Eclipse project, you would enter the location that points to your phpunit.bat file, set the Working Directory to "${project_loc}\tests\system", and set the arguments to <code>--bootstrap servers\configdef.php suite\TestSuite.php</code>. This is shown in the screenshot below.

[[Image:Selenium_tutorial_screenshot_20100205.png]]

: The argument <code>suite\TestSuite.php</code> identifies the test that you wish to run. To run a different test, change this argument to the test that you wish to run. For example, to run com_users user0001Test.php, you would use <code>suite\com_users\user0001Test.php</code>. Remember that we have already set the Working Directory as \tests\system.

: Then you can run this from inside Eclipse and the console output will show in the Eclipse console. Note that you still need to have the Selenium RC program running in the background first, before running the suite. Note that you need to select a file in the current project before running this command so the <code>{project_loc}</code> variable is set correctly.

* You can create a configuration to make it easy to run any single test in your project. To do this, create a new External Tools Configuration as shown below:

[[Image:Selenium_tutorial_screenshot_20100211.png]]

: This is the same as the configuration above except that the second argument is ${selected_resource_loc}. To use this configuration, select the desired test file by clicking on it in the PHP Explorer view or in the edit area. Then start this launch configuration. The selected test file will be run.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]]

Running Automated Tests for the Joomla CMS

2010-02-25T18:03:59Z

Lemings: /* Create a Selenium Configuration File */

== Introduction ==
As of February 2010, a tests folder has been added to the Joomla! SVN download. This folder contains a growing library of unit and functional tests. The unit tests use PHPUnit and the functional tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium functional tests actually run Joomla! from a browser and test it as a user would.

Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run the functional tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

Windows users not using WAMP / XAMP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

Ubuntu users would use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

More detailed instructions can be found here: [http://www.phpunit.de/manual/3.0/en/installation.html http://www.phpunit.de/manual/3.0/en/installation.html].

== Install Selenium RC ==
Selenium RC is the package that allows you to run Selenium tests from PHP or other programming languages. To install it, just go to the Selenium site [http://seleniumhq.org/projects/remote-control http://seleniumhq.org/projects/remote-control] and download the package. Then unzip the file into a folder.

For example, in Windows if you create a folder called <code>C:\selenium</code> and unzip this file there, it will create a folder called selenium-server-1.0.1. In that folder, create a Windows bat file (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:

<code>c:\program files (x86)\Java\jre6\bin\java.exe" -jar selenium-server.jar -browserSessionReuse</code>

Note the argument <code>browserSessionReuse</code> is used to allow you to run multiple tests without closing and re-opening the browser each time. Save this file so you can easily find and execute it when needed.

This program needs to be running in the background before you can run any Selenium functional tests.

== Create a Selenium Configuration File ==
To run the Selenium tests, we have to tell Selenium how to navigate and login to your local Joomla! installation. This is done by creating a PHP file called <code>configdef.php</code>. The Joomla! download includes a file called <code>tests/system/servers/config-def.php-dist</code>. This is a sample file that you can use to create the real file. Copy this file to a file called <code>tests/system/servers/configdef.php</code> and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.

== Run the Test Suite ==
At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium RC process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium RC. This will continue to run until you cancel it.

Once Selenium RC is running, you need to execute the functional tests. There are several ways you can do this.

To run all tests from the command line in Windows, change to the <code>tests/system</code> folder and run the following command (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

This will run all of the tests in the TestSuite.php file. You should see a series of messages display in the console telling you what tests are being run and what the tests are doing. You should also see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run.

The tests will run for a few minutes, depending on the speed of your system. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show.

An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected.

== Tips ==
* Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state.
* If you find errors or failures when you run the tests, you can run the tests against the Joomla! trunk to see if the problems are in trunk or just in your branch.
* If you maintain more than one local Joomla! project (for example, one for trunk, another for a branch), you will need to make sure to have a configdef.php file for each that has the right path and login information. You can watch the browser window while the tests are running to make sure you are testing the URL that you expect.

== Eclipse Users ==
You can use the External Tools Configurations option, found under the Run -> External Tools menu, to create launch configurations to run the tests.

* For example, to create a launch configuration to run the Test Suite of the currently-selected Eclipse project, you would enter the location that points to your phpunit.bat file, set the Working Directory to "${project_loc}\tests\system", and set the arguments to <code>--bootstrap servers\configdef.php suite\TestSuite.php</code>. This is shown in the screenshot below.

[[Image:Selenium_tutorial_screenshot_20100205.png]]

: The argument <code>suite\TestSuite.php</code> identifies the test that you wish to run. To run a different test, change this argument to the test that you wish to run. For example, to run com_users user0001Test.php, you would use <code>suite\com_users\user0001Test.php</code>. Remember that we have already set the Working Directory as \tests\system.

: Then you can run this from inside Eclipse and the console output will show in the Eclipse console. Note that you still need to have the Selenium RC program running in the background first, before running the suite. Note that you need to select a file in the current project before running this command so the <code>{project_loc}</code> variable is set correctly.

* You can create a configuration to make it easy to run any single test in your project. To do this, create a new External Tools Configuration as shown below:

[[Image:Selenium_tutorial_screenshot_20100211.png]]

: This is the same as the configuration above except that the second argument is ${selected_resource_loc}. To use this configuration, select the desired test file by clicking on it in the PHP Explorer view or in the edit area. Then start this launch configuration. The selected test file will be run.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]]

Running Automated Tests for the Joomla CMS

2010-02-25T18:01:45Z

Lemings: /* Create a Selenium Configuration File */

== Introduction ==
As of February 2010, a tests folder has been added to the Joomla! SVN download. This folder contains a growing library of unit and functional tests. The unit tests use PHPUnit and the functional tests use PHPUnit and Selenium. The unit tests perform tests primarily on the Joomla! framework. The Selenium functional tests actually run Joomla! from a browser and test it as a user would.

Before you can run the tests, you need to install some programs on your local workstation, as documented below. This document explains how to run the functional tests from your local workstation.

== Install PHPUnit ==
Both the unit and functional tests rely on PHPUnit. PHPUnit is a testing framework that requires PHP to be installed on the local workstation. XAMP / WAMP users can use the PHP installation that comes with them. Otherwise, you may need to install PHP, and the PEAR package, on your local workstation. More detailed instructions can be found at [http://www.php.net/manual/en/install.php http://www.php.net/manual/en/install.php].

On most PHP installations, PNPUnit can be installed using the standard PEAR installation process.

For example, on XAMPP version 1.7.3 on Windows, you would do the following commands:

* <code>cd c:\xampp\php</code>
* <code>pear channel-discover pear.phpunit.de</code>
* <code>pear channel-discover pear.symfony-project.com</code>
* <code>pear install phpunit/PHPUnit</code>

Windows users not using WAMP / XAMP can use the same procedure, with substituting the location of your PHP installation for <code>cd c:\xampp\php</code>.

Ubuntu users would use the following commands to install PHPUnit:

* <code>$sudo pear channel-discover pear.phpunit.de</code>
* <code>$sudo pear channel-discover pear.symfony-project.com</code>
* <code>$sudo pear install phpunit/PHPUnit</code>

More detailed instructions can be found here: [http://www.phpunit.de/manual/3.0/en/installation.html http://www.phpunit.de/manual/3.0/en/installation.html].

== Install Selenium RC ==
Selenium RC is the package that allows you to run Selenium tests from PHP or other programming languages. To install it, just go to the Selenium site [http://seleniumhq.org/projects/remote-control http://seleniumhq.org/projects/remote-control] and download the package. Then unzip the file into a folder.

For example, in Windows if you create a folder called <code>C:\selenium</code> and unzip this file there, it will create a folder called selenium-server-1.0.1. In that folder, create a Windows bat file (such as selenium.bat though the name does not matter) or Linux shell script that runs the following command:

<code>java -jar selenium-server.jar -browserSessionReuse</code>

If the Java executable is not on your path, then you will need to indicate the full path to it, like the following:

<code>c:\program files (x86)\Java\jre6\bin\java.exe" -jar selenium-server.jar -browserSessionReuse</code>

Note the argument <code>browserSessionReuse</code> is used to allow you to run multiple tests without closing and re-opening the browser each time. Save this file so you can easily find and execute it when needed.

This program needs to be running in the background before you can run any Selenium functional tests.

== Create a Selenium Configuration File ==
To run the Selenium tests, we have to tell Selenium how to navigate and login to your local Joomla! installation. This is done by creating a PHP file called <code>configdef.php</code>. The Joomla! download includes a file called <code>tests/system/servers/config-def.php-dist</code>. This is a sample file that you can use to create the real file. Copy this file to a file called <code>tests/system/servers/configdef.php</code> and edit it to reflect your test systems configuration. There are comments in the file that tell you how to do this.

If You are using Firefox 3.6.x you will run in problems with this configuration. Check out this link: http://www.qaautomation.net/?p=15 how to get it working on Firefox 3.6.x.

== Run the Test Suite ==
At this point, we are ready to actually run the tests. There are two steps to running a test. First, you need to make sure the Selenium RC process is running in the background. To do this, just execute the command (bat file or shell script) you created when you installed Selenium RC. This will continue to run until you cancel it.

Once Selenium RC is running, you need to execute the functional tests. There are several ways you can do this.

To run all tests from the command line in Windows, change to the <code>tests/system</code> folder and run the following command (the phpunit.bat file comes from the PHPUnit installation):

<code>phpunit.bat --bootstrap servers\configdef.php suite\TestSuite.php </code>

In Linux, the command is:

<code>phpunit --bootstrap servers/configdef.php suite/TestSuite.php </code>

This will run all of the tests in the TestSuite.php file. You should see a series of messages display in the console telling you what tests are being run and what the tests are doing. You should also see two browser windows open. One will display Selenium commands that are being executed. The other will show the Joomla! website and the various screens that are being opened and closed as the tests are run.

The tests will run for a few minutes, depending on the speed of your system. When they are done, you will get a summary display showing how many tests were run and whether there were errors or failures. If there are errors or failures, the line of code from the test program that generated the error or failure will also show.

An error occurs when the test encounters an actual PHP error. A failure occurs when the test gets a result that is different than expected.

== Tips ==
* Make sure you run the tests on a clean database that has been installed with sample data. If you have made database changes, you should re-install Joomla! or otherwise put the database back to it's original post-installed state.
* If you find errors or failures when you run the tests, you can run the tests against the Joomla! trunk to see if the problems are in trunk or just in your branch.
* If you maintain more than one local Joomla! project (for example, one for trunk, another for a branch), you will need to make sure to have a configdef.php file for each that has the right path and login information. You can watch the browser window while the tests are running to make sure you are testing the URL that you expect.

== Eclipse Users ==
You can use the External Tools Configurations option, found under the Run -> External Tools menu, to create launch configurations to run the tests.

* For example, to create a launch configuration to run the Test Suite of the currently-selected Eclipse project, you would enter the location that points to your phpunit.bat file, set the Working Directory to "${project_loc}\tests\system", and set the arguments to <code>--bootstrap servers\configdef.php suite\TestSuite.php</code>. This is shown in the screenshot below.

[[Image:Selenium_tutorial_screenshot_20100205.png]]

: The argument <code>suite\TestSuite.php</code> identifies the test that you wish to run. To run a different test, change this argument to the test that you wish to run. For example, to run com_users user0001Test.php, you would use <code>suite\com_users\user0001Test.php</code>. Remember that we have already set the Working Directory as \tests\system.

: Then you can run this from inside Eclipse and the console output will show in the Eclipse console. Note that you still need to have the Selenium RC program running in the background first, before running the suite. Note that you need to select a file in the current project before running this command so the <code>{project_loc}</code> variable is set correctly.

* You can create a configuration to make it easy to run any single test in your project. To do this, create a new External Tools Configuration as shown below:

[[Image:Selenium_tutorial_screenshot_20100211.png]]

: This is the same as the configuration above except that the second argument is ${selected_resource_loc}. To use this configuration, select the desired test file by clicking on it in the PHP Explorer view or in the edit area. Then start this launch configuration. The selected test file will be run.

[[Category:Bug Squad]] [[Category:Development]] [[Category:Testing]]

Archived:Creating a file uploader in your component

2009-12-05T21:00:45Z

Lemings: There was mistake $accept instead of $okMIMETypes

== Creating a file uploader in your component: Method 1, SWFUpload ==

=== Part 1: Introduction ===

SWFUpload is a free open source multiple file uploader available for download from http://swfupload.org/

A demo of swfupload is available here: http://demo.swfupload.org/v220/simpledemo/index.php

The standard way to upload a file is with a HTML form. This works great if you are uploading one file, but browsers do not let you select and upload more than one file at a time.

The most common way of selecting multiple files for upload is to use flash and javascript. The flash part of the script opens up a selct file dialog where multiple files can be selected, and the flash/javascript sends each file, and recieves the response from the server.

The most popular scripts used to do this are SWFUpload and Fancy upload (http://digitarald.de/project/fancyupload/). The flash uploader in Joomla's media manager is based on Fancy Upload version 1.0. As Fancy upload 2.0 and 3.0 use mootools 1.2, and Joomla 1.5 uses mootools 1.11, we can not use Fancy Upload 2.0/3.0 in the admin pages of Joomla. Fancy Upload 1.0 could be used, but it is not updated or supported anymore.

SWFUpload does not use Mootools or Jquery. Because of this it will likely work on any page with Mootools 1.11 (Joomla 1.5), or Mootools 1.2 (Joomla 1.6). Therefore we will be using SWFUpload in this article.

Download ths latest version of SWFUpload from the download page (http://code.google.com/p/swfupload/). Download the SWFUpload v2.2.0.1 Samples.zip file.

Inside the file there will be a demos folder, and inside that a simpledemo folder. This is the example we are going to integrate into a Joomla component.

This tutorial assumes you have followed the http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1 tutorial and are familiar with Joomla's MVC structure.

----

=== Part 2: Adding The External Javascript ===

We need to add in the external links in the head of the document, put some javascript into the head of the doc, and put some HTML in our body.

If you look at the simpledemo/index.php page you will see links to 5 files in the head of the page.

Make a folder within the root of your components folder called swfupload, copy the ../css/default.css, ../swfupload/swfupload.js, js/swfupload.queue.js, js/fileprogress.js and js/handlers.js files into this folder.

We also need to copy the ../swfupload/swfupload.swf and images/TestImageNoText_65x29.png files into this folder.

Within your view.html.php file add in the following code:
<source lang="php">
//get the hosts name
jimport('joomla.environment.uri' );
$host = JURI::root();

//add the links to the external files into the head of the webpage (note the 'administrator' in the path, which is not nescessary if you are in the frontend)
$document =& JFactory::getDocument();
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/swfupload.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/swfupload.queue.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/fileprogress.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/handlers.js');
$document->addStyleSheet($host.'administrator/components/com_mycomponent/swfupload/default.css');
</source>
That is the external files part done. We still have to add in the head javascript, and the body html.

----
=== Part 3: Adding The Head Javascript ===

Head javascript part:
The javascript below is almost the same as the javascript from the simple demo, the few modifications are commented. It is nescessary to read through it and change the parts (such as task) that are relevant to your component.
<source lang="php">
//when we send the files for upload, we have to tell Joomla our session, or we will get logged out
$session = & JFactory::getSession();

$swfUploadHeadJs ='
var swfu;

window.onload = function()
{

var settings =
{
//this is the path to the flash file, you need to put your components name into it
flash_url : "'.$host.'administrator/components/com_mycomponent/swfupload/swfupload.swf",

//we can not put any vars into the url for complicated reasons, but we can put them into the post...
upload_url: "index.php",
post_params:
{
"option" : "com_mycomponent",
"controller" : "mycontroller",
"task" : "mytask",
"id" : "'.$myItemObject->id.'",
"'.$session->getName().'" : "'.$session->getId().'",
"format" : "raw"
},
//you need to put the session and the "format raw" in there, the other ones are what you would normally put in the url
file_size_limit : "5 MB",
//client side file chacking is for usability only, you need to check server side for security
file_types : "*.jpg;*.jpeg;*.gif;*.png",
file_types_description : "All Files",
file_upload_limit : 100,
file_queue_limit : 100,
custom_settings :
{
progressTarget : "fsUploadProgress",
cancelButtonId : "btnCancel"
},
debug: false,

// Button settings
button_image_url: "'.$host.'administrator/components/com_mycomponent/swfupload/images/TestImageNoText_65x29.png",
button_width: "85",
button_height: "29",
button_placeholder_id: "spanButtonPlaceHolder",
button_text: \'<span class="theFont">Choose Files</span>\',
button_text_style: ".theFont { font-size: 13; }",
button_text_left_padding: 5,
button_text_top_padding: 5,

// The event handler functions are defined in handlers.js
file_queued_handler : fileQueued,
file_queue_error_handler : fileQueueError,
file_dialog_complete_handler : fileDialogComplete,
upload_start_handler : uploadStart,
upload_progress_handler : uploadProgress,
upload_error_handler : uploadError,
upload_success_handler : uploadSuccess,
upload_complete_handler : uploadComplete,
queue_complete_handler : queueComplete // Queue plugin event
};
swfu = new SWFUpload(settings);
};

';

//add the javascript to the head of the html document
$document->addScriptDeclaration($swfUploadHeadJs);
</source>
If you want more info on what each paramater is, have a look at the swfupload docs:
http://demo.swfupload.org/Documentation/

----

=== Part 4: Adding The Body HTML ===

We still have to add in our body HTML, in you tmpl/default.php file add in:
<source lang="html4strict">
<div id="swfuploader">
<form id="form1" action="index.php" method="post" enctype="multipart/form-data">
<fieldset class="adminform">

<div class="fieldset flash" id="fsUploadProgress">
<span class="legend">Upload Queue</span>
</div>
<div id="divStatus">0 Files Uploaded</div>
<div>
<span id="spanButtonPlaceHolder"></span>
<input id="btnCancel" type="button" value="Cancel All Uploads" onclick="swfu.cancelQueue();" disabled="disabled" style="margin-left: 2px; font-size: 8pt; height: 29px;" />

</div>
</fieldset>
</form>
</div>
</source>
If all has gone well, you will be able to upload files to your components script, although nothing will happen on the server as there is no PHP to recieve the image.

=== Part 5: Recieveing The File With PHP ===

It is worth noting that allowing users to upload files to the server is possibly the most dangerous thing to do in terms of security, and if someone with malicious intentions manages to upload a php file to your server, then they can easily take control of the site.

It is recommeneded you do some reading on file upload security. This is a good start:

http://www.scanit.be/uploads/php-file-upload.pdf

And there are many other good resources on the internet. It is important you understand how file upload security works, rather than copying and pasting some code that checks the MIME type, and assuming the script is safe.

Here is some example PHP that will check if the file is an image, and upload it. It is not an exhaustive example of security checking, but it is a good start:
<source lang="php">
//import joomlas filesystem functions, we will do all the filewriting with joomlas functions,
//so if the ftp layer is on, joomla will write with that, not the apache user, which might
//not have the correct permissions
jimport('joomla.filesystem.file');
jimport('joomla.filesystem.folder');

//this is the name of the field in the html form, filedata is the default name for swfupload
//so we will leave it as that
$fieldName = 'Filedata';

//any errors the server registered on uploading
$fileError = $_FILES[$fieldName]['error'];
if ($fileError > 0)
{
switch ($fileError)
{
case 1:
echo JText::_( 'FILE TO LARGE THAN PHP INI ALLOWS' );
return;

case 2:
echo JText::_( 'FILE TO LARGE THAN HTML FORM ALLOWS' );
return;

case 3:
echo JText::_( 'ERROR PARTIAL UPLOAD' );
return;

case 4:
echo JText::_( 'ERROR NO FILE' );
return;
}
}

//check for filesize
$fileSize = $_FILES[$fieldName]['size'];
if($fileSize > 2000000)
{
echo JText::_( 'FILE BIGGER THAN 2MB' );
}

//check the file extension is ok
$fileName = $_FILES[$fieldName]['name'];
$uploadedFileNameParts = explode('.',$fileName);
$uploadedFileExtension = array_pop($uploadedFileNameParts);

$validFileExts = explode(',', 'jpeg,jpg,png,gif');

//assume the extension is false until we know its ok
$extOk = false;

//go through every ok extension, if the ok extension matches the file extension (case insensitive)
//then the file extension is ok
foreach($validFileExts as $key => $value)
{
if( preg_match("/$value/i", $uploadedFileExtension ) )
{
$extOk = true;
}
}

if ($extOk == false)
{
echo JText::_( 'INVALID EXTENSION' );
return;
}

//the name of the file in PHP's temp directory that we are going to move to our folder
$fileTemp = $_FILES[$fieldName]['tmp_name'];

//for security purposes, we will also do a getimagesize on the temp file (before we have moved it
//to the folder) to check the MIME type of the file, and whether it has a width and height
$imageinfo = getimagesize($fileTemp);

//we are going to define what file extensions/MIMEs are ok, and only let these ones in (whitelisting), rather than try to scan for bad
//types, where we might miss one (whitelisting is always better than blacklisting)
$okMIMETypes = 'image/jpeg,image/pjpeg,image/png,imagex-png,image/gif';
$validFileTypes = explode(",", $okMIMETypes);

//if the temp file does not have a width or a height, or it has a non ok MIME, return
if( !is_int($imageinfo[0]) || !is_int($imageinfo[1]) || !in_array($imageinfo['mime'], $validFileTypes) )
{
echo JText::_( 'INVALID FILETYPE' );
return;
}

//lose any special characters in the filename
$fileName = ereg_replace("[^A-Za-z0-9.]", "-", $fileName);

//always use constants when making file paths, to avoid the possibilty of remote file inclusion
$uploadPath = JPATH_SITE.DS.'images'.DS.'stories'.DS.$fileName;

if(!JFile::upload($fileTemp, $uploadPath))
{
echo JText::_( 'ERROR MOVING FILE' );
return;
}
</source>
If all want well the uploaded files will be in the images/stories folder.

=== Part 6: Flash plugin COOKIE bug on non-IE browsers ===

Also you should pay attention to Flash player cookie bug!

It is described here http://swfupload.org/forum/generaldiscussion/383

The Flash Player Plugin for FireFox, Opera and Safari (and probably other non-IE based browsers) has a bug which sends persistent cookies from IE to the upload URL instead of the cookies from the browser. Session only cookies from IE are not sent.

1) Any cookies from a non-IE browser (ie, authentication, login, etc) will not be sent with the file upload. Rather the cookies from IE will be sent. So, no cookies or the wrong cookies will be sent. In most cases this means sessions and cookie based authentication are lost when making an upload.

2) Cookies set by the upload script do get set, but only for Flash. The browser will not see them.

3) This bug affects Flash 8 and Flash 9 and all versions of SWFUpload

4) You cannot rely on cookies when using SWFUpload (or any Flash based upload tool). You must send the data you need from the cookies in another way. There are several threads regarding this issue in the forum and many of the demos show workarounds for restoring PHP sessions and some sample files show how to restore the cookies so Session and Authentication are restored in ASP.Net.

5) This could be considered a security issue but probably not severe enough to actually compromise any data. The cookies created in IE by Flash still have all the rules and restricts associated with cookies in any browser.

Solution is modify function _start() (libraries\joomla\session\session.php):
<source lang="php">

$sn = session_name();

if(isset($_COOKIE[$sn]) && isset($_POST[$sn]))
{
$_COOKIE[$sn] = $_POST[$sn];
session_id($_POST[$sn]);
}

session_start();
</source>