<?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>StuckOn &#187; Wordpress</title>
	<atom:link href="http://www.stuckon.co.uk/news/wordpress/feed" rel="self" type="application/rss+xml" />
	<link>http://www.stuckon.co.uk</link>
	<description>Internet marketing services</description>
	<lastBuildDate>Sat, 31 Jul 2010 06:49:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>WordPress scheduling issue</title>
		<link>http://www.stuckon.co.uk/wordpress-scheduling-issue-1543.html</link>
		<comments>http://www.stuckon.co.uk/wordpress-scheduling-issue-1543.html#comments</comments>
		<pubDate>Tue, 05 Jan 2010 16:07:29 +0000</pubDate>
		<dc:creator>Cheryl</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.stuckon.co.uk/?p=1543</guid>
		<description><![CDATA[Anyone who upgraded their version of WordPress to 2.9 just before Christmas may have received a nasty surprise when they came back from the Christmas and New Year break. Those smart enough to have scheduled their content across Christmas and New Year could have found that none of their posts went live, thanks to a [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone who upgraded their version of <strong>WordPress</strong> to 2.9 just before Christmas may have received a nasty surprise when they came back from the Christmas and New Year break. Those smart enough to have scheduled their content across Christmas and New Year could have found that none of their posts went live, thanks to a bug in WordPress 2.9.</p>
<p>The chaps at WordPress have fixed this in their hurriedly released WordPress 2.9.1 (2.9 didn’t last long) but the damage for many will have already been done. Content is vitally important for <a href="http://www.stuckon.co.uk/seo-services/search-engine-optimisation"  class="alinks_links" onclick="return alinks_click(this);" title="SEO"  rel="external">SEO</a> and websites need to stay refreshed over inactive periods such as the Christmas and New Year break. Scheduling content is one of the best ways of ensuring this happens, but for WordPress to <span id="more-1543"></span>fail at this oh so simple task would be a mighty pain.</p>
<p>WordPress had <a href="http://wordpress.org/development/2010/01/wordpress-2-9-1/">this to say</a> about the ‘glitch’:</p>
<blockquote><p>After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we’re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of these issues affect you, give 2.9.1 a try.  Download 2.9.1 or upgrade automatically from the Tools-&gt;Upgrade menu in your blog’s admin area.</p></blockquote>
<p>Shame they couldn’t have tested that before releasing a new version that can cause posts to display that dreaded ‘missed schedule’ label in the dashboard – right before most businesses disappear for two weeks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.stuckon.co.uk/wordpress-scheduling-issue-1543.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exclude Pages plugin for WordPress</title>
		<link>http://www.stuckon.co.uk/exclude-pages-plugin-for-wordpress-413.html</link>
		<comments>http://www.stuckon.co.uk/exclude-pages-plugin-for-wordpress-413.html#comments</comments>
		<pubDate>Tue, 07 Jul 2009 12:06:33 +0000</pubDate>
		<dc:creator>Carl</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[SEO Advice]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.stuckon.co.uk/?p=413</guid>
		<description><![CDATA[Google’s head of spam, Matt Cutts, recently spoke about PageRank sculpting and how people’s efforts to ‘sculpt’ their PageRank by adding nofollow tags to unimportant pages were redundant. SEOs would add the Google created nofollow tag to links to pages such as ‘terms and conditions’ and ‘privacy policy’ pages so that the link juice, or [...]]]></description>
			<content:encoded><![CDATA[<p>Google’s head of spam, Matt Cutts, recently spoke about <a href="http://www.stuckon.co.uk/has-google-called-time-on-pagerank-sculpting-307.html">PageRank sculpting</a> and how people’s efforts to ‘sculpt’ their PageRank by adding nofollow tags to unimportant pages were redundant.</p>
<p>SEOs would add the Google created nofollow tag to links to pages such as ‘terms and conditions’ and ‘privacy policy’ pages so that the link juice, or PageRank, that existed on each page could be spread to more important, more deserving pages. This meant that if you had 6 links from your homepage, and 3 of them were nofollowed, the 3 that were followed would get a third of the PageRank each.</p>
<p>Matt Cutts now claims that the extra PageRank that would have been saved by nofollowing links is now lost in the ether, and suggests that webmasters <span id="more-413"></span>take more time to properly structure their websites rather than adding nofollow tags if they want to pass PageRank through to important pages.</p>
<p><a rel="attachment wp-att-414" href="http://www.stuckon.co.uk/exclude-pages-plugin-for-wordpress-413.html/exclude-pages"><img class="alignright size-full wp-image-414" style="margin-left: 6px; margin-right: 6px;" title="exclude-pages" src="http://www.stuckon.co.uk/wp-content/uploads/2009/07/exclude-pages.gif" alt="exclude-pages" width="378" height="209" /></a>Whether you believe Matt Cutts or not, and whether you believe that the extra PageRank really is ‘lost’, it’s definitely worthwhile looking at new ways to structure pages and to make sure that unimportant pages aren’t featured in navigation menus. For this purpose we recently started using the ‘<a href="http://wordpress.org/extend/plugins/exclude-pages/">Exclude Pages</a>’ plugin for WordPress. This plugin allows you to select pages that you don’t want included in your navigation, wherever pages may be listed.</p>
<p>So for example if you’ve used WordPress to create your Terms and Conditions page, and it’s appearing on your site in the navigation, this plugin can remove it from the list. By unchecking the box which appears on your ‘edit page’ section you’re able to remove any page from your navigation, so Google can’t follow it. This ensures that any PageRank isn’t lost in the ether, as Google seem to want to do.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.stuckon.co.uk/exclude-pages-plugin-for-wordpress-413.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 2.8 released yesterday, have you upgraded yet?</title>
		<link>http://www.stuckon.co.uk/wordpress-2-8-released-yesterday-have-you-upgraded-yet-322.html</link>
		<comments>http://www.stuckon.co.uk/wordpress-2-8-released-yesterday-have-you-upgraded-yet-322.html#comments</comments>
		<pubDate>Fri, 12 Jun 2009 14:46:00 +0000</pubDate>
		<dc:creator>Cheryl</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.stuckon.co.uk/?p=322</guid>
		<description><![CDATA[The release of a new version of WordPress used to fill us with dread as we run numerous websites on the platform. Why the feelings of dread and doom? Because when a new version of WordPress comes out you used to have go through every site copying the files across, changing the config file and [...]]]></description>
			<content:encoded><![CDATA[<p>The release of a new version of WordPress used to fill us with dread as we run numerous websites on the platform.</p>
<p>Why the feelings of dread and doom? Because when a new version of WordPress comes out you used to have go through every site copying the files across, changing the config file and then uploading the whole lot to the server, before running the upgrade program.</p>
<p>However, those clever people at WordPress saw this was tiresome and installed a one-click upgrade for the whole blog. Now when the dreaded ‘new version available’ link appears at the top of the WordPress dashboard, you don’t have head to <span id="more-322"></span>WordPress to download it and go through the lengthy process of upgrading all of your websites.</p>
<p>Just click the link, let WordPress do the rest!</p>
<p>Some of the nice features in this <a href="http://wordpress.org/development/2009/06/wordpress-28/">latest version of WordPress</a> are a better way of managing your widgets, more control over plugins (including the ability to delete files from the backend) and a much more in-depth theme manager.</p>
<p>The guys at WordPress have done well.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.stuckon.co.uk/wordpress-2-8-released-yesterday-have-you-upgraded-yet-322.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
