<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><!-- generator="Joomla! 1.5 - Open Source Content Management" --><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
	<channel>
		<title>Joomla How Tos and Tutorials</title>
		<description />
		<link>http://ostraining.com/howtojoomla/</link>
		<lastBuildDate>Fri, 25 May 2012 15:43:21 +0000</lastBuildDate>
		<generator>Joomla! 1.5 - Open Source Content Management</generator>
		<language>en-gb</language>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/howtojoomla" /><feedburner:info uri="howtojoomla" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>howtojoomla</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
			<title>How To Package Joomla Libraries</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/aRsUmTZmgfo/how-to-package-joomla-libraries</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/how-tos/development/how-to-package-joomla-libraries</guid>
			<description>&lt;p&gt;You’ve seen it before: the monster Joomla installation package. It’s a giant component, several side modules, and at least one plugin. Once you dig through the code, you notice the plugin isn’t even responding to events: it’s merely there to load up code shared by the other extensions.&lt;/p&gt;
&lt;p&gt;Fortunately, Joomla 1.6 and higher provide a better way of handling this. Reusable code libraries can now be installed into the &lt;code&gt;libraries&lt;/code&gt; folder without creating extraneous plugins. Just like any other extension in Joomla, a library is packaged as a .zip file with an XML manifest to guide the installation.&lt;/p&gt;
&lt;p&gt;If you’ve created Joomla XML manifest files before, creating one for a library is straightforward. The main thing you need to keep in mind is the added &lt;code&gt;&amp;lt;libraryname&amp;gt;&lt;/code&gt; element. This element is the “system name” for the library: make sure it is valid as a directory name across platforms. When coming up with this “system name,” avoid spaces, capital letters, and special characters. Upon installation, Joomla will create a subfolder of &lt;code&gt;libraries&lt;/code&gt; using name specified by &lt;code&gt;&amp;lt;libraryname&amp;gt;&lt;/code&gt;. Contrast this with the &lt;code&gt;&amp;lt;name&amp;gt;&lt;/code&gt; element, which identifies an extension with a human readable name.&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/aRsUmTZmgfo" height="1" width="1"/&gt;</description>
			<author>joe@jlleblanc.com (Joseph LeBlanc)</author>
			<category>frontpage</category>
			<pubDate>Thu, 13 Oct 2011 23:16:03 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/how-tos/development/how-to-package-joomla-libraries</feedburner:origLink></item>
		<item>
			<title>How to override offline mode in Joomla without requiring a login</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/UnFWlqtUzPA/how-to-override-offline-mode-in-joomla-without-requiring-a-login</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/20110117153/how-tos/mambots/plugins/how-to-override-offline-mode-in-joomla-without-requiring-a-login</guid>
			<description>&lt;p&gt;As you may know, you can set your Joomla site "offline" by setting "Site Offline" to "Yes" in the Global Configuration. This is a great feature that enables you to build or troubleshoot your site in offline mode, restricting access only to backend users who login through the login form displayed on the offline page.&lt;/p&gt;
