<?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>Weblog Tools Collection &#187; admin</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/admin/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Mon, 13 Feb 2012 13:00:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Adding Menus To The Admin Bar</title>
		<link>http://weblogtoolscollection.com/archives/2010/12/17/adding-menus-to-the-admin-bar/</link>
		<comments>http://weblogtoolscollection.com/archives/2010/12/17/adding-menus-to-the-admin-bar/#comments</comments>
		<pubDate>Fri, 17 Dec 2010 20:00:29 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[LinkyLoo]]></category>
		<category><![CDATA[WordPress FAQs]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[menus]]></category>
		<category><![CDATA[wpengineer]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=9239</guid>
		<description><![CDATA[As part of their ongoing series, WPEngineer has published a cool post that explains how to add new menus to the admin bar coming in WordPress 3.1. In the example, Frank adds a Codex Search button to the admin bar which is pretty convenient! He covers the function add_menu() and it&#8217;s various parameters as well. In the comments of that post however, Latz brings up an interesting point. Oh great, now every plugin will put a menu in the admin bar, Next stop: a plugin preventing others from cluttering the admin bar. While it&#8217;s pretty funny to think about the admin bar containing menus for all sorts of different plugins, it&#8217;s a potential problem that users may have to deal with in the future. Hopefully, plugin authors are diligent with not adding a menu to their options page as part of the default package of a plugin. For certain plugins, [...]]]></description>
			<content:encoded><![CDATA[<p>As part of their ongoing series, WPEngineer has published a cool post that explains <a href="http://wpengineer.com/2113/add-menus-to-the-admin-bar-of-wordpress/">how to add new menus</a> to the admin bar coming in WordPress 3.1. In the example, Frank adds a Codex Search button to the admin bar which is pretty convenient! He covers the function add_menu() and it&#8217;s various parameters as well. In the comments of that post however, <a href="http://wpengineer.com/2113/add-menus-to-the-admin-bar-of-wordpress/#comment-5651">Latz</a> brings up an interesting point.</p>
<blockquote><p>Oh great, now every plugin will put a menu in the admin bar, Next stop: a plugin preventing others from cluttering the admin bar.</p></blockquote>
<p>While it&#8217;s pretty funny to think about the admin bar containing menus for all sorts of different plugins, it&#8217;s a potential problem that users may have to deal with in the future. Hopefully, plugin authors are diligent with not adding a menu to their options page as part of the default package of a plugin. For certain plugins, the idea works well but not for all of them.</p>
<p>So while this is a neat little tutorial on how to add menus to the admin bar, are you worried that plugin developers may take this too far? </p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2010/12/17/adding-menus-to-the-admin-bar/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Flattered Or Ripped Off?</title>
		<link>http://weblogtoolscollection.com/archives/2010/01/06/flattered-or-ripped-off/</link>
		<comments>http://weblogtoolscollection.com/archives/2010/01/06/flattered-or-ripped-off/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 21:26:48 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[movabletype]]></category>
		<category><![CDATA[publishing]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=7481</guid>
		<description><![CDATA[WordPress fans are out in full force over the new admin interface presented in MovableType 5.1 which was released today. The controversy stems from how eerily similar the admin interface resembles the one that was introduced in WordPress 2.7. The similarities are easy to spot when you look at both interfaces side by side as evident by the post on BloggingPro.com. No doubt about it, the interfaces look the same albeit with MT&#8217;s added touches. While many fans of WordPress are giving Six Apart an earful, I&#8217;ve taken a bit more relaxed approach. One of the things that people constantly refer to WordPress for is its publishing interface. Since this interface is loved by many, is it really any surprise that something similar to it would appear in other publishing platforms? Also, I highly doubt WordPress was the first to have the layout that it does now. So with that [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress fans are out in full force over the new admin interface presented in <a href="http://www.movabletype.com/blog/2010/01/introducing-movable-type-5-1.html">MovableType 5.1</a> which was released today. The controversy stems from how eerily similar the admin interface resembles the one that was introduced in WordPress 2.7. The similarities are easy to spot when you look at both interfaces side by side as evident by the post on <a href="http://www.bloggingpro.com/archives/2010/01/06/six-apart-introduces-movable-type-5-with-interesting-new-dashboard-design/">BloggingPro.com</a>.</p>
<p><a href="http://weblogtoolscollection.com/wp-content/uploads/2010/01/mt5-dash.jpg" rel="thumbnail"><img src="http://weblogtoolscollection.com/wp-content/uploads/2010/01/mt5-dash.jpg" alt="" title="mt5-dash" width="585" height="260" class="aligncenter size-full wp-image-7482" /></a></p>
<p><a href="http://weblogtoolscollection.com/wp-content/uploads/2010/01/wordpress-dash.jpg" rel="thumbnail"><img src="http://weblogtoolscollection.com/wp-content/uploads/2010/01/wordpress-dash.jpg" alt="" title="wordpress-dash" width="585" height="352" class="aligncenter size-full wp-image-7483" /></a></p>
<p>No doubt about it, the interfaces look the same albeit with MT&#8217;s added touches. While many fans of WordPress are giving Six Apart an earful, I&#8217;ve taken a bit more relaxed approach. One of the things that people constantly refer to WordPress for is its publishing interface. Since this interface is loved by many, is it really any surprise that something similar to it would appear in other publishing platforms? Also, I highly doubt WordPress was the first to have the layout that it does now.</p>
<p>So with that in mind, if I were a core developer or someone involved with the UI for WordPress, I would be flattered to see another publishing system use a similar interface. To me, it&#8217;s further proof that the interface works.</p>
<p>What&#8217;s more interesting to me is that some folks have stated they like the MT version better than the WordPress one. I&#8217;m curious to hear from anyone who has used both interfaces to let me know why one is better than the other despite their similarity. </p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2010/01/06/flattered-or-ripped-off/feed/</wfw:commentRss>
		<slash:comments>59</slash:comments>
		</item>
		<item>
		<title>Distributed WordPress Admin Account Cracking</title>
		<link>http://weblogtoolscollection.com/archives/2009/11/30/distributed-wordpress-admin-account-cracking/</link>
		<comments>http://weblogtoolscollection.com/archives/2009/11/30/distributed-wordpress-admin-account-cracking/#comments</comments>
		<pubDate>Mon, 30 Nov 2009 19:37:45 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[cracking]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=7277</guid>
		<description><![CDATA[Bojan Zdrnja has published a post on the SANS Internet Storm Center blog today highlighting a distributed WordPress admin account cracking script. The script was discovered by one of the sites readers on a virtual private server (VPS). The acquired script is written in PHP and performs brute force cracking attempts to WordPress admin accounts. While this particular version is relatively simple, the power behind the script and the MySQL database allows the attacker to distribute the attacks not only by sites, but also by passwords tried as well. The article goes into detail explaining how the script works and suggests the typical security precautions such as using strong passwords, changing the admin username and limiting the admin login page to only your IP address. Brute force attacks on WordPress are nothing new but it&#8217;s interesting to see this approach using a distributed technique. Hat tip to WPVibe.]]></description>
			<content:encoded><![CDATA[<p>Bojan Zdrnja has <a href="http://isc.sans.org/diary.html?storyid=7663" target="_blank">published a post</a> on the SANS Internet Storm Center blog today highlighting a distributed WordPress admin account cracking script. The script was discovered by one of the sites readers on a virtual private server (VPS). The acquired script is written in PHP and performs brute force cracking attempts to WordPress admin accounts. </p>
<blockquote><p>While this particular version is relatively simple, the power behind the script and the MySQL database allows the attacker to distribute the attacks not only by sites, but also by passwords tried as well.</p></blockquote>
<p>The article goes into detail explaining how the script works and suggests the typical security precautions such as using strong passwords, changing the admin username and limiting the admin login page to only your IP address. Brute force attacks on WordPress are nothing new but it&#8217;s interesting to see this approach using a distributed technique. </p>
<p>Hat tip to <a href="http://twitter.com/wpvibe/statuses/6208163666" target="_blank">WPVibe</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2009/11/30/distributed-wordpress-admin-account-cracking/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>How Do You Do That?</title>
		<link>http://weblogtoolscollection.com/archives/2009/11/18/how-do-you-do-that/</link>
		<comments>http://weblogtoolscollection.com/archives/2009/11/18/how-do-you-do-that/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 12:55:08 +0000</pubDate>
		<dc:creator>James Dimick</dc:creator>
				<category><![CDATA[HOW-TO]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Discussions]]></category>
		<category><![CDATA[Wordpress for Beginners]]></category>
		<category><![CDATA[WordPress Tips]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[beginner]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[links]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[questions]]></category>
		<category><![CDATA[themes]]></category>
		<category><![CDATA[urls]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=7131</guid>
		<description><![CDATA[Ever wanted to do something in WordPress but just wasn&#8217;t sure how? In my experience this happens quite often, mostly with people new to WordPress. But, even the experts run into trouble sometimes. Today I thought I&#8217;d start a series of posts which will aim to explain how to do certain things in WordPress. Hopefully this will cover anything from quick tips and simple little functions, all the way up to more complex custom code and the like. So, stick around and you just might learn something. I think I&#8217;ll kick off the series with a couple simple ones&#8230; Why isn&#8217;t this plugin working with my theme? This is probably one of the most common issues I read about regarding WordPress. Sometimes even more experienced WPers can get this one wrong. Now, I&#8217;m not saying this is the solution to all problems between plugins and themes. Its just that this [...]]]></description>
			<content:encoded><![CDATA[<p>Ever wanted to do something in WordPress but just wasn&#8217;t sure how? In my experience this happens quite often, mostly with people new to WordPress. But, even the experts run into trouble sometimes. Today I thought I&#8217;d start a series of posts which will aim to explain how to do certain things in WordPress. Hopefully this will cover anything from quick tips and simple little functions, all the way up to more complex custom code and the like. So, stick around and you just might learn something. <img src='http://weblogtoolscollection.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I think I&#8217;ll kick off the series with a couple simple ones&#8230;</p>
<ul>
<li>
<h5>Why isn&#8217;t this plugin working with my theme?</h5>
<p>This is probably one of the most common issues I read about regarding WordPress. Sometimes even more experienced WP<em>ers</em> can get this one wrong. Now, I&#8217;m not saying this is the solution to <strong>all</strong> problems between plugins and themes. Its just that this little bugger is often the culprit.</p>
<p>Try ensuring that your theme has <code>&lt;?php <a href="http://codex.wordpress.org/Theme_Development#Plugin_API_Hooks">wp_head</a>() ?&gt;</code> somewhere inside the <code>&lt;head&gt;</code> section of the document. Also, for that matter, make sure it has <code>&lt;?php <a href="http://codex.wordpress.org/Theme_Development#Plugin_API_Hooks">wp_footer</a>() ?&gt;</code> somewhere in the foot of the document; Before the <code>&lt;/body&gt;</code> tag.</p>
<p>If your theme lacks these function calls many plugins that manipulate your theme will not be able to hook into the required areas. This can cause many headaches.</p>
<p>If you have no idea what I&#8217;m talking about, you may be better off having a coder buddy take a look at the theme for you. Or you can also contact the theme author, if the theme you use was created by someone else.</li>
<li>
<h5>How come my URLs are yucky?</h5>
<p>Or, &#8220;<em>How come my URLs look like <code>www.mysite.com?p=123</code> instead of <code>www&#8203;.mysite.&#8203;com&#8203;/my-&#8203;sample-&#8203;post/</code>?</em>&#8221;</p>
<p>This one is right up there with the previous question. I see it all the time. However, more and more web hosts these days support the &#8220;<em>nice</em>&#8221; URLs by default without requiring any extra effort. So, its just a matter of going into the WordPress control panel, changing your Permalink Settings and then saving. Unfortunately, we&#8217;re not all this lucky&#8230;</p>
<p>The first thing to try would be to contact your web host support and make sure they have whats known as <code>mod_rewrite</code> <em>(or similar functionality)</em> enabled on your account. If such functionality is not available on your web host, and you really need this feature, you may need to upgrade to a new host that does support it.</p>
<p>If your host does support it and has it enabled on your account, but it still doesn&#8217;t work, you can check that WordPress is able to write to the <code>.htaccess</code> file <em>(which is where all the &#8220;nice&#8221; URL magic happens)</em>.</p>
<p>For WordPress, on Unix-based systems, the htaccess file should be &#8220;<em><code><a href="http://codex.wordpress.org/Changing_File_Permissions#About_Chmod">CHMOD</a></code>ed</em>&#8221; to at least <code>666</code>. On Windows-based systems the procedure is a bit different. It can be different depending on your particular setup so I won&#8217;t go into that.</p>
<p>Basically, as was the case with the previous question, you may need to seek help to figure this out. If you don&#8217;t have a code buddy, get one! They are really great to have around. Just make sure you buy them a nice gift for their trouble. <img src='http://weblogtoolscollection.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </li>
<li>
<h5>Can I have a link to login to WordPress somewhere in my theme?</h5>
<p>Sure! It&#8217;s actually easier than you might think&#8230;</p>
<p>Some themes have a link for that already. But, there are also some that seem to lack this obvious and simple feature. You can easily add this to any theme yourself. No need for any programming knowledge. Simply add <code>&lt;?php <a href="http://codex.wordpress.org/Function_Reference/wp_loginout">wp_loginout</a>() ?&gt;</code> somewhere in your theme and you&#8217;re done. Easy right?</p>
<p>Another nice function along the same lines is <code>&lt;?php <a href="http://codex.wordpress.org/Function_Reference/wp_register">wp_register</a>() ?&gt;</code>, which will show a link to your registration page <em>(if your settings allow users to register)</em>, or a link to the WordPress control panel if you are already logged in.</p>
<p>Do note though that by default the link will be output wrapped inside <code>&lt;li&gt;</code> tags. This is so you can include the link in a list of other links, like a &#8220;<em>meta</em>&#8221; section. If, however, that is not how you want it to be output you can use the function like <code>&lt;?php wp_register('', '') ?&gt;</code>. That will simply output the link and nothing else.</p>
<p>An example of how to customize that is something like <code>&lt;?php wp_register('&lt;p&gt;', '&lt;/p&gt;') ?&gt;</code>, which will output the link wrapped in its own paragraph. Just change the opening and closing tags in the function to make it output how you want. Dead simple!</li>
</ul>
<p>That&#8217;s all for now&#8230; I hope it helps!</p>
<p style="background-color:#fae8d3;padding:5px 10px;margin-bottom:20px">Do you have a question about WordPress? Want to see it answered here on Weblog Tools Collection? If so, please <a href="http://weblogtoolscollection.com/archives/2007/02/06/contact-me/">send us an E-Mail</a> or drop a comment here. Your question just might be featured in the series!</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2009/11/18/how-do-you-do-that/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>For The Love Of 2.3</title>
		<link>http://weblogtoolscollection.com/archives/2008/06/26/for-the-love-of-23/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/06/26/for-the-love-of-23/#comments</comments>
		<pubDate>Thu, 26 Jun 2008 11:58:06 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[LinkyLoo]]></category>
		<category><![CDATA[WordPress Templates WordPress Skins WordPress Themes]]></category>
		<category><![CDATA[2.3]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[colors]]></category>
		<category><![CDATA[colorscheme]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=3685</guid>
		<description><![CDATA[James Dimick, author of the Easy Admin Color Schemes plugin for WordPress has released a color scheme based exclusively on WordPress 2.3. Now, when you install this plugin, the default color scheme selected is called &#8220;For the Love of 2.3&#8221; which will take the new WordPress and make it look like the old. Something many WordPressers have wanted since the release of 2.5. However, James mentions that: It isn’t a completely faithful recreation but I think it’s pretty darn close. The scheme was created purely from CSS with no modifications to the core code. So while you might not be able to make WordPress 2.5 look similar to the way WordPress 2.3 did in terms of the user interface, you can at least slap on old faithful for that nostalgic look.]]></description>
			<content:encoded><![CDATA[<p>James Dimick, author of the <a href="http://www.jamesdimick.com/creations/easy-admin-color-schemes/">Easy Admin Color Schemes</a> plugin for WordPress has released a color scheme based exclusively on WordPress 2.3. Now, when you install this plugin, the default color scheme selected is called &#8220;<strong>For the Love of 2.3</strong>&#8221; which will take the new WordPress and make it look like the old. Something many WordPressers have wanted since the release of 2.5. However, James mentions that:</p>
<blockquote><p>It isn’t a completely faithful recreation but I think it’s pretty darn close.</p></blockquote>
<p style="text-align: center;"><a href="http://weblogtoolscollection.com/b2-img/2008/06/for-the-love-of-23-big.gif" rel="thumbnail"><img src="http://weblogtoolscollection.com/b2-img/2008/06/for-the-love-of-23-big-262x300.gif" alt="2.3 Old Style Color Scheme" title="2.3 Old Style Color Scheme" class="alignnone size-medium wp-image-3686 aligncenter" height="300" width="262" /></a></p>
<p>The scheme was created purely from CSS with no modifications to the core code. So while you might not be able to make WordPress 2.5 look similar to the way WordPress 2.3 did in terms of the user interface, you can at least slap on old faithful for that nostalgic look.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/06/26/for-the-love-of-23/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Create Your Own Admin Color Scheme</title>
		<link>http://weblogtoolscollection.com/archives/2008/05/03/create-your-own-admin-color-scheme/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/05/03/create-your-own-admin-color-scheme/#comments</comments>
		<pubDate>Sat, 03 May 2008 19:31:42 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[backend]]></category>
		<category><![CDATA[colorschemes]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[easyadmin]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=3487</guid>
		<description><![CDATA[Here at WeblogToolsCollection.com, we have already discussed how you can change the color scheme in the WordPress 2.5 administration panel from Classic to Fresh. We have also highlighted an awesome plugin that was written by Kaspars which gives users up to 8 different color schemes to choose from. However, what if you want to create your own color scheme? Thanks to a plugin written by James Dimick called Easy Admin Color Schemes, users can now create their own flavor of the WordPress 2.5 back end. After downloading and installing the plugin, you can access it by browsing to SETTINGS-COLOR SCHEMES. There are three color schemes to start you off, Classic, Fresh and Washedout. The plugin does not allow you to delete nor edit the Classic and Fresh color schemes. This makes sense as you wouldn&#8217;t want to screw up a default skin only to have to reinstall WordPress to fix [...]]]></description>
			<content:encoded><![CDATA[<p>Here at WeblogToolsCollection.com, we have <a title="http://weblogtoolscollection.com/archives/2008/03/16/colorful-future-for-wp-25-admin/" href="http://weblogtoolscollection.com/archives/2008/03/16/colorful-future-for-wp-25-admin/" target="_blank">already discussed</a> how you can change the color scheme in the WordPress 2.5 administration panel from Classic to Fresh. We have also highlighted an <a title="http://weblogtoolscollection.com/archives/2008/04/20/baltic-amber-admin-colour-schemes-for-wordpress-25/" href="http://weblogtoolscollection.com/archives/2008/04/20/baltic-amber-admin-colour-schemes-for-wordpress-25/" target="_blank">awesome plugin</a> that was written by Kaspars which gives users up to 8 different color schemes to choose from. However, what if you want to create your own color scheme? Thanks to a plugin written by James Dimick called <a title="http://www.jamesdimick.com/creations/easy-admin-color-schemes/" href="http://www.jamesdimick.com/creations/easy-admin-color-schemes/" target="_blank">Easy Admin Color Schemes</a>, users can now create their own flavor of the WordPress 2.5 back end.</p>
<p style="text-align: center;"><a href="http://weblogtoolscollection.com/b2-img/2008/04/defaultcolorschemes.png" rel="thumbnail"><img class="alignnone size-full wp-image-3488 aligncenter" title="defaultcolorschemes" src="http://weblogtoolscollection.com/b2-img/2008/04/defaultcolorschemes.png" alt="Default Easy Admin Color Schemes" width="254" height="173" /></a></p>
<p>After downloading and installing the plugin, you can access it by browsing to <strong>SETTINGS-COLOR SCHEMES. </strong>There are three color schemes to start you off, <strong>Classic, Fresh and Washedout</strong>. The plugin does not allow you to delete nor edit the Classic and Fresh color schemes. This makes sense as you wouldn&#8217;t want to screw up a default skin only to have to reinstall WordPress to fix the issue. However, you can edit the Washedout color scheme which introduces you to the plugins functionality.</p>
<p>The plugin starts off by giving you the chance to name your color scheme. Next, give your color scheme four primary colors. If you don&#8217;t know of a six digit color code, there is a small arrow to the right of the text field that will open up a color picker. Opening the color picker and then selecting a color will automatically place the corresponding color code into the text field.</p>
<p style="text-align: center;"><a href="http://weblogtoolscollection.com/b2-img/2008/04/editingthecolors.png" rel="thumbnail"><img class="alignnone size-medium wp-image-3489 aligncenter" title="editingthecolors" src="http://weblogtoolscollection.com/b2-img/2008/04/editingthecolors-300x181.png" alt="Creating your own color scheme" width="300" height="181" /></a></p>
<p>Once you have your four primary colors in order, the next step which is the longest of them all is to go through all of the CSS specific code and change the color code values to something else you prefer. There at least 10 different CSS files which make up the styling of the administration panel. There are more if you want to include support for<strong> RIGHT TO LEFT</strong> text. This plugin takes all of those CSS files and puts them in one place for you to edit, which makes things so much easier. Also, for those who have javascript enabled in their browser, you can view a live preview of what the changes will look like on an active WordPress administration page.  Very handy as it cuts down on the browser refreshes.</p>
<p>One thing that I think this plugin is missing is an easy way for users to share their creations. If a download or save link could be added to the color schemes which would automatically package the necessary files together which could then be saved to my desktop for distribution, this would make the plugin a home run.</p>
<p>If you are looking at adding some spice to your WordPress back end, give this plugin a try. I don&#8217;t think it could be any easier than this plugin. The only problem with creating a color scheme is figuring out where each CSS class or DIV is defined. That&#8217;s where <a title="https://addons.mozilla.org/en-US/firefox/addon/1843" href="https://addons.mozilla.org/en-US/firefox/addon/1843" target="_blank">FireBug</a> comes in.</p>
<p>Good luck and if you happen to create a color scheme using this plugin, be sure to say so in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/05/03/create-your-own-admin-color-scheme/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/admin/feed/ ) in 0.75309 seconds, on Feb 14th, 2012 at 1:34 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 2:34 pm UTC -->
