Joomla! Documentation - User contributions [en]

Nginx

2015-04-01T07:14:45Z

Oc666: remove unsupported argument

[http://nginx.net/ nginx] is a lightweight Web server that powers about 13% of Web servers across all domains[http://en.wikipedia.org/wiki/Nginx#Description]. Unless you have specific requirements that demand a heavy Web server like Apache, you are much better off using nginx.

Below are instructions on how to get Joomla! running with [http://wiki.nginx.org/PHPFcgiExample nginx and PHP via FastCGI].

== Install nginx ==
For Ubuntu, run <tt>aptitude install nginx</tt>. For other distros, run the corresponding package manager, or see http://wiki.nginx.org/Install.

== Install PHP FastCGI ==
For Ubuntu, read this excellent page on how to [http://wiki.nginx.org/PHPFcgiExample configure PHP and FastCGI for nginx].

For Gentoo, PHP will run as a FastCGI service (fpm), so the nginx server will run PHP as a separated process:
<pre>
# echo "dev-lang/php gd gd2 curl simplexml tokenizer dom tidy sqlite xml fpm cgi" >> /etc/portage/package.use
# emerge php
</pre>
The default settings of php-fpm are good for most servers. For special configurations, visit the [http://php.net/manual/en/install.fpm.php PHP FPM site].

== Configure Nginx ==
nginx configuration files reside in:
* <tt>/etc/nginx/sites-available/</tt> on Ubuntu (for sites running on that nginx instance)
* <tt>/etc/nginx/nginx.conf</tt> on Gentoo and Raspbian(= Debian optimized for Raspberry Pi)

Here is an sample nginx configuration file, joomla.conf, that you can reuse over all your nginx enabled-sites.

<pre>
server {
listen 80;
server_name YOUR_DOMAIN;
server_name_in_redirect off;

access_log /var/log/nginx/localhost.access_log;
error_log /var/log/nginx/localhost.error_log info;

root PATH_ON_SERVER;
index index.php index.html index.htm default.html default.htm;
# Support Clean (aka Search Engine Friendly) URLs
location / {
try_files $uri $uri/ /index.php?$args;
}

# deny running scripts inside writable directories
location ~* /(images|cache|media|logs|tmp)/.*\.(php|pl|py|jsp|asp|sh|cgi)$ {
return 403;
error_page 403 /403_error.html;
}

location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi.conf;
}

# caching of files
location ~* \.(ico|pdf|flv)$ {
expires 1y;
}

location ~* \.(js|css|png|jpg|jpeg|gif|swf|xml|txt)$ {
expires 14d;
}

}
</pre>

Pay attention to a few things:
# The parameter <tt>fastcgi_pass</tt> is set to 127.0.0.1:9000, corresponding to the port that fpm is configured to listen to. This means you can run the PHP processes on separate servers. On Gentoo, you can find this configuration in <tt>/etc/php/fpm-php5.3/php-fpm.conf/</tt>
# Don't forget to replace YOUR_DOMAIN & PATH_ON_SERVER above depending on your domain and the path of Joomla on your server.

== GZip support ==
If you need GZip compression support, add the following section to the http section of the main nginx configuration file:
<pre>
gzip on;
gzip_http_version 1.1;
gzip_comp_level 6;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain application/xhtml+xml text/css application/xml application/xml+rss text/javascript application/javascript application/x-javascript
gzip_proxied any;
gzip_disable "MSIE [1-6]\.";
</pre>

== Sources ==
* [http://en.gentoo-wiki.com/wiki/Nginx Nginx in Gentoo]
* [http://www.kevinworthington.com/nginx-for-windows/ Nginx for Windows]
* [http://wiki.nginx.org/Install#Ubuntu_PPA Nginx in Ubuntu]
* [http://www.debianadmin.com/howto-install-nginx-webserver-in-debian.html Nginx in Debian]
* [http://php.net/manual/en/install.fpm.php PHP-FPM installation and configuration]
* [http://wiki.nginx.org/HttpGzipModule GZip in Nginx]
* [http://wiki.nginx.org/HttpRewriteModule Rewrite in Nginx]
* [http://nginx.org/en/docs/http/request_processing.html How nginx processes a request]

Joomla info page/he-IL

2015-03-10T22:41:43Z

Oc666: /* אירועים אזוריים / Joomladays */

{{RightTOC}}
= Hebrew / עברית =

== מה זה ג'ומלה? ==
ג'ומלה היא מערכת ניהול תוכן עטורת פרסים, אשר מאפשרת לך לבנות אתרי אינטרנט ויישומים מקוונים רבי עוצמה. היבטים רבים, כולל שימוש קלות ויכולת הרחבתה, הפכו את ג'ומלה לתוכנת אתרי האינטרנט הפופולרית ביותר. החשוב מכל, ג'ומלה הינו פתרון קוד פתוח והוא זמין באופן חופשי לכולם. היתרונות של ג'ומלה! כוללים:
* התקנה קלה
* אתר אינטרנט פשוט לתחזוקה
* אבטחה מעולה ויציבות
* הרחבות חינם ומסחריות רבות עוצמה
* שפע תבניות כדי לשנות בקלות את המראה של האתר שלך

== איפה ניתן להשיג ג'ומלה? ==
* הורדת ג'ומלה: http://www.joomla.org.il/download.html
* הורדת ג'ומלה חבילת שפה עבור עברית (he-IL): http://joomlacode.org/gf/project/jtranslation1_6/frs/?action=FrsReleaseBrowse&frs_package_id=5685

== איפה ניתן לקבל הרחבות? ==
* הורדת הרחבות: http://extensions.joomla.org/
* הורדת חבילות שפה עברית עבור הרחבות: http://www.joomla.org.il

== היכן להשיג תיעוד של ג'ומלה? ==
* תיעוד באנגלית: http://docs.joomla.org
* תיעוד בעברית: http://www.joomla.org.il/תיעוד.html

== איפה ניתן לקבל תמיכה עבור ג'ומלה? ==
* תמיכה חינם באנגלית: http://forum.joomla.org/
* תמיכה חינם בעברית:
** http://forum.joomla.org/viewforum.php?f=172
** http://www.joomla.org.il/פורום.html
* תמיכה מסחרית: http://resources.joomla.org/ (האתר באנגלית)

== אירועים אזוריים / Joomladays ==
[http://jday11.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2011]

[http://jday12.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2012]

[http://jday13.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2013]

[http://jday14.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2014]

קהילות מקומיות ברחבי העולם מארגנות ימי ג'ומלה. יום ג'ומלה הינו אירוע שנוצר באופן בלעדי עבור משתמשי ג'ומלה ופרויקטים ובדרך כלל מושך קהל אזורי. מידע נוסף: http://community.joomla.org/events/joomla-days.html

== קבוצות משתמשי ג'ומלה (JUG) ==
קבוצות משתמשי ג'ומלה מקומיות הם דרך מצוינת להכיר אנשים חדשים, לקבל עזרה עם פרויקט, או לחלוק את הידע שלכם עם משתמשי ג'ומלה אחרים. ג'ומלה נמצא בכל מקום, אז בדקו אם יש כבר קבוצה כזו באזורך. אם לא, אולי כדאי לך לשקול להקים אחד.

* JUG בישראל: http://community.joomla.org/user-groups/middle-east/israel/tel-aviv-jug.html
* JUG שאלות נפוצות: http://community.joomla.org/user-groups/jug-faq.html

== כיצד לתרום לג'ומלה? ==
* לענות על שאלות בפורום ג'ומלה http://www.joomla.org.il
* כתוב או תרגם הדרכה או תיעוד http://www.joomla.org.il/תיעוד.html (נדרש רישום)
* לפתח הרחבה או תבנית
* לבדוק או לדווח על בעיה: http://docs.joomla.org/How_do_you_report_a_bug%3F
* הצטרף לקבוצת עבודה של ג'ומלה!
* לעזור בארגון אירוע ג'ומלה!
* לתרום בדרכים אחרות http://contribute.joomla.org

JoomlaDays/History

2014-09-29T11:41:21Z

Oc666: update JoomlaDay Israel 2013 link

The Joomla! community has a long history of JoomlaDay™ events from around the world. Let's document these here, so we can ensure we have a historical timeline of JoomlaDay™s. See current events at [http://events.joomla.org/joomladays Joomla Days]

Instructions: please add the name, date, location, and if possible the web address, of any JoomlaDay™s that have happened in the past. Please use the following format: Name_of_JoomlaDay™ - Month DD-DD, YYYY - City, Country

== 2005 ==

(1 Event)

MamboDay Germany, May 28, 2005 - Bonn, Germany
(worldwide first Mambo / Joomla conference) [http://www.joomladay.de/fakten/historie/mamboday-2005 (german)]

== 2006 ==

(5 Events)

JoomlaDay™ Netherlands (1) - April 22, 2006 - Breda, Netherlands

JoomlaDay™ UK (1) - July 30, 2006 - Leeds, United Kingdom [http://web.archive.org/web/20060709173546/http://www.joomlatraining.org.uk/joomla-day/ programme] [http://web.archive.org/web/20060814225232/http://www.joomlatraining.org.uk/content/view/297/36/ Day 1] [http://web.archive.org/web/20060813123831/http://www.joomlatraining.org.uk/content/view/298/36/ Day 2]

JoomlaDay™ Sweden - October 6-7, 2006 - Västerås, Sweden

JoomlaDay™ Netherlands (2) - December 8-9 2006 - Den Bosch, Netherlands

JoomlaDay™ Germany - September 29-30, 2006 - Bonn, Germany [http://www.joomladay.de/fakten/historie/joomladay-2006 Report in German]

== 2007 ==

(17 Events)

JoomlaDay™ Melbourne - January 24, 2007 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?f=306&t=116577&start=150] and [http://forum.joomla.org/viewtopic.php?t=134393]

JoomlaDay™ France - March 25, 2007 - Paris, France

JoomlaDay™ Norway - June 2, 2007 - Drammen, Norway

JoomlaDay™ Cape Town (South Africa) - June 16, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-june-16-2007.html programme]

JoomlaDay™ Johannesburg (South Africa) - July 14, 2007 [http://www.joomladay.org.za/archive/2007-johannesburg-july-14-2007.html programme]

JoomlaDay™ (Central) USA and Mexico - July 21, 2007 - Austin, Texas, USA

JoomlaDay™ Bangkok - August 4, 2008 - Bangkok , Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157601327115053/]

JoomlaDay™ Brasil - August 18, 2007 - São Paulo/SP, Brazil

JoomlaDay™ USA West - May 12-13, 2007 - Mountain View, California, USA

JoomlaDay™ NYC - October 13, 2007 - New York, New York, USA

JoomlaDay™ Hungary - October 21, 2007 - Budapest, Hungary

JoomlaDay™ Sweden - November 3, 2007 - Västerås, Sweden

JoomlaDay™ Helsinki - November 12, 2007 - Helsinki, Finland

JoomlaDay™ Cape Town (South Africa) - December 10, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-december-10-2007.html programme]

JoomlaDay™ Nigeria - date unknown

JoomlaDay™ Serbia - November 17, 2007 - Belgrade, Serbia

JoomlaDay™ New Zealand - December 15, 2007

== 2008 ==

(20 Events)

JoomlaDay™ Italy - January 19, 2008 - Rome, Italy

JoomlaDay™ Melbourne - February 2, 2008 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?p=1184586]

JoomlaDay™ Spain (1) - April 19, 2008 - Madrid[http://www.joomladay.info/2008/]

JoomlaDay™ Netherlands (3), April 4-5, 2008 - Utrecht, Netherlands

JoomlaDay™ Norway - April 26, 2008 - Drammen, Norway

JoomlaDay™ France - April 27, 2008 - Paris, France

JoomlaDay™ Bangkok - May 10, 2008 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157605299681211/]

JoomlaDay™ Byron Bay - May 11, 2008 - Byron Bay, NSW, Australia]] [http://forum.joomla.org/viewtopic.php?f=306&t=262909]

JoomlaDay™ Sydney - May 19, 2008 - Sydney, Australia [http://forum.joomla.org/viewtopic.php?p=1304388]

JoomlaDay™ Vancouver - June 14, 2008 - Vancouver, British Columbia, Canada]] [http://community.joomla.org/events/joomla-days/400-joomla-day-vancouver-2008.html]

JoomlaDay™ Philippines - June 14, 2008

JoomlaDay™ Hungary - June 20-21, 2008

JoomlaDay™ Durban - June 20-21, 2008 - Durban, South Africa

JoomlaDay™ Brasil - August 16, 2008 - São Paulo/SP, Brazil

JoomlaDay™ San Francisco - September 20, 2008 - San Francisco, California, USA

JoomlaDay™ Johannesburg - October 18, 2008 - Johannesburg, South Africa

JoomlaDay™ Turkey - October 25, 2008

JoomlaDay™ Switzerland - November 15, 2008

JoomlaDay™ Sweden - November 15, 2008

JoomlaDay™ Nigeria - November 19, 2008

== 2009 ==

(23 Events)

JoomlaDay™ Turkey - January 10, 2009

JoomlaDay™ Melbourne - February 7-8, 2009 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/641-joomladay-melbourne-2009.html]

JoomlaDay™ UK (2) - March 13-14, 2009 - Maidstone, England, United Kingdom

JoomlaDay™ Las Vegas - April 4, 2009 - Las Vegas, Nevada, USA [http://lasvegas.joomladayusa.org/]

JoomlaDay™ India - April 25, 2009 - Pune, India [http://community.joomla.org/blogs/community/811-joomla-day-pune-india-a-big-success.html]

JoomlaDay™ Sweden - May 15-16, 2009 - Stockholm, Sweden

JoomlaDay™ France - May 24, 2009 - Paris, France

JoomlaDay™ New England - May 30, 2009 - Brattleboro, Vermont, USA [http://community.joomla.org/events/joomla-days/771-joomladay-new-england-2009.html]

JoomlaDay™ Netherlands (4) - June 12-13, 2009 - Nieuwegein, Netherlands

JoomlaDay™ Cape Town - August 14, 2009 - Cape Town, South Africia

JoomlaDay™ Bangkok - August 22-23, 2009 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157622115004400/]

JoomlaDay™ Brasil - September, 12, 2009 - Rio de Janeiro/RJ, Brazil

JoomlaDay™ Germany - September, 24 - 26, 2009 - Bad Nauheim, Germany

JoomlaDay™ Mongolia - September 29-30, 2009 - Ulan Bataar, Mongolia

JoomlaDay™ Norway - October ?, 2009 - Drammen, Norway

JoomlaDay™ Gauteng - October 8-10, 2009 - Gauteng, South Africa

JoomlaDay™ Hungary - October 10, 2009 - Budapest, Hungary

JoomlaDay™ New York - October 12, 2009 - New York, New York, USA [http://community.joomla.org/events/joomla-days/912-joomla-day-new-york.html]

JoomlaDay™ Sydney - October 17-18, 2009 - Sydney, Australia [http://sydney.joomladay.org.au/groups/viewgroup/5-Welcome+to+Sydney+JoomlaDay+17%2B18+Oct+2009]

JoomlaDay™ Vietnam - November 1, 2009 - Hồ Chí Minh City, Vietnam [http://community.joomla.org/events/joomla-days/1056-joomladay-vietnam-2009.html]

JoomlaDay™ Italy - November 21, 2009 - Rome, Italy

JoomlaDay™ Spain (2) - December 11-12, 2009 - Barcelona, Spain [http://www.joomladay.info/2009/]

JoomlaDay™ Nigeria - December 12, 2009 - Lagos, Nigeria

== 2010 ==

(17 Events)

JoomlaDay™ Melbourne - February 12-14, 2010 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/1102-joomladay-melbourne-2010.html]

JoomlaDay™ France - March 21, 2010 - Bordeaux, France

JoomlaDay™ Spain (3) - April 9-10, 2010 - Mallorca, Spain [http://www.joomladay.cat/]

JoomlaDay™ Netherlands (5) - April 23-24, 2010 - Utrecht, Netherlands [http://www.joomladagen.nl/]

JoomlaDay™ Sweden - April 23-24, 2010 - Stockholm, Sweden [http://www.joomladay.se/]

JoomlaDay™ Norway - June 4-5, 2010 - Drammen, Norway [http://www.joomladay.no/]

JoomlaDay™ New England - June 5, 2010 - Marlboro, Vermont, USA

JoomlaDay™ Brisbane - June 18-19, 2010 - Brisbane, Australia

JoomlaDay™ Brasil - September 11-12, 2010 - Brasília/DF, Brazil [http://www.joomladaybrasil.org/2010]

JoomlaDay™ USA West - October 1-3, 2010 - San Jose, California, USA [http://www.joomladaywest.com/]

JoomlaDay™ Italy - October 9, 2010 - Verona, Italy

JoomlaDay™ DC - October 16, 2010 - Chevy Chase, Maryland, USA [http://www.joomladaydc.com]

JoomlaDay™ Denmark - October 29-30, 2010 - Kolding, Denmark [http://www.joomladay.dk]

JoomlaDay™ UK (3) - October 30-31, 2010 - Ipswich, England, United Kingdom

JoomlaDay™ Bangkok - November 13-14, 2010 - Bangkok, Thailand [http://www.joomladay.in.th/]

JoomlaDay™ Spain (4) - November 26-27, 2010 - Valencia, Spain [http://www.joomladay2010.es/]

JoomlaDay™ NYC - December 4-5, 2010 - New York City, New York, USA

JoomlaDay™ Nigeria - December 11, 2010 - Lagos, Nigeria

== 2011 ==

(29 Events)

JoomlaDay™ Chile - January 18, 2011 - Santiago, Chile [http://www.joomladay-chile.cl/]

Joomla!Night Stockholm - February 4, 2011 - Stockholm, Sweden

JoomlaDay™ India - March 12-13, 2011 - Pune, Maharashtra, India [http://www.joomladay.co.in]

JoomlaDay™ Netherlands (6) - April 2-3, 2011 - Doorn, Netherlands [http://www.joomladagen.nl/]

JoomlaDay™ New England - April 2, 2011 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org]
[[Media:JoomlaDayNEProgram2011-schedule.jpg]]
[[Media:JoomlaDayNEProgram2011-speakers.jpg]]

JoomlaDay™ France - April 2-3, 2011 - Lyon, France [http://www.joomladay.fr/]

JoomlaDay™ Algeria - April 19 2011 - Alger, Algeria [http://www.joomladayalgerie.com/]

JoomlaDay™ Greece - May 28-29, 2011 - Athens, Greece [http://joomladay.gr/]

JoomlaDay™ Malaysia - June 25, 2011 - Kuala Lumpur, Malaysia [http://www.joomla-day.org.my/2011/]

Joomla!Night Chile - July 6, 2011 - Santiago, Chile [http://joomlanight-chile.cl/]

JoomlaDay™ Chicago - August 5-6, 2011 - Chicago, Illinois, USA [http://www.joomladaychicago.com]

JoomlaDay™ Norway - August 12-13, 2011 - Drammen, Norway [http://www.joomladay.no/]

JoomlaDay™ Bosnia and Herzegovina - August 12-14, 2011 - Tesanj, Bosnia [http://www.joomla.ba/konferencija]

JoomlaDay™ Cape Town - August 19-20, 2011 - Cape Town, South Africa [http://www.joomladay.org.za/] [http://www.joomladay.org.za/talks-sessions/programme.html programme]

JoomlaDay™ Germany - September 2-3, 2011 - Hamburg, Germany [http://www.joomladay.de]

JoomlaDay™ Brasil - September 2-4, 2011 - Florianópolis/SC, Brazil [http://www.joomladaybrasil.org/2011]

JoomlaDay™ Austin - September 15, 2011 - Austin, Texas, USA [http://www.joomladayaustin.com]

JoomlaDay™ UK - September 24-25, 2011 - London, England [http://www.joomladayuk2011.org]

JoomlaDay™ Israel - October 10, 2011 - Tel Aviv, Israel [http://jday11.joomla.org.il]

JoomlaDay™ Italy - October 22, 2011 - Florence, Italy [http://www.joomladay.it]

JoomlaDay™ NYC - October 22-23, 2011 - New York City, New York, USA [http://www.joomladaynyc.com]

JoomlaDay™ Denmark - October 28-29, 2011 - Kolding, Denmark [http://www.joomladay.dk]

JoomlaDay™ Australia - November 5-6, 2011 - Sydney, Australia [http://sydney.joomladay.org.au/]

JoomlaDay™ Finland - November 5, 2011 - Helsinki, Finland [http://joomladayfinland.com/]

JoomlaDay™ Spain - November 9-10, 2011 - Zaragoza, Spain [http://www.joomladay2011.es/]

JoomlaDay™ Midwest - November 12, 2011 - Milwaukee, Wisconsin, USA [http://www.joomladaymidwest.org]

JoomlaDay™ Algeria - November 19, 2011 - Oran, Algeria [http://www.joomladayoran.com/]

JoomlaDay™ Los Angeles - December 3, 2011 - Los Angeles, California, USA [http://www.jdayla.com]

JoomlaDay™ Lagos - December 17, 2011 - Lagos, Nigeria [http://joomlang.com/]

== 2012 ==
(29 events)

JoomlaDay™ Chile - January 19, 2012 - Santiago, Chile

JoomlaDay™ Bangkok - February 25, 2012 - Bangkok, Thailand [http://www.joomladay.in.th]

JoomlaDay™ Guatemala - February 29 - March 3, 2012 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2012/]

JoomlaDay™ France - March 24, 2012 - Strasbourg, France [http://www.joomladay.fr/]

JoomlaDay™ New England - March 31, 2012 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

JoomlaDay™ Iran - April 12, 2012 - Mashhad, Iran [http://www.joomladay.ir]

JoomlaDay™ Netherlands (7) - April 21-22, 2012 - Zeist, Netherlands [http://www.joomladagen.nl/]

JoomlaDay™ Ribeirão Preto - May 11-12, 2012 - Ribeirão Preto, Brasil [http://jdrp.unaerp.br/]

JoomlaDay™ Sweden - May 26, 2012 - Stockholm, Sweden [http://www.joomladay.se/]

JoomlaDay™ China 2012 - June 2, 2012 - Pudong, China [http://joomla.51qiangzuo.com/]

JoomlaDay™ Greece 2012 - June 2-3, 2012 - Athens, Greece [http://joomladay.gr]

JoomlaDay™ Togo - June 14, 2012 - Assahoun, Togo

JoomlaDay™ Mexico - June 22-23, 2012 - Mexico City, Mexico [http://www.joomladaymexico.org/]

JoomlaDay™ Chicago - August 10-11, 2012 - Chicago, Illinois, USA [http://joomladaychicago.com]

JoomlaDay™ Cape Town - August 17-18, 2012 - Cape Town, South Africa [http://www.joomladay.org.za]

JoomlaDay™ Colombia - September 06, 2012 - Cali, Colombia [http://www.joomladay.com.co/]

JoomlaDay™ Brasil - September 07-08, 2012 - Belo Horizonte, Minas Gerais, Brasil [http://www.joomladaybrasil.org/]

JoomlaDay™ Poland - September 22-23, 2012 - Poznań, Poland [http://www.joomla-day.pl/]

JoomlaDay™ NYC - September 22-23, 2012 - New York, New York, USA [http://www.joomladaynyc.com/]

JoomlaDay™ Spain - September 28-29, 2012 - Mérida, Spain [http://www.joomladayspain.com/]

JoomlaDay™ Italy - September 29, 2012 - Turin, Italy [http://www.joomladay.it/]

JoomlaDay™ Turkey - September 29, 2012 - Konya, Turkey [http://www.joomla.org.tr/en/Konya]

JoomlaDay™ Germany - October 05-06, 2012 - Berlin, Germany [http://www.joomladay.de/]

JoomlaDay™ Israel - October 10, 2012- Tel Aviv, Israel [http://jday12.joomla.org.il]

JoomlaDay™ Bulgaria - October 13, 2012 - Sofia, Bulgaria [http://joomladay.bg/]

JoomlaDay™ Australia - October 20-21, 2012 - Sydney, Australia [http://sydney.joomladay.org.au/]

JoomlaDay™ Denmark - October 26-27, 2012 - Kolding, Denmark [http://www.joomladay.dk]

JoomlaDay™ Iran - November 15, 2012 - Kerman, Iran [http://www.joomladay.ir/]

Joomla! World Conference - November 16-18, 2012 - San Jose, California, USA [http://conference.joomla.org]

== 2013 ==
(35 events)

JoomlaDay™ Melbourne - January 19-20, 2013 - Melbourne, Australia [http://melbourne.joomladay.org.au/]

JoomlaDay™ India - February 8-10, 2013 - Mumbai, India [http://www.joomladayindia.in/]

JoomlaDay™ North Carolina - February 23, 2013 - Raleigh, North Carolina, USA [http://joomladaync.org]

JoomlaDay™ Gabon - March 7-8, 2013 - Libreville, Gabon [http://www.joomladaygabon.info]

JoomlaDay™ Boston - March 16, 2013 - Cambridge, MA, USA [http://joomladayboston.com/]

JoomlaDay™ France - March 22-24, 2013 - Blagnac, France [http://www.joomladay.fr/]

JoomlaDay™ New England - April 13, 2013 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

JoomlaDay™ Alger - April 18, 2013 - Alger, Algérie [http://www.joomladayalger.com/]

JoomlaDay™ Netherlands - April 20-21, 2013 - Zeist, Netherlands [http://www.joomladagen.nl/2013/]

JoomlaDay™ Guatemala - April 25-26, 2013 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2013/]

JoomlaDay™ Bosnia and Herzegovina - May 3, 2013 - Sarajevo, Bosnia and Herzegovina [http://www.joomladay.ba/]

JoomlaDay™ Greece - June 15-17, 2013 - Athens, Greece [http://joomladay.gr/]

JoomlaDay™ Taiwan - June 15, 2013 - Taipei City, Taiwan [http://joomladay.tw/]

JoomlaDay™ São Paulo - July 5-6, 2013 - São Paulo, Brazil [http://www.joomladaysp.com.br/2013/]

JoomlaDay™ Cotonou (Benin) - July 5, 2013 - Cotonou, Bénin [http://joomladaybenin.info/]

JoomlaDay™ Kenya - August 2, 2013 - Nairobi, Kenya [http://www.joomladay.or.ke/]

JoomlaDay™ Germany - September 13-14, 2013 - Nuremberg, Germany [http://joomladay.de/]

JoomlaDay™ Switzerland - September 21, 2013 - Berne, Switzerland [http://www.joomladayswiss.org/]

JoomlaDay™ Spain - September 27-29, 2013 - Albacete, Spain [http://www.joomladayspain.org/]

JoomlaDay™ San Francisco - September 27-29, 2013 - San Francisco, CA, USA [http://www.joomladaysf.com/]

JoomlaDay™ UK - October 5-6, 2013 - Ascot, Berkshire, United Kingdom [http://www.joomladay.co.uk/]

JoomlaDay™ Poland - October 5-6, 2013 - Łódź, Poland [http://www.joomla-day.pl/]

JoomlaDay™ Israel - October 10, 2013 - Tel Aviv, Israel [http://jday13.joomla.org.il]

JoomlaDay™ Italy - October 12, 2013 - Naples, Italy [http://www.joomladay.it/]

JoomlaDay™ Bulgaria - October 12, 2013 - Sofia, Bulgaria [http://joomladay.bg]

JoomlaDay™ Hungary - October 12, 2013 - Budapest, Hungary [http://joomladay.hu/]

JoomlaDay™ South Africa - October 18-19, 2013 - Johannesburg, South Africa [http://www.joomladay.org.za/]

JoomlaDay™ Houston - October 19, 2013 - Houston, TX, USA [http://joomladayhouston.com]

JoomlaDay™ Sydney - October 19, 2013 - Sydney, NSW, Australia [http://sydney.joomladay.org.au/]

Joomla! World Conference - November 8-10, 2013 - Boston, Massachusetts, USA [http://conference.joomla.org]

JoomlaDay™ Rio de Janeiro - November 15-17, 2013 - Rio de Janeiro, Brazil [http://www.joomladayrio.com.br/]

JoomlaDay™ Bangkok - November 22-24, 2013 - Bangkok, Thailand [http://www.joomladay.in.th/en/]

JoomlaDay™ Mexico City - November 27-29, 2013 - Mexico DF, Mexico [http://www.joomladaymx.com/]

JoomlaDay™ Colombia - November 28-29, 2013 - Ibagué, Colombia [http://www.joomladay.com.co/]

JoomlaDay™ Lagos - December 14, 2013 - Lagos, Nigeria [http://www.joomlang.com/]

== 2014 ==
(35 events)

JoomlaDay™ Addis Ababa - 16th February 2014, Ethiopia [http://www.joomladayaddis.org/]

JoomlaDay™ Gabon - 20th February 2014, Gabon [http://jday.ga/]

JoomlaDay™ Prague - 1st March 2014, Prague [http://joomladayprague.org/]

JoomlaDay™ Denmark - 7-8th March 2014, Copenhagen, Denmark [http://www.joomladay.dk]

JoomlaDay™ Boston - 15-16th March 2014, Cambridge, Massachusetts, USA [http://joomladayboston.com/]

JoomlaDay™ Netherlands - 22-23rd March 2014, Zeist, Netherlands [http://www.joomladagen.nl/]

JoomlaDay™ La Rioja - 3rd April 2014, Logroño, Spain [http://joomladaylarioja.org/]

JoomlaDay™ Norway - 4-5th April 2014, Oslo, Norway [http://www.joomladay.no/]

JoomlaDay™ Atlanta - 5th April 2014, Atlanta, Georgia, USA [http://www.joomladayatlanta.com]

JoomlaDay™ Brazil - 2-3 May 2014, Sao Paulo, Brazil [http://joomladaybrasil.org/2014/]

JoomlaDay™ Algeria - 15-16th May 2014, Alger, Algeria [http://www.joomladayalger.com/]

JoomlaDay™ France - 23-24th May 2014, Paris, France [http://www.joomladay.fr/]

JoomlaDay™ Russia - 26th June 2014, Moscow, Russia [http://joomladay.ru/]

JoomlaDay™ Mexico City - July 17-18, 2014 - Mexico DF, Mexico [http://joomladaymexico.com/]

JoomlaDay™ Minnesota - July 19, 2014 - Minneapolis, Minnesota, USA [http://joomladay.mn/]

Joomla! Developer Conference - August 7-8, 2014 - Chicago, IL, USA [http://devcon.joomla.org/]

JoomlaDay™ Chicago - August 9th, 2014 - Chicago, IL, USA [http://www.joomladaychicago.com]

JoomlaDay™ Kenya - September 5th, 2014 - Nairobi, Kenya [http://joomladay.or.ke/]

JoomlaDay™ Benin - September 11-13, 2014 - Cotonou, Benin [http://jdaybenin.com]

JoomlaDay™ Deutschland - September 12-13, 2014 - Cologne, Germany [http://www.joomladay.de]

JoomlaDay™ Poland - September 20-21, 2014 - Warsaw, Poland [http://joomla-day.pl]

JoomlaDay™ Houston - September 20th, 2014 Houston, TX, USA [http://joomladayhouston.com]

JoomlaDay™ Ghana - October 2-3, 2014 - Accra, Ghana [http://joomladayghana.net]

JoomlaDay™ UK - October 4-5, 2014 - Ascot, United Kingdom [http://www.joomladay.co.uk]

JoomlaDay™ Spain - October 10-11, 2014 - Madrid, Spain [http://joomladayspain.org]

JoomlaDay™ NYC - October 11-12, 2014 - New York City, NY, USA [http://joomladaynyc.com]

JoomlaDay™ Bulgaria - October 11th, 2014 - Sofia, Bulgaria [http://joomladay.bg]

JoomlaDay™ Viña del mar - October 17-18, 2014 - Viña del Mar, Chile [http://www.joomladay.cl/]

JoomlaDay™ Hungary - October 17th - Budapest, Hungary [http://joomladay.hu/]

JoomlaDay™ Israel - October 20th, 2014 - Tel Aviv, Israel [http://jday.joomla.org.il]

Joomla! World Conference - November 7-9, 2014 - Cancún, Mexico [http://conference.joomla.org]

JoomlaDay™ Italy - November 8th, 2014 - Milan, Italy [http://www.joomladay.it]

JoomlaDay™ Málaga - November 14th, 2014 - Málaga, Spain [http://joomladaymalaga.org]

JoomlaDay™ Faso - November 14-15, 2014 - Ouagadougou, Burkina Faso [http://jdayfaso.net]

JoomlaDay™ Cuba - November 15th, 2014 Havana, Cuba [http://www.joomladaycuba.org]

[[Category:Events Working Group]]
[[Category:Events]]

J3.x:Module article news ordering ascending

2013-11-07T17:48:17Z

Oc666:

== What is the cause ==
Module article news show articles in reverse order.

== How to fix ==
Go to modules/mod_articles_news/helper.php and change the value of list.direction from ASC to DESC. See the change in the next patch: https://github.com/joomla/joomla-cms/pull/2446.diff

<noinclude>
[[Category:Version 3.2.0 FAQ]]
</noinclude>

J3.x:Module article news ordering ascending

2013-11-07T17:45:43Z

Oc666: Created page with "== What is the cause == Module article news show articles in reverse order. == How to fix == Go to modules/mod_articles_news/helper.php and change the value of list.direction..."

JoomlaDays/History

2013-05-21T16:05:54Z

Oc666:

The Joomla! community has a long history of Joomla!Day events from around the world. Let's document these here, so we can ensure we have a historical timeline of Joomla!Days. See current events at [http://events.joomla.org/joomla-days.html Joomla Days]

Instructions: please add the name, date, location, and if possible the web address, of any Joomla!Days that have happened in the past. Please use the following format: Name_of_Joomla!Day - Month DD-DD, YYYY - City, Country

== 2005 ==

(1 Event)

MamboDay Germany, May 28, 2005 - Bonn, Germany
(worldwide first Mambo / Joomla conference) [http://www.joomladay.de/fakten/historie/mamboday-2005/item/mamboday-2005.html (german)]

== 2006 ==

(5 Events)

Joomla!Day Netherlands (1) - April 22, 2006 - Breda, Netherlands

Joomla!Day UK (1) - July 30, 2006 - Leeds, United Kingdom [http://web.archive.org/web/20060709173546/http://www.joomlatraining.org.uk/joomla-day/ programme] [http://web.archive.org/web/20060814225232/http://www.joomlatraining.org.uk/content/view/297/36/ Day 1] [http://web.archive.org/web/20060813123831/http://www.joomlatraining.org.uk/content/view/298/36/ Day 2]

Joomla!Day Sweden - October 6-7, 2006 - Västerås, Sweden

Joomla!Day Netherlands (2) - December 8-9 2006 - Den Bosch, Netherlands

Joomla!Day Germany - September 29-30, 2006 - Bonn, Germany [http://www.joomladay.de/fakten/historie/joomladay-2006.html Report in German]

== 2007 ==

(17 Events)

Joomla!Day Melbourne - January 24, 2007 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?f=306&t=116577&start=150] and [http://forum.joomla.org/viewtopic.php?t=134393]

Joomla!Day France - March 25, 2007 - Paris, France

Joomla!Day Norway - June 2, 2007 - Drammen, Norway

Joomla!Day Cape Town (South Africa) - June 16, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-june-16-2007.html programme]

Joomla!Day Johannesburg (South Africa) - July 14, 2007 [http://www.joomladay.org.za/archive/2007-johannesburg-july-14-2007.html programme]

Joomla!Day (Central) USA and Mexico - July 21, 2007 - Austin, Texas, USA

Joomla!Day Bangkok - August 4, 2008 - Bangkok , Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157601327115053/]

Joomla!Day Brasil - August 18, 2007 - São Paulo/SP, Brazil

Joomla!Day USA West - May 12-13, 2007 - Mountain View, California, USA

Joomla!Day NYC - October 13, 2007 - New York, New York, USA

Joomla!Day Hungary - October 21, 2007 - Budapest, Hungary

Joomla!Day Sweden - November 3, 2007 - Västerås, Sweden

Joomla!Day Helsinki - November 12, 2007 - Helsinki, Finland

Joomla!Day Cape Town (South Africa) - December 10, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-december-10-2007.html programme]

Joomla!Day Nigeria - date unknown

Joomla!Day Serbia - November 17, 2007 - Belgrade, Serbia

Joomla!Day New Zealand - December 15, 2007

== 2008 ==

(20 Events)

Joomla!Day Italy - January 19, 2008 - Rome, Italy

Joomla!Day Melbourne - February 2, 2008 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?p=1184586]

Joomla!Day Spain (1) - April 19, 2008 - Madrid[http://www.joomladay.info/2008/]

Joomla!Day Netherlands (3), April 4-5, 2008 - Utrecht, Netherlands

Joomla!Day Norway - April 26, 2008 - Drammen, Norway

Joomla!Day France - April 27, 2008 - Paris, France

Joomla!Day Bangkok - May 10, 2008 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157605299681211/]

Joomla!Day Byron Bay - May 11, 2008 - Byron Bay, NSW, Australia]] [http://forum.joomla.org/viewtopic.php?f=306&t=262909]

Joomla!Day Sydney - May 19, 2008 - Sydney, Australia [http://forum.joomla.org/viewtopic.php?p=1304388]

Joomla!Day Vancouver - June 14, 2008 - Vancouver, British Columbia, Canada]] [http://community.joomla.org/events/joomla-days/400-joomla-day-vancouver-2008.html]

Joomla!Day Philippines - June 14, 2008

Joomla!Day Hungary - June 20-21, 2008

Joomla!Day Durban - June 20-21, 2008 - Durban, South Africa

Joomla!Day Brasil - August 16, 2008 - São Paulo/SP, Brazil

Joomla!Day San Francisco - September 20, 2008 - San Francisco, California, USA

Joomla!Day Johannesburg - October 18, 2008 - Johannesburg, South Africa

Joomla!Day Turkey - October 25, 2008

Joomla!Day Switzerland - November 15, 2008

Joomla!Day Sweden - November 15, 2008

Joomla!Day Nigeria - November 19, 2008

== 2009 ==

(23 Events)

Joomla!Day Turkey - January 10, 2009

Joomla!Day Melbourne - February 7-8, 2009 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/641-joomladay-melbourne-2009.html]

Joomla!Day UK (2) - March 13-14, 2009 - Maidstone, England, United Kingdom

Joomla!Day Las Vegas - April 4, 2009 - Las Vegas, Nevada, USA [http://lasvegas.joomladayusa.org/]

Joomla!Day India - April 25, 2009 - Pune, India [http://community.joomla.org/blogs/community/811-joomla-day-pune-india-a-big-success.html]

Joomla!Day Sweden - May 15-16, 2009 - Stockholm, Sweden

Joomla!Day France - May 24, 2009 - Paris, France

Joomla!Day New England - May 30, 2009 - Brattleboro, Vermont, USA [http://community.joomla.org/events/joomla-days/771-joomladay-new-england-2009.html]

Joomla!Day Netherlands (4) - June 12-13, 2009 - Nieuwegein, Netherlands

Joomla!Day Cape Town - August 14, 2009 - Cape Town, South Africia

Joomla!Day Bangkok - August 22-23, 2009 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157622115004400/]

Joomla!Day Brasil - September, 12, 2009 - Rio de Janeiro/RJ, Brazil

Joomla!Day Germany - September, 24 - 26, 2009 - Bad Nauheim, Germany

Joomla!Day Mongolia - September 29-30, 2009 - Ulan Bataar, Mongolia

Joomla!Day Norway - October ?, 2009 - Drammen, Norway

Joomla!Day Gauteng - October 8-10, 2009 - Gauteng, South Africa

Joomla!Day Hungary - October 10, 2009 - Budapest, Hungary

Joomla!Day New York - October 12, 2009 - New York, New York, USA [http://community.joomla.org/events/joomla-days/912-joomla-day-new-york.html]

Joomla!Day Sydney - October 17-18, 2009 - Sydney, Australia [http://sydney.joomladay.org.au/groups/viewgroup/5-Welcome+to+Sydney+JoomlaDay+17%2B18+Oct+2009]

Joomla!Day Vietnam - November 1, 2009 - Hồ Chí Minh City, Vietnam [http://community.joomla.org/events/joomla-days/1056-joomladay-vietnam-2009.html]

Joomla!Day Italy - November 21, 2009 - Rome, Italy

Joomla!Day Spain (2) - December 11-12, 2009 - Barcelona, Spain [http://www.joomladay.info/2009/]

Joomla!Day Nigeria - December 12, 2009 - Lagos, Nigeria

== 2010 ==

(17 Events)

Joomla!Day Melbourne - February 12-14, 2010 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/1102-joomladay-melbourne-2010.html]

Joomla!Day France - March 21, 2010 - Bordeaux, France

Joomla!Day Spain (3) - April 9-10, 2010 - Mallorca, Spain [http://www.joomladay.cat/]

Joomla!Day Netherlands (5) - April 23-24, 2010 - Utrecht, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Sweden - April 23-24, 2010 - Stockholm, Sweden [http://www.joomladay.se/]

Joomla!Day Norway - June 4-5, 2010 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day New England - June 5, 2010 - Marlboro, Vermont, USA

Joomla!Day Brisbane - June 18-19, 2010 - Brisbane, Australia

Joomla!Day Brasil - September 11-12, 2010 - Brasília/DF, Brazil [http://www.joomladaybrasil.org/2010]

Joomla!Day USA West - October 1-3, 2010 - San Jose, California, USA [http://www.joomladaywest.com/]

Joomla!Day Italy - October 9, 2010 - Verona, Italy

Joomla!Day DC - October 16, 2010 - Chevy Chase, Maryland, USA [http://www.joomladaydc.com]

Joomla!Day Denmark - October 29-30, 2010 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day UK (3) - October 30-31, 2010 - Ipswich, England, United Kingdom

Joomla!Day Bangkok - November 13-14, 2010 - Bangkok, Thailand [http://www.joomladay.in.th/]

Joomla!Day Spain (4) - November 26-27, 2010 - Valencia, Spain [http://www.joomladay2010.es/]

Joomla!Day NYC - December 4-5, 2010 - New York City, New York, USA

Joomla!Day Nigeria - December 11, 2010 - Lagos, Nigeria

== 2011 ==

(29 Events)

Joomla!Day Chile - January 18, 2011 - Santiago, Chile [http://www.joomladay-chile.cl/]

Joomla!Night Stockholm - February 4, 2011 - Stockholm, Sweden

Joomla!Day India - March 12-13, 2011 - Pune, Maharashtra, India [http://www.joomladay.co.in]

Joomla!Day Netherlands (6) - April 2-3, 2011 - Doorn, Netherlands [http://www.joomladagen.nl/]

Joomla!Day New England - April 2, 2011 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org]
[[Media:JoomlaDayNEProgram2011-schedule.jpg]]
[[Media:JoomlaDayNEProgram2011-speakers.jpg]]

Joomla!Day France - April 2-3, 2011 - Lyon, France [http://www.joomladay.fr/]

Joomla!Day Algeria - April 19 2011 - Alger, Algeria [http://www.joomladayalgerie.com/]

Joomla!Day Greece - May 28-29, 2011 - Athens, Greece [http://joomladay.gr/]

Joomla!Day Malaysia - June 25, 2011 - Kuala Lumpur, Malaysia [http://www.joomla-day.org.my/2011/]

Joomla!Night Chile - July 6, 2011 - Santiago, Chile [http://joomlanight-chile.cl/]

Joomla!Day Chicago - August 5-6, 2011 - Chicago, Illinois, USA [http://www.joomladaychicago.com]

Joomla!Day Norway - August 12-13, 2011 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day Bosnia and Herzegovina - August 12-14, 2011 - Tesanj, Bosnia [http://www.joomla.ba/konferencija]

Joomla!Day Cape Town - August 19-20, 2011 - Cape Town, South Africa [http://www.joomladay.org.za/] [http://www.joomladay.org.za/talks-sessions/programme.html programme]

Joomla!Day Germany - September 2-3, 2011 - Hamburg, Germany [http://www.joomladay.de]

Joomla!Day Brasil - September 2-4, 2011 - Florianópolis/SC, Brazil [http://www.joomladaybrasil.org/2011]

Joomla!Day Austin - September 15, 2011 - Austin, Texas, USA [http://www.joomladayaustin.com]

Joomla!Day UK - September 24-25, 2011 - London, England [http://www.joomladayuk2011.org]

Joomla!Day Israel - October 10, 2011 - Tel Aviv, Israel [http://jday11.joomla.org.il]

Joomla!Day Italy - October 22, 2011 - Florence, Italy [http://www.joomladay.it]

Joomla!Day NYC - October 22-23, 2011 - New York City, New York, USA [http://www.joomladaynyc.com]

Joomla!Day Denmark - October 28-29, 2011 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day Australia - November 5-6, 2011 - Sydney, Australia [http://sydney.joomladay.org.au/]

Joomla!Day Finland - November 5, 2011 - Helsinki, Finland [http://joomladayfinland.com/]

Joomla!Day Spain - November 9-10, 2011 - Zaragoza, Spain [http://www.joomladay2011.es/]

Joomla!Day Midwest - November 12, 2011 - Milwaukee, Wisconsin, USA [http://www.joomladaymidwest.org]

Joomla!Day Algeria - November 19, 2011 - Oran, Algeria [http://www.joomladayoran.com/]

Joomla!Day Los Angeles - December 3, 2011 - Los Angeles, California, USA [http://www.jdayla.com]

Joomla!Day Lagos - December 17, 2011 - Lagos, Nigeria [http://joomlang.com/]

== 2012 ==
(29 events)

Joomla!Day Chile - January 19, 2012 - Santiago, Chile

Joomla!Day Bangkok - February 25, 2012 - Bangkok, Thailand [http://www.joomladay.in.th]

Joomla!Day Guatemala - February 29 - March 3, 2012 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2012/]

Joomla!Day France - March 24, 2012 - Strasbourg, France [http://www.joomladay.fr/]

Joomla!Day New England - March 31, 2012 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Joomla!Day Iran - April 12, 2012 - Mashhad, Iran [http://www.joomladay.ir]

Joomla!Day Netherlands (7) - April 21-22, 2012 - Zeist, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Ribeirão Preto - May 11-12, 2012 - Ribeirão Preto, Brasil [http://jdrp.unaerp.br/]

Joomla!Day Sweden - May 26, 2012 - Stockholm, Sweden [http://www.joomladay.se/]

Joomla!Day China 2012 - June 2, 2012 - Pudong, China [http://joomla.51qiangzuo.com/]

Joomla!Day Greece 2012 - June 2-3, 2012 - Athens, Greece [http://joomladay.gr]

Joomla!Day Togo - June 14, 2012 - Assahoun, Togo

Joomla!Day Mexico - June 22-23, 2012 - Mexico City, Mexico [http://www.joomladaymexico.org/]

Joomla!Day Chicago - August 10-11, 2012 - Chicago, Illinois, USA [http://joomladaychicago.com]

Joomla!Day Cape Town - August 17-18, 2012 - Cape Town, South Africa [http://www.joomladay.org.za]

Joomla!Day Colombia - September 06, 2012 - Cali, Colombia [http://www.joomladay.com.co/]

Joomla!Day Brasil - September 07-08, 2012 - Belo Horizonte, Minas Gerais, Brasil [http://www.joomladaybrasil.org/]

Joomla!Day Poland - September 22-23, 2012 - Poznań, Poland [http://www.joomla-day.pl/]

Joomla!Day NYC - September 22-23, 2012 - New York, New York, USA [http://www.joomladaynyc.com/]

Joomla!Day Spain - September 28-29, 2012 - Mérida, Spain [http://www.joomladayspain.com/]

Joomla!Day Italy - September 29, 2012 - Turin, Italy [http://www.joomladay.it/]

Joomla!Day Turkey - September 29, 2012 - Konya, Turkey [http://www.joomla.org.tr/en/Konya]

Joomla!Day Germany - October 05-06, 2012 - Berlin, Germany [http://www.joomladay.de/]

Joomla!Day Israel - October 10, 2012- Tel Aviv, Israel [http://jday12.joomla.org.il]

Joomla!Day Bulgaria - October 13, 2012 - Sofia, Bulgaria [http://joomladay.bg/]

Joomla!Day Australia - October 20-21, 2012 - Sydney, Australia [http://sydney.joomladay.org.au/]

Joomla!Day Denmark - October 26-27, 2012 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day Iran - November 15, 2012 - Kerman, Iran [http://www.joomladay.ir/]

Joomla World Conference - November 16-18, 2012 - San Jose, California, USA [http://conference.joomla.org]

== 2013 ==

Joomla!Day Melbourne - January 19-20, 2013 - Melbourne, Australia [http://melbourne.joomladay.org.au/]

Joomla!Day India - February 8-10, 2013 - Mumbai, India [http://www.joomladayindia.in/]

Joomla!Day North Carolina - February 23, 2013 - Raleigh, North Carolina, USA [http://joomladaync.org]

Joomla!Day Gabon - March 7-8, 2013 - Libreville, Gabon [www.joomladaygabon.info]

Joomla!Day Boston - March 16, 2013 - Cambridge, MA, USA [http://joomladayboston.com/]

Joomla!Day France - March 22-24, 2013 - Blagnac, France [http://www.joomladay.fr/]

Joomla!Day New England - April 13, 2013 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Joomla!Day Netherlands - April 20-21, 2013 - Zeist, Netherlands [http://www.joomladagen.nl/2013/]

Joomla!Day Guatemala - April 25-26, 2013 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2013/]

Joomla!Day Taiwan - June 15, 2013 - Taipei City, Taiwan [http://joomladay.tw/]

Joomla!Day Germany - September 13,14, 2013 - Nuremberg, German [http://joomladay.de/]

Joomla!Day Switzerland - September 21, 2013 - Berne, Switzerland [http://www.joomladay.ch/]

Joomla!Day Israel - October 10, 2013- Tel Aviv, Israel [http://jday.joomla.org.il]

JoomlaDay™ Italy - October 12, 2013 - Naples, Italy [http://www.joomladay.it/]

[[Category:Events Working Group]]
[[Category:Events]]

Nginx

2013-05-17T18:56:15Z

Oc666:

[http://nginx.net/ nginx] is a lightweight web server that powers 12.07% of web servers across all domains[http://en.wikipedia.org/wiki/Nginx#Usage]. Unless you have specific requirements that demand a heavy web server like Apache, you are much better off using nginx.

Below are instructions on how to get Joomla! running with [http://wiki.nginx.org/PHPFcgiExample nginx and PHP via FastCGI].

== Install nginx ==
For Ubuntu, run <tt>aptitude install nginx</tt>. For other distros, run the corresponding package manager, or see http://wiki.nginx.org/Install.

== Install PHP FastCGI ==
For Ubuntu, read this excellent page on how to [http://wiki.nginx.org/PHPFcgiExample configure PHP and FastCGI for nginx].

For Gentoo, PHP will run as a FastCGI service (fpm), so the nginx server will run PHP as a separated process:
<pre>
# echo "dev-lang/php gd gd2 curl simplexml tokenizer dom tidy sqlite xml fpm cgi" >> /etc/portage/package.use
# emerge php
</pre>
The default settings of php-fpm are good for most servers. For special configuration visit the [http://php.net/manual/en/install.fpm.php PHP FPM site].

== Configure Nginx ==
nginx configuration files reside in:
* <tt>/etc/nginx/sites-available/</tt> on Ubuntu (for sites running on that nginx instance)
* <tt>/etc/nginx/nginx.conf</tt> on Gentoo and Raspbian(= Debian optimized for Raspberry Pi)

Here is an sample nginx configuration file joomla.conf that you can reuse over all your nginx enabled-sites

<pre>
server {
listen 80;
server_name YOUR_DOMAIN;
server_name_in_redirect off;

access_log /var/log/nginx/localhost.access_log main;
error_log /var/log/nginx/localhost.error_log info;

root PATH_ON_SERVER;
index index.php index.html index.htm default.html default.htm;
# Support Clean (aka Search Engine Friendly) URLs
location / {
try_files $uri $uri/ /index.php?$args;
}

# deny running scripts inside writable directories
location ~* /(images|cache|media|logs|tmp)/.*\.(php|pl|py|jsp|asp|sh|cgi)$ {
return 403;
error_page 403 /403_error.html;
}

location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi.conf;
}

# caching of files
location ~* \.(ico|pdf|flv)$ {
expires 1y;
}

location ~* \.(js|css|png|jpg|jpeg|gif|swf|xml|txt)$ {
expires 14d;
}

}
</pre>

Pay attention for few things:
# The parameter <tt>fastcgi_pass</tt> is set to 127.0.0.1:9000, corresponding to the port that fpm is configured to listen to. This means you can run the PHP processes on separate servers. On Gentoo, you can find this configuration in <tt>/etc/php/fpm-php5.3/php-fpm.conf/</tt>
# Don't forget to replace YOUR_DOMAIN & PATH_ON_SERVER depend on your domain and the path of Joomla on your server.

== GZip support ==
If you need GZip compression support, add the following section to the http section of the main nginx configuration file:
<pre>
gzip on;
gzip_http_version 1.1;
gzip_comp_level 6;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain application/xhtml+xml text/css application/xml application/xml+rss text/javascript application/javascript application/x-javascr$
gzip_proxied any;
gzip_disable "MSIE [1-6]\.";
</pre>

== Sources ==
* [http://en.gentoo-wiki.com/wiki/Nginx Nginx in Gentoo]
* [http://www.kevinworthington.com/nginx-for-windows/ Nginx for Windows]
* [http://wiki.nginx.org/Install#Ubuntu_PPA Nginx in Ubuntu]
* [http://www.debianadmin.com/howto-install-nginx-webserver-in-debian.html Nginx in Debian]
* [http://php.net/manual/en/install.fpm.php PHP-FPM installation and configuration]
* [http://wiki.nginx.org/HttpGzipModule GZip in Nginx]
* [http://wiki.nginx.org/HttpRewriteModule Rewrite in Nginx]
* [http://nginx.org/en/docs/http/request_processing.html How nginx processes a request]

Archived:Developing a MVC Component/Adding categories

2013-03-12T16:01:43Z

Oc666: fix PHP strict standard - inheritance should have the same stamp as parent

{{version/tutor|2.5}}
{{Chunk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Contents}}

== Introduction ==
This tutorial is part of the [[Developing a Model-View-Controller (MVC) Component for Joomla!2.5]] tutorial. You are encouraged to read the previous parts of the tutorial before reading this.

The Joomla framework has implemented the use of categories for all components. Adding categorized ability to a component is fairly simple.

== Modifying the SQL ==
In order to manage categories, we have to change the SQL tables.

With your favorite editor, modify ''admin/sql/install.mysql.utf8.sql'' and put these lines:

<span id="admin/sql/install.mysql.utf8.sql">
''admin/sql/install.mysql.utf8.sql''
<source lang="sql">
DROP TABLE IF EXISTS `#__helloworld`;

CREATE TABLE `#__helloworld` (
`id` int(11) NOT NULL auto_increment,
`greeting` varchar(25) NOT NULL,
`catid` int(11) NOT NULL default '0',
PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=0 DEFAULT CHARSET=utf8;

INSERT INTO `#__helloworld` (`greeting`) VALUES
('Hello World!'),
('Good bye World!');
</source>
</span>

<span id="admin/sql/updates/mysql/0.0.12.sql">
''admin/sql/updates/mysql/0.0.12.sql''
<source lang="sql">
ALTER TABLE `#__helloworld` ADD `catid` int(11) NOT NULL default '0'
</source>
</span>

== Modifying the form ==
A HelloWorld message can now belong to a category. We have to modify the editing form. In the ''admin/models/forms/helloworld.xml'' file, put these lines:

<span id="admin/models/forms/helloworld.xml">
''admin/models/forms/helloworld.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<form
addrulepath="/administrator/components/com_helloworld/models/rules"
>
<fieldset>
<field
name="id"
type="hidden"
/>
<field
name="greeting"
type="text"
label="COM_HELLOWORLD_HELLOWORLD_FIELD_GREETING_LABEL"
description="COM_HELLOWORLD_HELLOWORLD_FIELD_GREETING_DESC"
size="40"
class="inputbox validate-greeting"
validate="greeting"
required="true"
default=""
/>
<field
name="catid"
type="category"
extension="com_helloworld"
class="inputbox"
default=""
label="COM_HELLOWORLD_HELLOWORLD_FIELD_CATID_LABEL"
description="COM_HELLOWORLD_HELLOWORLD_FIELD_CATID_DESC"
required="true"
>
<option value="0">JOPTION_SELECT_CATEGORY</option>
</field>
</fieldset>
</form>
</source>
</span>

Note that the category can be 0 (representing no category).

== Modifying the menu type ==
The HelloWorld menu type displays a drop down list of all messages. If the message is categorized, we have to add the category in this display.

In the ''admin/models/fields/helloworld.php'' file, put these lines:

<span id="admin/models/fields/helloworld.php">
''admin/models/fields/helloworld.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die;

// import the list field type
jimport('joomla.form.helper');
JFormHelper::loadFieldClass('list');

/**
* HelloWorld Form Field class for the HelloWorld component
*/
class JFormFieldHelloWorld extends JFormFieldList
{
/**
* The field type.
*
* @var string
*/
protected $type = 'HelloWorld';

/**
* Method to get a list of options for a list input.
*
* @return array An array of JHtml options.
*/
protected function getOptions()
{
$db = JFactory::getDBO();

/// $query = new JDatabaseQuery; WARNING - There's an error in this line, JDatabaseQuery is an abstract class
$query = $db->getQuery(true); // THIS IS THE FIX, WARNING IT MUST BE FIXED IN THE ZIP FILES

$query->select('#__helloworld.id as id,greeting,#__categories.title as category,catid');
$query->from('#__helloworld');
$query->leftJoin('#__categories on catid=#__categories.id');
$db->setQuery((string)$query);
$messages = $db->loadObjectList();
$options = array();
if ($messages)
{
foreach($messages as $message)
{
$options[] = JHtml::_('select.option', $message->id, $message->greeting .
($message->catid ? ' (' . $message->category . ')' : ''));
}
}
$options = array_merge(parent::getOptions(), $options);
return $options;
}
}
</source>
</span>

It will now display the category between parenthesis.

== Managing the submenu ==
The ''com_categories'' component allows to set the submenu using a helper file. With your favorite file manager and editor, put a ''admin/helpers/helloworld.php'' file containing these lines:

<span id="admin/helpers/helloworld.php">
''admin/helpers/helloworld.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die;

/**
* HelloWorld component helper.
*/
abstract class HelloWorldHelper
{
/**
* Configure the Linkbar.
*/
public static function addSubmenu($submenu)
{
JSubMenuHelper::addEntry(JText::_('COM_HELLOWORLD_SUBMENU_MESSAGES'),
'index.php?option=com_helloworld', $submenu == 'messages');
JSubMenuHelper::addEntry(JText::_('COM_HELLOWORLD_SUBMENU_CATEGORIES'),
'index.php?option=com_categories&view=categories&extension=com_helloworld',
$submenu == 'categories');
// set some global property
$document = JFactory::getDocument();
$document->addStyleDeclaration('.icon-48-helloworld ' .
'{background-image: url(../media/com_helloworld/images/tux-48x48.png);}');
if ($submenu == 'categories')
{
$document->setTitle(JText::_('COM_HELLOWORLD_ADMINISTRATION_CATEGORIES'));
}
}
}
</source>
</span>
'''NOTE:''' You MUST use your component name (without com_) for the helper file name, or else your submenus won't show in category view.

This function will be automatically called by the ''com_categories'' component. Note that it will
* change the submenu
* change some css properties (for displaying icons)
* change the browser title if the submenu is ''categories''
* change the title and add a ''preferences'' button

We have to change the general controller to call this function and modify the component entry point (the ''.icon-48-helloworld'' css class is now set in the ''addSubmenu'' function)

<span id="admin/controller.php">
''admin/controller.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

// import Joomla controller library
jimport('joomla.application.component.controller');

/**
* General Controller of HelloWorld component
*/
class HelloWorldController extends JController
{
/**
* display task
*
* @return void
*/
public function display($cachable = false, $urlparams = false)
{
// set default view if not set
$input = JFactory::getApplication()->input;
$input->set('view', $input->getCmd('view', 'HelloWorlds'));

// call parent behavior
parent::display($cachable, $urlparams);

// Set the submenu
HelloWorldHelper::addSubmenu('messages');
}
}
</source>
</span>

<span id="admin/helloworld.php">
''admin/helloworld.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

// require helper file
JLoader::register('HelloWorldHelper', dirname(__FILE__) . DS . 'helpers' . DS . 'helloworld.php');

// import joomla controller library
jimport('joomla.application.component.controller');

// Get an instance of the controller prefixed by HelloWorld
$controller = JController::getInstance('HelloWorld');

// Perform the Request task
$input = JFactory::getApplication()->input;
$controller->execute($input->getCmd('task'));

// Redirect if set by the controller
$controller->redirect();
</source>
</span>

== Adding some translation strings ==
Some strings have to be translated. In the ''admin/language/en-GB/en-GB.com_helloworld.ini'' file, put these lines:

<span id="admin/language/en-GB/en-GB.com_helloworld.ini">
''admin/language/en-GB/en-GB.com_helloworld.ini''
<source lang="ini">
COM_HELLOWORLD="Hello World!"
COM_HELLOWORLD_ADMINISTRATION="HelloWorld - Administration"
COM_HELLOWORLD_ADMINISTRATION_CATEGORIES="HelloWorld - Categories"
COM_HELLOWORLD_HELLOWORLD_CREATING="HelloWorld - Creating"
COM_HELLOWORLD_HELLOWORLD_DETAILS="Details"
COM_HELLOWORLD_HELLOWORLD_EDITING="HelloWorld - Editing"
COM_HELLOWORLD_HELLOWORLD_ERROR_UNACCEPTABLE="Some values are unacceptable"
COM_HELLOWORLD_HELLOWORLD_FIELD_CATID_DESC="The category the messages belongs to"
COM_HELLOWORLD_HELLOWORLD_FIELD_CATID_LABEL="Category"
COM_HELLOWORLD_HELLOWORLD_FIELD_GREETING_DESC="This message will be displayed"
COM_HELLOWORLD_HELLOWORLD_FIELD_GREETING_LABEL="Message"
COM_HELLOWORLD_HELLOWORLD_HEADING_GREETING="Greeting"
COM_HELLOWORLD_HELLOWORLD_HEADING_ID="Id"
COM_HELLOWORLD_MANAGER_HELLOWORLD_EDIT="HelloWorld manager: Edit Message"
COM_HELLOWORLD_MANAGER_HELLOWORLD_NEW="HelloWorld manager: New Message"
COM_HELLOWORLD_MANAGER_HELLOWORLDS="HelloWorld manager"
COM_HELLOWORLD_N_ITEMS_DELETED_1="One message deleted"
COM_HELLOWORLD_N_ITEMS_DELETED_MORE="%d messages deleted"
COM_HELLOWORLD_SUBMENU_MESSAGES="Messages"
COM_HELLOWORLD_SUBMENU_CATEGORIES="Categories"
</source>
</span>

== Packaging the component ==

Content of your code directory
* ''[[#helloworld.xml|helloworld.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_02#site/helloworld.php|site/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_02#site/controller.php|site/controller.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/helloworld/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_04#site/views/helloworld/view.html.php|site/views/helloworld/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/helloworld/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#site/views/helloworld/tmpl/default.xml|site/views/helloworld/tmpl/default.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_02#site/views/helloworld/tmpl/default.php|site/views/helloworld/tmpl/default.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/models/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#site/models/helloworld.php|site/models/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/language/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/language/en-GB/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_08#site/language/en-GB/en-GB.com_helloworld.ini|site/language/en-GB/en-GB.com_helloworld.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/index.html]]''
* ''[[#admin/helloworld.php|admin/helloworld.php]]''
* ''[[#admin/controller.php|admin/controller.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#admin/sql/install.mysql.utf8.sql|admin/sql/install.mysql.utf8.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#admin/sql/uninstall.mysql.utf8.sql|admin/sql/uninstall.mysql.utf8.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/updates/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/updates/mysql/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#admin/sql/updates/mysql/0.0.1.sql|admin/sql/updates/mysql/0.0.1.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#admin/sql/install.mysql.utf8.sql|admin/sql/updates/mysql/0.0.6.sql]]''
* ''[[#admin/sql/updates/mysql/0.0.12.sql|admin/sql/updates/mysql/0.0.12.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/fields/index.html]]''
* ''[[#admin/models/fields/helloworld.php|admin/models/fields/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/forms/index.html]]''
* ''[[#admin/models/forms/helloworld.xml|admin/models/forms/helloworld.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/models/forms/helloworld.js|admin/models/forms/helloworld.js]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/rules/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/models/rules/greeting.php|admin/models/rules/greeting.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/models/helloworld.php|admin/models/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_09#admin/models/helloworlds.php|admin/models/helloworlds.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworlds/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_10#admin/views/helloworlds/view.html.php|admin/views/helloworlds/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworlds/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_09#admin/views/helloworlds/tmpl/default.php|admin/views/helloworlds/tmpl/default.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_head.php|admin/views/helloworlds/tmpl/default_head.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_body.php|admin/views/helloworlds/tmpl/default_body.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_foot.php|admin/views/helloworlds/tmpl/default_foot.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworlds/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/views/helloworld/view.html.php|admin/views/helloworld/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/views/helloworld/submitbutton.js|admin/views/helloworld/submitbutton.js]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworld/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/views/helloworld/tmpl/edit.php|admin/views/helloworld/tmpl/edit.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/helpers/index.html]]''
* ''[[#admin/helpers/helloworld.php|admin/helpers/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/tables/index.html]]''
* ''[[#admin/tables/helloworld.php|admin/tables/helloworld.php]]''
* ''[[#admin/language/en-GB/en-GB.com_helloworld.ini|admin/language/en-GB/en-GB.com_helloworld.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_08#admin/language/en-GB/en-GB.com_helloworld.menu.ini|admin/language/en-GB/en-GB.com_helloworld.menu.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/controllers/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/controllers/helloworld.php|admin/controllers/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/controllers/helloworlds.php|admin/controllers/helloworldlist.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_08#language/en-GB/en-GB.ini|language/en-GB/en-GB.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|media/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|media/images/index.html]]''
* ''media/images/tux-16x16.png''
* ''media/images/tux-48x48.png''

Create a compressed file of this directory or directly download the [http://joomlacode.org/gf/download/frsrelease/11394/58410/com_helloworld-1.6-part12.zip archive] and install it using the extension manager of Joomla. You can add a menu item of this component using the menu manager in the backend.

<span id="helloworld.xml">
''helloworld.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension type="component" version="2.5.0" method="upgrade">

<name>COM_HELLOWORLD</name>

<creationDate>November 2009</creationDate>
<author>John Doe</author>
<authorEmail>john.doe@example.org</authorEmail>
<authorUrl>http://www.example.org</authorUrl>
<copyright>Copyright Info</copyright>
<license>License Info</license>

<version>0.0.12</version>

<description>COM_HELLOWORLD_DESCRIPTION</description>

<install> 
<sql>
<file driver="mysql" charset="utf8">sql/install.mysql.utf8.sql</file>
</sql>
</install>
<uninstall> 
<sql>
<file driver="mysql" charset="utf8">sql/uninstall.mysql.utf8.sql</file>
</sql>
</uninstall>
<update> 
<schemas>
<schemapath type="mysql">sql/updates/mysql</schemapath>
</schemas>
</update>



<files folder="site">
<filename>index.html</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>
<folder>views</folder>
<folder>models</folder>
<folder>language</folder>
</files>

<media destination="com_helloworld" folder="media">
<filename>index.html</filename>
<folder>images</folder>
</media>

<administration>

<menu img="../media/com_helloworld/images/tux-16x16.png">COM_HELLOWORLD_MENU</menu>


<files folder="admin">

<filename>index.html</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>

<folder>sql</folder>

<folder>tables</folder>

<folder>models</folder>

<folder>views</folder>

<folder>controllers</folder>

<folder>helpers</folder>
</files>

<languages folder="admin">
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.ini</language>
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.sys.ini</language>
</languages>
</administration>

</extension>
</source>
</span>

== Zips ==
Download the zip file for this Part:
[https://github.com/downloads/rvsjoen/joomla-tutorials/com_helloworld-part12.zip]

== Navigate ==
[[Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 11|Prev: Adding verifications]]
[[Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 13|Next: Adding configuration]]

== Contributors ==
*[[User:cdemko|Christophe Demko]]
*[[User:oaksu|Ozgur Aksu]]
*[[User:Anibal.sanchez|Anibal Sanchez]] // Just a fix

[[Category:Development]]
[[Category:Joomla! 1.6]]
[[Category:Joomla! 1.7]]
[[Category:Joomla! 2.5]]

J1.5:Plugin/Events/User

2012-11-26T14:49:02Z

Oc666:

{{RightTOC}}

{{Warning|This page is under migrating to Joomla 2.5 new plugin trigger methods}}

In a standard installation of Joomla! 2.5 we have several predefined events which, when triggered, call functions in the associated plugins.

The user events are divided into two parts. First we have the events used while
authentication of a user takes place:
*onUserLogin (on Joomla 1.5: onLoginUser)
*onUserLogout (on Joomla 1.5: onLogoutUser)
*onUserAuthenticate (on Joomla 1.5: onAuthenticate)
*onUserAuthorisationFailure (on Joomla 1.5: onAuthenticateFailure)

Second we have the events triggered during user management:
*onUserBeforeSave (on Joomla 1.5: onBeforeStoreUser)
*onUserAfterSave (on Joomla 1.5: onAfterStoreUser)
*onUserBeforeDelete (on Joomla 1.5: onBeforeDeleteUser)
*onUserAfterDelete (on Joomla 1.5: onAfterDeleteUser)

==onUserLogin==
===Description===
This event is triggered after the user is authenticated against the Joomla! user-base.

If you need to abort the login process (authentication), you will need to use [http://docs.joomla.org/Reference:User_Events_for_Plugin_System#5.3.4_onAuthenticate onAuthenticate] instead.

===Parameters===
* $user - an associative array of [http://api.joomla.org/Joomla-Framework/User/JAuthenticationResponse.html JAuthenticateResponse] type (see link for array keys)
* $options - an associative array containing these keys: ["remember"] => bool, ["return"] => string, ["entry_url"] => string

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserLogout==
===Description===
This event is triggered before the user is logged out of the system. <del>If one plugin
returns false, the global logout fails.</del> (needs verification)

===Parameters===
* $credentials - an associative array containing these keys: ["username"] => string, ["id"] => int
* $options - an associative array containing this key: ["clientid"] => int

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAuthenticate==
===Description===
This event is triggered to verify that a set of login credentials is valid.
===Parameters===
Array of credentials. Structure:\\
['username']\\
['password']\\
Alternative authentication mechanisms can supply additional credentials.

===Return Value===
An array of [[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] objects detailing the results of each called plugin, including success or failure.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>
*<tt>plugins/authentication/gmail.php</tt>
*<tt>plugins/authentication/joomla.php</tt>
*<tt>plugins/authentication/ldap.php</tt>
===Examples===
*<tt>plugins/authentication/example.php</tt>

==onUserLoginFailure==
===Description===
This event is triggered whenever a user authentication request is failed by any plugin.
===Parameters===
Two parameters. The credentials array for the user (see onAuthenticate), and the
[[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] that caused the failure.
===Return Value===
Unknown. The return value appears to be ignored in any case.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>

==onUserBeforeSave==
===Description===
This event is triggered before an update of a user record.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* $user - An associative array of the columns in the user table (current values).
* $isnew - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
Note; You can retrieve the values that are about to get updated with JFactory::getUser();

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAfterSave==
===Description===
This event is triggered after an update of a user record, or when a new user has been stored in the database.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* '''$user''' - An associative array of the columns in the user table.
* '''$isnew''' - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
* '''$success''' - Boolean to identify if the store was successful
* '''$msg''' - Error message if store failed
Note: The old values that were just updated are not available here or afterwards. In case you need the old values, use onBeforeStoreUser().

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserBeforeDelete==
===Description===
The event is triggered when a user is about to be deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAfterDelete==
===Description===
The event is triggered after a user has been deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.
* $succes - Boolean to identify if the deletion was successful
* $msg - Error message if delete failed ([http://api.joomla.org/Joomla-Framework/Error/JError.html JError] object detailing the error, if any)

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

<noinclude>[[Category:Plugin Development]][[Category:Specifications]]</noinclude>

J1.5:Plugin/Events/User

2012-11-26T14:37:11Z

Oc666:

{{RightTOC}}

{{Warning|This page is under migrating to Joomla 2.5 new plugin trigger methods}}

In a standard installation of Joomla! 2.5 we have several predefined events which, when triggered, call functions in the associated plugins.

The user events are divided into two parts. First we have the events used while
authentication of a user takes place:
*onUserLogin (on Joomla 1.5: onLoginUser)
*onUserLogout (on Joomla 1.5: onLogoutUser)
*onUserAuthorisation (on Joomla 1.5: onAuthenticate)
*onUserAuthorisationFailure (on Joomla 1.5: onAuthenticateFailure)

Second we have the events triggered during user management:
*onUserBeforeSave (on Joomla 1.5: onBeforeStoreUser)
*onUserAfterSave (on Joomla 1.5: onAfterStoreUser)
*onUserBeforeDelete (on Joomla 1.5: onBeforeDeleteUser)
*onUserAfterDelete (on Joomla 1.5: onAfterDeleteUser)

==onUserLogin==
===Description===
This event is triggered after the user is authenticated against the Joomla! user-base.

If you need to abort the login process (authentication), you will need to use [http://docs.joomla.org/Reference:User_Events_for_Plugin_System#5.3.4_onAuthenticate onAuthenticate] instead.

===Parameters===
* $user - an associative array of [http://api.joomla.org/Joomla-Framework/User/JAuthenticationResponse.html JAuthenticateResponse] type (see link for array keys)
* $options - an associative array containing these keys: ["remember"] => bool, ["return"] => string, ["entry_url"] => string

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserLogout==
===Description===
This event is triggered before the user is logged out of the system. <del>If one plugin
returns false, the global logout fails.</del> (needs verification)

===Parameters===
* $credentials - an associative array containing these keys: ["username"] => string, ["id"] => int
* $options - an associative array containing this key: ["clientid"] => int

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAuthorisation==
===Description===
This event is triggered to verify that a set of login credentials is valid.
===Parameters===
Array of credentials. Structure:\\
['username']\\
['password']\\
Alternative authentication mechanisms can supply additional credentials.

===Return Value===
An array of [[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] objects detailing the results of each called plugin, including success or failure.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>
*<tt>plugins/authentication/gmail.php</tt>
*<tt>plugins/authentication/joomla.php</tt>
*<tt>plugins/authentication/ldap.php</tt>
===Examples===
*<tt>plugins/authentication/example.php</tt>

==onUserLoginFailure==
===Description===
This event is triggered whenever a user authentication request is failed by any plugin.
===Parameters===
Two parameters. The credentials array for the user (see onAuthenticate), and the
[[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] that caused the failure.
===Return Value===
Unknown. The return value appears to be ignored in any case.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>

==onUserBeforeSave==
===Description===
This event is triggered before an update of a user record.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* $user - An associative array of the columns in the user table (current values).
* $isnew - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
Note; You can retrieve the values that are about to get updated with JFactory::getUser();

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAfterSave==
===Description===
This event is triggered after an update of a user record, or when a new user has been stored in the database.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* '''$user''' - An associative array of the columns in the user table.
* '''$isnew''' - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
* '''$success''' - Boolean to identify if the store was successful
* '''$msg''' - Error message if store failed
Note: The old values that were just updated are not available here or afterwards. In case you need the old values, use onBeforeStoreUser().

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserBeforeDelete==
===Description===
The event is triggered when a user is about to be deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onUserAfterDelete==
===Description===
The event is triggered after a user has been deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.
* $succes - Boolean to identify if the deletion was successful
* $msg - Error message if delete failed ([http://api.joomla.org/Joomla-Framework/Error/JError.html JError] object detailing the error, if any)

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

<noinclude>[[Category:Plugin Development]][[Category:Specifications]]</noinclude>

J1.5:Plugin/Events/User

2012-10-16T07:36:13Z

Oc666: /* Description */

In a standard installation of Joomla! 1.5 we have several predefined events which, when triggered, call functions in the associated plugins.

The user events are divided into two parts. First we have the events used while
authentication of a user takes place:
*onLoginUser
*onLogoutUser
*onAuthenticate
*onAuthenticateFailure

Second we have the events triggered during user management:
*onBeforeStoreUser
*onAfterStoreUser
*onBeforeDeleteUser
*onAfterDeleteUser

==onLoginUser==
===Description===
This event is triggered after the user is authenticated against the Joomla! user-base.

If you need to abort the login process (authentication), you will need to use [http://docs.joomla.org/Reference:User_Events_for_Plugin_System#5.3.4_onAuthenticate onAuthenticate] instead.

===Parameters===
* $user - an associative array of [http://api.joomla.org/Joomla-Framework/User/JAuthenticationResponse.html JAuthenticateResponse] type (see link for array keys)
* $options - an associative array containing these keys: ["remember"] => bool, ["return"] => string, ["entry_url"] => string

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onLogoutUser==
===Description===
This event is triggered before the user is logged out of the system. <del>If one plugin
returns false, the global logout fails.</del> (needs verification)

===Parameters===
* $credentials - an associative array containing these keys: ["username"] => string, ["id"] => int
* $options - an associative array containing this key: ["clientid"] => int

===Return Value===
Boolean
===Used in files===
*<tt>libraries/joomla/application/application.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onAuthenticate==
===Description===
This event is triggered to verify that a set of login credentials is valid.
===Parameters===
Array of credentials. Structure:\\
['username']\\
['password']\\
Alternative authentication mechanisms can supply additional credentials.

===Return Value===
An array of [[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] objects detailing the results of each called plugin, including success or failure.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>
*<tt>plugins/authentication/gmail.php</tt>
*<tt>plugins/authentication/joomla.php</tt>
*<tt>plugins/authentication/ldap.php</tt>
===Examples===
*<tt>plugins/authentication/example.php</tt>

==onLoginFailure==
===Description===
This event is triggered whenever a user authentication request is failed by any plugin.
===Parameters===
Two parameters. The credentials array for the user (see onAuthenticate), and the
[[references:joomla.framework:user:jauthenticateresponse|JAuthenticateResponse]] that caused the failure.
===Return Value===
Unknown. The return value appears to be ignored in any case.
===Used in files===
*<tt>libraries/joomla/application/user/authentication.php</tt>

==onBeforeStoreUser==
===Description===
This event is triggered before an update of a user record.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* $user - An associative array of the columns in the user table (current values).
* $isnew - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
Note; You can retrieve the values that are about to get updated with JFactory::getUser();

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onAfterStoreUser==
===Description===
This event is triggered after an update of a user record, or when a new user has been stored in the database.

Password in $user array is already hashed at this point. You may retrieve the cleartext password using $_POST['password'].

===Parameters===
* '''$user''' - An associative array of the columns in the user table.
* '''$isnew''' - Boolean to identify if this is a new user (true - insert) or an existing one (false - update)
* '''$success''' - Boolean to identify if the store was successful
* '''$msg''' - Error message if store failed
Note: The old values that were just updated are not available here or afterwards. In case you need the old values, use onBeforeStoreUser().

===Return Value===
None
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onBeforeDeleteUser==
===Description===
The event is triggered when a user is about to be deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

==onAfterDeleteUser==
===Description===
The event is triggered after a user has been deleted from the system.
===Parameters===
* $user - An associative array of the columns in the user table.
* $succes - Boolean to identify if the deletion was successful
* $msg - Error message if delete failed ([http://api.joomla.org/Joomla-Framework/Error/JError.html JError] object detailing the error, if any)

===Return Value===
None.
===Used in files===
*<tt>libraries/joomla/user/user.php</tt>
*<tt>plugins/user/joomla.php</tt>
===Examples===
*<tt>plugins/user/example.php</tt>

<noinclude>[[Category:Plugin Development]][[Category:Specifications]]</noinclude>

How to update from joomla 3.0 to 3.0.1

2012-10-10T20:50:41Z

Oc666:

(note: Joomla 3.0.1 will be released at approximately 9am PDT on October 9th, 2012)

This tutorial will show you how to update from Joomla 3.0.0 to 3.0.1, which is a bit different than normal.

If you use Joomla!'s FTP layer please see Note 3 below.

== Backup your site ==

The update process is generally safe, but it's always a good idea to make a backup before updating. So please go ahead and make a backup of your site now.

== Install the hotfix patch via Extension Manager. ==

[[Image:media_1349743656750.png|frame|none]]

=== Go to the Install from URL tab===
=== Copy and Past the Update URL===
The URL for the hot patch is: http://joomlacode.org/gf/download/frsrelease/17575/76677/joomla_3-0-0_hotpatch.zip. Copy and paste this into the Install URL text box.

[[Image:media_1349749085366.png|frame|none]]

== Install ==

If you have any difficulty installing from URL, download the file to your computer and install using Upload Package File.

== Set the Joomla! Update Server to Short Term Support ==

Navigate to Components→Joomla! Update and click the Options button. Change the Update server to Short Term Support as shown below.

[[Image:Version-3-0-1-update-image01.png|frame|none]]
Click '''Save & Close''' to save the change.

== Update to Joomla 3.0.1 via the Joomla! update component==
After getting the success message, go to Components >> Joomla! Update.

[[Image:media_1349749557492.png|frame|none]]

Note #1: If you are not getting the "Note: Hot patch for 3.0.1 update is installed" message, then please repeat Step 2 or ask for some help from a trusted developer.

Note #2: If you're not getting the "Joomla! update was found", click on Purge Cache button.

If you see both of the above, Install the Update.
[[Image:media_1349745128572.png|frame|none]]

Note #3: If you use FTP, you might have to FTP the update package, which you can download at:

http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=6517

<noinclude>[[Category:Version 3.0 FAQ]]
[[Category:Version 3.0.0 FAQ]]
[[Category:Version 3.0.1 FAQ]]</noinclude>

Languages cannot be installed using install languages

2012-09-29T19:56:57Z

Oc666: Created page with "If you're getting the next error when trying to install language: <pre> Warning Error connecting to the server: %s Install path does not exist Error Invalid URL Message Err..."

If you're getting the next error when trying to install language:
<pre>
Warning
Error connecting to the server: %s

Install path does not exist

Error
Invalid URL

Message
Error installing Hebrew Try again later or contact the language team coordinator
</pre>
You have 2 options to solve this:
# Download the language [http://joomlacode.org/gf/project/jtranslation3_x/frs/?action=index manually], and install it via extension manager.
# Apply this [http://joomlacode.org/gf/download/trackeritem/29374/76505/29374-oc.patch patch].

Note: This will be corrected automatically when you update to version 3.0.1.

<noinclude>[[Category:Version 3.0 FAQ]]
[[Category:Version 3.0.0 FAQ]]</noinclude>

Incorrect files permissions in version 3.0.0

2012-09-28T23:35:02Z

Oc666: Undo revision 76038 by Oc666 (talk)

The Linux file permissions for version 3.0.0 are incorrectly set in the download archive files. The correct file permissions should be read/write only for the owner and read-only for group and other. In the 3.0.0 archives, this is incorrectly set as read-write for the owner and group members.

For example, if you do the command <code>ls -l</code> at the Joomla root folder, you will see:

<code>-rw-rw-r-- ..... joomla.xml</code>

Instead you should see:

<code>-rw-r--r-- ..... joomla.xml</code>.

You can fix this from the Linux command line by navigating to the root folder of Joomla and typing this command:

<code>chmod -R g-w *</code>

Note: This will be corrected automatically when you update to version 3.0.1.

<noinclude>[[Category:Version 3.0 FAQ]]
[[Category:Version 3.0.0 FAQ]]</noinclude>

Incorrect files permissions in version 3.0.0

2012-09-28T23:32:39Z

Oc666:

The Linux file permissions for version 3.0.0 are incorrectly set in the download archive files. The correct file permissions should be read/write only for the owner and read-only for group and other. In the 3.0.0 archives, this is incorrectly set as read-write for the owner and group members.

For example, if you do the command <code>ls -l</code> at the Joomla root folder, you will see:

<code>-rw-rw-r-- ..... joomla.xml</code>

Instead you should see:

<code>-rw-r--r-- ..... joomla.xml</code>.

You can fix this from the Linux command line by navigating to the root folder of Joomla and typing the next two commands:

<code>find . -type f -exec chmod 644 {} \;</code>

<code>find . -type d -exec chmod 755 {} \;</code>

Note: This will be corrected automatically when you update to version 3.0.1.

<noinclude>[[Category:Version 3.0 FAQ]]
[[Category:Version 3.0.0 FAQ]]</noinclude>

Nginx

2012-09-25T10:33:40Z

Oc666: Update nginx statistics world wide and add link for SEF guide

[http://nginx.net/ nginx] is a lightweight web server that powers 11.53% of web servers across all domains[http://en.wikipedia.org/wiki/Nginx#Usage]. Unless you have specific requirements that demand a heavy web server like Apache, you are much better off using nginx.

Below are instructions on how to get Joomla! running with [http://wiki.nginx.org/PHPFcgiExample nginx and PHP via FastCGI].

== Install nginx ==
For Ubuntu, run <tt>aptitude install nginx</tt>. For other distros, run the corresponding package manager, or see http://wiki.nginx.org/Install.

== Install PHP FastCGI ==
For Ubuntu, read this excellent page on how to [http://wiki.nginx.org/PHPFcgiExample configure PHP and FastCGI for nginx].

For Gentoo, PHP will run as a FastCGI service (fpm), so the nginx server will run PHP asa different process:
<pre>
# echo "dev-lang/php gd gd2 curl simplexml tokenizer dom tidy sqlite xml fpm cgi" >> /etc/portage/package.use
# emerge php
</pre>
The default settings of php-fpm are good for most servers. For special configuration visit the [http://php.net/manual/en/install.fpm.php PHP FPM site].

== Configure Nginx ==
nginx configuration files reside in:
* <tt>/usr/local/nginx/conf/</tt> on Ubuntu
* <tt>/etc/nginx/nginx.conf</tt> on Gentoo

Here is an sample nginx configuration file joomla.conf that you can reuse over all your nginx enabled-sites

<pre>
server {
listen 80;
server_name YOUR_DOMAIN;
server_name_in_redirect off;

access_log /var/log/nginx/localhost.access_log main;
error_log /var/log/nginx/localhost.error_log info;

root PATH_ON_SERVER;
index index.php index.html index.htm default.html default.htm;
# Support Clean (aka Search Engine Friendly) URLs
location / {
try_files $uri $uri/ /index.php?q=$uri&$args;
}

# deny running scripts inside writable directories
location ~* /(images|cache|media|logs|tmp)/.*\.(php|pl|py|jsp|asp|sh|cgi)$ {
return 403;
error_page 403 /403_error.html;
}

location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi.conf;
}

# caching of files
location ~* \.(ico|pdf|flv)$ {
expires 1y;
}

location ~* \.(js|css|png|jpg|jpeg|gif|swf|xml|txt)$ {
expires 14d;
}

}
</pre>

Pay attention for few things:
# The parameter <tt>fastcgi_pass</tt> is set to 127.0.0.1:9000, corresponding to the port that fpm is configured to listen to. This means you can run the PHP processes on separate servers. On Gentoo, you can find this configuration in <tt>/etc/php/fpm-php5.3/php-fpm.conf/</tt>
# Don't forget to replace YOUR_DOMAIN & PATH_ON_SERVER depend on your domain and the path of Joomla on your server.

== GZip support ==
If you need GZip compression support, add the following section to the http section of the main nginx configuration file:
<pre>
gzip on;
gzip_http_version 1.1;
gzip_comp_level 6;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain application/xhtml+xml text/css application/xml application/xml+rss text/javascript application/javascript application/x-javascr$
gzip_proxied any;
gzip_disable "MSIE [1-6]\.";
</pre>

== Sources ==
* [http://en.gentoo-wiki.com/wiki/Nginx Nginx in Gentoo]
* [http://www.kevinworthington.com/nginx-for-windows/ Nginx for Windows]
* [http://wiki.nginx.org/Install#Ubuntu_PPA Nginx in Ubuntu]
* [http://www.debianadmin.com/howto-install-nginx-webserver-in-debian.html Nginx in Debian]
* [http://www.cyberciti.biz/faq/rhel-fedora-install-configure-nginx-php5/ Nginx in RedHat/Centos]
* [http://php.net/manual/en/install.fpm.php PHP-FPM installation and configuration]
* [http://wiki.nginx.org/HttpGzipModule GZip in Nginx]
* [http://wiki.nginx.org/HttpRewriteModule Rewrite in Nginx]
* [http://nginx.org/en/docs/http/request_processing.html How nginx processes a request]
* [http://www.waltercedric.com/index.php/joomlacms/2004-best-nginx-configuration-for-joomla Best nginx configuration for Joomla]

Pizza Bugs and Fun September 15, 2012

2012-09-13T22:29:17Z

Oc666: /* Locations */ Add Israel to locations

[[Image:pbf.png|right]]
{{RightTOC}}

We are announcing a Joomla! Pizza, Bugs and Fun event scheduled for Saturday, September 15, 2012. The event is global for virtual participants with local venues wherever they are organized. Joomla 3 is scheduled to be released on September 27th, so hopefully this Bug Squish will play a big part in squashing the remaining bugs.

This is also a birthday celebration for Joomla! so it's actually a Pizza Bugs Birthday Cake and Fun event. Be sure to add birthday cake, ice cream or stroopwafels to your party!

'''See the section [http://docs.joomla.org/Pizza_Bugs_and_Fun_September_15,_2012#General_Instructions General Instructions] below for instructions.'''

This wiki will be used as the central resource for coordinating efforts and accumulating results from this event.

The '''twitter''' hash tag is #jpbf12.

== Goals ==

* '''Bugs''' : We will be working through the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] where there are bug reports needing patches and/or testing.

* '''Documentation''' : We still have documentation that needs to be done. If you want to help out writing documentation, you're also more than welcome.

== Organization, logistics and communications ==

=== Communication ===
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only and you are all invited. This is the same chat we used for the PBF in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF. This Skype chat will be in English, but other languages can set up their own chat groups as well.

=== General Instructions ===

These instructions may change as we get closer to the event.

==== If you want to test bug fixes (i.e. patches) ====
* Look for issues with a status of Pending. We want at least 2 testers and more on complex issues, so you can test what others have tested already.
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, which means you download the patch from the tracker and apply it to a current SVN copy of Joomla.
* Most of the issues should have test instructions with them.
* Once you have tested, add comments to the tracker on your results. Start your comment with @test so you will get counted in the stats as a tester.
* Note: You don't have to delete the installation folder when you are using the development version of Joomla. This allows you to reinstall just by deleting the configuration.php file.
* Note: See the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#FAQ FAQ] on how to apply a Git pull request as an SVN patch.

===== Helpful Documentation =====
* [[Git for Testers and Trackers]] - We'd recommend beginners to use TortoiseGit
* [[Tortoise SVN]] - This is only if you're using SVN. We'd recommend using Git instead (see above) though.

==== If you want to code bug fixes ====
* Use the [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 CMS Issue Tracker] as usual, looking for the issues with a status of Confirmed.
* When you have a patch, add it to the tracker and change the status to Pending if you are able to. Add testing instructions if they don't already exist.

* If you want to just put your toe in the water at first, you could see if any of the older patches with a Pending status need updating to the newest build. When you find one that won't apply, you can manually apply it as necessary and then recreate the patch. Uploading to the tracker as a later version and note that you've updated it to the current build. Just make sure that you are using Unix End of Line and create that patch at the project level.

Helpful documentation:
* [[Setting up your workstation for Joomla! development]]. A step-by-step guide to installing the Eclipse IDE on your local workstation for Joomla! development.
* [http://community.joomla.org/blogs/community/828-webinar-using-eclipse-for-joomla-development.html Using Eclipse for Joomla! Development] Video webinar demonstrating overview of Eclipse features for Joomla! development
* [[Git for Testers and Trackers]]
* [[Working with git and github/My first pull request]]
* [[Secure coding guidelines]]
* [[Development Best Practices]]

==== If you want to work on Documentation ====
* To edit this Documentation Wiki, you will need a user account on the wiki. If you don't already have one, you may register on [[Special:UserLogin]]. You only need a valid email address and once registered you will have immediate permission to edit any page except for a few that are protected because they are high profile spam targets.
* Get your user account a few days before and make sure that you are able to sign in since the automatic authorization system can lock some people out.
* If you'd like something to be edited, but you're not sure what to write exactly, use talk pages to add comments to pages.
* During the PBF, several experienced Wiki editors will be available in the Skype chat to help you.

You are free to work on any aspect of the documentation that takes your fancy, but here are some suggestions for stuff that really needs some love and attention:
* Help screens for Joomla 3.0.
*: I would suggest you pick a particular part of the help screens and propagate that through all the help screens, rather than trying to complete a single help screen. For example, make sure every page has an up-to-date screenshot or make sure every page has a correct and up-to-date description, and so on. [[Help30:Help screens]] is a complete list of all the help screens.
* [[Getting Started with Joomla!]]
* [[Administrators]]
*: The plan is for this page to become the entry point into a comprehensive, task-orientated Administrators Manual. As you can see, there are plenty of gaps that need filling, so please fill away :P
* [[Secure coding guidelines]]
*: This needs to be updated, or perhaps a new version created, following the introduction of JInput and the deprecation of JRequest.
* [[Developers]]
*: A re-organisation of the [[Developers]] page is long overdue and suggestions are welcome. Rather than editing this page directly, I would suggest adding a new sub-page under your user page (eg. [[User:Jane Doe/Developers]] so that it can be reviewed and improved before committing a major change to this important page).

=== Pizza ===
We are offering pizza (or any comparable locally popular main course) and soda for pre-registered groups. Be sure to also get some birthday cake to celebrate Joomla's birthday. We are not setting a specific maximum, but please don’t go crazy with it. Get enough so there’s plenty for everyone, but not a week’s worth of pizza and soda leftovers for everyone. Contact Andrea Tarr (andrea.tarr@joomla.org) before the event to register and get details.

== Locations ==

If you want to get people together and have a venue to share, please add it below. Share as much as possible details like exact location, url for more information about the venue, ways to register, date and time the venue is available etc.

If you set up a location please send contact information to Andy Tarr (andrea.tarr@joomla.org). Feel free to contact her with any questions.

===Virtual===
====Skype Chat====
We have set up a Skype chat for all attendees of the PBF. Skype is invitation only. This is the same Skype chat we used in March. To get an invitation, email your Skype name to Andy Tarr (andrea.tarr@joomla.org). To make sure you can get in, get your invitation and log in before the day of the PBF.

If you don't already have Skype, you can download it for free from [http://skype.com Skype].

=== Europe ===
[http://www.joomla.fr/actualites-de-joomlaorg/session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-30 Joomla User Group France]
B5Prod agency
31 rue des Tuiliers
69008 Lyon
10:00 - 18:00 GMT
Contact: [mailto:marc.studer@joomla.fr Marc Studer]

[http://www.joomla.fr/actualites-de-joomlaorg/session-pizza-bugs-and-fun-2012-participez-a-la-stabilisation-de-joomla-30 Joomla User Group France]
Le Node
12 rue des Faussets
33000 Bordeaux
9:00 - 18:00 GMT
Contact: [mailto:eric.lamy@joomla.fr Eric Lamy]

=== North America ===

=== South America ===

=== Asia/Pacific ===

=== Africa ===

=== Middle East ===
[https://www.facebook.com/groups/joomlaisrael/permalink/459141894130485/ Joomla User Group Israel]
Place: TBD. Currently skype
21:00 UTC+3
Contact: [mailto:info@joomla.org.il info at joomla dot org dot il]

== Registration ==
=== For write access to this wiki ===
To get write access to this wiki you will need to [[Special:Userlogin|register here first]]. Please be aware that the registration process requires a valid email address. This is the same login for updating Joomla documentation.

=== At a physical location ===
If you wish to be present at one of the physical locations listed above then you must register in advance because space most likely is limited. Registrations are the responsibility of the individual location organizers and you should click on the appropriate link above for more information.

=== Taking bugs, tasks and pizza ===

Please check the [http://docs.joomla.org/Pizza_Bug_and_Fun_September_15,_2012#Organization.2C_logistics_and_communications Organization, logistics and communications section] for details on how to get involved in working on tasks.

==Requirements==
* All code must be made available under the [http://www.gnu.org/licenses/gpl-2.0.html General Public Licence version 2].
* All documentation contributions must be made available under the [[JEDL|Joomla! Electronic Documentation License]]. Further information on the JEDL is available in the [[JEDL/FAQ|JEDL Frequently Asked Questions]]
* No advertising or self-promotion will be allowed. This includes back links to your website or anyone else's. The one exception is that if you have made a contribution then feel free to add your name and an optional link to your website to the [[Pizza Bugs and Fun September 15, 2012/Contributors List|Contributors List]]
* All contributions must be in English. Note that the official language of the Joomla! project is British English.

== FAQ ==
Q: Where is the code for Joomla?

A: The current Joomla code can be found either on Joomlacode or GitHub.

*GitHub - https://github.com/joomla/joomla-cms
*SVN - http://joomlacode.org/svn/joomla/development/trunk

Q: Which one is 3.0?

A: On GitHub, it is the master branch. For SVN, it is the main trunk.

Q: Any known issues with JForge and Chrome on Windows?

A: It have been seen that browsing the JForge tracker, Chrome may ask for a missing plugin (windows media player). No workaround for this is yet known.

Q: How do I apply a Git pull request as an SVN Patch?

A: Git & SVN are two different ways of doing version control for software. Joomla is in a transition stage of moving from SVN to Git. Many of the patches will be SVN patches which you'll find in the files tab at the bottom of the tracker. Some trackers will have Git "pull requests" instead.

These git pull requests can still usually be applied like SVN patches if you only have SVN. Take the URL of the pull request, add ".patch" to the end of it and use that as a URL to the patch.

[[Image:eclipse-pull-request-1.png]]

Many of this pull requests will also have extra folders on the internal file names like a/ and b/.

[[Image:eclipse-pull-request-3.png]]

In Eclipse, to remove those automatically, change Ignore Leading Path Name Segments to 1.

[[Image:eclipse-pull-request-2.png]]

==Contributors==
{{:Pizza Bugs and Fun September 15, 2012/Contributors List}}

<noinclude>[[Category:Bug Squad]]
[[Category:Development]][[Category:Events]]</noinclude>

Joomla info page/he-IL

2012-08-14T16:56:06Z

Oc666: /* אירועים אזוריים / Joomladays */

{{RightTOC}}
= Hebrew / עברית =

== מה זה ג'ומלה? ==
ג'ומלה היא מערכת ניהול תוכן עטורת פרסים, אשר מאפשרת לך לבנות אתרי אינטרנט ויישומים מקוונים רבי עוצמה. היבטים רבים, כולל שימוש קלות ויכולת הרחבתה, הפכו את ג'ומלה לתוכנת אתרי האינטרנט הפופולרית ביותר. החשוב מכל, ג'ומלה הינו פתרון קוד פתוח והוא זמין באופן חופשי לכולם. היתרונות של ג'ומלה! כוללים:
* התקנה קלה
* אתר אינטרנט פשוט לתחזוקה
* אבטחה מעולה ויציבות
* הרחבות חינם ומסחריות רבות עוצמה
* שפע תבניות כדי לשנות בקלות את המראה של האתר שלך

== איפה ניתן להשיג ג'ומלה? ==
* הורדת ג'ומלה: http://www.joomla.org.il/download.html
* הורדת ג'ומלה חבילת שפה עבור עברית (he-IL): http://joomlacode.org/gf/project/jtranslation1_6/frs/?action=FrsReleaseBrowse&frs_package_id=5685

== איפה ניתן לקבל הרחבות? ==
* הורדת הרחבות: http://extensions.joomla.org/
* הורדת חבילות שפה עברית עבור הרחבות: http://www.joomla.org.il

== היכן להשיג תיעוד של ג'ומלה? ==
* תיעוד באנגלית: http://docs.joomla.org
* תיעוד בעברית: http://www.joomla.org.il/תיעוד.html

== איפה ניתן לקבל תמיכה עבור ג'ומלה? ==
* תמיכה חינם באנגלית: http://forum.joomla.org/
* תמיכה חינם בעברית:
** http://forum.joomla.org/viewforum.php?f=172
** http://www.joomla.org.il/פורום.html
* תמיכה מסחרית: http://resources.joomla.org/ (האתר באנגלית)

== אירועים אזוריים / Joomladays ==
[http://jday11.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2011]

[http://jday.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2012]

קהילות מקומיות ברחבי העולם מארגנות ימי ג'ומלה. יום ג'ומלה הינו אירוע שנוצר באופן בלעדי עבור משתמשי ג'ומלה ופרויקטים ובדרך כלל מושך קהל אזורי. מידע נוסף: http://community.joomla.org/events/joomla-days.html

== קבוצות משתמשי ג'ומלה (JUG) ==
קבוצות משתמשי ג'ומלה מקומיות הם דרך מצוינת להכיר אנשים חדשים, לקבל עזרה עם פרויקט, או לחלוק את הידע שלכם עם משתמשי ג'ומלה אחרים. ג'ומלה נמצא בכל מקום, אז בדקו אם יש כבר קבוצה כזו באזורך. אם לא, אולי כדאי לך לשקול להקים אחד.

* JUG בישראל: http://community.joomla.org/user-groups/middle-east/israel/tel-aviv-jug.html
* JUG שאלות נפוצות: http://community.joomla.org/user-groups/jug-faq.html

== כיצד לתרום לג'ומלה? ==
* לענות על שאלות בפורום ג'ומלה http://www.joomla.org.il
* כתוב או תרגם הדרכה או תיעוד http://www.joomla.org.il/תיעוד.html (נדרש רישום)
* לפתח הרחבה או תבנית
* לבדוק או לדווח על בעיה: http://docs.joomla.org/How_do_you_report_a_bug%3F
* הצטרף לקבוצת עבודה של ג'ומלה!
* לעזור בארגון אירוע ג'ומלה!
* לתרום בדרכים אחרות http://contribute.joomla.org

Archived:Developing a MVC Component

2012-08-11T16:01:20Z

Oc666: /* Articles in this Series */

==Articles in this Series==
{{Chunk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Contents}}

Chunk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Contents

2012-08-11T12:11:11Z

Oc666: Change urls due to change of articles names

* [[Developing a Model-View-Controller Component/2.5/Developing a Basic Component|Developing a Basic Component]]
* [[Developing a Model-View-Controller Component/2.5/Adding a view to the site part|Adding a view to the site part]]
* [[Developing a Model-View-Controller Component/2.5/Adding a menu type to the site part|Adding a menu type to the site part]]
* [[Developing a Model-View-Controller Component/2.5/Adding a model to the site part|Adding a model to the site part]]
* [[Developing a Model-View-Controller Component/2.5/Adding a variable request in the menu type|Adding a variable request in the menu type]]
* [[Developing a Model-View-Controller Component/2.5/Using the database|Using the database]]
* [[Developing a Model-View-Controller Component/2.5/Basic backend|Basic backend]]
* [[Developing a Model-View-Controller Component/2.5/Adding language management|Adding language management]]
* [[Developing a Model-View-Controller Component/2.5/Adding backend actions|Adding backend actions]]
* [[Developing a Model-View-Controller Component/2.5/Adding decorations to the backend|Adding decorations to the backend]]
* [[Developing a Model-View-Controller Component/2.5/Adding verifications|Adding verifications]]
* [[Developing a Model-View-Controller Component/2.5/Adding categories|Adding categories]]
* [[Developing a Model-View-Controller Component/2.5/Adding configuration|Adding configuration]]
* [[Developing a Model-View-Controller Component/2.5/Adding ACL|Adding ACL]]
* [[Developing a Model-View-Controller Component/2.5/Adding an install-uninstall-update script file|Adding an install/uninstall/update script file]]
* [[Developing a Model-View-Controller Component/2.5/Using the language filter facility|Using the language filter facility]]
* [[Developing a Model-View-Controller Component/2.5/Adding an update server|Adding an update server]]
* [[Developing a Model-View-Controller Component/2.5/Example of a frontend update function|Example of a Frontend Update Function]]
* [[Developing a Model-View-Controller Component/2.5/Example of menu parameters and stylesheets|Example of Menu Parameters & Stylesheets]]

Archived:Access Control List Tutorial

2012-08-04T13:47:10Z

Oc666:

{{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}
=Overview of ACL in Versions 1.6/1.7/2.5=

This section outlines the major ACL changes between versions 1.5 and 2.5 series (including 1.6 and 1.7). The table below summarizes the major changes from version 1.5.

{| class="wikitable" cellspacing="0" cellpadding="4" border="1"
| <br />
! Version 1.5
! 2.5 series
|-
! Groups
| 7 fixed groups (Public, Registered, Author, Editor, Publisher, Manager, Administrator, and Super-Administrator)
| Unlimited user-defined Groups
|-
! Users & Groups
| A User can be assigned to only one group
| A User can be assigned to multiple groups
|-
! Access Levels
| 3 fixed Access Levels (Public, Registered, Special)
| Unlimited user-defined Access Levels
|-
! Access Levels & Groups
| Relationship between Groups and Access Levels was fixed.
| Groups are assigned to Access Levels. Any combination of Groups can be assigned to any Access Level.
|}

We see that in every case the ACL has been made much more flexible, with unlimited Groups and Access Levels, and the ability to assign one User to multiple Groups and any Groups to any Access Level.

=Separate ACL for Viewing and Doing=

The Joomla ACL system can be thought of as being divided into two completely separate systems. One system controls what things on the site users can ''view''. The other controls what things users can ''do'' (what actions a user can take). The ACL for each is set up differently.

==Controlling What Users Can See==

The setup for controlling what users can see is done as follows:
# Create the different User Groups required for the site. Each Group can be thought of as a role that a user will have for the site. Keep in mind that one User can be a member of one or more Groups. If desired, groups can have parent groups. In this case, they automatically inherit the Access Levels of the parent group.
# Create the set of Access Levels required for the site. This could be a small number or a large number depending on the number of different groups and how many categories of items there are. Assign each Access Level to one or more of the User Groups created in step 1.
# Assign each item to be viewed to one Access Level. Items include content items (articles, contacts, and so on), menu items, and modules.

Any time a user is about to view an item on a Joomla page, the the program checks whether the user has access to the item, as follows:
# Creates a list of all the Access Levels that the User has access to, based on all Groups that the User belongs to. Also, if a group has a parent group, access levels for the parent group are also included in the list.
# Checks whether the Access Level for the item (article, module, menu item, and so on) is on that list. If yes, then the item is displayed to the user. If no, then the item is not displayed.

Note that Access Levels are set separately for each Group and are not inherited from a group's parent group.

==Controlling What Users Can Do==

The system for setting up what users can do -- what actions they can take on a given item -- is set up with the Permissions tab of Global Configuration and the Permissions tab of the Options screen of each component. Permissions can also be set up at the Category level for core components and at the Article level for articles.

Note that this set up is independent of the setup for viewing.

When a user wants to initiate a specific action against a component item (for example, edit an article), the system checks the permission for this combination of user, item, and action. If it is allowed, then the user can proceed. Otherwise, the action is not allowed.

The remainder of this tutorial discusses how we control what users can do -- what action permissions they have.

=Actions, Groups, and Inheritance=

The other side of ACL is granting permissions to users to take actions on objects. Here again there is a big change between Version 1.5 and 1.6. In 1.5, the actions allowed for a given group were fixed. For example, a User in the Author group could only submit an article whereas someone in the Publisher group could submit, edit, and publish articles. Also, in version 1.5 the permissions were all-or-nothing. A member of the Editor group could edit all articles on the site.

The table below shows what has changed between versions 1.5 and 2.5 series (including 1.6 and 1.7).

{| class="wikitable" cellspacing="0" cellpadding="4" border="1"
| <br />
! Version 1.5
! 2.5 series
|-
! Groups and Actions
| Actions allowed by different groups are fixed.
| Actions allowed for each group are defined by site administrator.
|-
! Permission Scope
| Entire Site. User has same permissions for all objects on the site.
| Permissions can be set at multiple levels in hierarchy: Site, Component, Category, Object.
|-
! Permission Inheritance
| Not applicable
| Permissions can be inherited from parent Groups and parent Categories
|}

==How Permissions Work==

There are four possible permissions for actions, as outlined below:

* '''Not set''': Defaults to "deny" but, unlike the Deny permission, this permission can be overridden by setting a child group or a lower level in the permission hierarchy to "Allow". This permission only applies to the Global Configuration permissions.
* '''Inherit''': Inherits the value from a parent Group or from a higher level in the permission hierarchy. This permission applies to all levels except the Global Configuration level.
* '''Deny''': Denies this action for this level and group. '''IMPORTANT:''' This also denies this action for all child groups and all lower levels in the permission hierarchy. Putting in Allow for a child group or a lower level will not have any effect. The action will always be denied for any child group member and for any lower level in the permission hierarchy.
* '''Allow''': Allows this action for this level and group and for lower levels and child groups. This does not have any effect if a higher group or level is set to Deny or Allow. If a higher group or level is set to Deny, then this permission will always be denied. If a higher group or level is set to Allow, then this permission will already be allowed.

==Permission Hierarchy Levels==

Action permissions in version 2.5 can be defined at up to four levels, as follows:
# '''Global Configuration''': determines the default permissions for each action and group.
# '''Component Options->Permissions''': can override the default permissions for this component (for example, Articles, Menus, Users, Banners, and so on)
# '''Category''': can override the default permissions for objects in one or more categories. Applies to all components with categories, including Articles, Banners, Contacts, Newsfeeds, and Weblinks.
# '''Article''': Can override the permissions for a specific article. This level only applies to articles. Other components only allow the first three levels.

===Global Configuration===
This is accessed from Site → Global Configuration → Permissions. This screen allows you set the top-level permission for each group for each action, as shown in the screenshot below.
[[Image:screenshot_acl_tutorial_20110111-01.png|center]]
The options for each value are Inherited, Allowed, or Denied. The Calculated Setting column shows you the setting in effect. It is either Not Allowed (the default), Allowed, or Denied.

You work on one Group at a time by opening the slider for that group. You change the permissions in the Select New Settings drop-down list boxes.

Note that the Calculated Setting column is not updated until you press the Save button in the toolbar. To check that the settings are what you want, press the Save button and check the Calculated Settings column.

===Component Options->Permissions===
This is accessed for each component by clicking the Options icon in the toolbar. This screen is similar to the Global Configuration screen above. For example, clicking the Options toolbar icon in the Menu Manager shows the Menus Configuration below.
[[Image:screenshot_acl_tutorial_20110111-02.png|center]]
Access to Options is only available to members of groups who have permission for the Configure action in for each component. In the example above, the Administrator group has Allowed permission for the Configure option, so members of this group can access this screen.

===Category===
Category permissions are accessed in the Category Manager: Edit Category screen, in a slider at the bottom of the screen. This screen has five permissions, as shown below.
[[Image:screenshot_acl_tutorial_20110111-03.png|center]]
In these screens, you work on the permissions for one User Group at a time. In the example above, we are editing the permissions for the Administrator group.

Note that the Configure and Access Component actions do not apply at the category level, so those actions are not included.

Note also that Categories can be arranged in a hierarchy. If so, then action permissions in a parent category are inherited automatically by a child category. For example, if you had a category hierarchy of Animals → Pets → Dogs, then the full permission level hierarchy for an article in the Dogs category would be as follows:
* Global Configuration
* Article Manager → Options → Permission
* Animals Category
* Pets Category
* Dogs Category
* specific article

===Article===
Permissions for a single article are access in the Article Manager: Edit Article screen, again in a slider at the bottom of the screen. This screen has three actions, as shown below.
[[Image:screenshot_acl_tutorial_20110111-04.png|center]]
Again, you edit each group by clicking on it to open the slider for that group. You can then change the permissions under the Select New Setting column. To see the effect of any changes, press the Save button to update the Calculated Setting column.

Note that the Configure, Access Component, and Create actions do not apply at the article level, so these actions are not included. Permission to create an article is set at one of the higher levels in the hierarchy.

==Access Levels==

Access Levels in 2.5 series are simple and flexible. The screen below shows the Special Access Level.
[[Image:screenshot_acl_tutorial_20110111-05.png|center]]
Simply check the box for each group you want included in that level. The Special Access Level includes the Manager, Author, and Super Users groups. It also includes child groups of those groups. So, Administrator group is included, since it is a child group of the Manager group. The Editor, Publisher, and Shop Suppliers groups are included, since they are child groups of Author. (Note that we could check all of the child groups if we wanted and it wouldn't hurt anything.)

Once Access Levels are created, they are used in the same way as in version 1.5. Each object in the front end is assigned an Access Level. If the level is Public, then anyone may access that object. Otherwise, only members of groups assigned to that access level may access that object. Access levels are assigned to Menu Items and to Modules. Each one can only be assigned to one access level.

For example, the screen below shows the Edit Menu Item screen with the list of available access levels.

[[Image:screenshot_acl_tutorial_20110111-06.png|center]]

=Default ACL Setup=

When Joomla! is installed, these are set to their initial default settings. We will discuss these initial settings as a way to understand how the ACL works.

==Default Groups==

Version 2.5 allows you to define your own Groups. When you install version 2.5, it includes a set of default groups, as shown below.

[[Image:screenshot_acl_tutorial_20110111-07.png|center]]

The arrows indicate the child-parent relationships. As discussed above, when you set a permission for a parent group, this permission is automatically inherited by all child groups. The Inherited, and Allowed permissions can be overridden for a child group. The Denied permission cannot be overridden and will always deny an action for all child groups.

==Global Configuration==

Joomla! version 2.5 will install with the same familiar back-end permissions as that of version 1.5. However, with 2.5, you can easily change these to suit the needs of your site.

As discussed earlier, the permissions for each action are inherited from the level above in the permission hierarchy and from a group's parent group. Let's see how this works. The top level for this is the entire site. This is set up in the Site->Global Configuration->Permissions, as shown below.

[[Image:screenshot_acl_tutorial_20110111-08.png|center|]]

The first thing to notice are the nine Actions: Site Login, Admin Login, Super Admin, Access Component, Create, Delete, Edit, Edit State. and Edit Own. These are the actions that a user can perform on an object in Joomla. The specific meaning of each action depends on the context. For the Global Configuration screen, they are defined as follows:

;Site Login : Login to the front end of the site

;Admin Login : Login to the back end of the site

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

;Access Component: Open the component manager screens (User Manager, Menu Manager, Article Manager, and so on)

;Create : Create new objects (for example, users, menu items, articles, weblinks, and so on)

;Delete : Delete existing objects

;Edit : Edit existing objects

;Edit State : Change object state (Publish, Unpublish, Archive, and Trash)

;Edit Own : Edit objects that you have created.

Each Group for the site has its own slider which is opened by clicking on the group name. In this case (with the sample data installed), we have the standard 7 groups that we had in version 1.5 plus two additional groups called "Shop Suppliers" and "Customer Group". Notice that our groups are set up with the same permissions as they had in version 1.5. Keep in mind that we can change any of these permissions to make the security work the way we want. Let's go through this to see how it works.

* '''Public''' has everything set to "Not set", as shown below.
[[Image:screenshot_acl_tutorial_20110112-06.png|center|]]
: This can be a bit confusing. Basically, "Not Set" is the same as "Inherited". Because Public is our top-level group, and because Global Configuration is the top level of the component hierarchy, there is nothing to inherit from. So "Not Set" is used instead of "Inherit".
: The default in this case is for no permissions. So, as you would expect, the Public group has no special permissions. Also, it is important to note that, since nothing is set to Denied, all of these permissions may be overridden by child groups or by lower levels in the permission hierarchy.

* '''Manager''' is a "child" group of the Public group. It has Allowed permissions for everything except Access Component and Super Admin. So a member of this group can do everything in the front and back end of the site except change Global Permissions and Component Options.

* '''Administrator''' group members inherit all of the Manager permissions and also have Allowed for Access Component. So members of this group by default can access the Options screens for each component.

* '''Registered''' is the same a Public except for the Allow permission for the Site Login action. This means that members of the Registered group can login to the site. Since default permissions are inherited, this means that, unless a child group overrides this permission, all child groups of the Registered group will be able to login as well.

* '''Author''' is a child of the Registered group and inherits its permissions and also adds Create and Edit Own. Since Author, Editor, and Publisher have no back-end permissions, we will discuss them below, when we discuss front-end permissions.

* '''Editor''' is a child of the Authors group and adds the Edit permission.

* '''Publisher''' is a child of Editor and adds the Edit State permission.

* '''Shop Suppliers''' is an example group that is installed if you install the sample data. It is a child group of Author.

* '''Customer Group''' is an example group that is installed if you install the sample data. It is a child group of Registered.

* '''Super Users''' group has the Allow permission for the Super Admin action. Because of this, members of this group have super user permissions throughout the site. They are the only users who can access and edit values on the Global Configuration screen. Users with permission for the Super Admin action have some special characteristics:
** If a user has Super Admin permissions, no other permissions for this user matter. The user can perform any action on the site.
** Only Super Admin users can create, edit, or delete other Super Admin users or groups.

There are two very important points to understand from this screen. The first is to see how the permissions can be inherited from the parent Group. The second is to see how you can control the default permissions by Group and by Action.

This provides a lot of flexibility. For example, if you wanted Shop Suppliers to be able to have the ability to login to the back end, you could just change their Admin Login value to "Allowed". If you wanted to not allow members of Administrator group to delete objects or change their state, you would change their permissions in these columns to Inherited (or Denied).

It is also important to understand that the ability to have child groups is completely optional. It allows you to save some time when setting up new groups. However, if you like, you can set up all groups to have Public as the parent and not inherit any permissions from a parent group.

==Component Options & Permissions==

Now, let's continue to see how the default back-end permissions for version 2.5 mimic the permissions for version 1.5. The Super Users group in 2.5 is equivalent to the Super Administrator group in 1.5.

Just looking at the Global Configuration screen above, it would appear that the Administrator group and the Manager group have identical permissions. However, in version 1.5 Administrators can do everything except Global Configuration, whereas Managers are not permitted to add users or work with menu items. That is also true in the default version 2.5 configuration. Let's see how this is accomplished.

If we navigate to Users->User Manager and click the Options button in the toolbar, we see the screen below:

[[Image:screenshot_acl_tutorial_20110111-09.png|center|]]
[[Image:screenshot_acl_tutorial_20110111-10.png|center|]]

This screen is the same as the Global Configuration Permissions screen, except that these values only affect working with Users. Let's look at how this works.

First, notice that the Administrator group has Allow permission for the Admin action and the Manager group has Deny permission for this action. Remember that the Admin action in the Global Configuration screen gives the group "super user" permissions. In this screen, the Admin action allows you to edit the Options values. So, the Administrator group can do this but the Manager group cannot.

Next, notice that the Administrator has Inherit for the Manage action and the Manager group has Deny permission. In this screen, the Manage action gives a group access to the User Manager. Since the Administrator has Allow for the Manage action by default, then the Inherit permission here means they inherit the Allow permission for the Manage action. Since the Manager group has Deny permission for the Manage action, members of the Manager group cannot access the User Manager and therefore cannot do any of the other user-related actions.

If you look at the Options for Menus->Menu Manager, you will see the same default settings as for the User Manager. Again, the Administrator group can manage and set default permissions for Menu Manager objects whereas the Manager group cannot.

In short, we can see that the different permissions for the Administrator and Manager groups are set using the Options->Permissions forms on the User Manager and Menu Manager screens.

It is also important to understand that this same Options->Permissions form for setting default permissions is available for all Joomla! objects, including Media Manager, Banners, Contacts, Newsfeeds, Redirect, Search Statistics, Web Links, Extensions, Modules, Plugins, Templates, and Language. So you now have the option to create user groups with fine-tuned sets of back-end permissions.

==Front End Permissions==

Default permissions for the front end are also set using the Options form. Let's look at Content->Article Manager->Options->Permissions. First, let's look at the permissions for Manager, as shown below.
[[Image:screenshot_acl_tutorial_20110111-11a.png|center|frame]]
Manager has allowed permission for all actions except Configure. So members of the Manager group can do everything with Articles except open the Options screen.

Now let's look at Administrator, as shown below.
[[Image:screenshot_acl_tutorial_20110111-12a.png|center|frame]]
Administrator has Allowed for Configure, so Administrators can edit this Options screen.

Both groups can create, delete, edit, and change the state of articles.

Now, let's look at the groups Publisher, Editor, and Author and see how their permissions are set.

Authors only have Create and Edit Own permissions, as shown below.
[[Image:screenshot_acl_tutorial_20110112-07.png|center|frame]]
This means that Authors can create articles and can edit articles they have created. They may not delete articles, change the published state of articles, or edit articles created by others.

Editors have the same permissions as Authors with the addition of permission for the Edit action, as shown below.
[[Image:screenshot_acl_tutorial_20110112-08.png|center|frame]]
So Editors can edit articles written by anyone.

Publishers can do everything Editors can do plus they have permission for the Edit State action, as shown below.
[[Image:screenshot_acl_tutorial_20110112-09.png|center|frame]]
So Publishers can change the published state of an article. The possible states include Published, Unpublished, Archived, and Trashed.

All of these groups have Inherit permission for Configure and Access Component. Remember that Author is a child of the Registered group, and Registered does not have any default permissions except for Login. Since Registered does not have permission for Configure and Access Component, and since Author's permission for these actions is "Inherited", then Author does not have these permissions either. This same permission is passed from Author to Editor and from Editor to Publisher. So, by default, none of these groups are allowed to work with articles in the back end.

It is important to remember that these permissions are only default settings for categories and articles and for any child groups that are created. So they can be overridden for child groups, for categories, and for specific articles.

Also, note that there are no Denied permissions for any actions in the default settings. This allows you to add Allowed permissions at any level. Remember, once you have an action set for Denied, this action will be denied at all lower levels in the hierarchy. For example, if you set the Admin Login for Registered to Denied (instead of Inherited), you could not grant Publishers Allowed permissions for this action.

== Article Manager & Actions Diagram ==

The diagram below shows how each action in the permissions form relates to the various options on the Article Manager screen.

[[Image:screenshot_acl_tutorial_20110111-16.png|center|]]

* '''Configure''' allows you to view and change the Options for the component.
* '''Access Component''' allows you to navigate to the Article Manager. Without this permission, no other actions are possible.
* '''Create''' allows you to add new articles.
* '''Delete''' allows you to delete trashed articles. Note that the Delete icon only shows in the toolbar when you have the "Select State" filter set to "Trash".
* '''Edit''' allows you to edit existing articles.
* '''Edit State''' allows to you Publish, Unpublish, Archive, or Trash articles.
* '''Edit Own''' is the same as Edit except that it only applies to articles written by you.

=Allowing Guest-Only Access to Menu Items and Modules=

Version 1.6 introduces the ability to create a View Access Level that is only for guests of the site (meaning a user who is not logged in). The example below shows how you can set up this new feature.

#Create a new user group called Guest. Make it a child of the Public group as shown below. [[Image:screenshot_acl_tutorial_20110112-01.png|center|frame]]
# Create a new access level called Guest and grant only the Guest group access to this level, as shown below.[[Image:screenshot_acl_tutorial_20110112-02.png|center|frame]]
# Navigate to User Manager→Options→Component and change the Guest User Group from the default value of "Public" to "Guest", as shown below.
[[Image:screenshot_acl_tutorial_20110112-04.png|center|frame]]

Now, if we assign a menu item, module, or other object to the Guest access level, only non-logged in users will have access. For example, if we create a new menu item with access level of Guest, as shown below,
[[Image:screenshot_acl_tutorial_20110112-05.png|center|frame]]
this menu item will only be visible to non-logged-in visitors to the site.

If required other user groups like Author can be granted access in the Guest access level, this would allow Authors to view articles in the front end for editing.

'''N.B. Login/logout in front end (''for changing data in session'') to see the change.'''

=Using Permission and Group Levels Together=

As discussed above, it is possible to define groups in a hierarchy, where each child group inherits action permissions (for example, the create permission) from its parent group. Action permissions are also be inherited from the permission level above. For example, a permission in the Article Manager is inherited from the same permission in the Global Configuration, and a permission in a child Category is inherited from the parent Category permission.

This dual inheritance can be confusing, but it can also be useful. Let's consider an example as follows. We have a school with a group hierarchy of Teachers → History Teachers → Assistant History Teachers. We also have a category hierarchy of Assignments → History Assignments. We want History Teachers and Assistant History Teachers to have the following permissions:

* both groups can create new articles only in the History Assignments category.

* only History Teachers (not Assistant History Teachers) can Publish or otherwise have Edit State permission.

This ACL scheme is very easy to implement. The diagram below shows how this would be set up for the Create Action.

[[Image:Acl example diagram1 20091018.png|center|]]

In the diagram, the Permission Hierarchy is shown down the left side and the Group hierarchy is shown across the top. Permissions are inherited down and to the right, as shown by the arrows. To implement the desired permissions, we leave the Global Configuration blank (Not Set) for all three groups. Similarly, in the Article Manager and Assignments Category, we leave the Create permission to Inherit for all the groups. As shown in the diagram, this means that these groups do not have Create permission for articles in general or for articles in the Assignments group.

To sum up so far, we have not set any special permissions to get to this point. Now, in the History Assignments category permissions screen, we set the Create permission to Allow for the History Teachers group. This setting overrides the Soft (Implicit) Deny that we had by default and gives members of this group permission to create content (articles and child categories) for this category. This Allow setting also is inherited by the Assistant History Teachers group.

Next, we need to grant History Teachers the Edit State permission while denying this permission to Assistant History Teachers. This is done as shown in the diagram below.

[[Image:Acl example diagram2 20091018.png|center|]]

This configuration is the same as the one above except that this time we set the Edit State permission in the History Assignments category to Deny for the Assistant History Teachers group. This means that Assistant History Teachers will not be able to Publish or Unpublish articles in this category.

Note that this was accomplished by setting just two permissions in the History Assignments category: Allow for the History Teachers group and Deny for the Assistant History Teachers group.

=ACL Action Permission Examples=
Here are some examples of how you might set up the ACL for some specific situations.

==Back-end Article Administrator==

'''Problem:'''

We want to create a group called "Article Administrator" with back-end permissions only for articles and not for any other back-end menu options. Members of this group should be able to use all of the features of the article manager, including setting article permissions.

'''Solution:'''

# Create a new group called Article Administrator and make its parent group Public, as shown below.[[Image:screenshot_acl_tutorial_20110112-10.png|center|frame]] Because its parent group is Public, it won't have any permissions by default.
# In Users → Access Levels, edit the Special Access level to add the new group. That way they can get access to the back end menu items and modules (This assumes that the modules for the admin menu and quickicons have the Special Access level assigned to them, which is the default.) [[Image:screenshot_acl_tutorial_20110112-11.png|center|frame]] By default, the back-end menu items and modules are set to Special access, so if you forget to add the new group to the Special access level, you won't see any modules or menu items when you log in as a user of the new group.
# In Site → Global Configuration → Permissions, click on the Article Administrator group and change the permissions to Allowed for the following actions: Admin Login, Create, Delete, Edit, Edit State, and Edit Own. The screen below shows what will show before you press Save. [[Image:screenshot_acl_tutorial_20110112-12.png|center|frame]]After you save, the Calculated Permissions should show as shown below.[[Image:screenshot_acl_tutorial_20110112-13.png|center|frame]]Note that the permission for the Access Component is Inherited, which translates to Not Allowed. This is important. This means that this group will only be able to access components if we give the group "Allowed" permission for Access Component. So we only have to change the one component we want to give them access to and don't have to change any settings for the components where we don't want them to have access. If we had a case where we wanted to give a group access to everything except for one component, we could set the default to Allowed and then set the one component to Denied. Also note that we did not give the group Site Login permission, so users in this group will not be able to log into the front end. (If we wanted to allow that, we would just change the permission to Allowed for Site Login.)
# In Article Manager → Options → Permissions, change permissions to Allowed for this group for the Access Component action, as shown below.[[Image:screenshot_acl_tutorial_20110112-14.png|center|frame]]All of the other desired permissions are inherited.

That's all you need to do. Members of this group can login to the back end and do everything in Article Manager but can't do anything else in the back end. For example, the screen below shows what a user in the Article Manager will see when they login to the back end.[[Image:screenshot_acl_tutorial_20110112-15.png|center|frame]]

=ACL View Access Levels Examples=

A basic concept of using Access Levels is that all items with the same Access will be viewable by the same group of users. In other words, if two items have the same Access, you can't have one viewable by one user and not viewable by another user. On the other hand, it is easy to have one Group view any number of items with different Access levels.

Similarly, each Group has exactly the same combination of Access levels, but one User can be a member of more than one group. Depending on the situation, you may want to have users only in one Group or you may need to have a User in more than one Group.

This means that we may need to group our items so that items so that all items in a group have the same level of sensitivity. Here are some examples.

==Hierarchical Example==

In this example, Access levels are hierarchical, for example, like government security clearance codes. Say for example we have the following sets of classified documents: Classified, Secret, and Top Secret. Users have corresponding clearence codes. Users with Classified clearance can only see Classified documents and cannot see Secret or Top Secret. Users with Secret clearance can see Classified and Secret documents but not Top Secret. Users with Top Secret can see all documents.

In this case, you would create three Access levels: Classified, Secret, and Top Secret and the same three Groups. Users would only be members of one group, as follows:

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| User
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Group
| style="border:0.0007in solid #000000;padding:0.0382in;"| Access Levels

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| C1, C2, C3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Classified
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Classified

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| S1, S2, S3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Secret
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Classified, Secret

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| TS1, TS2, TS3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Top Secret
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Classified, Secret, Top Secret

|}

In this case, all users are in exactly one group, but some groups have access to more than one Access Level of items. In other words, we have a one-to-one relationship between users and groups, but a one-to-many relationship between Groups and Access Levels.

==Team Security Example==

Another possible use case is a set of non-hierarchical teams. Let's say we have three teams, T1, T2, and T3. Some users are only on one team, but others might be on two or more teams. In this case, we could set up our Access Levels and Groups by team. Documents for each team have the access level for that team, and the Group for the team has only the one access level. When a User is on more than one team, they get added to the group for each team, as follows:

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| User
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Description
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Group
| style="border:0.0007in solid #000000;padding:0.0382in;"| Access Levels

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team 1 member
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team 2 member
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team 3 member
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T3

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Member of teams 1 and 2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1, T2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Member of teams 1 and 3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1, T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T3

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| U1-2-3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Member of teams 1,2, and 3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| T1,T2, T3
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| T1, T2, T3

|}

==Hybrid Example==

In a real-world situation, you might have a combination of these two arrangements. Say for example we have Managers and Staff. Staff can only see Staff documents and Managers can see Manager and Staff documents. Both types of users can be assigned to teams as well, in which case they can see all of the documents for that team. In addition, say that Managers can access some, but not all, team documents. Staff can only access team documents if they are members of that team.

In this example, we could set up the following Access Levels:

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Access Level
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Description
| style="border:0.0007in solid #000000;padding:0.0382in;"| Groups

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Manager
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Non-team manager documents
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Manager

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Staff
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Non-team staff documents
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Manager, Staff

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Sensitive Team1 documents (no access outside team)
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Team1

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team1-Manager
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team1 documents that can be accessed by all managers
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Team1, Manager

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Sensitive Team2 documents (no access outside team)
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Team2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team2-Manager
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Team2 documents that can be accessed by all managers
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Team2, Manager

|}

Then, users could be assigned to groups as follows:

{| style="border-spacing:0;"
| style="border-top:0.0007in solid #000000;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| User Type
| style="border:0.0007in solid #000000;padding:0.0382in;"| Group

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Manager on no teams
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Manager

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Staff on no teams
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Staff

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Manager on team 1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Manager, Team1

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Staff on team 1
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Staff, Team1

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Manager on teams 1 and 2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Manager, Team1, Team2

|-
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:none;padding:0.0382in;"| Staff on teams 1 and 2
| style="border-top:none;border-bottom:0.0007in solid #000000;border-left:0.0007in solid #000000;border-right:0.0007in solid #000000;padding:0.0382in;"| Staff, Team1, Team2

|}

[[Category:Joomla! 1.6]] [[Category:Joomla! 1.7]] [[Category:Joomla! 2.5]] [[Category:Tutorials]][[Category:Access Control]][[Category:Access Management]]

Security Checklist/Getting Started

2012-08-01T14:47:04Z

Oc666: /* How to read these documents */

{{RightTOC}}
== Read Me First==

=== Security matters ===

:Internet security is a fast moving challenge and ever present threat. There is no one right way to secure a website, and all security methods are subject to instant obsolescence, incremental improvement, and constant revision. All public facing websites are open to constant attack. Are you willing and able to invest the time it takes to administer a dynamic, 24x7, world-accessible, database-driven, interactive, user-authenticated website? Do you have the time and resources to respond to the constant flow of new Internet security issues? The [[Top 10 Stupidest Administrator Tricks]] is a comic/tragic look at what can go wrong. Don't learn these tricks the hard way! Depending on your own experience, reading the ''Stupidest Tricks'' will either make you laugh or cry. Luckily, there are some well-established principles upon which to base your defensive plans. The following checklists point you toward current best practices for Joomla security.

=== How to read these documents ===
#Not all techniques are appropriate for every level of experience. Apply the techniques you understand and read up on the ones you don't.
#Not all techniques are appropriate for every server. If you use a shared server, you must depend on the settings established by your hosting provider. If you are using a virtual or dedicated server, you can apply more creative security tactics.
#Not all security tactics are appropriate for all versions of Joomla. Where a technique applies to only one version it is noted by one of the following icons: {{JVer|1.0}}{{JVer|1.5}}{{JVer|1.6}}{{JVer|1.7}}{{JVer|2.5}}.

=== The most important guidelines===
:These checklists are long and growing because the full plot is thick, complex, and expanding, but don't despair! Here are a few essential guidelines for securing any website. Following them will protect you from most catastrophes.

# '''Back up early and often:''' Set up (and use and test) a regular backup and recovery process. When done well, this ensures that you can recover from almost any imaginable disaster.
# '''Update early and often:''' Promptly update to the latest ''stable'' version of Joomla! and any installed third-party extensions. This ensures that your site is protected from the newest vulnerabilities as soon as a fix is released and from the latest attack methods as soon as a defense is developed.
# '''Use a secure host''': Use a high-quality Web host. Do not be fooled by offers of 'unlimited bandwidth, unlimited hard drive space, unlimited databases, etc.
# '''Use the community''': Don't forget the truism, "If a deal is too good to be true, it is." It seems that nothing on Earth is unlimited--except perhaps the gullibility of fools and the greed of those who prey upon them. Consider hiring professional assistance if you have inadequate experience or knowledge in this area. One of the advantages of GNU software is that user support is free. Take good advantage of this by asking good questions within the [http://forum.joomla.org Joomla! Forums]. When doing so, be sure to use the the most appropriate board, such as Installation, Migration and Updating, Administration.

::The most helpful posts in the Joomla! Security Forum are converted into [[Security and Performance FAQs]]. Many of the items on this list are explained in much greater detail in the FAQs.

::You may want to read the excellent [[Beginners|Absolute Beginners Guide to Joomla!]] It has wealth of tips and tricks presented in an easy to understand format. Even experienced Joomlaists find great ideas here.

::Hunt down the many nuggets of wisdom found in the [http://forum.joomla.org Joomla! Forums], in particular the [http://forum.joomla.org/viewforum.php?f=432 Joomla! 1.5 Security Forum] and the [http://forum.joomla.org/viewforum.php?f=267 Joomla! 1.0 Security Forum].

::To receive all Joomla security announcements, subscribe to Joomla Security News. There are several ways to subscribe:

::# [http://feedburner.google.com/fb/a/mailverify?uri=JoomlaSecurityNews Automatic Email Notification]
::# [http://feeds.joomla.org/JoomlaSecurityNews RSS feed].

=== The bad news ===
#'''There is no perfect security on the Web!''' As economists would say, "There's no free lunch." Don't be fooled by Joomla's award winning ease-of-use. Maintaining a secure Web site on the open Internet is not easy. Maintaining adequate security requires a wide and ever-growing range of skills and knowledge, constant watchfulness, and a robust backup and recovery process.
#'''There's no one right way!''' Due to the variety and complexity of modern web systems, security issues can't be resolved with simple, one-size-fits-all solutions. You (or someone you trust) must learn enough about your server infrastructure to make valid security decisions. Strong security is a moving target. Today's expert might be tomorrow's victim. Welcome to the game...
#'''There's no substitute for experience!''' To secure your Web site, you must gain real experience (some of which will be bitter), or get experienced help from others. If you haven't invested the considerable time it takes to learn how to maintain a secure Web site, be sure you can consult with someone who has. Read this tongue-in-cheek description of the [[Top_10_Stupidest_Administrator_Tricks|Top 10 Stupidest Administrator Tricks]] which illustrates typical, blow-by-blow examples of how to learn Web security the hard way.

=== The good news ===

#'''Even a beginner can start at the head of the herd''' User forums for many systems are clogged with [http://www.google.com/search?q=Help!+I've+been+hacked Help! I've been hacked] posts by people who did NOT follow standard security practices. If you are studying this checklist before your site is attacked, congratulations, you're already ahead of the herd.
#'''It's not as hard as it looks''' If this is one of your first websites, security issues may seem overwhelming, but you don't have to deal with all of them at once. Start with the most critical issues. As you become more familiar with [http://www.gnu.org GNU] tools and techniques, including [http://www.gnu.org/ GNU/Linux], [http://www.apache.org Apache], [http://www.mysql.com MySQL], [http://en.wikipedia.org/wiki/SQL SQL], [http://www.php.net PHP], [http://en.wikipedia.org/wiki/HTTP HTTP], [http://en.wikipedia.org/wiki/CSS CSS], [http://en.wikipedia.org/wiki/XML XML], [http://en.wikipedia.org/wiki/RSS RSS], [http://en.wikipedia.org/wiki/TCP/IP TCP/IP], [http://en.wikipedia.org/wiki/FTP FTP], [http://subversion.tigris.org/ Subversion], [http://en.wikipedia.org/wiki/JavaScript JavaScript], and [http://www.joomla.org Joomla!], you'll add refinements to your set of security tactics.
#'''You can get help''' If you believe your website was attacked, '''do not''' simply post an announcement with full details in the Joomla! forums. If you are dealing with a new vulnerability or new form of attack, publishing that information could put other websites at risk. Instead, report possible security vulnerabilities to the [http://developer.joomla.org/security/contact-the-team.html Joomla! Security Task Force].

== Security Checklists Table of Contents==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]


[[Category:Security Checklist]]

Nginx

2012-07-12T20:42:11Z

Oc666: /* Configure Nginx */

[http://nginx.net/ nginx] is a lightweight web server that powers 8.5% of web servers across all domains[http://en.wikipedia.org/wiki/Nginx#Usage]. Unless you have specific requirements that demand a heavy web server like Apache, you are much better off using nginx.

Below are instructions on how to get Joomla! running with [http://wiki.nginx.org/PHPFcgiExample nginx and PHP via FastCGI].

== Install nginx ==
For Ubuntu, run <tt>aptitude install nginx</tt>. For other distros, run the corresponding package manager, or see http://wiki.nginx.org/Install.

== Install PHP FastCGI ==
For Ubuntu, read this excellent page on how to [http://wiki.nginx.org/PHPFcgiExample configure PHP and FastCGI for nginx].

For Gentoo, PHP will run as a FastCGI service (fpm), so the nginx server will run PHP asa different process:
<pre>
# echo "dev-lang/php gd gd2 curl simplexml tokenizer dom tidy sqlite xml fpm cgi" >> /etc/portage/package.use
# emerge php
</pre>
The default settings of php-fpm are good for most servers. For special configuration visit the [http://php.net/manual/en/install.fpm.php PHP FPM site].

== Configure Nginx ==
nginx configuration files reside in:
* <tt>/usr/local/nginx/conf/</tt> on Ubuntu
* <tt>/etc/nginx/nginx.conf</tt> on Gentoo

Here is an sample nginx configuration file joomla.conf that you can reuse over all your nginx enabled-sites

<pre>
server {
listen 80;
server_name YOUR_DOMAIN;
server_name_in_redirect off;

access_log /var/log/nginx/localhost.access_log main;
error_log /var/log/nginx/localhost.error_log info;

root PATH_ON_SERVER;
index index.php index.html index.htm default.html default.htm;
# Support Clean (aka Search Engine Friendly) URLs
location / {
try_files $uri $uri/ /index.php?q=$uri&$args;
}

# deny running scripts inside writable directories
location ~* /(images|cache|media|logs|tmp)/.*\.(php|pl|py|jsp|asp|sh|cgi)$ {
return 403;
error_page 403 /403_error.html;
}

location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include /etc/nginx/fastcgi.conf;
}

# caching of files
location ~* \.(ico|pdf|flv)$ {
expires 1y;
}

location ~* \.(js|css|png|jpg|jpeg|gif|swf|xml|txt)$ {
expires 14d;
}

}
</pre>

Pay attention for few things:
# The parameter <tt>fastcgi_pass</tt> is set to 127.0.0.1:9000, corresponding to the port that fpm is configured to listen to. This means you can run the PHP processes on separate servers. On Gentoo, you can find this configuration in <tt>/etc/php/fpm-php5.3/php-fpm.conf/</tt>
# Don't forget to replace YOUR_DOMAIN & PATH_ON_SERVER depend on your domain and the path of Joomla on your server.

== GZip support ==
If you need GZip compression support, add the following section to the http section of the main nginx configuration file:
<pre>
gzip on;
gzip_http_version 1.1;
gzip_comp_level 6;
gzip_min_length 1100;
gzip_buffers 4 8k;
gzip_types text/plain application/xhtml+xml text/css application/xml application/xml+rss text/javascript application/javascript application/x-javascr$
gzip_proxied any;
gzip_disable "MSIE [1-6]\.";
</pre>

== Sources ==
* [http://en.gentoo-wiki.com/wiki/Nginx Nginx in Gentoo]
* [http://www.kevinworthington.com/nginx-for-windows/ Nginx for Windows]
* [http://wiki.nginx.org/Install#Ubuntu_PPA Nginx in Ubuntu]
* [http://www.debianadmin.com/howto-install-nginx-webserver-in-debian.html Nginx in Debian]
* [http://www.cyberciti.biz/faq/rhel-fedora-install-configure-nginx-php5/ Nginx in RedHat/Centos]
* [http://php.net/manual/en/install.fpm.php PHP-FPM installation and configuration]
* [http://wiki.nginx.org/HttpGzipModule GZip in Nginx]
* [http://wiki.nginx.org/HttpRewriteModule Rewrite in Nginx]
* [http://nginx.org/en/docs/http/request_processing.html How nginx processes a request]

Archived:Making a Language Pack for Joomla

2012-06-23T13:37:01Z

Oc666:

This is a Tutorial explaining how to create your CORE language packs in {{JVer|1.6}}, {{JVer|1.7}} and {{JVer|2.5}}.

'''For 3pd extensions self-contained ini files installation''', see http://docs.joomla.org/Making_non-core_language_packs_in_2.5

The localise component may help you create and update the ini files: http://extensions.joomla.org/extensions/languages/language-edition/17755

fr-FR is taken as an example of language prefix.

# In the case of a '''FULL''' pack, the package is composed of 3 files, then zipped.
#* pkg_fr-FR.xml
#* site_fr-FR.zip
#* admin_fr-FR.zip
# In the case of a '''site''' or '''administrator''' only pack, 2 files.
#* pkg_site_fr-FR.xml OR pkg_admin_fr-FR.xml
#* site_fr-FR.zip OR admin_fr-FR.zip
# Naming of the pack
#* fr-FR_joomla_lang_full_1.7.0v1.zip
#* fr-FR_joomla_lang_site_1.7.0v1.zip if only site pack, fr-FR_joomla_lang_admin_1.7.0v1.zip if only administrator pack.
# If one separates the site and admin packs then the pkg_ name should be different, i.e for example: pkg_site_fr-FR.xml and pkg_admin_fr-FR.xml. In this case beware of the <packagename> tag.
# '''IMPORTANT''': Since some administrator ini files are necessary in front-end and some changes were brought in the loading of the plugin ini files, it is always necessary to include some admin part in the final pack, even for a ''''site-only'''' pack. See below http://docs.joomla.org/Making_a_Language_Pack_for_Joomla_1.6#The_Site-only_pack

Also, each pack should include a fr-FR.lib_joomla.ini and a fr-FR.localise.php to cope for deletion of site or admin pack by the user.

==A pkg_fr-FR.xml file==

<source lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
<extension type="package" version="1.7">
<name>French Language Pack</name>
<packagename>fr-FR</packagename> 
<version>1.7.x</version> 
<creationDate></creationDate> 
<author></author> 
<authorEmail></authorEmail> 
<authorUrl></authorUrl> 
<description>1.7.x Joomla French Language Package</description>
<files>
<file type="language" client="site" id="fr-FR">site_fr-FR.zip</file>
<file type="language" client="administrator" id="fr-FR">admin_fr-FR.zip</file>
</files>
<updateservers>
<server type="collection" priority="1" name="Accredited Joomla! Translations">http://update.joomla.org/language/translationlist.xml</server>
</updateservers>
</extension> </source>

==One zip per client (i.e. site and admin)==

* site_fr-FR.zip
* admin_fr-FR.zip

Content of the client's zip (example below is for admin)

===an install.xml ===

<source lang="xml"><?xml version="1.0" encoding="utf-8" ?>
<extension version="1.7" client="administrator" type="language" method="upgrade"> // change to client="site" if site pack
<name>French (Fr)</name>
<tag>fr-FR</tag>
<version>1.7</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2010 Joomla.fr et Open Source Matters. Tous droits réservés</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>French language pack for Joomla! 1.7</description>
<files>
<filename>index.html</filename>
<filename>fr-FR.com_admin.ini</filename>
<filename>fr-FR.com_admin.sys.ini</filename>
<filename> .....ini</filename>
[...]

<filename>fr-FR.lib_joomla.ini</filename> 
<filename>fr-FR.ini</filename>
<filename>fr-FR.css</filename> 
<filename file="meta">fr-FR.xml</filename> 
<filename file="meta">install.xml</filename> 
<filename>fr-FR.localise.php</filename> 
</files>
<media destination="fr-FR"> 
<filename>index.html</filename>
<filename>js/index.html</filename>
<filename>js/calendar-setup.js</filename>
<filename>js/calendar.js</filename>
</media>
</extension></source>

===All the ini files===
Beware of new formatting!

Double quotes in the value should be written as "_QQ_" or as &quot;

NEVER use an escaped quote '''\"''' as these will break in php 5.2.x

===the fr-FR.xml===

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<metafile version="1.7" client="administrator" method="upgrade" >
<tag>fr-FR</tag>
<name>French (FR)</name>
<description>French administrator language for Joomla 1.6</description>
<version>1.7</version>
<creationDate>2010-08-01</creationDate>
<author>French translation team : Joomla!fr</author>
<authorEmail>traduction@joomla.fr</authorEmail>
<authorUrl>www.joomla.fr</authorUrl>
<copyright>Copyright (C) 2005 - 2011 Open Source Matters & Joomla.fr. All rights reserved.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<metadata>
<name>French (FR)</name>
<tag>fr-FR</tag>
<rtl>0</rtl>
<locale>fr_FR.utf8, fr_FR.UTF-8, fr_FR.UTF-8@euro, French_Standard,french, fr_FR, fre_FR, fr</locale> 
<firstDay>1</firstDay> 
</metadata>
<params />
</metafile></source>

===the fr-FR.localise.php===

(This is normally in the site pack. Add in admin pack if the pack does only provide admin language. Add in both when providing a full pack to cope with user deleting one of the packs)

Explanation of this file:

It replaces the fr-FR.ignore.php and it can be customized depending on languages.

*Ignore search words.

*Define upper and lower limit of search words length.

*Define number of characters to display for the result of the search.

*Define specific plural functionality for some languages where the value of the string can change depending on the count (Russian for example).

*Define custom transliteration (i.e. when NOT using the Unicode URLS parameter in Global Configuration) to ensure proper change of some alphabets to ascii for the alias used when SEF is on. (The transliteration which is now default in 1.7 should take care of all latin-based languages.)

*Define a custom calendar by adding a function as well as some js files

'''ALWAYS SAVE THIS FILE AS UTF8 NO BOM''' if it contains non-ascii glyphs (accented letters, etc.)

Example of a basic fr-FR.localise.php (where custom transliteration is NOT implemented)
<source lang="php"><?php
/**
* @version $Id: fr-FR.localise.php 15628 2010-03-27 05:20:29Z infograf768 $
* @copyright Copyright (C) 2005 - 2010 Open Source Matters, Inc. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
*/

/**
* fr-FR localise class
*
* @package Joomla.Site
* @since 1.6
*/
abstract class fr_FRLocalise { //// !!!! NOTE the use of fr_FR for the class !!!// do the same for your language prefix.
/**
* Returns the potential suffixes for a specific number of items
*
* @param int $count The number of items.
* @return array An array of potential suffixes.
* @since 1.6
*/
public static function getPluralSuffixes($count) {
if ($count == 0) {
$return = array('0');
}
elseif($count == 1) {
$return = array('1');
}
else {
$return = array('MORE'); // Beware, this will be added to a language KEY. It should be in ascii and Uppercase.
}
return $return;
}
/**
* Returns the ignored search words
*
* @return array An array of ignored search words.
* @since 1.6
*/
public static function getIgnoredSearchWords() {
$search_ignore = array();
$search_ignore[] = "et";
$search_ignore[] = "si";
$search_ignore[] = "ou";
return $search_ignore;
}
/**
* Returns the lower length limit of search words
*
* @return integer The lower length limit of search words.
* @since 1.6
*/
public static function getLowerLimitSearchWord() {
return 3;
}
/**
* Returns the upper length limit of search words
*
* @return integer The upper length limit of search words.
* @since 1.6
*/
public static function getUpperLimitSearchWord() {
return 20;
}
/**
* Returns the number of chars to display when searching
*
* @return integer The number of chars to display when searching.
* @since 1.6
*/
public static function getSearchDisplayedCharactersNumber() {
return 200;
}
}</source>

===Example of the function to add when custom transliteration is desired===

<source lang="php">
/**
* This method processes a string and replaces all accented UTF-8 characters by unaccented
* ASCII-7 "equivalents"
*
* @param string $string The string to transliterate
* @return string The transliteration of the string
* @since 1.6
*/
public static function transliterate($string)
{
$str = JString::strtolower($string);

//Specific language transliteration.
//This one is for latin 1, latin supplement , extended A, Cyrillic, Greek

$glyph_array = array(
'a' => 'a,à,á,â,ã,ä,å,ā,ă,ą,ḁ,α,ά',
'ae' => 'æ',
'b' => 'β,б',
'c' => 'c,ç,ć,ĉ,ċ,č,ћ,ц',
'ch' => 'ч',
'd' => 'ď,đ,Ð,д,ђ,δ,ð',
'dz' => 'џ',
'e' => 'e,è,é,ê,ë,ē,ĕ,ė,ę,ě,э,ε,έ',
'f' => 'ƒ,ф',
'g' => 'ğ,ĝ,ğ,ġ,ģ,г,γ',
'h' => 'ĥ,ħ,Ħ,х',
'i' => 'i,ì,í,î,ï,ı,ĩ,ī,ĭ,į,и,й,ъ,ы,ь,η,ή',
'ij' => 'ĳ',
'j' => 'ĵ,j',
'ja' => 'я',
'ju' => 'яю',
'k' => 'ķ,ĸ,κ',
'l' => 'ĺ,ļ,ľ,ŀ,ł,л,λ',
'lj' => 'љ',
'm' => 'μ,м',
'n' => 'ñ,ņ,ň,ŉ,ŋ,н,ν',
'nj' => 'њ',
'o' => 'ò,ó,ô,õ,ø,ō,ŏ,ő,ο,ό,ω,ώ',
'oe' => 'œ,ö',
'p' => 'п,π',
'ph' => 'φ',
'ps' => 'ψ',
'r' => 'ŕ,ŗ,ř,р,ρ,σ,ς',
's' => 'ş,ś,ŝ,ş,š,с',
'ss' => 'ß,ſ',
'sh' => 'ш',
'shch' => 'щ',
't' => 'ţ,ť,ŧ,τ,т',
'th' => 'θ',
'u' => 'u,ù,ú,û,ü,ũ,ū,ŭ,ů,ű,ų,у',
'v' => 'в',
'w' => 'ŵ',
'x' => 'χ,ξ',
'y' => 'ý,þ,ÿ,ŷ',
'z' => 'ź,ż,ž,з,ж,ζ'
);

foreach( $glyph_array as $letter => $glyphs ) {
$glyphs = explode( ',', $glyphs );
$str = str_replace( $glyphs, $letter, $str );
}

return $str;
}
</source>

Here is an example of a function to add in the localise.php file in order to implement a custom calendar for fa-IR (Persian language)

<source lang="php">
/**
* fa-IR Date class
*
* @package Joomla.Site
* @since 1.6
*/
jimport('joomla.utilities.date');
class fa_IRDate extends JDate {
const DAY_NUMBER = "\x027\x03";
const DAY_NUMBER2 = "\x030\x03";
const DAY_YEAR = "\x032\x03";
const MONTH_ABBR = "\x033\x03";
const MONTH_NAME = "\x034\x03";
const MONTH_NUMBER = "\x035\x03";
const MONTH_NUMBER2 = "\x036\x03";
const MONTH_LENGTH = "\x037\x03";
const YEAR_ABBR = "\x040\x03";
const YEAR_NAME = "\x041\x03";
const AM_LOWER = "\x042\x03";
const AM_UPPER = "\x043\x03";
const PERSIAN_EPOCH = 1948320.5;

protected static $month_names = array("فروردين","ارديبهشت","خرداد","تیر","مرداد","شهریور","مهر","آبان","آذر","دی","بهمن","اسفند");

/**
* Gets the date as a formatted string.
*
* @param string The date format specification string (see {@link PHP_MANUAL#date})
* @param boolean True to return the date string in the local time zone, false to return it in GMT.
* @return string The date string in the french republican calendar (see @link{http://en.wikipedia.org/wiki/French_Republican_Calendar}).
* @since 1.6
*/
public function calendar($format, $local = false, $translate = true)
{
// Do string replacements for date format options that can be translated.
$format = preg_replace('/(^|[^\\\])d/', "\\1".self::DAY_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])j/', "\\1".self::DAY_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])z/', "\\1".self::DAY_YEAR, $format);
$format = preg_replace('/(^|[^\\\])M/', "\\1".self::MONTH_ABBR, $format);
$format = preg_replace('/(^|[^\\\])F/', "\\1".self::MONTH_NAME, $format);
$format = preg_replace('/(^|[^\\\])n/', "\\1".self::MONTH_NUMBER, $format);
$format = preg_replace('/(^|[^\\\])m/', "\\1".self::MONTH_NUMBER2, $format);
$format = preg_replace('/(^|[^\\\])t/', "\\1".self::MONTH_LENGTH, $format);
$format = preg_replace('/(^|[^\\\])y/', "\\1".self::YEAR_ABBR, $format);
$format = preg_replace('/(^|[^\\\])Y/', "\\1".self::YEAR_NAME, $format);
$format = preg_replace('/(^|[^\\\])a/', "\\1".self::AM_LOWER, $format);
$format = preg_replace('/(^|[^\\\])A/', "\\1".self::AM_UPPER, $format);

// Format the date.
$return = parent::calendar($format, $local);

$jd = gregoriantojd($this->month, $this->day, $this->year);
$jalaliDate = self::jd_to_persian($jd);
$m = $jalaliDate['mon'];
$d = $jalaliDate['day'];
$y = $jalaliDate['year'];

// Manually modify the strings in the formated time.
if (strpos($return, self::DAY_NUMBER) !== false) {
$return = str_replace(self::DAY_NUMBER, $d , $return);
}
if (strpos($return, self::DAY_NUMBER2) !== false) {
$return = str_replace(self::DAY_NUMBER2, sprintf("%02d",$d), $return);
}
if (strpos($return, self::DAY_YEAR) !== false) {
$return = str_replace(self::DAY_YEAR, $jd - self::persian_to_jd(1,1,$y)+1, $return);
}
if (strpos($return, self::MONTH_ABBR) !== false) {
$return = str_replace(self::MONTH_ABBR, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NAME) !== false) {
$return = str_replace(self::MONTH_NAME, self::$month_names[$m-1] , $return);
}
if (strpos($return, self::MONTH_NUMBER) !== false) {
$return = str_replace(self::MONTH_NUMBER, $m , $return);
}
if (strpos($return, self::MONTH_NUMBER2) !== false) {
$return = str_replace(self::MONTH_NUMBER2, sprintf("%02d", $m) , $return);
}
if (strpos($return, self::MONTH_LENGTH) !== false) {
$return = str_replace(self::MONTH_LENGTH, $m < 7 ? 31 : $m < 12 ? 30 : self::leap_persian($y) ? 30 : 29 , $return);
}
if (strpos($return, self::YEAR_ABBR) !== false) {
$return = str_replace(self::YEAR_ABBR, sprintf("%02d",$y % 100), $return);
}
if (strpos($return, self::YEAR_NAME) !== false) {
$return = str_replace(self::YEAR_NAME, $y, $return);
}
if (strpos($return, self::AM_LOWER) !== false) {
$return = str_replace(self::AM_LOWER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}
if (strpos($return, self::AM_UPPER) !== false) {
$return = str_replace(self::AM_UPPER, $this->format('a',$local)=='pm' ? 'ب ظ' : 'ق ظ', $return);
}

return $return;
}
public static function jd_to_persian($jd)

{

//var $year, $month, $day, $depoch, $cycle, $cyear, $ycycle,

// $aux1, $aux2, $yday;

$jd = floor($jd) + 0.5;

$depoch = $jd - self::persian_to_jd(1, 1, 475);

$cycle = floor($depoch / 1029983);

$cyear = $depoch % 1029983;

if ($cyear == 1029982) {

$ycycle = 2820;

} else {

$aux1 = floor($cyear / 366);

$aux2 = $cyear % 366;

$ycycle = floor(((2134 * $aux1) + (2816 * $aux2) + 2815) / 1028522) +

$aux1 + 1;

}

$year = $ycycle + (2820 * $cycle) + 474;

if ($year <= 0) {

$year--;

}

$yday = ($jd - self::persian_to_jd(1, 1, $year)) + 1;

$month = ($yday <= 186) ? ceil($yday / 31) : ceil(($yday - 6) / 30);

$day = ($jd - self::persian_to_jd($month, 1, $year)) + 1;

return array('year'=>$year, 'mon'=>$month,'day'=> $day);

}
public static function persian_to_jd($month, $day, $year)

{

//var $epbase, $epyear;

$epbase = $year - (($year >= 0) ? 474 : 473);

$epyear = 474 + $epbase % 2820;

return $day +

(($month <= 7) ?

(($month - 1) * 31) :

((($month - 1) * 30) + 6)

) +

floor((($epyear * 682) - 110) / 2816) +

($epyear - 1) * 365 +

floor($epbase / 2820) * 1029983 +

self::PERSIAN_EPOCH;

}

public static function leap_persian($year) {

return (((((($year - (($year > 0) ? 474 : 473)) % 2820) + 474) + 38) * 682) % 2816) < 682;

}

}
</source>

One has also to add the right calendar.js files in the package.

===The Site-only pack===
'''
Concerning those of you providing "site only" packs:'''

The packages have to be made on the model of http://joomlacode.org/gf/download/frsrelease/16677/72539/gd-GB_joomla_lang_full_2.5.1.zip
(Download and decompress locally to see the exact structure of the pack (install.xml, files included, etc.)

I.e. IT IS NECESSARY TO PROVIDE A LIMITED ADMIN PACK and to post a unique package including both

Why? ==> because some plugin ini files are used in front-end! Here is a typical xml for admin in this case. Example for 2.5:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<install version="2.5" client="administrator" type="language" method="upgrade">
<name>Scottish Gaelic (GB)</name>
<tag>gd-GB</tag>
<version>2.5.1</version>
<creationDate>2012-02-13</creationDate>
<author>akerbeltz</author>
<authorEmail>fios@akerbeltz.org</authorEmail>
<authorUrl>www.akerbeltz.org</authorUrl>
<copyright>Copyright (C) 2005 - 2012 Joomla Open Source Matters. Gach còir glèidhte.</copyright>
<license>GNU General Public License version 2 or later; see LICENSE.txt</license>
<description>Scottish Gaelic language pack for Joomla! 2.5</description>
<files>
<filename>index.html</filename>
<filename>gd-GB.plg_captcha_recaptcha.ini</filename>
<filename>gd-GB.plg_finder_categories.ini</filename>
<filename>gd-GB.plg_finder_contacts.ini</filename>
<filename>gd-GB.plg_finder_content.ini</filename>
<filename>gd-GB.plg_finder_newsfeeds.ini</filename>
<filename>gd-GB.plg_finder_weblinks.ini</filename>
<filename>gd-GB.plg_content_pagebreak.ini</filename>
<filename>gd-GB.plg_content_vote.ini</filename>
<filename>gd-GB.plg_editors-xtd_article.ini</filename>
<filename>gd-GB.plg_editors-xtd_image.ini</filename>
<filename>gd-GB.plg_editors-xtd_pagebreak.ini</filename>
<filename>gd-GB.plg_editors-xtd_readmore.ini</filename>
<filename>gd-GB.plg_search_categories.ini</filename>
<filename>gd-GB.plg_search_contacts.ini</filename>
<filename>gd-GB.plg_search_content.ini</filename>
<filename>gd-GB.plg_search_newsfeeds.ini</filename>
<filename>gd-GB.plg_search_weblinks.ini</filename>
<filename>gd-GB.plg_user_profile.ini</filename>
<filename file="meta">install.xml</filename>
<filename file="meta">gd-GB.xml</filename>
</files>
</install>
</source>
[[Category:Joomla! 1.6]]
[[Category:Tutorials]]
[[Category:Language Development]]

Joomla info page/he-IL

2012-05-07T14:07:34Z

Oc666: /* איפה ניתן לקבל הרחבות? */

{{RightTOC}}
= Hebrew / עברית =

== מה זה ג'ומלה? ==
ג'ומלה היא מערכת ניהול תוכן עטורת פרסים, אשר מאפשרת לך לבנות אתרי אינטרנט ויישומים מקוונים רבי עוצמה. היבטים רבים, כולל שימוש קלות ויכולת הרחבתה, הפכו את ג'ומלה לתוכנת אתרי האינטרנט הפופולרית ביותר. החשוב מכל, ג'ומלה הינו פתרון קוד פתוח והוא זמין באופן חופשי לכולם. היתרונות של ג'ומלה! כוללים:
* התקנה קלה
* אתר אינטרנט פשוט לתחזוקה
* אבטחה מעולה ויציבות
* הרחבות חינם ומסחריות רבות עוצמה
* שפע תבניות כדי לשנות בקלות את המראה של האתר שלך

== איפה ניתן להשיג ג'ומלה? ==
* הורדת ג'ומלה: http://www.joomla.org.il/download.html
* הורדת ג'ומלה חבילת שפה עבור עברית (he-IL): http://joomlacode.org/gf/project/jtranslation1_6/frs/?action=FrsReleaseBrowse&frs_package_id=5685

== איפה ניתן לקבל הרחבות? ==
* הורדת הרחבות: http://extensions.joomla.org/
* הורדת חבילות שפה עברית עבור הרחבות: http://www.joomla.org.il

== היכן להשיג תיעוד של ג'ומלה? ==
* תיעוד באנגלית: http://docs.joomla.org
* תיעוד בעברית: http://www.joomla.org.il/תיעוד.html

== איפה ניתן לקבל תמיכה עבור ג'ומלה? ==
* תמיכה חינם באנגלית: http://forum.joomla.org/
* תמיכה חינם בעברית:
** http://forum.joomla.org/viewforum.php?f=172
** http://www.joomla.org.il/פורום.html
* תמיכה מסחרית: http://resources.joomla.org/ (האתר באנגלית)

== אירועים אזוריים / Joomladays ==
[http://jday.joomla.org.il ג'ומלה דיי ישראל Joomla!Day Israel 2011]

קהילות מקומיות ברחבי העולם מארגנות ימי ג'ומלה. יום ג'ומלה הינו אירוע שנוצר באופן בלעדי עבור משתמשי ג'ומלה ופרויקטים ובדרך כלל מושך קהל אזורי. מידע נוסף: http://community.joomla.org/events/joomla-days.html

== קבוצות משתמשי ג'ומלה (JUG) ==
קבוצות משתמשי ג'ומלה מקומיות הם דרך מצוינת להכיר אנשים חדשים, לקבל עזרה עם פרויקט, או לחלוק את הידע שלכם עם משתמשי ג'ומלה אחרים. ג'ומלה נמצא בכל מקום, אז בדקו אם יש כבר קבוצה כזו באזורך. אם לא, אולי כדאי לך לשקול להקים אחד.

* JUG בישראל: http://community.joomla.org/user-groups/middle-east/israel/tel-aviv-jug.html
* JUG שאלות נפוצות: http://community.joomla.org/user-groups/jug-faq.html

== כיצד לתרום לג'ומלה? ==
* לענות על שאלות בפורום ג'ומלה http://www.joomla.org.il
* כתוב או תרגם הדרכה או תיעוד http://www.joomla.org.il/תיעוד.html (נדרש רישום)
* לפתח הרחבה או תבנית
* לבדוק או לדווח על בעיה: http://docs.joomla.org/How_do_you_report_a_bug%3F
* הצטרף לקבוצת עבודה של ג'ומלה!
* לעזור בארגון אירוע ג'ומלה!
* לתרום בדרכים אחרות http://contribute.joomla.org

GSoC 2012 - Student / Mentor Orientation

2012-05-01T14:44:40Z

Oc666: /* Webinars */

'''''This document is under massive editing!'''''

== Agenda ==
*Community Bonding Period
:Why it is key
*Overview of the summer
*Webinars
*Questions

== Introductions ==
*Who are you?
*Students: What class are you working on?
*Any immediate concerns?

== Community Bonding Period ==
You should be doing:
*Detailed Discussions with Mentor/student
*Working on Detailed Plan
*Includes Milestones, Tasks, and Dates for entire summer - Turn in by May 21st
*Writing an article about your project for the magazine
*Set up repository in github
*Set up eclipse or other IDE
*Learn PHPUnit
*Reviewing Joomla! Coding Standards
*Studying API to Present (date TBA around May 21)
*Create account @ developer.joomla.org
*Don't forget to do well on exams

== Summer Overview ==
*Coding Starts May 21st
*Turn in detailed plan by May 21st
*Weekly Checkin Form
:http://developer.joomla.org
*Midterms [ July 9th - July 13th]
*Blogging [Blog for June JCM, Due May 23rd]
:http://magazine.joomla.org
*Finals [August 20th - August 24th]

== Webinars ==
=== Confimed ===
*Phing - [http://www.timeanddate.com/worldclock/fixedtime.html?msg=Phing+webminar&iso=20120503T17 May 3rd, 17 UTC]

=== To be Confirmed ===
*DocBook & Conventions - TBD (this week)
*Contributing to FOSS - Week of May 7th
*Github, Eclipse - Week of May 7th
*Unit Testing - Week of May 14

GSoC 2012 - Student / Mentor Orientation

2012-05-01T14:41:42Z

Oc666: Created page with "'''''This document is under massive editing!''''' == Agenda == *Community Bonding Period :Why it is key *Overview of the summer *Webinars *Questions == Introductions == *Who ar..."

'''''This document is under massive editing!'''''

== Agenda ==
*Community Bonding Period
:Why it is key
*Overview of the summer
*Webinars
*Questions

== Introductions ==
*Who are you?
*Students: What class are you working on?
*Any immediate concerns?

== Community Bonding Period ==
You should be doing:
*Detailed Discussions with Mentor/student
*Working on Detailed Plan
*Includes Milestones, Tasks, and Dates for entire summer - Turn in by May 21st
*Writing an article about your project for the magazine
*Set up repository in github
*Set up eclipse or other IDE
*Learn PHPUnit
*Reviewing Joomla! Coding Standards
*Studying API to Present (date TBA around May 21)
*Create account @ developer.joomla.org
*Don't forget to do well on exams

== Summer Overview ==
*Coding Starts May 21st
*Turn in detailed plan by May 21st
*Weekly Checkin Form
:http://developer.joomla.org
*Midterms [ July 9th - July 13th]
*Blogging [Blog for June JCM, Due May 23rd]
:http://magazine.joomla.org
*Finals [August 20th - August 24th]

== Webinars ==
=== Confimed ===
*Phing - May 3rd, 17 UTC

=== To be Confirmed ===
*DocBook & Conventions - TBD (this week)
*Contributing to FOSS - Week of May 7th
*Github, Eclipse - Week of May 7th
*Unit Testing - Week of May 14

JoomlaDays/History

2012-05-01T14:31:37Z

Oc666: /* 2012 */

The Joomla! community has a long history of Joomla!Day events from around the world. Let's document these here, so we can ensure we have a historical timeline of Joomla!Days.

Instructions: please add the name, date, location, and if possible the web address, of any Joomla!Days that have happened in the past. Please use the following format: Name_of_Joomla!Day - Month DD-DD, YYYY - City, Country

== 2006 ==

(5 Events)

Joomla!Day Netherlands (1) - April 22, 2006 - Breda, Netherlands

Joomla!Day UK (1) - July 30, 2006 - Leeds, United Kingdom [http://web.archive.org/web/20060709173546/http://www.joomlatraining.org.uk/joomla-day/ programme] [http://web.archive.org/web/20060814225232/http://www.joomlatraining.org.uk/content/view/297/36/ Day 1] [http://web.archive.org/web/20060813123831/http://www.joomlatraining.org.uk/content/view/298/36/ Day 2]

Joomla!Day Sweden - October 6-7, 2006 - Västerås, Sweden

Joomla!Day Netherlands (2) - December 8-9 2006 - Den Bosch, Netherlands

Joomla!Day Germany - September 29-30, 2006 - Bonn, Germany [http://www.joomladay.de/fakten/historie/joomladay-2006.html Report in German]

== 2007 ==

(17 Events)

Joomla!Day Melbourne - January 24, 2007 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?f=306&t=116577&start=150] and [http://forum.joomla.org/viewtopic.php?t=134393]

Joomla!Day France - March 25, 2007 - Paris, France

Joomla!Day Norway - June 2, 2007 - Drammen, Norway

Joomla!Day Cape Town (South Africa) - June 16, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-june-16-2007.html programme]

Joomla!Day Johannesburg (South Africa) - July 14, 2007 [http://www.joomladay.org.za/archive/2007-johannesburg-july-14-2007.html programme]

Joomla!Day (Central) USA and Mexico - July 21, 2007 - Austin, Texas, USA

Joomla!Day Bangkok - August 4, 2008 - Bangkok , Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157601327115053/]

Joomla!Day Brasil - August 18, 2007 - São Paulo/SP, Brazil

Joomla!Day USA West - May 12-13, 2007 - Mountain View, California, USA

Joomla!Day NYC - October 13, 2007 - New York, New York, USA

Joomla!Day Hungary - October 21, 2007 - Budapest, Hungary

Joomla!Day Sweden - November 3, 2007 - Västerås, Sweden

Joomla!Day Helsinki - November 12, 2007 - Helsinki, Finland

Joomla!Day Cape Town (South Africa) - December 10, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-december-10-2007.html programme]

Joomla!Day Nigeria - date unknown

Joomla!Day Serbia - November 17, 2007 - Belgrade, Serbia

Joomla!Day New Zealand - December 15, 2007

== 2008 ==

(20 Events)

Joomla!Day Italy - January 19, 2008 - Rome, Italy

Joomla!Day Melbourne - February 2, 2008 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?p=1184586]

Joomla!Day Spain (1) - April 19, 2008 - Madrid[http://www.joomladay.info/2008/]

Joomla!Day Netherlands (3), April 4-5, 2008 - Utrecht, Netherlands

Joomla!Day Norway - April 26, 2008 - Drammen, Norway

Joomla!Day France - April 27, 2008 - Paris, France

Joomla!Day Bangkok - May 10, 2008 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157605299681211/]

Joomla!Day Byron Bay - May 11, 2008 - Byron Bay, NSW, Australia]] [http://forum.joomla.org/viewtopic.php?f=306&t=262909]

Joomla!Day Sydney - May 19, 2008 - Sydney, Australia [http://forum.joomla.org/viewtopic.php?p=1304388]

Joomla!Day Vancouver - June 14, 2008 - Vancouver, British Columbia, Canada]] [http://community.joomla.org/events/joomla-days/400-joomla-day-vancouver-2008.html]

Joomla!Day Philippines - June 14, 2008

Joomla!Day Hungary - June 20-21, 2008

Joomla!Day Durban - June 20-21, 2008 - Durban, South Africa

Joomla!Day Brasil - August 16, 2008 - São Paulo/SP, Brazil

Joomla!Day San Francisco - September 20, 2008 - San Francisco, California, USA

Joomla!Day Johannesburg - October 18, 2008 - Johannesburg, South Africa

Joomla!Day Turkey - October 25, 2008

Joomla!Day Switzerland - November 15, 2008

Joomla!Day Sweden - November 15, 2008

Joomla!Day Nigeria - November 19, 2008

== 2009 ==

(23 Events)

Joomla!Day Turkey - January 10, 2009

Joomla!Day Melbourne - February 7-8, 2009 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/641-joomladay-melbourne-2009.html]

Joomla!Day UK (2) - March 13-14, 2009 - Maidstone, England, United Kingdom

Joomla!Day Las Vegas - April 4, 2009 - Las Vegas, Nevada, USA [http://lasvegas.joomladayusa.org/]

Joomla!Day India - April 25, 2009 - Pune, India [http://community.joomla.org/blogs/community/811-joomla-day-pune-india-a-big-success.html]

Joomla!Day Sweden - May 15-16, 2009 - Stockholm, Sweden

Joomla!Day France - May 24, 2009 - Paris, France

Joomla!Day New England - May 30, 2009 - Brattleboro, Vermont, USA [http://community.joomla.org/events/joomla-days/771-joomladay-new-england-2009.html]

Joomla!Day Netherlands (4) - June 12-13, 2009 - Nieuwegein, Netherlands

Joomla!Day Cape Town - August 14, 2009 - Cape Town, South Africia

Joomla!Day Bangkok - August 22-23, 2009 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157622115004400/]

Joomla!Day Brasil - September, 12, 2009 - Rio de Janeiro/RJ, Brazil

Joomla!Day Germany - September, 24 - 26, 2009 - Bad Nauheim, Germany

Joomla!Day Mongolia - September 29-30, 2009 - Ulan Bataar, Mongolia

Joomla!Day Norway - October ?, 2009 - Drammen, Norway

Joomla!Day Gauteng - October 8-10, 2009 - Gauteng, South Africa

Joomla!Day Hungary - October 10, 2009 - Budapest, Hungary

Joomla!Day New York - October 12, 2009 - New York, New York, USA [http://community.joomla.org/events/joomla-days/912-joomla-day-new-york.html]

Joomla!Day Sydney - October 17-18, 2009 - Sydney, Australia [http://sydney.joomladay.org.au/groups/viewgroup/5-Welcome+to+Sydney+JoomlaDay+17%2B18+Oct+2009]

Joomla!Day Vietnam - November 1, 2009 - Hồ Chí Minh City, Vietnam [http://community.joomla.org/events/joomla-days/1056-joomladay-vietnam-2009.html]

Joomla!Day Italy - November 21, 2009 - Rome, Italy

Joomla!Day Spain (2) - December 11-12, 2009 - Barcelona, Spain [http://www.joomladay.info/2009/]

Joomla!Day Nigeria - December 12, 2009 - Lagos, Nigeria

== 2010 ==

(17 Events)

Joomla!Day Melbourne - February 12-14, 2010 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/1102-joomladay-melbourne-2010.html]

Joomla!Day France - March 21, 2010 - Bordeaux, France

Joomla!Day Spain (3) - April 9-10, 2010 - Mallorca, Spain [http://www.joomladay.cat/]

Joomla!Day Netherlands (5) - April 23-24, 2010 - Utrecht, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Sweden - April 23-24, 2010 - Stockholm, Sweden [http://www.joomladay.se/]

Joomla!Day Norway - June 4-5, 2010 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day New England - June 5, 2010 - Marlboro, Vermont, USA

Joomla!Day Brisbane - June 18-19, 2010 - Brisbane, Australia

Joomla!Day Brasil - September 11-12, 2010 - Brasília/DF, Brazil [http://www.joomladaybrasil.org/2010]

Joomla!Day USA West - October 1-3, 2010 - San Jose, California, USA [http://www.joomladaywest.com/]

Joomla!Day Italy - October 9, 2010 - Verona, Italy

Joomla!Day DC - October 16, 2010 - Chevy Chase, Maryland, USA [http://www.joomladaydc.com]

Joomla!Day Denmark - October 29-30, 2010 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day UK (3) - October 30-31, 2010 - Ipswich, England, United Kingdom

Joomla!Day Bangkok - November 13-14, 2010 - Bangkok, Thailand [http://www.joomladay.in.th/]

Joomla!Day Spain (4) - November 26-27, 2010 - Valencia, Spain [http://www.joomladay2010.es/]

Joomla!Day NYC - December 4-5, 2010 - New York City, New York, USA

Joomla!Day Nigeria - December 11, 2010 - Lagos, Nigeria

== 2011 ==

(29 Events)

Joomla!Day Chile - January 18, 2011 - Santiago, Chile [http://www.joomladay-chile.cl/]

Joomla!Night Stockholm - February 4, 2011 - Stockholm, Sweden

Joomla!Day India - March 12-13, 2011 - Pune, Maharashtra, India [http://www.joomladay.co.in]

Joomla!Day Netherlands (6) - April 2-3, 2011 - Doorn, Netherlands [http://www.joomladagen.nl/]

Joomla!Day New England - April 2, 2011 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org]
[[Media:JoomlaDayNEProgram2011-schedule.jpg]]
[[Media:JoomlaDayNEProgram2011-speakers.jpg]]

Joomla!Day France - April 2-3, 2011 - Lyon, France [http://www.joomladay.fr/]

Joomla!Day Algeria - April 19 2011 - Alger, Algeria [http://www.joomladayalgerie.com/]

Joomla!Day Greece - May 28-29, 2011 - Athens, Greece [http://joomladay.gr/]

Joomla!Day Malaysia - June 25, 2011 - Kuala Lumpur, Malaysia [http://www.joomla-day.org.my/2011/]

Joomla!Night Chile - July 6, 2011 - Santiago, Chile [http://joomlanight-chile.cl/]

Joomla!Day Chicago - August 5-6, 2011 - Chicago, Illinois, USA [http://www.joomladaychicago.com]

Joomla!Day Norway - August 12-13, 2011 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day Bosnia and Herzegovina - August 12-14, 2011 - Tesanj, Bosnia [http://www.joomla.ba/konferencija]

Joomla!Day Cape Town - August 19-20, 2011 - Cape Town, South Africa [http://www.joomladay.org.za/] [http://www.joomladay.org.za/talks-sessions/programme.html programme]

Joomla!Day Germany - September 2-3, 2011 - Hamburg, Germany [http://www.joomladay.de]

Joomla!Day Brasil - September 2-4, 2011 - Florianópolis/SC, Brazil [http://www.joomladaybrasil.org/2011]

Joomla!Day Austin - September 15, 2011 - Austin, Texas, USA [http://www.joomladayaustin.com]

Joomla!Day UK - September 24-25, 2011 - London, England [http://www.joomladayuk2011.org]

Joomla!Day Israel - October 10, 2011 - Tel Aviv, Israel [http://jday11.joomla.org.il]

Joomla!Day Italy - October 22, 2011 - Florence, Italy [http://www.joomladay.it]

Joomla!Day NYC - October 22-23, 2011 - New York City, New York, USA [http://www.joomladaynyc.com]

Joomla!Day Denmark - October 28-29, 2011 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day Australia - November 5-6, 2011 - Sydney, Australia [http://sydney.joomladay.org.au/]

Joomla!Day Finland - November 5, 2011 - Helsinki, Finland [http://joomladayfinland.com/]

Joomla!Day Spain - November 9-10, 2011 - Zaragoza, Spain [http://www.joomladay2011.es/]

Joomla!Day Midwest - November 12, 2011 - Milwaukee, Wisconsin, USA [http://www.joomladaymidwest.org]

Joomla!Day Algeria - November 19, 2011 - Oran, Algeria [http://www.joomladayoran.com/]

Joomla!Day Los Angeles - December 3, 2011 - Los Angeles, California, USA [http://www.jdayla.com]

Joomla!Day Lagos - December 17, 2011 - Lagos, Nigeria [http://joomlang.com/]

== 2012 ==

Joomla!Day Bangkok - February 25, 2012 - Bangkok, Thailand [http://www.joomladay.in.th]

Joomla!Day Guatemala - February 29 - March 3, 2012 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2012/]

Joomla!Day France - March 24, 2012 - Strasbourg, France [http://www.joomladay.fr/]

Joomla!Day New England - March 31, 2012 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Joomla!Day Iran - April 12, 2012 - Mashhad, Iran [http://www.joomladay.ir]

Joomla!Day Netherlands (7) - April 21-22, 2012 - Zeist, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Ribeirão Preto - May 11-12, 2012 - Ribeirão Preto, Brasil [http://jdrp.unaerp.br/]

Joomla!Day Togo - June 14, 2012 - Assahoun, Togo

Joomla!Day Mexico - June 22-23, 2012 - Mexico City, Mexico [http://www.joomladaymexico.org/]

Joomla!Day Brasil - September 07-08, 2012 - Belo Horizonte, Minas Gerais, Brasil [http://www.joomladaybrasil.org/]

Joomla!Day Poland - September 22-23, 2012 - Poznań, Poland [http://www.joomla-day.pl/]

Joomla!Day Germany - October 05-06, 2012 - Berlin, Germany [http://www.joomladay.de/]

Joomla!Day Israel - October 10, 2012- Tel Aviv, Israel [http://jday.joomla.org.il]

Joomla!Day West - TBA - San Jose, California, USA [http://www.joomladaywest.com]

JoomlaDays/History

2012-04-27T19:51:39Z

Oc666:

The Joomla! community has a long history of Joomla!Day events from around the world. Let's document these here, so we can ensure we have a historical timeline of Joomla!Days.

Instructions: please add the name, date, location, and if possible the web address, of any Joomla!Days that have happened in the past. Please use the following format: Name_of_Joomla!Day - Month DD-DD, YYYY - City, Country

== 2006 ==

(5 Events)

Joomla!Day Netherlands (1) - April 22, 2006 - Breda, Netherlands

Joomla!Day UK (1) - July 30, 2006 - Leeds, United Kingdom [http://web.archive.org/web/20060709173546/http://www.joomlatraining.org.uk/joomla-day/ programme] [http://web.archive.org/web/20060814225232/http://www.joomlatraining.org.uk/content/view/297/36/ Day 1] [http://web.archive.org/web/20060813123831/http://www.joomlatraining.org.uk/content/view/298/36/ Day 2]

Joomla!Day Sweden - October 6-7, 2006 - Västerås, Sweden

Joomla!Day Netherlands (2) - December 8-9 2006 - Den Bosch, Netherlands

Joomla!Day Germany - September 29-30, 2006 - Bonn, Germany [http://www.joomladay.de/fakten/historie/joomladay-2006.html Report in German]

== 2007 ==

(17 Events)

Joomla!Day Melbourne - January 24, 2007 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?f=306&t=116577&start=150] and [http://forum.joomla.org/viewtopic.php?t=134393]

Joomla!Day France - March 25, 2007 - Paris, France

Joomla!Day Norway - June 2, 2007 - Drammen, Norway

Joomla!Day Cape Town (South Africa) - June 16, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-june-16-2007.html programme]

Joomla!Day Johannesburg (South Africa) - July 14, 2007 [http://www.joomladay.org.za/archive/2007-johannesburg-july-14-2007.html programme]

Joomla!Day (Central) USA and Mexico - July 21, 2007 - Austin, Texas, USA

Joomla!Day Bangkok - August 4, 2008 - Bangkok , Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157601327115053/]

Joomla!Day Brasil - August 18, 2007 - São Paulo/SP, Brazil

Joomla!Day USA West - May 12-13, 2007 - Mountain View, California, USA

Joomla!Day NYC - October 13, 2007 - New York, New York, USA

Joomla!Day Hungary - October 21, 2007 - Budapest, Hungary

Joomla!Day Sweden - November 3, 2007 - Västerås, Sweden

Joomla!Day Helsinki - November 12, 2007 - Helsinki, Finland

Joomla!Day Cape Town (South Africa) - December 10, 2007 [http://www.joomladay.org.za/archive/2007-cape-town-december-10-2007.html programme]

Joomla!Day Nigeria - date unknown

Joomla!Day Serbia - November 17, 2007 - Belgrade, Serbia

Joomla!Day New Zealand - December 15, 2007

== 2008 ==

(20 Events)

Joomla!Day Italy - January 19, 2008 - Rome, Italy

Joomla!Day Melbourne - February 2, 2008 - Melbourne, Australia [http://forum.joomla.org/viewtopic.php?p=1184586]

Joomla!Day Spain (1) - April 19, 2008 - Madrid[http://www.joomladay.info/2008/]

Joomla!Day Netherlands (3), April 4-5, 2008 - Utrecht, Netherlands

Joomla!Day Norway - April 26, 2008 - Drammen, Norway

Joomla!Day France - April 27, 2008 - Paris, France

Joomla!Day Bangkok - May 10, 2008 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157605299681211/]

Joomla!Day Byron Bay - May 11, 2008 - Byron Bay, NSW, Australia]] [http://forum.joomla.org/viewtopic.php?f=306&t=262909]

Joomla!Day Sydney - May 19, 2008 - Sydney, Australia [http://forum.joomla.org/viewtopic.php?p=1304388]

Joomla!Day Vancouver - June 14, 2008 - Vancouver, British Columbia, Canada]] [http://community.joomla.org/events/joomla-days/400-joomla-day-vancouver-2008.html]

Joomla!Day Philippines - June 14, 2008

Joomla!Day Hungary - June 20-21, 2008

Joomla!Day Durban - June 20-21, 2008 - Durban, South Africa

Joomla!Day Brasil - August 16, 2008 - São Paulo/SP, Brazil

Joomla!Day San Francisco - September 20, 2008 - San Francisco, California, USA

Joomla!Day Johannesburg - October 18, 2008 - Johannesburg, South Africa

Joomla!Day Turkey - October 25, 2008

Joomla!Day Switzerland - November 15, 2008

Joomla!Day Sweden - November 15, 2008

Joomla!Day Nigeria - November 19, 2008

== 2009 ==

(23 Events)

Joomla!Day Turkey - January 10, 2009

Joomla!Day Melbourne - February 7-8, 2009 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/641-joomladay-melbourne-2009.html]

Joomla!Day UK (2) - March 13-14, 2009 - Maidstone, England, United Kingdom

Joomla!Day Las Vegas - April 4, 2009 - Las Vegas, Nevada, USA [http://lasvegas.joomladayusa.org/]

Joomla!Day India - April 25, 2009 - Pune, India [http://community.joomla.org/blogs/community/811-joomla-day-pune-india-a-big-success.html]

Joomla!Day Sweden - May 15-16, 2009 - Stockholm, Sweden

Joomla!Day France - May 24, 2009 - Paris, France

Joomla!Day New England - May 30, 2009 - Brattleboro, Vermont, USA [http://community.joomla.org/events/joomla-days/771-joomladay-new-england-2009.html]

Joomla!Day Netherlands (4) - June 12-13, 2009 - Nieuwegein, Netherlands

Joomla!Day Cape Town - August 14, 2009 - Cape Town, South Africia

Joomla!Day Bangkok - August 22-23, 2009 - Bangkok, Thailand [http://www.flickr.com/photos/laithaiphoto/sets/72157622115004400/]

Joomla!Day Brasil - September, 12, 2009 - Rio de Janeiro/RJ, Brazil

Joomla!Day Germany - September, 24 - 26, 2009 - Bad Nauheim, Germany

Joomla!Day Mongolia - September 29-30, 2009 - Ulan Bataar, Mongolia

Joomla!Day Norway - October ?, 2009 - Drammen, Norway

Joomla!Day Gauteng - October 8-10, 2009 - Gauteng, South Africa

Joomla!Day Hungary - October 10, 2009 - Budapest, Hungary

Joomla!Day New York - October 12, 2009 - New York, New York, USA [http://community.joomla.org/events/joomla-days/912-joomla-day-new-york.html]

Joomla!Day Sydney - October 17-18, 2009 - Sydney, Australia [http://sydney.joomladay.org.au/groups/viewgroup/5-Welcome+to+Sydney+JoomlaDay+17%2B18+Oct+2009]

Joomla!Day Vietnam - November 1, 2009 - Hồ Chí Minh City, Vietnam [http://community.joomla.org/events/joomla-days/1056-joomladay-vietnam-2009.html]

Joomla!Day Italy - November 21, 2009 - Rome, Italy

Joomla!Day Spain (2) - December 11-12, 2009 - Barcelona, Spain [http://www.joomladay.info/2009/]

Joomla!Day Nigeria - December 12, 2009 - Lagos, Nigeria

== 2010 ==

(17 Events)

Joomla!Day Melbourne - February 12-14, 2010 - Melbourne, Australia [http://community.joomla.org/events/joomla-days/1102-joomladay-melbourne-2010.html]

Joomla!Day France - March 21, 2010 - Bordeaux, France

Joomla!Day Spain (3) - April 9-10, 2010 - Mallorca, Spain [http://www.joomladay.cat/]

Joomla!Day Netherlands (5) - April 23-24, 2010 - Utrecht, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Sweden - April 23-24, 2010 - Stockholm, Sweden [http://www.joomladay.se/]

Joomla!Day Norway - June 4-5, 2010 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day New England - June 5, 2010 - Marlboro, Vermont, USA

Joomla!Day Brisbane - June 18-19, 2010 - Brisbane, Australia

Joomla!Day Brasil - September 11-12, 2010 - Brasília/DF, Brazil [http://www.joomladaybrasil.org/2010]

Joomla!Day USA West - October 1-3, 2010 - San Jose, California, USA [http://www.joomladaywest.com/]

Joomla!Day Italy - October 9, 2010 - Verona, Italy

Joomla!Day DC - October 16, 2010 - Chevy Chase, Maryland, USA [http://www.joomladaydc.com]

Joomla!Day Denmark - October 29-30, 2010 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day UK (3) - October 30-31, 2010 - Ipswich, England, United Kingdom

Joomla!Day Bangkok - November 13-14, 2010 - Bangkok, Thailand [http://www.joomladay.in.th/]

Joomla!Day Spain (4) - November 26-27, 2010 - Valencia, Spain [http://www.joomladay2010.es/]

Joomla!Day NYC - December 4-5, 2010 - New York City, New York, USA

Joomla!Day Nigeria - December 11, 2010 - Lagos, Nigeria

== 2011 ==

(29 Events)

Joomla!Day Chile - January 18, 2011 - Santiago, Chile [http://www.joomladay-chile.cl/]

Joomla!Night Stockholm - February 4, 2011 - Stockholm, Sweden

Joomla!Day India - March 12-13, 2011 - Pune, Maharashtra, India [http://www.joomladay.co.in]

Joomla!Day Netherlands (6) - April 2-3, 2011 - Doorn, Netherlands [http://www.joomladagen.nl/]

Joomla!Day New England - April 2, 2011 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org]
[[Media:JoomlaDayNEProgram2011-schedule.jpg]]
[[Media:JoomlaDayNEProgram2011-speakers.jpg]]

Joomla!Day France - April 2-3, 2011 - Lyon, France [http://www.joomladay.fr/]

Joomla!Day Algeria - April 19 2011 - Alger, Algeria [http://www.joomladayalgerie.com/]

Joomla!Day Greece - May 28-29, 2011 - Athens, Greece [http://joomladay.gr/]

Joomla!Day Malaysia - June 25, 2011 - Kuala Lumpur, Malaysia [http://www.joomla-day.org.my/2011/]

Joomla!Night Chile - July 6, 2011 - Santiago, Chile [http://joomlanight-chile.cl/]

Joomla!Day Chicago - August 5-6, 2011 - Chicago, Illinois, USA [http://www.joomladaychicago.com]

Joomla!Day Norway - August 12-13, 2011 - Drammen, Norway [http://www.joomladay.no/]

Joomla!Day Bosnia and Herzegovina - August 12-14, 2011 - Tesanj, Bosnia [http://www.joomla.ba/konferencija]

Joomla!Day Cape Town - August 19-20, 2011 - Cape Town, South Africa [http://www.joomladay.org.za/] [http://www.joomladay.org.za/talks-sessions/programme.html programme]

Joomla!Day Germany - September 2-3, 2011 - Hamburg, Germany [http://www.joomladay.de]

Joomla!Day Brasil - September 2-4, 2011 - Florianópolis/SC, Brazil [http://www.joomladaybrasil.org/2011]

Joomla!Day Austin - September 15, 2011 - Austin, Texas, USA [http://www.joomladayaustin.com]

Joomla!Day UK - September 24-25, 2011 - London, England [http://www.joomladayuk2011.org]

Joomla!Day Israel - October 10, 2011 - Tel Aviv, Israel [http://jday11.joomla.org.il]

Joomla!Day Italy - October 22, 2011 - Florence, Italy [http://www.joomladay.it]

Joomla!Day NYC - October 22-23, 2011 - New York City, New York, USA [http://www.joomladaynyc.com]

Joomla!Day Denmark - October 28-29, 2011 - Kolding, Denmark [http://www.joomladay.dk]

Joomla!Day Australia - November 5-6, 2011 - Sydney, Australia [http://sydney.joomladay.org.au/]

Joomla!Day Finland - November 5, 2011 - Helsinki, Finland [http://joomladayfinland.com/]

Joomla!Day Spain - November 9-10, 2011 - Zaragoza, Spain [http://www.joomladay2011.es/]

Joomla!Day Midwest - November 12, 2011 - Milwaukee, Wisconsin, USA [http://www.joomladaymidwest.org]

Joomla!Day Algeria - November 19, 2011 - Oran, Algeria [http://www.joomladayoran.com/]

Joomla!Day Los Angeles - December 3, 2011 - Los Angeles, California, USA [http://www.jdayla.com]

Joomla!Day Lagos - December 17, 2011 - Lagos, Nigeria [http://joomlang.com/]

== 2012 ==

Joomla!Day Bangkok - February 25, 2012 - Bangkok, Thailand [http://www.joomladay.in.th]

Joomla!Day Guatemala - February 29 - March 3, 2012 - Guatemala City, Guatemala [http://www.joomlagt.org/joomladay2012/]

Joomla!Day France - March 24, 2012 - Strasbourg, France [http://www.joomladay.fr/]

Joomla!Day New England - March 31, 2012 - Brattleboro, Vermont, USA [http://www.joomladaynewengland.org/]

Joomla!Day Iran - April 12, 2012 - Mashhad, Iran [http://www.joomladay.ir]

Joomla!Day Netherlands (7) - April 21-22, 2012 - Zeist, Netherlands [http://www.joomladagen.nl/]

Joomla!Day Ribeirão Preto - May 11-12, 2012 - Ribeirão Preto, Brasil [http://jdrp.unaerp.br/]

Joomla!Day Togo - June 14, 2012 - Assahoun, Togo

Joomla!Day Mexico - June 22-23, 2012 - Mexico City, Mexico [http://www.joomladaymexico.org/]

Joomla!Day Brasil - September 07-08, 2012 - Belo Horizonte, Minas Gerais, Brasil [http://www.joomladaybrasil.org/]

Joomla!Day Poland - September 22-23, 2012 - Poznań, Poland [http://www.joomla-day.pl/]

Joomla!Day Germany - October 05-06, 2012 - Berlin, Germany [http://www.joomladay.de/]

Joomla!Day Israel - October 10, 2011 - Tel Aviv, Israel [http://jday.joomla.org.il]

Joomla!Day West - TBA - San Jose, California, USA [http://www.joomladaywest.com]

J1.5:Developing a MVC Component/Introduction

2012-03-26T01:48:29Z

Oc666:

{{Template:Warning|This guide is for Joomla! {{JVer|1.5}} version. If you are working with Joomla! {{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}, please redirect to [[Developing a Model-View-Controller (MVC) Component for Joomla!2.5|this guide]]}}
== Introduction ==
A software framework is the base of an application that can be used by a developer. The framework in Joomla! 1.5 unleashes a great deal of power for them. The Joomla! code has been designed for extensibility. This tutorial will guide you through the process of developing a component using the framework.

The scope of this project will be to develop a simple Hello World! component. In future tutorials, this simple framework will be built upon to show the full power and versatility of the MVC design pattern in Joomla!

== Requirements ==
You need Joomla! 1.5 or greater for this tutorial.

== Introduction to Model-View-Controller ==
[[image:MVC basics.png|frameless|right]]While the idea behind a component may seem extremely simple, code can quickly become very complex as additional features are added or the interface is customized.

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

These three main roles are the basis for the Joomla MVC. They are described here in brief, but for a more thorough explanation, please refer to the links provided at the end of this tutorial.

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

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

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

=== MVC connection ===
[[image:MVC joomla.png|frameless|right]]The simplified picture on the right depicts the basic components being used within Joomla. Besides the Model, the View and the Controller, an Entry Point has been added that is depicted as a small circle. Attached to the viewer (view) a Template has been added. With these five components you should be able to understand this tutorial about making a basic Joomla! MVC component.

Part 1 of the tutorial only focuses on the Controller and the View (with the use of the Template); these are marked with the blue colour in the picture. Part 2 adds and Part 3 extends the model functionality for the data manipulation abstraction; marked with the green colour in the picture.

Keep in mind that this simplified picture only applies for the site section (i.e the front-end). An identical picture is applicable for the admin section (i.e. the back-end). The administrative section is taken care of in Parts 4 through 6 of this component development tutorial. Both the site and the admin section are maintained and configured in an XML based installation file (typically termed a manifest file).

== Joomla! MVC Implementation ==
In Joomla!, the MVC pattern is implemented using three classes: [http://api.joomla.org/Joomla-Framework/Application/JModel.html JModel], [http://api.joomla.org/Joomla-Framework/Application/JView.html JView] and [http://api.joomla.org/Joomla-Framework/Application/JController.html JController]. For more detailed information about these classes, please refer to the API reference documentation (WIP).

For learning purposes and debugging, adding a run-time debugger to your Joomla! site might be a good extension especially during development of your (tutorial) component. A good example is the community project [http://extensions.joomla.org/extensions/miscellaneous/development/1509/details J!Dump] that has the advantage of being a pop-up which leaves the view output unchanged. The J!Dump system allows you to view not only your development properties but also the methods.

== Creating a Component ==
For our basic component, we only require five files:

* site/hello.php - this is the entry point to our component
* site/controller.php - this file contains our base controller
* site/views/hello/view.html.php - this file retrieves the necessary data and pushes it into the template
* site/views/hello/tmpl/default.php - this is the template for our output
* hello.xml - this is an XML (manifest) file that tells Joomla! how to install our component.

Remember that the filename for the entry point must have the same name of the component. For example, if you call your component "Very Intricate Name Component", at install time (see below in the hello.xml section) Joomla! will create the folder com_veryintricatenamecomponent and the entry point php file must be named veryintricatenamecomponent.php otherwise it will not work. Be aware that use of some special characters, notibly the underscore '_', may have special meaning in Joomla and should be avoided in component names or files.

The site directory here is for the parts of the component which are installed in the front end site.

=== Naming conventions ===

Main article: [[Naming conventions]]

At this point it is important to say that some words are reserved for using in component or its class names, and violating some of that will produce a hard for debugging error. One of them is "view" (in any character case) for view class (subclass of JView) and controller class (subclass of JController), because view class need to have first part of name the same as controller class name, and component name (although violating of last one won't produce an error, it's just a useful convention).

All filenames and foldernames for models, views and controllers must be lower-case in order to operate well on Unix/Linux-systems.

=== Creating the Entry Point ===
{{review}}
Joomla! is always accessed through a single point of entry: index.php for the Site Application or administrator/index.php for the Administrator Application. The application will then load the required component, based on the value of 'option' in the URL or in the POST data. For our component, the URL would be:

<source lang="php">index.php?option=com_hello&view=hello</source>

This will load our main file, which can be seen as the single point of entry for our component: components/com_hello/hello.php.

The code for this file is fairly typical across components.

site/hello.php:
<source lang="php"><?php
/**
* @package Joomla.Tutorials
* @subpackage Components
* components/com_hello/hello.php
* @link http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1
* @license GNU/GPL
*/

// No direct access
defined( '_JEXEC' ) or die( 'Restricted access' );

// Require the base controller

require_once( JPATH_COMPONENT.DS.'controller.php' );

// Require specific controller if requested
if($controller = JRequest::getWord('controller')) {
$path = JPATH_COMPONENT.DS.'controllers'.DS.$controller.'.php';
if (file_exists($path)) {
require_once $path;
} else {
$controller = '';
}
}

// Create the controller
$classname = 'HelloController'.$controller;
$controller = new $classname( );

// Perform the Request task
$controller->execute( JRequest::getWord( 'task' ) );

// Redirect if set by the controller
$controller->redirect();</source>

The first statement is a security check.

JPATH_COMPONENT is the absolute path to the current component, in our case components/com_hello. If you specifically need either the Site component or the Administrator component, you can use JPATH_COMPONENT_SITE or JPATH_COMPONENT_ADMINISTRATOR.

DS is the directory separator of your system: either '/' or '\'. This is automatically set by the framework so the developer doesn't have to worry about developing different versions for different server OSs. The 'DS' constant should always be used when referring to files on the local server.

After loading the base controller, we check if a specific controller is needed. In this component, the base controller is the only controller, but we will leave this conditional check "in place" for future use.

JRequest::getWord() finds a word variable in the URL or the POST data. So if our URL is index.php?option=com_hello&controller=controller_name, then we can retrieve our controller name in our component using: echo JRequest::getWord('controller');

Now we have our base controller 'HelloController' in com_hello/controller.php, and, if needed, additional controllers like 'HelloControllerController1' in com_hello/controllers/controller1.php. Using this standard naming scheme will make things easy later on: '{Componentname}{Controller}{Controllername}'

After the controller is created, we instruct the controller to execute the task, as defined in the URL: index.php?option=com_hello&task=sometask. If no task is set, the default task 'display' will be assumed. When display is used, the 'view' variable will decide what will be displayed. Other common tasks are save, edit, new...

The controller might decide to redirect the page, usually after a task like 'save' has been completed. This last statement takes care of the actual redirection.

The main entry point (hello.php) essentially passes control to the controller, which handles performing the task that was specified in the request.

Note that we don't use a closing php tag in this file: ?>. The reason for this is that we will not have any unwanted whitespace in the output code. This is default practice since Joomla! 1.5, and will be used for all php-only files.

=== Creating the Controller ===
Our component only has one task - greet the world. Therefore, the controller will be very simple. No data manipulation is required. All that needs to be done is the appropriate view loaded. We will have only one method in our controller: display(). Most of the required functionality is built into the JController class, so all that we need to do is invoke the JController::display() method.

The code for the base controller site/controller.php is:
<source lang="php"><?php
/**
* @package Joomla.Tutorials
* @subpackage Components
* @link http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1
* @license GNU/GPL
*/

// No direct access

defined( '_JEXEC' ) or die( 'Restricted access' );

jimport('joomla.application.component.controller');

/**
* Hello World Component Controller
*
* @package Joomla.Tutorials
* @subpackage Components
*/
class HelloController extends JController
{
/**
* Method to display the view
*
* @access public
*/
function display()
{
parent::display();
}

}</source>

The JController constructor will always register a display() task and unless otherwise specified (using the registerDefaultTask() method), it will set it as the default task.

This barebones display() method isn't really even necessary since all it does is invoke the parent constructor. However, it is a good visual clue to indicate what is happening in the controller.

The JController::display() method will determine the name of the view and layout from the request and load that view and set the layout. When you create a menu item for your component, the menu manager will allow the administrator to select the view that they would like the menu link to display and to specify the layout. A view usually refers to a view of a certain set of data (i.e. a list of cars, a list of events, a single car, a single event). A layout is a way that that view is organized.

In our component, we will have a single view called hello, and a single layout (default).

=== Creating the View ===
The task of the view is very simple: It retrieves the data to be displayed and pushes it into the template. Data is pushed into the template using the JView::assignRef method.
<small>(Note: The key (the first argument) passed to the assignRef method cannot be preceded by an underscore i.e. $this->assignRef('_greeting',$greeting). Doing so will cause the assignRef method to return false and your variable will not be pushed into the template.)</small>

The code for the view at site/views/hello/view.html.php:

<source lang="php"><?php
/**
* @package Joomla.Tutorials
* @subpackage Components
* @link http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1
* @license GNU/GPL
*/

// no direct access

defined( '_JEXEC' ) or die( 'Restricted access' );

jimport( 'joomla.application.component.view');

/**
* HTML View class for the HelloWorld Component
*
* @package HelloWorld
*/

class HelloViewHello extends JView
{
function display($tpl = null)
{
$greeting = "Hello World!";
$this->assignRef( 'greeting', $greeting );

parent::display($tpl);
}
}</source>

==== Creating the Template ====

Joomla! templates/layouts are regular PHP files that are used to layout the data from the view in a particular manner. The variables assigned by the JView::assignRef method can be accessed from the template using $this->{propertyname} (see the template code below for an example).

Our template is very simple: we only want to display the greeting that was passed in from the view - this file is:<br>site/views/hello/tmpl/default.php:

<source lang="php"><?php

// No direct access

defined('_JEXEC') or die('Restricted access'); ?>
<h1><?php echo $this->greeting; ?></h1></source>

=== Wrapping It All Up - Creating the hello.xml File ===
It is possible to install a component manually by copying the files using an FTP client and modifying the database tables. It is more efficient to create a package file that will allow the Joomla! Installer to do this for you. This package file contains a variety of information:

* basic descriptive details about your component (i.e. name), and optionally, a description, copyright and license information.
* a list of files that need to be copied.
* optionally, a PHP file that performs additional install and uninstall operations.
* optionally, an SQL file which contains database queries that should be executed upon install/uninstall

The format of the XML file at hello.xml is as follows:

<source lang="xml"><?xml version="1.0" encoding="utf-8"?>
<install type="component" version="1.5.0">
<name>Hello</name>

<creationDate>2007-02-22</creationDate>
<author>John Doe</author>
<authorEmail>john.doe@example.org</authorEmail>
<authorUrl>http://www.example.org</authorUrl>
<copyright>Copyright Info</copyright>
<license>License Info</license>

<version>1.01</version>

<description>Description of the component ...</description>



<files folder="site">
<filename>controller.php</filename>
<filename>hello.php</filename>
<filename>index.html</filename>
<filename>views/index.html</filename>
<filename>views/hello/index.html</filename>
<filename>views/hello/view.html.php</filename>
<filename>views/hello/tmpl/default.php</filename>
<filename>views/hello/tmpl/index.html</filename>
</files>

<administration>

<menu>Hello World!</menu>


<files folder="admin">
<filename>hello.php</filename>
<filename>index.html</filename>
</files>

</administration>
</install></source>

{{notice|
Put this xml file, also called manifest, in the root of your package (because the installer will take its path as the root path for all other files).{{1}}Don't include itself under <files>...}}

You may have noticed the manifest source above mentioned files we have not discussed. These are the index.html files and the admin files. An index.html file is placed in each directory to prevent prying users from getting a directory listing. If there is no index.html file, some web servers will list the directory contents. This is often undesirable. These files have the simple line:

<source lang="php"><html><body bgcolor="#FFFFFF"></body></html></source>

It will simply display a blank page.

The hello.php file in the admin folder is the entry point for the our component's admin section. Since our component has no administrator needs (yet), this file will have the same content as the index.html files for now.

If you've followed along, you can visit URL index.php?option=com_hello to see your work. To do this, zip up the main folder and install via the extensions manager. If it still does not work, download the package at the bottom of this page and install for a working example.

== Articles in this Series ==
[[Developing a Model-View-Controller Component - Part 1]]

[[Developing a Model-View-Controller Component - Part 2 - Adding a Model]]

[[Developing a Model-View-Controller Component - Part 3 - Using the Database]]

[[Developing a Model-View-Controller Component - Part 4 - Creating an Administrator Interface]]

[[Developing a Model-View-Controller Component - Part 5 - Basic Backend Framework]]

[[Developing a Model-View-Controller Component - Part 6 - Adding Backend Actions]]

== Contributors ==
* mjaz
* staalanden
* dannystaple
* Stilgar
* presto

== Download ==
The component can be downloaded at: [http://joomlacode.org/gf/download/frsrelease/8108/29433/com_hello1_01.zip com_hello1_01]

[[Category:Tutorials]]
[[Category:Component Development]]

Archived:How to override the output from the Joomla! core

2012-03-22T14:43:20Z

Oc666: /* Further tips */

There may be occasions where you would like to change the way a Joomla! Extension (such as a Component or Module, whether from the Joomla! core or produced by a third party) is displayed on your site. Of course, you could recode the Extension from scratch, but that may be a bit ambitious for you! Thankfully, there is another way.

The standard output from any Joomla! Module or Component can be overridden by adding code to the <code>html</code> directory of your template. It is also possible to override two aspects of core functionality: Module chrome, and pagination.

== Getting a head-start with overrides ==
If you are new to Joomla! development, then it is probably easiest to start with an existing view, and try modifying it to get what you want. To do this, you should make a copy of the existing view in the <code>html</code> directory of your template, and then modify the copy.

The directory structure you need is:<br/>
<source lang="xml">TEMPLATE_NAME/html/EXTENSION_NAME/VIEW_NAME/FILE_NAME.php</source>

For example, if you want to change the way that the '<code>Article</code>' view displays a <code>com_content</code> article, then you should copy the file at

<source lang="xml">
PATH_TO_JOOMLA/components/com_content/views/article/tmpl/default.php
to
TEMPLATE_NAME/html/com_content/article/default.php
</source>

(note the slight difference in directory structure)

Similarly, if you want to change how the <code>mod_login</code> Module is displayed, then you should copy

<source lang="xml">
PATH_TO_JOOMLA/modules/mod_login/tmpl/default.php
to
TEMPLATE_NAME/html/mod_login/default.php
</source>

Joomla! comes pre-packaged with a frontend template called [[Beez]]. Beez utilizes template overrides to produce a table-less layout for faster, smoother, and semantically correct markup. To see how it's done, locate your Joomla! installation's <code>template</code> directory, and you'll notice the Beez template. Inside the Beez template directory, you'll find a directory named <code>html</code>

the entire directory structure is as follows:
<source lang="xml">/your_joomla/templates/Beez/html/</source>

If you want to try modifying the overrides used in Beez, you could simply copy and paste the Beez <code>html</code> directory into your own template's main directory.
However you choose to make your override files, you will need to ensure that they are correctly installed with your template. To do this, you should add the following code to your template's <code>templateDetails.xml</code> file (in between the <code><files></code> and <code></files></code> tags):

<source lang="xml">
<folder>html</folder>
</source>

The above code in essence lets the Joomla! [[Installer|package installer]] know that there are files to extract, and that they are part of the template as a whole.

== Further tips ==
Template overrides are almost limitless. They allow you to add, edit, and remove the components of the Joomla! core output.
Note: For the FireFox web browser, an extension called [https://addons.mozilla.org/en-US/firefox/addon/1843 Firebug] is available, which is useful for browsing a page's HTML source and matching it up with the PHP code used in template overrides. For more information, please watch [[Using Firebug With Your Joomla Website|the free video tutorial on using Firebug with Joomla]].
Now firebug is also available for IE called [http://getfirebug.com/lite/ie.html Firebug Lite].

More information is available from the following resources:
* The article [[Understanding Output Overrides]] explains the theory behind template overrides.
* The preferred way of changing text output is by [[Making templates translatable|using translations in your template]].
* A [http://help.joomla.org/ghop/feb2008/task059/Getting_Started_with_Template_Overrides_v2.tar.gz downloadable tutorial] is also available.
* [https://github.com/AmyStephen/Layout-Override-Plugin Example in github] how to override layout of view without override the view, but extending it.
<noinclude>
[[Category:Tutorials]]
[[Category:Templates]]
[[Category:Tips and tricks]]
[[Category:Tips and tricks 1.5]]
[[Category:Tips and tricks 1.6]]
[[Category:Overrides]]
</noinclude>

Pizza Bugs and Fun March 3, 2012/Contributors List

2012-03-16T14:58:35Z

Oc666:

Thanks to everyone who participanted in the Joomla! Pizza, Bugs and Fun on March 3, 2012. Lots of people worldwide tested, coded/fixed and documented new features and issues in Joomla! 2.5, helping to improve the release. Some of the countries represented were the United Kingdom, France, Germany, Denmark, The Netherlands, Israel, the United States, Canada, Brazil, Chile, Argentina, Australia, Malaysia, South Africa, Algeria and India. Over half of the people participating were not in the Joomla Bug Squad so we had a lot of new volunteers. It was great to see so many people come out to help.
These are the statistics from the Joomla CMS Issue Tracker and Joomla CMS Feature Tracker for the period. Thanks must also go out to the people not on these charts including those who did documentation, those who tested but didn't have a login to the trackers and those giving support.

* Andrea Tar (Event organizer)
* Mark Dexter
* Elin Waring
* Jean-Marie Simonet
* Brian Teeman
* Ofer Cohen
* Saurabh Shah

Pizza Bugs and Fun March 3, 2012/Contributors List

2012-03-16T14:12:37Z

Oc666: Created page with "Thanks to everyone who participanted in the Joomla! Pizza, Bugs and Fun on March 3, 2012. Lots of people worldwide tested, coded/fixed and documented new features and issues in J..."

Wrong date format in profile plugin

2012-03-15T15:08:36Z

Oc666:

If you see % (ampersand) in your date field, which is part of the profile plugin (date of birth field), you can fix it easily with editing the file ''plugins/user/profile/profile.php''.

Line #227 currently (Joomla! 2.5.1) is:
<pre>
$data['profile']['dob'] = $date->format('%Y-%m-%d');
</pre>
and should be changed to:
<pre>
$data['profile']['dob'] = $date->format('Y-m-d');
</pre>

== See also ==
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27918 issue in the tracker] (bug tracker #27918)

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.1 FAQ]]
[[Category:Version 2.5.2 FAQ]]
[[Category:Version 2.5.3 FAQ]]

J2.5:Joomla 2.5 com content generates non-valid xhtml

2012-03-15T15:08:29Z

Oc666:

Joomla 2.5 content component generates non-valid xhtml if an article has empty parameters: Link A, Link B, Link C.

The problem is located in this file: components\com_content\views\article\tmpl\default_links.php

For fixing the issue apply the next patch:
<pre>
Index: components/com_content/views/article/tmpl/default_links.php
===================================================================
--- components/com_content/views/article/tmpl/default_links.php (revision 22800)
+++ components/com_content/views/article/tmpl/default_links.php (working copy)
@@ -12,11 +12,11 @@

// Create shortcuts to some parameters.
$params = $this->item->params;
+if ($urls AND (!empty($urls->urla) OR !empty($urls->urlb) OR !empty($urls->urlc))) :
?>
<div class="content-links">
<ul>
<?php
- if ($urls) :
$urlarray = array(
array($urls->urla, $urls->urlatext, $urls->targeta, 'a'),
array($urls->urlb, $urls->urlbtext, $urls->targetb, 'b'),
@@ -73,5 +73,5 @@
</li>
<?php endforeach; ?>
</ul>
- <?php endif; ?>
</div>
+<?php endif; ?>
</pre>

*<nowiki>+ means line added</nowiki>
*<nowiki>- means line removed</nowiki>
== See also ==
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27870 issue in the tracker] (bug tracker #27870)

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.1 FAQ]]
[[Category:Version 2.5.2 FAQ]]
[[Category:Version 2.5.3 FAQ]]

Error notice using search

2012-03-15T15:08:20Z

Oc666:

=== Issue ===
When making a search within the search module, the next notice appears:
<pre>
Notice: Trying to get property of non-object in /path/to/joomla/plugins/search/content/content.php on line 234
</pre>

=== Fix ===
<pre>
Go to plugins/search/content/content.php

Search $itemid = isset($item) ? '&Itemid='.$item->id : '';

Replace with the following line:

$itemid = isset($item->id) ? '&Itemid='.$item->id : '';

Save

</pre>

== See also ==
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27853 issue in the tracker] (bug tracker #27853)

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.1 FAQ]]
[[Category:Version 2.5.2 FAQ]]
[[Category:Version 2.5.3 FAQ]]

Editors buttons Issues in FireFox

2012-03-15T15:08:02Z

Oc666:

When you are inserting images or page break (on tinyMCE), the location of the item you added is on beginning position of the article and not the original location when the mouse cursor was before press the button.

For fixing this issue, you'll require to add the next css code to the end of the file media/system/css/modal.css:
<pre>
@-moz-document url-prefix() {
.body-overlayed {
overflow: visible;
}
}
</pre>

== See also ==
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27600 issue in the tracker] (bug tracker #27660)

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.1 FAQ]]
[[Category:Version 2.5.2 FAQ]]
[[Category:Version 2.5.3 FAQ]]

User talk:Rvsjoen/tutorial/Developing a Module/Part 05

2012-03-13T18:59:01Z

Oc666: Created page with "IMHO, the helper contain the business logic of the module. In addition, we can add one more example for helper use - call component method for interacting with other parts of Joo..."

IMHO, the helper contain the business logic of the module. In addition, we can add one more example for helper use - call component method for interacting with other parts of Joomla. [[User:Oc666|oc666]] 13:59, 13 March 2012 (CDT)

User talk:Rvsjoen/tutorial/Developing a Module/Part 03

2012-03-13T18:55:57Z

Oc666: Created page with "Can we mark (background for example) the config part in the xml? ~~~~"

Can we mark (background for example) the config part in the xml? [[User:Oc666|oc666]] 13:55, 13 March 2012 (CDT)

User talk:Rvsjoen/tutorial/Developing a Module/Part 02

2012-03-13T18:54:08Z

Oc666: Created page with "I think we should write what are the advantage of using module template (like template overrides). ~~~~"

I think we should write what are the advantage of using module template (like template overrides). [[User:Oc666|oc666]] 13:54, 13 March 2012 (CDT)

User talk:Rvsjoen/tutorial/Developing a Module/Part 01

2012-03-13T18:54:05Z

Oc666: Created page with ""...That means you can place the files in the correct places inside your Joomla! installation..." - what are those places? ~~~~"

"...That means you can place the files in the correct places inside your Joomla! installation..." - what are those places? [[User:Oc666|oc666]] 13:54, 13 March 2012 (CDT)

J2.5:Joomla 2.5 com content generates non-valid xhtml

2012-02-29T13:53:08Z

Oc666: Created page with "Joomla 2.5 content component generates non-valid xhtml if an article has empty parameters: Link A, Link B, Link C. The problem is located in this file: components\com_content\vi..."

Archived:Getting Started with Joomla!

2012-02-16T14:54:20Z

Oc666:

{{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}

This series of documents introduces Joomla! to people who have not previously used it. This introduction aims to help you make the best use of the series. This is the introduction to version 1.6+ . There is a separate series [[Getting Started with Joomla! 1.5| for using Joomla! version 1.5]]

==Background==

===Which versions are covered?===

There are two versions in common use:-
* '''Version 1.5''' is well established and widely used, and will be supported till January 2012. See [[Getting Started with Joomla! 1.5]] for the corresponding series.
* Version 1.6 was released January 2011 and is not supported anymore.
* Version 1.7 was released July 2011 and will not be supported after 24 February 2012.
* '''Version 2.5''' (long-term-support (LTS) version that replaces version 1.6 & 1.7) was released January 2012.

There are many similarities between the versions but they are presented separately to newcomers to Joomla! in order to use 'hands-on' material.

===Who is it written for?===

The series is for anyone who wants to use Joomla! at a number of levels. Its main focus is:-
* on people with limited computing experience
* on using Joomla! for a small web site, such as a club or association or small business
but
* there are sections which will be useful to experienced designers and developers.

At the start of each article there is an indication of who it is aimed at and, on occasions, about the pitfalls for the inexperienced or unwary. </br>
[[GS/Readership|Some more detail about the intended readership]]

== Introduction to the Getting Started series ==

Joomla! is introduced using detailed 'hands-on' instructions about adding, altering and manipulating content. At the same time, general points about Joomla! are made which are intended to help people to learn more and do more. As the tasks require more background knowledge, so there are fewer hands-on instructions and more general pointers to the extensive documentation available for Joomla!

The series divides into four parts:-
:*'''Hands-on a Joomla! site:''' There is an initial section on how to get 'hands-on' a Joomla! site. This is followed by practical instructions about doing key tasks needed for adding, altering and manipulating content on an existing site.
:*'''Setting up a Joomla! site:''' This has background information about the design of a Joomla! Web site. There is a hands-on section on the mechanics of creating a new site using the core features that come with Joomla!
:*'''Looking after a Joomla! site:''' This is a brief introduction to the day-to-day adminstration of a Joomla! web Site.
:*'''Doing more and learning more:''' The final part links into other documentation and is intended as a guide ahead for taking Joomla! beyond the basics.

=== Hands-on a Joomla! site ===

You must have the use of a Joomla! Web site to use 'hands-on' instructions. There are several possibilites:-
:*[[Use an existing Joomla! 1.6 site| '''Use a site that has already been set up.''']] If you are going to be adding content to an existing site and do not have much computing experience this is a good option.
:* [[Use Joomla! on your own computer| '''Install a copy of Joomla! (with Sample Data) on your own computer.''']] This is sometimes referred to as a 'localhost' installation. Installing with Sample Data enables you to to explore a Joomla! site before you have created one for your own content. This is a good option for beginners.
:* [[Install_1.7| '''Install a copy of Joomla! (with Sample Data) on a Hosting server.''']] This is sometimes referred to as a 'remote host' installation. Installing with Sample Data enables you to to explore a Joomla! site before you have created one for your own content. This is a good option for beginners. [http://resources.joomla.org/directory/support-services/hosting.html]
:*'''Use the Demo on the Joomla! site.''' - Probably not doing this for version 1.6 Some example sites needed even if not interactive.

=== Hands-on adding and altering articles ===
Start here no matter what your previous experience. Articles are the building blocks of any Joomla! web site and everyone needs to know the basics of how to edit and create them. And doing this helps you to understand the inner workings of Joomla!

:*[[Hands-on editing an article: Joomla! 1.6| '''How to edit an Article''']] - aimed at helping everyone to use the editor and understand what articles look like and where they are stored.
:*[[Hands-on adding a new article: Joomla! 1.6| '''How to create a new Article''']] - aimed at helping everyone to add a new article to a web site

===More about editing articles===
These are aimed at helping everyone who wants to learn more about articles and managing them from the main Site, also called the Front-end.
:*[[Add links to other pages: Joomla! 1.6|'''Hands-on adding links to other pages''']]
:*[[Add a table: Joomla! 1.6|'''Hands-on adding a table''']]
:*[[Add an image: Joomla! 1.6|'''Hands-on adding a picture''']]
:*[[How to split an Article 1.6|'''Hands-on splitting a long article''']]
====Managing content using the Front-end of Joomla!====
:*[[Manage articles using the Front-end of Joomla! 1.6|'''Manipulating and publishing Articles''' ]] using the Front-end

===Setting up a Joomla! site===
There is a distinction between the mechanics of setting up a new site and the things you need to know before you set up a site. There is often a trial and error process involved in doing this, with muddle and frustration as a result. The problem is that you cannot design a site without knowing some background: and it is often easiest to learn the background by using a site. So this series presents the background to understanding how Joomla! sites work separately from the mechanics of creating a site. It emphasises that some initial thought can save hassle later.
====Background - things you need to know====
These are hands-on documents to familiarise you with designing a new site. The background is separate so that the flow of creating the site is not interrupted by asides. The background is aimed at helping you to understand what is going on, whether you have a large or a small site.
:*[[Get to know the Administrator Back-end of Joomla! 1.6|'''Background: get to know the Back-end''']]
:*[[How permissions work in Joomla! 1.6|'''Background: controlling user access to a Joomla! Site''']]
:*[[Design the content: Categories in Joomla! 1.6|'''Background: design the content - Categories in Joomla! 1.6''']]
:*[[Design appearance using Menus and Modules: Joomla! 1.6|'''Background:design appearance using Menus and Modules''']]
:*[[Design appearance using default Templates: Joomla! 1.6|'''Background: design appearance using default Templates''']]

====The mechanics of setting up a new site====
This covers the mechanics of creating new content and appearance of a simple site, using core Joomla! facilities.
:*[[The mechanics of creating a Joomla! 1.6 web site|'''Doing it: hands-on setting up a Joomla! site''']]

===General administration of a Joomla! site===
The work is not done even when a site is set up and there are people adding and altering the content. There are some day-to-day tasks that need attention, as well as minor alterations to the site.
:*[[Start to manage a Joomla! 1.6 site|'''Getting Started with day-to-day Administration of a Joomla! site''']]

==Take Joomla! beyond the basics==
There is more to learn about Joomla.
:* '''Beyond the basics: doing more Jooomla!''' - this is not yet completed - it points to ways ahead.

:*[[References|'''Books, links and helpful resources''']]

==Index to the documents in this series==
{{:GSFooter/1.6}}

Joomla 2.5 version history

2012-02-16T13:51:17Z

Oc666: categorize page

== Joomla! 2.5.1 ==
* 2 February 2012
* [http://www.joomla.org/announcements/release-news/5410-joomla-251-released.html Release Notes]
* [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=6257 Package and MD5s]
* [[:Category: Version 2.5.1 FAQ|FAQ and known issues]]

== Joomla! 2.5.0 ==
* 24 January 2012
* [http://www.joomla.org/announcements/release-news/5403-joomla-250-released.html Release Notes]
* [http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseBrowse&frs_package_id=6231 Package and MD5s]
* [[:Category: Version 2.5.0 FAQ|FAQ and known issues]]

[[Category:Joomla! 2.5]]

Joomla 2.5 version history

2012-02-16T13:42:28Z

Oc666: Add FAQ link to each version

Error notice using search

2012-02-16T13:36:37Z

Oc666: Created page with "=== Issue === When making a search within the search module, the next notice appears: <pre> Notice: Trying to get property of non-object in /path/to/joomla/plugins/search/content..."

=== Issue ===
When making a search within the search module, the next notice appears:
<pre>
Notice: Trying to get property of non-object in /path/to/joomla/plugins/search/content/content.php on line 234
</pre>

=== Fix ===
You have to replace in plugins/search/content/content.php line 234 with the following line:
<pre>
$itemid = isset($item->id) ? '&Itemid='.$item->id : '';
</pre>

== See also ==
* [http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=27853 issue in the tracker] (bug tracker #27853)

[[Category:Version 2.5 FAQ]]
[[Category:Version 2.5.1 FAQ]]

Archived talk:Developing a MVC Component/Example of a frontend update function

2012-02-14T06:49:54Z

Oc666:

This section of the tutorial seems to say that to add an "update" view to the helloworld component a new entry point file must be created with the same name as the view ("updhelloworld.php" in that example). I think this is wrong because:
1) I can delete this file and the example component still works
2) None of the other components have this structure (eg com_users just
has a switch in the main controller's display to select different
displays based on view name)
3) A "die()" in that file never gets executed.

Note that "helloworld.php" (without the "upd" prefix) was created as the entry point back in part 2.

:-Dave

:: I can't see why there is dispatcher in the model and another import of it in the controller. [[User:Oc666|oc666]] 00:49, 14 February 2012 (CST)

How do you put a module inside an article?

2012-02-14T06:39:43Z

Oc666:

{{JVer|1.5}} {{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}

You will usually want to associate modules with articles in some way. The modules are allocated to module positions and the module positions appear somewhere on the Web page as determined by the template. However, it is sometimes useful to have a module actually embedded within the article.

To insert a module inside an article, use the ''{loadposition xx}'' command, as follows:
#Create a module and set its position to any value that doesn't conflict with an existing template position. You can type in the position value instead of selecting it from the drop-down list. For example, use the position ''myposition''.
#Assign the module to the Menu Items that contain the articles that you want the module to show in. You can also just assign the module to '''all''' Menu Items.
#Edit the articles where you want this module to appear and insert the text ''{loadposition myposition}'' in the article at the place where you want the module.

Note that this only works when the [[Screen.plugins.edit.15#Content_-_Load_Module|''Content - Load Module'' plugin is enabled]]. If this plugin is disabled, the text ''{loadposition myposition}'' shows unchanged in the article.

[[Category:FAQ]]
[[Category:Version 1.5 FAQ]]
[[Category:Version 1.6 FAQ]]
[[Category:Version 1.7 FAQ]]
[[Category:Version 2.5 FAQ]]
[[Category:Administration FAQ]]
[[Category:Article Management]]
[[Category:Module Management]]

Archived:Developing a MVC Component/Example of a frontend update function

2012-02-13T15:48:01Z

Oc666:

This tutorial is for {{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}
== Warning - this article needs to be reviewed by someone who knows what they're doing ==

== Articles in this series ==
{{Chunk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Contents}}

== Introduction ==
This tutorial is part of the [[Developing a Model-View-Controller (MVC) Component for Joomla!2.5]] tutorial. You are encouraged to read the previous parts of the tutorial before reading this.

== Basic frontend form ==
Designing the frontend interface leads us to create a Model-View-Controller triptych similar to the backend in Part 7.

'''The rest of this subsection may be wrong. Check the [[{{TALKPAGENAME}}|discussion page]] for details.'''

We have to create an entry point of our component, the ''site/updhelloworld.php'' file.

<span id="site/updhelloworld.php">
''site/updhelloworld.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

// import joomla controller library
jimport('joomla.application.component.controller');

// Get an instance of the controller prefixed by UpdHelloWorld
$controller = JController::getInstance('UpdHelloWorld');

// Perform the Request task
$controller->execute(JRequest::getCmd('task'));

// Redirect if set by the controller
$controller->redirect();
</source>
</span>

== Create the specific controller ==
The entry point now gets an instance of an ''UpdHelloWorld'' prefixed controller which extends the function of JControllerForm. Let's create a basic controllerform for the site part:

<span id="site/controllers/updhelloworld.php">
''site/controllers/updhelloworld.php''
<source lang="php">
<?php

// No direct access.
defined('_JEXEC') or die;

// Include dependancy of the main controllerform class
jimport('joomla.application.component.controllerform');

class HelloWorldControllerUpdHelloWorld extends JControllerForm
{

public function getModel($name = '', $prefix = '', $config = array('ignore_request' => true))
{
return parent::getModel($name, $prefix, array('ignore_request' => false));
}

public function submit()
{
// Check for request forgeries.
JRequest::checkToken() or jexit(JText::_('JINVALID_TOKEN'));

// Initialise variables.
$app = JFactory::getApplication();
$model = $this->getModel('updhelloworld');

// Get the data from the form POST
$data = JRequest::getVar('jform', array(), 'post', 'array');

// Now update the loaded data to the database via a function in the model
$upditem = $model->updItem($data);

// check if ok and display appropriate message. This can also have a redirect if desired.
if ($upditem) {
echo "<h2>Updated Greeting has been saved</h2>";
} else {
echo "<h2>Updated Greeting failed to be saved</h2>";
}

return true;
}

}
</source>
</span>

This controller will display the appropriate message after the form is submitted.

== Create the view ==

With your favorite file manager and editor, create a file ''site/views/updhelloworld/view.html.php'' containing:

<span id="site/views/updhelloworld/view.html.php">
''site/views/updhelloworld/view.html.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

// import Joomla view library
jimport('joomla.application.component.view');

/**
* HTML View class for the UpdHelloWorld Component
*/
class HelloWorldViewUpdHelloWorld extends JView
{
// Overwriting JView display method
function display($tpl = null)
{
$app = JFactory::getApplication();
$params = $app->getParams();
$dispatcher = JDispatcher::getInstance();

// Get some data from the models
$state = $this->get('State');
$item = $this->get('Item');
$this->form = $this->get('Form');

// Check for errors.
if (count($errors = $this->get('Errors')))
{
JError::raiseError(500, implode('<br />', $errors));
return false;
}
// Display the view
parent::display($tpl);
}
}
</source>
</span>

In Joomla, views display data using a layout. With your favorite file manager and editor, put a file ''site/views/updhelloworld/tmpl/default.php'' containing

<span id="site/views/updhelloworld/tmpl/default.php">
''site/views/updhelloworld/tmpl/default.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

JHtml::_('behavior.keepalive');
JHtml::_('behavior.formvalidation');
JHtml::_('behavior.tooltip');

?>
<h2>Update the Hello World greeting</h2>

<form class="form-validate" action="<?php echo JRoute::_('index.php'); ?>" method="post" id="updhelloworld" name="updhelloworld">
<fieldset>
<dl>
<dt><?php echo $this->form->getLabel('id'); ?></dt>
<dd><?php echo $this->form->getInput('id'); ?></dd>
<dt></dt><dd></dd>
<dt><?php echo $this->form->getLabel('greeting'); ?></dt>
<dd><?php echo $this->form->getInput('greeting'); ?></dd>
<dt></dt><dd></dd>
<dt></dt>
<dd><input type="hidden" name="option" value="com_helloworld" />
<input type="hidden" name="task" value="updhelloworld.submit" />
</dd>
<dt></dt>
<dd><button type="submit" class="button"><?php echo JText::_('Submit'); ?></button>
<?php echo JHtml::_('form.token'); ?>
</dd>
</dl>
<fieldset>
</form>
<div class="clr"></div>

</source>
</span>

This layout utilises the forms design which resides with the related model. The getLabel and getInput will pickup the xml fields defined and display appropriately. More on the xml file within the models section of this tutorial.

Create a file ''site/views/updhelloworld/tmpl/default.xml'' containing

<span id="site/views/updhelloworld/tmpl/default.xml">
''site/views/updhelloworld/tmpl/default.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<metadata>
<layout title="COM_HELLOWORLD_UPDHELLOWORLD_VIEW_DEFAULT_TITLE">
<message>COM_HELLOWORLD_UPDHELLOWORLD_VIEW_DEFAULT_DESC</message>
</layout>
</metadata>

</source>
</span>

This enables a menu option to be allocated to the frontend form.

== Create the model ==
The ''UpdHelloWorld'' model sets up the data through from the related form and allows the mechanism to save the subsequent data loaded into the form into the database.

<span id="site/models/updhelloworld.php">
''site/models/updhelloworld.php''
<source lang="php">
<?php
// No direct access to this file
defined('_JEXEC') or die('Restricted access');

// Include dependancy of the main model form
jimport('joomla.application.component.modelform');
// import Joomla modelitem library
jimport('joomla.application.component.modelitem');
// Include dependancy of the dispatcher
jimport('joomla.event.dispatcher');

/**
* UpdHelloWorld Model
*/
class HelloWorldModelUpdHelloWorld extends JModelForm
{
/**
* @var object item
*/
protected $item;

/**
* Get the data for a new qualification
*/
public function getForm($data = array(), $loadData = true)
{

$app = JFactory::getApplication('site');

// Get the form.
$form = $this->loadForm('com_helloworld.updhelloworld', 'updhelloworld', array('control' => 'jform', 'load_data' => true));
if (empty($form)) {
return false;
}
return $form;

}

/**
* Get the message
* @return object The message to be displayed to the user
*/
function &getItem()
{

if (!isset($this->_item))
{
$cache = JFactory::getCache('com_helloworld', '');
$id = $this->getState('helloworld.id');
$this->_item = $cache->get($id);
if ($this->_item === false) {

}
}
return $this->_item;

}

public function updItem($data)
{
// set the variables from the passed data
$id = $data['id'];
$greeting = $data['greeting'];

// set the data into a query to update the record
$db = $this->getDbo();
$query = $db->getQuery(true);
$query->clear();
$query->update(' #__helloworld ');
$query->set(' greeting = '.$db->Quote($greeting) );
$query->where(' id = ' . (int) $id );

$db->setQuery((string)$query);

if (!$db->query()) {
JError::raiseError(500, $db->getErrorMsg());
return false;
} else {
return true;
}
}
}

</source>
</span>

The following file ''updhelloworld.xml'' should be created using your favourite editor and saved in the forms folder under the models directory. The first of the fields being referenced id using the sql type so that I returns the results from the query into a dropdown list form to be selected.
<span id="site/models/forms/updhelloworld.xml">
''site/models/forms/updhelloworld.xml''
<source lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<form name="updhelloworld">
<fieldset name="updhelloworld">

<field
name="id"
type="sql"
multiple="false"
size="1"
label="COM_HELLOWORLD_FORM_LBL_UPDHELLOWORLD_ID"
description="COM_HELLOWORLD_FORM_DESC_UPDHELLOWORLD_ID"
query="select id, greeting from #__helloworld"
key_field="id"
value_field="greeting"
default="0"
required="true"
>
<option value="">JOPTION_SELECT_ID</option>
</field>

<field
name="greeting"
type="text"
description="COM_HELLOWORLD_FORM_DESC_UPDHELLOWORLD_GREETING"
label="COM_HELLOWORLD_FORM_LBL_UPDHELLOWORLD_GREETING"
required="true"
size="50"
/>

</fieldset>
</form>

</source>
</span>

== Adding some language keys ==

This file provides the text link between the label in the model form definition to be displayed in the view. And being for the frontend, it resides in the site folder.

<span id="site/language/en-GB/en-GB.com_helloworld.ini">
''site/language/en-GB/en-GB.com_helloworld.ini''
<source lang="ini">
COM_HELLOWORLD_FORM_LBL_UPDHELLOWORLD_ID="Greeting ID"
COM_HELLOWORLD_FORM_DESC_UPDHELLOWORLD_ID="This is the ID of the Greeting record"
COM_HELLOWORLD_FORM_LBL_UPDHELLOWORLD_GREETING="Greeting"
COM_HELLOWORLD_FORM_DESC_UPDHELLOWORLD_GREETING="Greeting description"
JOPTION_SELECT_ID=" -- Select Greeting to Update -- "
</source>
</span>

Add the last 2 lines to the ''admin/language/en-GB/en-GB.com_helloworld.sys.ini'' file to provide the text link for the menu type display. And being for the backend, it resides in the admin language folder.

<span id="admin/language/en-GB/en-GB.com_helloworld.sys.ini">
''admin/language/en-GB/en-GB.com_helloworld.sys.ini''
<source lang="ini">
COM_HELLOWORLD="Hello World!"
COM_HELLOWORLD_DESCRIPTION="This is the Hello World description"
COM_HELLOWORLD_HELLOWORLD_VIEW_DEFAULT_DESC="This view displays a selected message"
COM_HELLOWORLD_HELLOWORLD_VIEW_DEFAULT_TITLE="Hello World"
COM_HELLOWORLD_INSTALL_TEXT="HelloWorld Install script"
COM_HELLOWORLD_MENU="Hello World!"
COM_HELLOWORLD_POSTFLIGHT_DISCOVER_INSTALL_TEXT="HelloWorld postlight discover install script"
COM_HELLOWORLD_POSTFLIGHT_INSTALL_TEXT="HelloWorld postflight install script"
COM_HELLOWORLD_POSTFLIGHT_UNINSTALL_TEXT="HelloWorld postflight uninstall script"
COM_HELLOWORLD_POSTFLIGHT_UPDATE_TEXT="HelloWorld postflight update script"
COM_HELLOWORLD_PREFLIGHT_DISCOVER_INSTALL_TEXT="HelloWorld preflight discover install script"
COM_HELLOWORLD_PREFLIGHT_INSTALL_TEXT="HelloWorld preflight install script"
COM_HELLOWORLD_PREFLIGHT_UNINSTALL_TEXT="HelloWorld preflight uninstall script"
COM_HELLOWORLD_PREFLIGHT_UPDATE_TEXT="HelloWorld preflight update script"
COM_HELLOWORLD_UNINSTALL_TEXT="HelloWorld Uninstall script"
COM_HELLOWORLD_UPDATE_TEXT="HelloWorld Update script"
COM_HELLOWORLD_UPDHELLOWORLD_VIEW_DEFAULT_TITLE="Update the Greeting"
COM_HELLOWORLD_UPDHELLOWORLD_VIEW_DEFAULT_DESC="Update greeting here"
</source>
</span>

The ''_populateState'' method is, by default, automatically called when a state is read by the ''getState'' method.

== Packaging the component ==

Content of your code directory-
* ''[[#helloworld.xml|helloworld.xml]]''
* ''[[#script.php|script.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_02#site/helloworld.php|site/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_02#site/controller.php|site/controller.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/updhelloworld.php|site/updhelloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/controllers/updhelloworld.php|site/controllers/updhelloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/controllers/index.html|site/controllers/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/helloworld/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#site/views/helloworld/view.html.php|site/views/helloworld/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/views/updhelloworld/view.html.php|site/views/updhelloworld/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/helloworld/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/views/updhelloworld/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#site/views/helloworld/tmpl/default.xml|site/views/helloworld/tmpl/default.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#site/views/helloworld/tmpl/default.php|site/views/helloworld/tmpl/default.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/views/updhelloworld/tmpl/default.xml|site/views/updhelloworld/tmpl/default.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/views/updhelloworld/tmpl/default.php|site/views/updhelloworld/tmpl/default.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/models/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#site/models/helloworld.php|site/models/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/models/updhelloworld.php|site/models/updhelloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_18#site/models/forms/updhelloworld.xml|site/models/forms/updhelloworld.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/models/forms/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/language/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|site/language/en-GB/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_08#site/language/en-GB/en-GB.com_helloworld.ini|site/language/en-GB/en-GB.com_helloworld.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/access.xml|admin/access.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/config.xml|admin/config.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/helloworld.php|admin/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_12#admin/controller.php|admin/controller.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#admin/sql/install.mysql.utf8.sql|admin/sql/install.mysql.utf8.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#admin/sql/uninstall.mysql.utf8.sql|admin/sql/uninstall.mysql.utf8.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/updates/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/sql/updates/mysql/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#admin/sql/updates/mysql/0.0.1.sql|admin/sql/updates/mysql/0.0.1.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_06#admin/sql/install.mysql.utf8.sql|admin/sql/updates/mysql/0.0.6.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_12#admin/sql/updates/mysql/0.0.12.sql|admin/sql/updates/mysql/0.0.12.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#admin/sql/updates/mysql/0.0.13.sql|admin/sql/updates/mysql/0.0.13.sql]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/fields/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_12#admin/models/fields/helloworld.php|admin/models/fields/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/forms/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#admin/models/forms/helloworld.xml|admin/models/forms/helloworld.xml]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/models/forms/helloworld.js|admin/models/forms/helloworld.js]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/models/rules/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/models/rules/greeting.php|admin/models/rules/greeting.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/models/helloworld.php|admin/models/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_09#admin/models/helloworlds.php|admin/models/helloworlds.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworlds/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/views/helloworlds/view.html.php|admin/views/helloworlds/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworlds/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/views/helloworlds/tmpl/default.php|admin/views/helloworlds/tmpl/default.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_head.php|admin/views/helloworlds/tmpl/default_head.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_body.php|admin/views/helloworlds/tmpl/default_body.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_07#admin/views/helloworlds/tmpl/default_foot.php|admin/views/helloworlds/tmpl/default_foot.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworld/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/views/helloworld/view.html.php|admin/views/helloworld/view.html.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/views/helloworld/submitbutton.js|admin/views/helloworld/submitbutton.js]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/views/helloworld/tmpl/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#admin/views/helloworld/tmpl/edit.php|admin/views/helloworld/tmpl/edit.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/helpers/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/helpers/helloworld.php|admin/helpers/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/tables/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_14#admin/tables/helloworld.php|admin/tables/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_13#admin/language/en-GB/en-GB.com_helloworld.ini|admin/language/en-GB/en-GB.com_helloworld.ini]]''
* ''[[#admin/language/en-GB/en-GB.com_helloworld.sys.ini|admin/language/en-GB/en-GB.com_helloworld.sys.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|admin/controllers/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/controllers/helloworld.php|admin/controllers/helloworld.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_11#admin/controllers/helloworlds.php|admin/controllers/helloworlds.php]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_08#language/en-GB/en-GB.ini|language/en-GB/en-GB.ini]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|media/index.html]]''
* ''[[Developing_a_Model-View-Controller_(MVC)_Component_for_Joomla!2.5_-_Part_01#index.html|media/images/index.html]]''
* ''media/images/tux-16x16.png''
* ''media/images/tux-48x48.png''

Create a compressed file of this directory or directly download the [http://joomlacode.org/gf/download/frsrelease/11394/58397/com_helloworld-1.6-part07.zip archive] and install it using the extension manager of Joomla. You can add a menu item of this component using the menu manager in the backend.

<span id="helloworld.xml">
''helloworld.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension type="component" version="2.5.0" method="upgrade">

<name>COM_HELLOWORLD</name>

<creationDate>November 2009</creationDate>
<author>John Doe</author>
<authorEmail>john.doe@example.org</authorEmail>
<authorUrl>http://www.example.org</authorUrl>
<copyright>Copyright Info</copyright>
<license>License Info</license>

<version>0.0.18</version>

<description>COM_HELLOWORLD_DESCRIPTION</description>


<scriptfile>script.php</scriptfile>

<install> 
<sql>
<file driver="mysql" charset="utf8">sql/install.mysql.utf8.sql</file>
</sql>
</install>
<uninstall> 
<sql>
<file driver="mysql" charset="utf8">sql/uninstall.mysql.utf8.sql</file>
</sql>
</uninstall>
<update> 
<schemas>
<schemapath type="mysql">sql/updates/mysql</schemapath>
</schemas>
</update>



<files folder="site">
<filename>index.html</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>
<filename>updhelloworld.php</filename>
<folder>views</folder>
<folder>models</folder>
<folder>controllers</folder>
<folder>language</folder>
</files>

<media destination="com_helloworld" folder="media">
<filename>index.html</filename>
<folder>images</folder>
</media>

<administration>

<menu img="../media/com_helloworld/images/tux-16x16.png">COM_HELLOWORLD_MENU</menu>


<files folder="admin">

<filename>index.html</filename>
<filename>config.xml</filename>
<filename>access.xml</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>

<folder>sql</folder>

<folder>tables</folder>

<folder>models</folder>

<folder>views</folder>

<folder>controllers</folder>

<folder>helpers</folder>
</files>

<languages folder="admin">
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.ini</language>
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.sys.ini</language>
</languages>
</administration>


<updateservers>

<server type="extension" priority="1" name="HelloWorld Update Site">http://yourdomain.com/update/helloworld-update.xml</server>
</updateservers>

</extension>

</source>
</span>

Now you can see in your component '''hello-world''' an array with two colums, two rows and checkboxes. You can click the checkboxes in order to select the different options you want.

== Zips ==
Download the zip file for this Part:
[http://www.glennarkell.com/joomlaorg/com_helloworld_0.0.18.zip]

== Navigate ==

[[Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Part 17|Prev: Adding an update server]]

== Contributors ==
*[[User:garkell|Glenn Arkell]]

[[Category:Development]]
[[category:Joomla! 1.6]]
[[category:Joomla! 1.7]]
[[category:Joomla! 2.5]]
[[category:Manual]]

Archived:Developing a MVC Component/Adding an update server

2012-02-13T15:45:37Z

Oc666:

This tutorial is for {{JVer|1.6}} {{JVer|1.7}} {{JVer|2.5}}

== Articles in this series ==
{{Chunk:Developing a Model-View-Controller (MVC) Component for Joomla!2.5 - Contents}}

== Introduction ==
This tutorial is part of the [[Developing a Model-View-Controller (MVC) Component for Joomla!2.5]] tutorial. You are encouraged to read the previous parts of the tutorial before reading this.

== Adding a updateserver definition ==
To add a updateserver functionality adjust the helloworld.xml to look like this.

<span id="helloworld.xml">
''helloworld.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<extension type="component" version="2.5.0" method="upgrade">

<name>COM_HELLOWORLD</name>

<creationDate>November 2009</creationDate>
<author>John Doe</author>
<authorEmail>john.doe@example.org</authorEmail>
<authorUrl>http://www.example.org</authorUrl>
<copyright>Copyright Info</copyright>
<license>License Info</license>

<version>0.0.15</version>

<description>COM_HELLOWORLD_DESCRIPTION</description>


<scriptfile>script.php</scriptfile>

<install> 
<sql>
<file driver="mysql" charset="utf8">sql/install.mysql.utf8.sql</file>
</sql>
</install>
<uninstall> 
<sql>
<file driver="mysql" charset="utf8">sql/uninstall.mysql.utf8.sql</file>
</sql>
</uninstall>
<update> 
<schemas>
<schemapath type="mysql">sql/updates/mysql</schemapath>
</schemas>
</update>



<files folder="site">
<filename>index.html</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>
<folder>views</folder>
<folder>models</folder>
<folder>language</folder>
</files>

<media destination="com_helloworld" folder="media">
<filename>index.html</filename>
<folder>images</folder>
</media>

<administration>

<menu img="../media/com_helloworld/images/tux-16x16.png">COM_HELLOWORLD_MENU</menu>


<files folder="admin">

<filename>index.html</filename>
<filename>config.xml</filename>
<filename>access.xml</filename>
<filename>helloworld.php</filename>
<filename>controller.php</filename>

<folder>sql</folder>

<folder>tables</folder>

<folder>models</folder>

<folder>views</folder>

<folder>controllers</folder>

<folder>helpers</folder>
</files>

<languages folder="admin">
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.ini</language>
<language tag="en-GB">language/en-GB/en-GB.com_helloworld.sys.ini</language>
</languages>
</administration>


<updateservers>

<server type="extension" priority="1" name="HelloWorld Update Site">http://yourdomain.com/update/helloworld-update.xml</server>
</updateservers>

</extension>
</source>
</span>

You also need to put a XML-file on your server which contains all update-informations.

<span id="helloworld-update.xml">
''helloworld-update.xml''
<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<updates>
<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.0</version>

<infourl title="HalloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.0-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>
<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.0</version>

<infourl title="HalloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.0-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>
<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.0</version>

<infourl title="HalloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.0-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>

<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.1</version>

<infourl title="HelloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.1-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>
<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.1</version>

<infourl title="HelloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.1-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>
<update>
<name>HelloWorld</name>
<description>HelloWorld Component</description>
<element>com_helloworld</element>
<type>component</type>
<version>1.5.1</version>

<infourl title="HelloWorld URL">http://yourdomain.com</infourl>
<downloads>
<downloadurl type="full" format="zip">http://yourdomain.com/files/com_helloworld-1.5.1-final.zip</downloadurl>
</downloads>
<tags>
<tag>some-tag</tag>
</tags>

<maintainer>HelloWorld Inc.</maintainer>
<maintainerurl>http://yourdomain.com</maintainerurl>
<section>some-section</section>
<targetplatform name="joomla" version="2.5" />
</update>

</updates>

</source>
</span>

You need to add a new update-node every time you publish a new release, as well as for each Joomla! version. (you will need a distinct update node for each targetplatform)

== Zips ==
Download the zip file for this Part:
[http://www.leyar.com/joomlaorg/part17.zip] (NOTE: This package is designed for Joomla only.)

== See Also ==
*[[Deploying an Update Server]]

== Contributors ==
*[[User:Cdemko|Christophe Demko]]
*[[User:oaksu|Ozgur Aksu]]
*[[User:HobbesPDX|Ben Sandberg]]

[[Category:Development]]
[[category:Joomla! 1.6]]
[[category:Joomla! 1.7]]
[[category:Joomla! 2.5]]
[[category:Manual]]