<?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>XC-Host -- Support Blog &#187; script</title>
	<atom:link href="http://xcblog.info/tag/script/feed/" rel="self" type="application/rss+xml" />
	<link>http://xcblog.info</link>
	<description></description>
	<lastBuildDate>Tue, 31 Aug 2010 07:47:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Keeping CMS / Blog Software up to date</title>
		<link>http://xcblog.info/keeping-cms-blog-software-up-to-date/</link>
		<comments>http://xcblog.info/keeping-cms-blog-software-up-to-date/#comments</comments>
		<pubDate>Thu, 29 Apr 2010 22:50:27 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[48]]></category>
		<category><![CDATA[48 hours]]></category>
		<category><![CDATA[500]]></category>
		<category><![CDATA[chmod]]></category>
		<category><![CDATA[compromised]]></category>
		<category><![CDATA[e107]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[hours]]></category>
		<category><![CDATA[mandatory]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[up to date]]></category>
		<category><![CDATA[updated]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://xcblog.info/?p=305</guid>
		<description><![CDATA[Just finished fixing two more sites that were giving 500 errors because of chmodded folders set to 777. I checked out one site at random and found an older install of wordpress running. As I&#8217;ve stated in the past you have to keep your installs up to date. Not doing so leaves the server open [...]]]></description>
			<content:encoded><![CDATA[<p>Just finished fixing two more sites that were giving 500 errors because of chmodded folders set to 777. I checked out one site at random and found an older install of wordpress running. As I&#8217;ve stated in the past you have to keep your installs up to date. Not doing so leaves the server open to potential exploits which in turn can cause the server to be compromised. That is why I offer to upgrade your wordpress installs whenever a new version comes out (minus 3.0 for now). All you have to do is submit a <a href="/support">Support Ticket</a>, send me an email or instant message on msn.<br />
As you also know I made this mandatory and your given 48 hours to fix the problem (or have me fix it) before the account is suspended. To see the specific post I&#8217;m talking about <a href="http://xcblog.info/2009/09/04/wordpress-attacks/" target="_blank">click here</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://xcblog.info/keeping-cms-blog-software-up-to-date/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Updated Server Status Script</title>
		<link>http://xcblog.info/updated-server-status-script/</link>
		<comments>http://xcblog.info/updated-server-status-script/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 16:17:53 +0000</pubDate>
		<dc:creator>Joe</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[host]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[mattf]]></category>
		<category><![CDATA[mjz]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[xc]]></category>

		<guid isPermaLink="false">http://xcblog.info/?p=157</guid>
		<description><![CDATA[I&#8217;ve given the link to some people. I&#8217;ve been using it since the inception of XC-Host because a friend (Matt) made it and let me use it. It&#8217;s always been good to have and has been in many screenshots.. A couple days ago I thought it was time I got with the times and find [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve given the link to some people. I&#8217;ve been using it since the inception of XC-Host because a friend (Matt) made it and let me use it. It&#8217;s always been good to have and has been in many screenshots.. A couple days ago I thought it was time I got with the times and find something that auto-updates and will actually email me when things go wrong. For security reasons some stuff has been removed / edited out. </p>
<p>This new script called status2k was originally introduced to me by mjz. Many, many years ago (pre xchost). I liked it but couldn&#8217;t afford the $20 or so it was to purchase it. I knew he had found it on wht (web hosting talk) so I eventually figured out his account name and spent a good 30 minutes going through every topic he ever posted in until I found it. Glad I did too because it&#8217;s changed A LOT since I last saw it <img src='http://xcblog.info/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />  Best money I&#8217;ve spent in a long time!! </p>
<p>For those of you completely lost check it out: <a href="http://xc-host.com/ss" target="_blank">http://xc-host.com/ss</a>. It&#8217;s now a link in the navigation as well <img src='http://xcblog.info/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>&#8211; Joe</p>
]]></content:encoded>
			<wfw:commentRss>http://xcblog.info/updated-server-status-script/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