&lt;p&gt;The only limitation to this feature is that you have to be logged in to see the frontend of the site, so you cannot test the site from the perspective of a user who is not logged in. For example, if you want to test registration, AEC or Ambra Subscriptions integration, or any number of other things that might require you to see the site from the perspective of a non-logged-in user, you cannot do that because offline mode requires you to log in to see the front end of the site.&lt;/p&gt;
&lt;p&gt;I have developed a &lt;a href="http://ostraining.com/howtojoomla/downloads/plugins"&gt;Joomla plugin&lt;/a&gt; called &lt;a href="http://ostraining.com/howtojoomla/downloads/plugins/offline-override"&gt;Offline Override&lt;/a&gt; that enables you to put the site in offline mode, and enter a keyword to override offline mode without requiring a login. You simply install and enable the &lt;a href="http://ostraining.com/howtojoomla/downloads/plugins/offline-override"&gt;Offline Override plugin&lt;/a&gt;, create your secret keyword (no spaces) and enter it in the plugin's parameters. Then, when your site is in offline mode, you can override the offline mode by adding "?keyword=&lt;em&gt;VALUE&lt;/em&gt;" in the address bar for the frontend of your site. For example, if your keyword is "joomlarocks", you would go to http://yoursite.com/?keyword=joomlarocks. The override only lasts the length of your session and you must re-enter the keyword in the address bar (http://yoursite.com/?keyword=joomlarocks) the next time you open your browser.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/UnFWlqtUzPA" height="1" width="1"/&gt;</description>
			<author>Y5tn_cory@corywebbmedia.com (Cory)</author>
			<category>frontpage</category>
			<pubDate>Mon, 17 Jan 2011 21:47:14 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/20110117153/how-tos/mambots/plugins/how-to-override-offline-mode-in-joomla-without-requiring-a-login</feedburner:origLink></item>
		<item>
			<title>Getting started with JForm</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/fUlKrcAzk_A/getting-started-with-jform</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/how-tos/development/getting-started-with-jform</guid>
			<description>&lt;p&gt;JForm is one of the most exciting new features to be introduced as part of Joomla! 1.6. The intention is to provide XML configurable forms complete with custom field types and form validation. I cannot stress enough just how much easier this is going to make life as a Joomla! developer. In this article we take a look at how to define JForms and how to display them.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/fUlKrcAzk_A" height="1" width="1"/&gt;</description>
			<author>james@webamoeba.co.uk (James Kennard)</author>
			<category>frontpage</category>
			<pubDate>Mon, 29 Nov 2010 15:35:14 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/how-tos/development/getting-started-with-jform</feedburner:origLink></item>
		<item>
			<title>Joomla! Day DC 2010</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/K_MTYIRN2v0/joomla-day-dc-2010</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/20100826151/blog/community/joomla-day-dc-2010</guid>
			<description>&lt;p&gt;&lt;a target="_blank" href="http://www.joomladaydc.com/"&gt;&lt;img style="border-color: #000000; border-width: 0px;" alt="Joomla Day DC, October 16, 2010" src="http://ostraining.com/howtojoomla/images/jddc-image.jpg" height="187" width="590" /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Far and wide across this great nation, Joomla! users have been waiting. Waiting for their voice to be heard. Waiting for their vote to count. On October 16th at the footsteps of Washington DC, the wait will be over. We will finally be hearing from the President himself... Mr. Ryan Ozimek, President of Open Source Matters!&lt;/p&gt;
&lt;p&gt;For many months now, &lt;a target="_blank" href="http://novajoomla.com/"&gt;NoVA Joomla&lt;/a&gt; has quietly lobbied from inside the Beltway to build a collation of representatives from across the nation. Delegates are traveling from the District of Columbia, New Hampshire, Massachusetts, New York, Virginia, Nebraska, Georgia, Louisiana, and Texas; we're even expecting visitors from England and Greece! Will you be represented? Only if you attend! Come with us and wave the Red, Green, and Blue! (and orangey-yellow too!)&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/K_MTYIRN2v0" height="1" width="1"/&gt;</description>
			<author>joe@jlleblanc.com (Joseph LeBlanc)</author>
			<category>frontpage</category>
			<pubDate>Thu, 26 Aug 2010 18:25:26 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/20100826151/blog/community/joomla-day-dc-2010</feedburner:origLink></item>
		<item>
			<title>How to track your Joomla! project with Git</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/aEWDrIHRWgU/how-to-track-your-joomla-project-with-git</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/how-tos/development/how-to-track-your-joomla-project-with-git</guid>
			<description>&lt;p&gt;If you’ve ever worked on an existing website, chances are you’ve run into a directory listing like the following:&lt;/p&gt;
