<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WP Wizard &#187; plugins</title>
	<atom:link href="http://wpwizard.net/tag/plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpwizard.net</link>
	<description>I ❤ WordPress</description>
	<lastBuildDate>Sat, 05 Mar 2011 12:30:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Add jQuery to your Theme or Plugin</title>
		<link>http://wpwizard.net/jquery/add-jquery-to-your-theme-or-plugin/</link>
		<comments>http://wpwizard.net/jquery/add-jquery-to-your-theme-or-plugin/#comments</comments>
		<pubDate>Sat, 27 Feb 2010 13:41:53 +0000</pubDate>
		<dc:creator>Stian Andreassen</dc:creator>
				<category><![CDATA[jQuery]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[theme]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://stianandreassen.com/?p=394</guid>
		<description><![CDATA[Add jQuery (and other script-libraries) to your Themes and Plugins in a clean way, that won't cause problems.]]></description>
			<content:encoded><![CDATA[<p>I often use <strong>jQuery</strong> in the <strong>Themes</strong> and, without exception, in all the <strong>Plugins</strong> I write. You can easilly add jQuery to any HTML-document by simply linking to Googles jQuery-script, but this is not always without problems, especially if your sites employs several libraries.<br />
<span id="more-394"></span></p>
<p>jQuery is often added with this line between  and <code>&lt;head&gt;</code> and <code>&lt;/head&gt;</code>:</p>
<pre class="brush: xml; auto-links: false; title: ;">
&lt;script type=&quot;text/javascript&quot; src=&quot;http://jqueryjs.googlecode.com/files/jquery-1.3.2.js&quot;&lt;/script&gt;
</pre>
<p>But this can – among other things – cause latency in page loading, and is really not necessary as <strong>WordPress</strong> comes pre-packed with a lot of script-libraries, including jQuery.</p>
<p>To add jQuery (or Script-A-Licious or ProtoType) to your Theme, you simply use the <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script">wp_enqueue_script()</a> function. In your Themes <code>functions.php</code> (if it doesn&#8217;t exists, simply create it) you add these lines:</p>
<pre class="brush: php; title: ;">
&lt;?php
function yourtheme_init(){
 wp_enqueue_script('jquery');
 wp_enqueue_script('jquery-ui-core');
}
add_filter('wp_enqueue_scripts', 'yourtheme_init');
?&gt;
</pre>
<p>This will load jQuery on your site’s frontend. If you have plugins that use jQuery, the upshot of this method is that WP will not load jQuery multiple times (as it will if you add it manually to your Theme), and thus not cause conflicts.</p>
<p>To avoid jQuery conflicts you should also surround your scripts with this:</p>
<pre class="brush: jscript; highlight: [5]; title: ;">
&lt;script type=&quot;text/javascript&quot;&gt;
jQuery.noConflict();
jQuery(document).ready(function($){

YOUR SCRIPT HERE

});
&lt;/script&gt;
</pre>
<div class="shr-publisher-394"></div>]]></content:encoded>
			<wfw:commentRss>http://wpwizard.net/jquery/add-jquery-to-your-theme-or-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up WordPress as a CMS – part 2</title>
		<link>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-2/</link>
		<comments>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-2/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 10:00:18 +0000</pubDate>
		<dc:creator>Stian Andreassen</dc:creator>
				<category><![CDATA[Customizing WordPress]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[dashboard]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wp-admin]]></category>

		<guid isPermaLink="false">http://www.stianandreassen.com/?p=234</guid>
		<description><![CDATA[How to exclude Pages from page navigation and add alternate titles (different from navigation titles) to Pages.]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-1/">part 1</a> I discussed how cleaning up the <strong>Dashboard </strong>in <strong>WordPress </strong>by removing excess admin panels and editor sections makes it easier to use, especially for users who are new to WordPress. In this part I&#8217;ll be discussing how to add options for excluding pages from navigation and how to add alternate titles.</p>
<h3><span id="more-234"></span>Exclude Pages from Navigation</h3>
<p>I often want to add <strong>Pages </strong>to my WordPress site, without showing it in <code>wp_list_pages()</code>. So far WordPress doesn&#8217;t have an option for excluding <strong>Pages </strong>from navigation menus without setting <em>Visibility </em>to <em>Private </em>(which makes them unavailable for non-logged-in users). For this we have to use a <strong>Plugin</strong>: <a href="http://wordpress.org/extend/plugins/exclude-pages/">Exclude Pages</a>. This plugin adds a checkbox to the <strong>Page Editor</strong>; “Include this page in menus”. Simply uncheck this to exclude <strong>Pages </strong>from the page navigation that users see on your site.</p>
<h3>Alternate Titles</h3>
<p>When creating <strong>Pages </strong>in WordPress, what you put in the <strong>Title Field</strong> will show up both in navigation and as a title on the website. This can be very impractical, not to say downright frustrating. Often I want the menu item to be &#8220;About Us&#8221;, but the Page title to be &#8220;Who We Are&#8221;, or something of the same. Not possible in WordPress out-of-the-box. The sollution is <strong>Custom Fields</strong>. In the Page Editor, add a new custom field called &#8220;alttitle&#8221;. Then edit your <code>page.php</code>, and replace <code>&lt;h2&gt;&lt;?php the_title();  ?&gt;&lt;/h2&gt;</code> with:</p>
<pre class="brush: php; title: ;">
&lt;?php $alttitle = get_post_meta($post-&gt;ID, 'alttitle', true); ?&gt;
&lt;h2&gt;&lt;?php if(!$alttitle) { the_title(); } else { echo $alttitle; } ?&gt;&lt;/h2&gt;
</pre>
<p>That&#8217;s it. The code checks if an alternate title is exists, and if so, displays it. Otherwise the default <strong>Page</strong> title is displayed.</p>
<h3>Make an Alternate Title Section in the Editor</h3>
<p>If you have hidden the custom fields section from your users, or just simply want to make the sollution more elegant, you can use the <a href="http://wordpress.org/extend/plugins/more-fields/">More Fields</a> plugin i mentioned in part 1. Here&#8217;s how to do it:</p>
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings &gt; More Fields and click &#8220;Add a new box!&#8221;</li>
<li>In <em>Box title</em> put &#8220;Alternate Title&#8221;, and select &#8220;Left&#8221; in the <em>Position </em>pull-down, save</li>
<li>Click the &#8220;Add new field!&#8221; button</li>
<li>In <em>Key </em>put &#8220;alttitle&#8221;, in <em>Title </em>put &#8220;Alternate Title is used as page heading, while Title field (above) is used for navigation items&#8221;, leave the rest as is, save</li>
<li>Click &#8220;Manage post types&#8221; in the top menu, click &#8220;Page&#8221;, scroll down to the bottom and check the checkbox next to <strong>Alternate Title</strong>, save</li>
</ol>
<p>You will now have a new editor section in the Page Editor, where you can write alternate titles for your <strong>Pages</strong>.</p>
<p style="text-align: center;"><img class="size-full wp-image-253 alignnone" title="alttitle_dump" src="http://wpwizard.net/wp-content/uploads/2009/12/alttitle_dump.png" alt="alttitle_dump" width="380" height="104" /></p>
<div class="shr-publisher-234"></div>]]></content:encoded>
			<wfw:commentRss>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Setting up WordPress as a CMS &#8211; part 1</title>
		<link>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-1/</link>
		<comments>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-1/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 08:55:01 +0000</pubDate>
		<dc:creator>Stian Andreassen</dc:creator>
				<category><![CDATA[Customizing WordPress]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[dashboard]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[wp-admin]]></category>

		<guid isPermaLink="false">http://www.stianandreassen.com/?p=3</guid>
		<description><![CDATA[By removing the excess funtions the users never need, WordPress feels more complete and functional as a CMS.]]></description>
			<content:encoded><![CDATA[<p><strong><a href="http://wordpress.org/">WordPress</a></strong> is best known as the leading (free) <strong>blogging software</strong> on the web. But it can also be used as a full-fledged <strong><abbr title="content management system">CMS</abbr> </strong> if you know how to take advantage of its flexibility. However, WordPress comes with a host of features which you probably won&#8217;t need if you&#8217;re using it as a CMS rather than a blogg &#8211; such as <strong>Comments</strong>, <strong>Links</strong>, and even <strong>Posts</strong>. So you might want to remove these, especially if you&#8217;re setting up a CMS for someone who&#8217;s inexperienced and/or have never used WordPress before. Cleaning up the <strong>Dashbaord </strong>and <strong>Editor </strong>by removing sections the users don&#8217;t need, users who are new to WordPress won&#8217;t be distracted by menu items and editor sections they&#8217;ll never need to use.</p>
<p><strong>Basically, by removing the excess funtions the users never need, WordPress feels more complete and functional as a CMS. This might make the learning curve a little less steep.</strong></p>
<p><span id="more-3"></span>Here&#8217;s a few things you might want to do:</p>
<h3>Hide Admin Panels</h3>
<p>It&#8217;s a good idea to clean up the <strong>Dashboard</strong>, and hide admin panels the users don&#8217;t need. For this I use <a href="http://wordpress.org/extend/plugins/hide-admin-panels/">Hide Admin Panels</a>, a plugin that let&#8217;s you do just what the name implies; hide panels from the <strong>Dashboard </strong>main menu, on a per-user-basis. If your users don&#8217;t use <strong>Links </strong>or <strong>Comments</strong>, they don&#8217;t need to see them in the <strong>Dashboard</strong>. Likewise, if your users only use <strong>Pages</strong>, hide the <strong>Post</strong> panel, et cetera.</p>
<p>(This, of course, has more potenial uses. For example, if the site you&#8217;re setting up has several users, where only some (or one) of them should have access to publish news, you simply hide the <strong>Post </strong>panel for those who shouldn&#8217;t have access.)</p>
<h3>&#8230; and rename the rest</h3>
<p>If you&#8217;re using WordPress as a CMS, some of the admin panels have names that average users don&#8217;t necessarily relate to. Maybe you want to change <strong>Posts </strong>to <strong>News</strong>, <strong>Pages </strong>to <strong>Content</strong>, and <strong>Media </strong>to <strong>Files</strong>? This is easily done. All you have to do is download <a href="http://svn.automattic.com/wordpress-i18n/pot/trunk/wordpress.pot">the latest language file</a> (or the latest one <a href="http://codex.wordpress.org/WordPress_in_Your_Language">in your language</a>, if you&#8217;re using a translation), open it in a POT-editor, for example <a href="http://www.poedit.net/">POEdit</a>, and change all instances of &#8220;Posts&#8221; to &#8220;News&#8221;, or whatever you like. This is a tedious and time-consuming task, but the good news is, once you&#8217;re done you can reuse your new language file on all your WordPress-sites.</p>
<p><strong>Read more about editing language files on <a href="http://codex.wordpress.org/Translating_WordPress">Translating WordPress</a>.</strong></p>
<h3>Hide Editor Sections</h3>
<p>It&#8217;s also a good idea to clean up the <strong>Editor</strong> (for <strong>Pages </strong>and <strong>Posts</strong>), by removing sections the users don&#8217;t need to see or use. For this I use <a href="http://wordpress.org/extend/plugins/more-fields/">More Fields</a>, a plugin with many uses (I&#8217;ll get back to some of them later), among them the opportunity to remove sections from the <strong>Editor</strong>. If your users don&#8217;t need <strong>Comments/Pingback</strong>, you hide that section. Likewise with <strong>Custom Fields</strong>, especially if you use them for certain functions you don&#8217;t want or need the users to see. Your users don&#8217;t need <strong>Excerpt</strong>? Remove it! You get the picture &#8230;</p>
<div class="shr-publisher-3"></div>]]></content:encoded>
			<wfw:commentRss>http://wpwizard.net/customizing-wordpress/setting-up-wordpress-as-a-cms-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

