<?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>Calva</title>
	<atom:link href="http://calvaweb.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://calvaweb.com</link>
	<description></description>
	<lastBuildDate>Thu, 16 Feb 2012 11:03:55 +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>Chrome moves into second place above Firefox in the internet browser market</title>
		<link>http://calvaweb.com/2012/01/27/ie-and-firefox-slowely-loosing-ground-to-chrome-in-the-uk-internet-browser-market/</link>
		<comments>http://calvaweb.com/2012/01/27/ie-and-firefox-slowely-loosing-ground-to-chrome-in-the-uk-internet-browser-market/#comments</comments>
		<pubDate>Fri, 27 Jan 2012 16:23:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Industry News]]></category>

		<guid isPermaLink="false">http://calvaweb.com/?p=419</guid>
		<description><![CDATA[Chrome overtook Firefox at the end of 2011 to become the second most widely used internet web browser after Internet Explorer. ]]></description>
			<content:encoded><![CDATA[<p>Chrome overtook Firefox at the end of 2011 to become the second most widely used internet web browser after Internet Explorer (StatsCounter statistics source).  Slowly but surely, both Internet explorer and Firefox are losing ground to Chrome.</p>
<div id="attachment_424" class="wp-caption alignnone" style="width: 574px"><a href="http://calvaweb.com/wp-content/uploads/2012/01/StatCounter-browser-ww-monthly-201112-201112-bar.jpg"><img class=" wp-image-424   " title="Internet Browser Usage December 2011 (StatsCounter)" src="http://calvaweb.com/wp-content/uploads/2012/01/StatCounter-browser-ww-monthly-201112-201112-bar.jpg" alt="Internet Browser Usage December 2011 (StatsCounter)" width="564" height="365" /></a>
<p class="wp-caption-text">Internet Browser Usage December 2011 (StatsCounter)</p>
</div>
<p>&nbsp;</p>
<p>Six months ago in July 2011 it was a different picture with Firefox still maintaining a comfortable lead on Chrome, but since then both Internet Explorer and Firefox have lost some ground to Chrome, with the majority of ground being lost to Internet Explorer. If this trend continues Chrome could also overtake Internet Explorer to become the most widely used web browser.</p>
<div id="attachment_425" class="wp-caption alignnone" style="width: 574px"><a href="http://calvaweb.com/wp-content/uploads/2012/01/StatCounter-browser-ww-monthly-201107-201107-bar.jpg"><img class=" wp-image-425   " title="Internet Browser Usage July 2011 (StatsCounter)" src="http://calvaweb.com/wp-content/uploads/2012/01/StatCounter-browser-ww-monthly-201107-201107-bar.jpg" alt="Internet Browser Usage July 2011 (StatsCounter)" width="564" height="365" /></a>
<p class="wp-caption-text">Internet Browser Usage July 2011 (StatsCounter)</p>
</div>
<h3>What are the implications for web development?</h3>
<p>This is a positive change for web developers. In general websites do not work as well in Internet Explorer as it displays web pages incorrectly causing formatting issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://calvaweb.com/2012/01/27/ie-and-firefox-slowely-loosing-ground-to-chrome-in-the-uk-internet-browser-market/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Calva moves to a new dedicated server</title>
		<link>http://calvaweb.com/2011/11/22/calva-moves-to-a-dedicated-server/</link>
		<comments>http://calvaweb.com/2011/11/22/calva-moves-to-a-dedicated-server/#comments</comments>
		<pubDate>Tue, 22 Nov 2011 13:37:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Asides]]></category>

		<guid isPermaLink="false">http://localhost.com/wp/?p=86</guid>
		<description><![CDATA[I am very excited to announce that we have moved our website to a faster dedicated server hosted with virtualDCS, a Leeds based company specialising in high availablility web hosting. So far the support has been very good and whenever we have raised any issues, they have been resolved very quickly.]]></description>
			<content:encoded><![CDATA[<p>I am very excited to announce that we have moved our website to a faster dedicated server hosted with <a href="http://www.virtualdcs.co.uk/">virtualDCS</a>, a Leeds based company specialising in high availablility web hosting. So far the support has been very good and whenever we have raised any issues, they have been resolved very quickly.</p>
]]></content:encoded>
			<wfw:commentRss>http://calvaweb.com/2011/11/22/calva-moves-to-a-dedicated-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Website upgrades &#8211; avoiding common pitfalls</title>
		<link>http://calvaweb.com/2011/10/10/website-upgrades-avoiding-errors/</link>
		<comments>http://calvaweb.com/2011/10/10/website-upgrades-avoiding-errors/#comments</comments>
		<pubDate>Mon, 10 Oct 2011 19:17:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://localhost.com/wp/?p=80</guid>
		<description><![CDATA[Ever find that your website stopped working after performing a relatively standard upgrade? All website have bugs and the only way to safeguard against passing them onto your website visitors, is to first test your upgrade.]]></description>
			<content:encoded><![CDATA[<p>Upgrade errors can range from relatively minor formatting issues causing the pages to be displayed incorrectly through to more serious problems where the page is not shown at all, but instead replaced with an <strong>internal server error</strong> or <strong>page cannot be displayed</strong>. </p>
<h3>Step 1: Test the upgrade first on a staging site</h3>
<p>In order to minimise the amount of downtime for your website (ie where it is unavailable), the upgrade should first be tested on a separate &#8216;staging&#8217; website. A staging site refers to a website setup as closely as possible to the live site including all files and databases, so that the upgrade can be tested under the exact same conditions.</p>
<p>The staging site should be setup on the same web server as the live site since differences in web server configurations can cause different results when testing your site. Normally the staging site is run on a sub-domain of the live site (ie staging.yoursite.com).</p>
<h3>Step 2: Restrict access to your live site during an upgrade</h3>
<p>Website access to your live site should be restricted during an upgrade, offering you time to check everything works <strong>before</strong> allowing anyone else access to it.</p>
<p>Access to your website can be restricted by IP address. An IP address is a numerical identifier assigned to each device when it connects to the internet. Finding out what your IP address is very easy and can be done with one of the many online tools such as <a href="http://getmyipaddress.org/" rel="nofollow">www.getmyipaddress.org</a>.</p>
<p>The web server can be configured to allow visitors from selected IP addresses access to your website whilst redirecting visitors with other IP addresses to a holding page. This holding page is normally a static web page which can sit outside your main website folder. It usually has some text to inform the visitor that the website is temporarily unavailable due to maintenance. Adding a time when you expect the website to be back up and running is also useful for visitors who see the page.  </p>
<h3>A warning about automatic upgrades</h3>
<p>With some open source software such as WordPress, there is an option to automatically upgrade your website to the latest release via a link in the admin section. However proper testing of the upgrade should still be carried out, since customisation of the standard software via plugins, themes or bespoke web development can present new scenarios on the website which have not been previously tested.</p>
<p><img class="imageborder size-full wp-image-103 alignnone" title="wordpress updates screen" src="http://calvaweb.com/wp-content/uploads/2011/07/wordpress-updates.jpg" alt="wordpress updates screen" width="497" height="262" /></p>
<h3>Most important: take a backup</h3>
<p>I almost forgot to mention this since it seems fairly obvious, but the most important thing you can do before updating your live site is to take a backup of all the files and databases for that website, so that you can revert back to the previous version, if the upgrade doesn&#8217;t work. Even if you didn&#8217;t bother doing anything else, you should always <strong>take a backup</strong> !   </p>
]]></content:encoded>
			<wfw:commentRss>http://calvaweb.com/2011/10/10/website-upgrades-avoiding-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