&lt;div class="code"&gt;
&lt;pre&gt;&lt;code&gt;Copy of index.html&lt;br /&gt;about.html&lt;br /&gt;contact.html&lt;br /&gt;favicon.ico&lt;br /&gt;index.html&lt;br /&gt;index.html.bak&lt;br /&gt;index.html.bak2&lt;br /&gt;index.html.old&lt;br /&gt;pricing.html&lt;br /&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;p&gt;It’s also quite possible you are responsible for having created a mess like this. We’re always told to make backups of our files, and so we make them, often right next to the files of a live site. While it’s a good idea to make a backup of your code before changing something that already works, .bak, .old, and .other files can accumulate very quickly.&lt;/p&gt;
&lt;p&gt;Made-up extensions like .bak tell us (let alone others) very little about the significance of each change. It would be nice if there were some way of keeping a history of &lt;em&gt;every&lt;/em&gt; change made to a file. Better still, tracking &lt;em&gt;who&lt;/em&gt; made each change would be useful. And a way of combining changes from two different copies of the same file would be fantastic.&lt;/p&gt;
&lt;p&gt;Fortunately, such systems already exist.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/aEWDrIHRWgU" height="1" width="1"/&gt;</description>
			<author>joe@jlleblanc.com (Joseph LeBlanc)</author>
			<category>frontpage</category>
			<pubDate>Mon, 05 Jul 2010 17:39:47 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/how-tos/development/how-to-track-your-joomla-project-with-git</feedburner:origLink></item>
		<item>
			<title>Deploying Large-Scale Websites with Joomla - Part 1: An Interview with Mitch Pirtle</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/mgh89WbsCJA/deploying-large-scale-websites-with-joomla-part-1-an-interview-with-mitch-pirtle</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/20100610149/how-tos/miscellaneous/deploying-large-scale-websites-with-joomla-part-1-an-interview-with-mitch-pirtle</guid>
			<description>&lt;p&gt;I've heard a lot of talk lately about whether or not Joomla can handle large-scale websites, or if it's best used for small mom-and-pop sites. I can say emphatically that the answer to that question is that Joomla is not only useful for small mom-and-pop sites, but it can also be used to build it medium and large-scale sites. There are a few popular examples of large-scale websites built with Joomla, and two developers have been involved in a number of these sites: Mitch Pirtle from &lt;a target="_self" href="http://www.spacemonkeylabs.com/"&gt;Space Monkey Labs&lt;/a&gt; and Fotis Evangelou from &lt;a target="_self" href="http://www.komrade.gr/"&gt;Komrade&lt;/a&gt; and &lt;a target="_self" href="http://www.joomlaworks.gr/"&gt;JoomlaWorks&lt;/a&gt;. In this 2-part series, I am interviewing both Mitch and Fotis to get their insights on what it takes to deploy large-scale websites with Joomla. Part 1 is my interview with Mitch.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/mgh89WbsCJA" height="1" width="1"/&gt;</description>
			<author>Y5tn_cory@corywebbmedia.com (Cory)</author>
			<category>frontpage</category>
			<pubDate>Thu, 10 Jun 2010 17:02:40 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/20100610149/how-tos/miscellaneous/deploying-large-scale-websites-with-joomla-part-1-an-interview-with-mitch-pirtle</feedburner:origLink></item>
		<item>
			<title>Establishing a patching process</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/xNOXNDuaiLg/establishing-a-patching-process</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/how-tos/security/establishing-a-patching-process</guid>
			<description>&lt;p&gt;Good day,&lt;/p&gt;
&lt;p&gt;Waaaaaay back in January, I took the time in this column to discuss with you the concept and need to patch your site. Since that article was written till now (May 16, 2010) there has been about 180 report vulnerabilities for Joomla extensions. And some number of them for the Joomla core (to be fair only a few).&lt;/p&gt;
&lt;p&gt;Given that you might be using one of these, its important to revisit this highly important topic.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/xNOXNDuaiLg" height="1" width="1"/&gt;</description>
			<author>joomlajabber@gmail.com (Tom Canavan)</author>
			<category>frontpage</category>
			<pubDate>Mon, 17 May 2010 20:49:40 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/how-tos/security/establishing-a-patching-process</feedburner:origLink></item>
		<item>
			<title>UTF-8 in Joomla</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/NTT5pAkLjMI/utf-8-in-joomla</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/how-tos/development/utf-8-in-joomla</guid>
			<description>&lt;p&gt;Have you ever browsed to a website only to find that half the content is unreadable? Or that certain characters are being displayed in strange and mysterious ways? Or perhaps you wanted to enter a foreign or unusual character but found that the result was a garbled mess.&lt;/p&gt;
&lt;p&gt;The chances are you have been subject to poorly managed character encodings. Joomla! extensions are no exception to these occurrences, but with a little bit of effort and some help from the Joomla! framework, we can avoid these problems with relative ease.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/NTT5pAkLjMI" height="1" width="1"/&gt;</description>
			<author>james@webamoeba.co.uk (James Kennard)</author>
			<category>frontpage</category>
			<pubDate>Sun, 18 Apr 2010 19:16:55 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/how-tos/development/utf-8-in-joomla</feedburner:origLink></item>
		<item>
			<title>Announcing /motif - a New Template Framework for Joomla!</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/4X54wT1zNZM/announcing-motif-a-new-template-framework-for-joomla</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/20100412145/blog/joomla/announcing-motif-a-new-template-framework-for-joomla</guid>
			<description>&lt;p&gt;&lt;a target="_blank" href="http://themeables.com/motif"&gt;&lt;img style="border-color: #000000; border-width: 0px; margin: 10px; float: right;" alt="/motif Joomla! Template Framework" src="http://themeables.com/images/motif.gif" height="67" width="150" /&gt;&lt;/a&gt;We are pleased to announce the beta launch of our new &lt;a target="_blank" href="http://themeables.com/motif"&gt;Joomla! template framework&lt;/a&gt;, &lt;a target="_blank" href="http://themeables.com/motif"&gt;/motif&lt;/a&gt;. Actually, it's not that new. We built /motif back in October of 2009 for our own purposes.&lt;/p&gt;
&lt;p&gt;/motif is a template development framework for Joomla! built to simplify the development of fully-custom Joomla! templates and empower web designers to become Joomla! template developers. We are Joomla! template designers and developers, and we built /motif in October 2009 to "scratch our own itch." We needed a simple, robust, and flexible template framework with a non-restrictive license so we could use it on all of the &lt;a href="http://themeables.com/joomla-templates/custom-joomla-templates"&gt;custom templates&lt;/a&gt; we build for our clients. Unfortunately, none of the frameworks available at the time quite fit what we needed, so we built our own.&lt;/p&gt;
&lt;p&gt;This framework will be the basis of a new Joomla! template club called &lt;a target="_blank" href="http://themeables.com/"&gt;Themeables&lt;/a&gt;, which we will be officially launching at &lt;a target="_blank" href="http://www.cmsassociation.com/70-2-1-50.html"&gt;CMS Expo&lt;/a&gt; in May. Head over to the Themeables website and &lt;a target="_blank" href="http://themeables.com/motif/download-motif"&gt;grab a copy of /motif for yourself&lt;/a&gt;. The framework is free (as in freedom and as in beer). If you want to learn more about /motif, check out the &lt;a target="_blank" href="http://themeables.com/motif/documentation"&gt;/motif documentation&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/4X54wT1zNZM" height="1" width="1"/&gt;</description>
			<author>Y5tn_cory@corywebbmedia.com (Cory)</author>
			<category>frontpage</category>
			<pubDate>Mon, 12 Apr 2010 16:44:29 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/20100412145/blog/joomla/announcing-motif-a-new-template-framework-for-joomla</feedburner:origLink></item>
		<item>
			<title>Better Communication with the Joomla Community</title>
			<link>http://feedproxy.google.com/~r/howtojoomla/~3/d2axN4z0TB8/better-communication-with-the-joomla-community</link>
			<guid isPermaLink="false">http://ostraining.com/howtojoomla/20100324144/blog/joomla/better-communication-with-the-joomla-community</guid>
			<description>&lt;p&gt;In recent months, there have been a few issues in the Joomla community and with Joomla's leadership that have caused some people to get upset with how decisions are made and with the lack of communication between the leadership team and the community over certain decisions. &lt;a target="_blank" href="http://www.alledia.com"&gt;Steve Burge&lt;/a&gt; has formed a team to address these issues and come up with a solution for better communication with the community. You can read about &lt;a target="_blank" href="http://community.joomla.org/blogs/community/1138-better-communication.html"&gt;this new initiative on Joomla.org&lt;/a&gt;. If you have a moment, please take some time to read through Steve's post and fill out the form at the end of the post to share your ideas. {jomcomment lock}&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/howtojoomla/~4/d2axN4z0TB8" height="1" width="1"/&gt;</description>
			<author>Y5tn_cory@corywebbmedia.com (Cory)</author>
			<category>frontpage</category>
			<pubDate>Wed, 24 Mar 2010 16:50:44 +0000</pubDate>
		<feedburner:origLink>http://ostraining.com/howtojoomla/20100324144/blog/joomla/better-communication-with-the-joomla-community</feedburner:origLink></item>
	</channel>
</rss>

