<?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>www.vegard.net &#187; WordPress</title>
	<atom:link href="http://www.vegard.net/archives/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vegard.net</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:26: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>Responsive.</title>
		<link>http://www.vegard.net/archives/4872/</link>
		<comments>http://www.vegard.net/archives/4872/#comments</comments>
		<pubDate>Thu, 19 Jan 2012 20:22:50 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Redesign]]></category>
		<category><![CDATA[Site News]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=4872</guid>
		<description><![CDATA[It&#8217;s been a few days now since WordCamp and everything has begun to sink in a little. Here are my main bullet points from the event: WordPress is huge. It&#8217;s no longer a pain in the ass to run on Windows. Responsive web design is the way to go. Plugin development is something I&#8217;d like [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a few days now since WordCamp and everything has begun to sink in a little. Here are my main bullet points from the event:</p>
<ul>
<li>WordPress is huge.</li>
<li>It&#8217;s no longer a pain in the ass to run on Windows.</li>
<li>Responsive web design is the way to go.</li>
<li>Plugin development is something I&#8217;d like to dive deeper into.</li>
<li>I discovered the distraction free writing feature.</li>
</ul>
<p>In the short term, responsive web design was the presentation that triggered me the most. I&#8217;m familiar with response web design and use a lot of responsive sites. Even this site is somewhat responsive, it&#8217;ll remove some white space on a device with a smaller screen, for instance a tablet device. Now I want to make the site&#8217;s design even more responsive and better looking on mobile devices. <a href="http://wordpress.org/extend/plugins/wptouch/" rel="external">WPtouch</a> is a great plugin, but when it&#8217;s possible to get the site to look familiar even on small screen, there&#8217;s really no need to use it.</p>
<p>One option would be to make the current theme more responsive, but that will probably be a lot of work for someone like me. Also, from past attempts to do my own redesign from scratch, I know my limitations. So my best bet is what I always do: Find a nice looking, free theme and hack away!</p>
<p>I&#8217;ve been looking around a little, and at this point <a href="http://renova.llow.it/wordpress/" rel="external">Renova</a> seems like a good option. But I&#8217;d prefer to have two columns, not just one. That can probably be arranged, though. It might take a while, but I&#8217;m positive the next design will be responsive. For more responsive goodness, have a look at the <a href="http://mediaqueri.es/" rel="external">Media Queries</a> showcase.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/4872/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>It&#8217;s WordCamp!</title>
		<link>http://www.vegard.net/archives/4822/</link>
		<comments>http://www.vegard.net/archives/4822/#comments</comments>
		<pubDate>Sat, 14 Jan 2012 07:14:00 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">https://www.vegard.net/?p=4822</guid>
		<description><![CDATA[Here we are. It&#8217;s the 14th of Januar and the first of what will hopefully be annual WordCamp Norway. The event is sold out, the presenters look sharp and judging by the attendees list, the crowd is good looking. Even though no one is reading this, I intend to update with pictures throughout the day. [...]]]></description>
			<content:encoded><![CDATA[<p>Here we are. It&#8217;s the 14th of Januar and the first of what will hopefully be annual WordCamp Norway. The event is sold out, the presenters look sharp and judging by the <a href="http://2012.norway.wordcamp.org/om/deltakere/" rel="external">attendees list</a>, the crowd is good looking. Even though no one is reading this, I intend to update with pictures throughout the day. I&#8217;m using the Android WordPress app, and I have to admit I&#8217;m struggling a bit with it. But we&#8217;ll send how it works out.</p>
<p>At least I managed to <strike>write</strike> wrestle through this entry and schedule it yesterday!</p>
<p>09:53 CET: After a good morning walk I&#8217;m at Thon Hotell Opera. I&#8217;ve got my name tag and t-shirt (another one of them convention t-shirts you never use) and the main room is starting to fill up, but it&#8217;s not crowded enough for a picture yet. I&#8217;ve seen one familiar face, one of the presenters &#8211; who looked somewhat hung over. There&#8217;s public Wi-Fi, by the way. I&#8217;m <a href="/archives/4784/">not connecting</a>.</p>
<p>I&#8217;ve been trying to use the Android WordPress app to update, but holy crap, the thing is unstable when handling images: Crashes, XML parsing errors, disappearing updates. The WordPress app has them all. So I fell back to using Opera Mobile, which works, but it&#8217;s not ideal since the WordPress admin GUIDE isn&#8217;t exactly exactly made for mobile.</p>
<p>11:25 CET: After Hanni Ross&#8217; opening remarks I know now even more ways how to contribute to WordPress. Not sure where she got the percentages on the Norwegian translations of WordPress, though, because they don&#8217;t match the ones on translate.wordpress.org. And now: &#8220;Writing a plugin&#8221; by Morten Hauan. Title in English, presentation in Norwegian. Trailer fraud? </p>
<p>12:08 CET: Hauan gave a great introduction to plugin writing in WordPress. I&#8217;ve only touched the surface of plugin development in WordPress myself, and got some ideas on how to change wp-days-ago with what I learned. Next up: &#8220;Responsive Web Design&#8221; by Wilhem Joys Andresen. Voted best dressed this evening.</p>
<p>12:38 CET: Woah, that was fast! Wilhem, former Opera Software employee, now independent consultant, briefly took us through media queries. Nothing new and groundbreaking, but the more you talk about it, the greater the chance designers around the world will see the light. It&#8217;s the future, man (and it started way back in 2001). Unlike 99% of other presenters, Joys Andresen finished twenty minutes before schedule. Soon it&#8217;s time for lunch and a room packed with nerds awkwardly socializing. </p>
<p>13:57 CET: We&#8217;re back from lunch and I&#8217;m happy to report that there will be <em>no</em> pictures of food. But the lunch was nice. Next Marko Heijnen will tell us how to create native apps with WordPress. Rumors have it that the hipster phone will be involved. Maybe Marko knows something about the bugs in the Android client as well. </p>
<p>14:31 CET: And Marko is done. Must have been a nightmare for the interpreters to handle that one. Not as much native focus as I&#8217;d hoped, but gave a good introduction to how you can use WordPress while thinking way out of the box. </p>
<p>14:52 CET: I don&#8217;t know about you, but I just had a powernap. Feeling fresh an ready for Josh Holmes, who will tell us how to run WordPress on Windows. My experience: Noooooo!</p>
<p>16:01 CET: Josh is done and I&#8217;m not scared of running WordPress on Windows anymore. The rest of the pack is preparing for lighting sessions, while I&#8217;m heading out to do some errands. Back at 17:00 sharp for Zé Fontainhas&#8217; keynote. </p>
<p>17:01 CET: Let the keynote commence!</p>
<p>17:38 CET: Aaand we&#8217;re done. Zé took us through the history of WordPress and took a quick look into the future. Certainly interesting stuff, followed by a good Q&#038; A session. </p>
<p>I&#8217;m coming back next year. Given that there will be a next year, of course. </p>
<p>Pictures after the break. <span id="more-4822"></span> </p>
<p><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-10-17-44-575.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-10-17-44-575-650x487.jpg" alt="" title="Scott Basgaard says hello. And someone brought their own interpreter. " width="650" height="487" class="aligncenter size-medium wp-image-4839" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-10-18-30-561.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-10-18-30-561-650x487.jpg" alt="" title="Matt, aka WordPress-Jesus, is also saying welcome. He&#039;s all grown up now!" width="650" height="487" class="aligncenter size-medium wp-image-4840" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-11-32-37-645.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-11-32-37-645-650x487.jpg" alt="" title="Morten Hauan with a great introduction to plugin writing in WordPress. Personal slogan: Every time you hack the core, God kills a kitten. Smart guy. " width="650" height="487" class="aligncenter size-medium wp-image-4845" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-12-14-34-250.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-12-14-34-250-650x487.jpg" alt="" title="Responsive Web Design with Wilhem Joys Andresen. Media queries is the dominant topic of his lightning talk." width="650" height="487" class="aligncenter size-medium wp-image-4848" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-14-07-18-016.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-14-07-18-016-650x487.jpg" alt="" title="Marko Heijnen: Creating native apps with WordPress." width="650" height="487" class="aligncenter size-medium wp-image-4853" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-14-57-11-862.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-14-57-11-862-650x487.jpg" alt="" title="Josh Holmes, and enthusiastic guy talking about WordPress on Windows." width="650" height="487" class="aligncenter size-medium wp-image-4859" /></a><a href="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-17-03-12-1601.jpg"><img src="http://www.vegard.net/wp-content/uploads/2012/01/2012-01-14-17-03-12-1601-650x487.jpg" alt="" title="Zé Fontainhas giving his keynote." width="650" height="487" class="aligncenter size-medium wp-image-4864" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/4822/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordCamp Norway 2012.</title>
		<link>http://www.vegard.net/archives/4652/</link>
		<comments>http://www.vegard.net/archives/4652/#comments</comments>
		<pubDate>Wed, 21 Dec 2011 21:11:33 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=4652</guid>
		<description><![CDATA[Once upon a time I made a piece of blogging software written in PHP. Inspired by Blogger, I named it &#8220;Bugger&#8221;. Childish, but an appropriate name: It was a buggy bugger. Still, it did its job well and since I was the one responsible for everything, I had a rather intimate relationship with the code, [...]]]></description>
			<content:encoded><![CDATA[<p>Once upon a time I made a piece of blogging software written in PHP. Inspired by <a href="http://www.blogger.com/" rel="external">Blogger</a>, I named it &#8220;Bugger&#8221;. Childish, but an appropriate name: It was a buggy bugger. Still, it did its job well and since I was the one responsible for everything, I had a rather intimate relationship with the code, making the software easy to extend when I needed new features. Open sourcing it was never an option, though, anyone else trying to maintain the code probably would have gone crazy &#8211; the curse of many one-man projects.</p>
<p>About three years ago, I called it quits, buried Bugger and <a href="/archives/1329/">switched</a> to <a href="http://www.wordpress.org/" rel="external">WordPress</a>. To be honest, I&#8217;ve never looked back. WordPress is, like Bugger, written in PHP and has, unlike Bugger, a thriving community of developers and designers who release tons of WordPress themes and plugins. I&#8217;ve written a plugin myself, <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">wp-days-ago</a> and I&#8217;m hosting my own WordPress installation on <a href="http://www.vbox-host.com/" rel="external">vbox-host.com</a>.</p>
<p>In short; I like WordPress. Now I&#8217;m going to my first WordCamp in January next year. The first ever WordCamp in Norway will be held in Oslo, more information is available <a href="http://2012.norway.wordcamp.org/" rel="external">on the official WordCamp Norway site</a>. The speaker list so far includes Isaac Keyet, John James Jacoby, Zé Fontainhas (all three Automattic employees), Magnus Jepson (WooThemes) and even a guy from my employer.</p>
<p>Right now there are only <strike>58</strike> <strike>54</strike> 48 tickets left so if you are an avid WordPress user, quickly <a href="http://2012.norway.wordcamp.org/pamelding/" rel="external">grab a ticket</a> &#8211; they are quite cheap &#8211; and get ready for WordCamp Norway 2012!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/4652/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>22 Essential WordPress Plugins.</title>
		<link>http://www.vegard.net/archives/4000/</link>
		<comments>http://www.vegard.net/archives/4000/#comments</comments>
		<pubDate>Sat, 30 Jul 2011 18:45:51 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=4000</guid>
		<description><![CDATA[All right, so &#8220;essential&#8221; might be a small exaggeration, but these are still plugins that every WordPress power-user should consider installing. And of course you&#8217;re a power-user, right? 1. After The Deadline After The Deadline uses artificial intelligence to check spelling, style, and grammar in WordPress. 2. Akismet Used by millions, Akismet is quite possibly [...]]]></description>
			<content:encoded><![CDATA[<p>All right, so &#8220;essential&#8221; might be a small exaggeration, but these are still plugins that every <a href="http://wordpress.org/" rel="external">WordPress</a> power-user should consider installing. And of course you&#8217;re a power-user, right?</p>
<h4>1. After The Deadline</h4>
<p><a href="http://wordpress.org/extend/plugins/after-the-deadline/" rel="external">After The Deadline</a> uses artificial intelligence to check spelling, style, and grammar in WordPress.</p>
<h4>2. Akismet</h4>
<p>Used by millions, <a href="http://wordpress.org/extend/plugins/akismet/" rel="external">Akismet</a> is quite possibly the best way in the world to protect your blog from comment and trackback SPAM. It keeps your site protected from spam even while you sleep. I can vouch for its effectiveness, very little SPAM gets through. As of right now, Akismet has blocked 23,287 SPAM comments on my humble site.</p>
<h4>3. All in One SEO Pack</h4>
<p>The <a href="http://wordpress.org/extend/plugins/all-in-one-seo-pack/" rel="external">All in One SEO Pack</a> Automatically optimizes your WordPress blog for Search Engines (Search Engine Optimization). Some features include support for Custom Post Types, automatic optimizing of titles for search engines and automatic META tags generation.</p>
<p><span id="more-4000"></span></p>
<h4>4. Contact Form 7</h4>
<p><a href="http://wordpress.org/extend/plugins/contact-form-7/" rel="external">Contact Form 7</a> can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on. I&#8217;m using this plugin on two pages; <a href="/one-liners/#contact">One-liners</a> and <a href="/about/#contact">About</a> and it works as advertised.</p>
<h4>5. FancyBox for WordPress</h4>
<p><a href="http://wordpress.org/extend/plugins/fancybox-for-wordpress/" rel="external">FancyBox for WordPress</a> Seamlessly integrates <a href="http://fancybox.net/">FancyBox</a> into your blog: Upload, activate, and you&#8217;re done. No further configuration needed. However, you can customize it from the Options Page if you like. It took quite a bit of tweaking for me to get this plugin to work exactly as I wanted, but as soon as I was happy with it, I started using it in every entry with pictures, for instance <a href="/archives/3854/">España</a>, which I posted only a few days ago.</p>
<h4>6. Google Analyticator</h4>
<p><a href="http://wordpress.org/extend/plugins/google-analyticator/" rel="external">Google Analyticator</a> adds the necessary JavaScript code to enable Google Analytics logging on any WordPress blog. This eliminates the need to edit your template code to begin logging. Google Analyticator also includes several widgets for displaying Analytics data in the admin and on your blog.</p>
<h4>7. Google Authenticator</h4>
<p>The <a href="http://wordpress.org/extend/plugins/google-authenticator/" rel="external">Google Authenticator</a> plugin for WordPress gives you two-factor authentication using the Google Authenticator app for Android/iPhone/Blackberry. If you are security aware, you may already have the Google Authenticator app installed on your smartphone, using it for two-factor authentication on your Gmail or Google Apps account. I covered the use of this plugin in June; <a href="/archives/3733/">How To Secure WordPress</a>.</p>
<h4>8. Google XML Sitemaps</h4>
<p>The <a href="http://wordpress.org/extend/plugins/google-sitemap-generator/" rel="external">Google XML Sitemaps</a> plugin will generate a special XML sitemap which will help search engines like Google, Bing, Yahoo and Ask.com to better index your blog. With such a sitemap, it&#8217;s much easier for the crawlers to see the complete structure of your site and retrieve it more efficiently. The plugin supports all kinds of WordPress generated pages as well as custom URLs. Additionally it notifies all major search engines every time you create a post about the new content.</p>
<h4>9. Last.fm Recently Played Tracks</h4>
<p>This is just for showing off my exceptional taste in music, and I&#8217;ve made some rather intrusive modifications to the original plugin. The result can be seen on the bottom of every page on this site. The original <a href="http://wordpress.org/extend/plugins/lastfm-recently-played-tracks/">Last.fm Recently Played Tracks</a> is still a great plugin if you want to display information from your Last.fm account on your WordPress site.</p>
<h4>10. NextGEN Gallery</h4>
<p><a href="http://wordpress.org/extend/plugins/nextgen-gallery/" rel="external">NextGEN Gallery</a> is a full integrated Image Gallery plugin for WordPress with dozens of options and features. I don&#8217;t use galleries much when I post, so I tend to use WordPress&#8217; internal image handling features and <a href="http://wordpress.org/extend/plugins/fancybox-for-wordpress/" rel="external">FancyBox for WordPress</a> for visual effects, but if you&#8217;re handling lots of pictures and need to sort them into galleries, NextGEN Gallery should be right up your alley.</p>
<h4>11. On This Day</h4>
<p><a href="http://wordpress.org/extend/plugins/on-this-day/" rel="external">On This Day</a> is currently being used in the footer to display entires that has the same calendar date as today. A great way to keep your visitors clicking on your links.</p>
<h4>12. Quotes Collection</h4>
<p>The <a href="http://wordpress.org/extend/plugins/quotes-collection/" rel="external">Quotes Collection</a> plugin helps you collect, manage and display your favourite quotations in your WordPress site, like my <a href="/one-liners/">One-liners</a> collection.</p>
<h4>13. Revision Control</h4>
<p>WordPress comes with a revision feature, which is nice. But if you work with a post or a page for a long time you can get quite a lot of revisions and only a few of them are relevant. Tons of unnecessary revisions can make your database morbidly obese. <a href="http://wordpress.org/extend/plugins/revision-control/" rel="external">Revision Control</a> solves this problem by letting you configure how many revisions WordPress saves.</p>
<h4>14. Shockingly Big IE6 Warning</h4>
<p><a href="http://wordpress.org/extend/plugins/shockingly-big-ie6-warning/" rel="external">Shockingly Big IE6 Warning</a> is a plugin that shows a warning message alerting the user why it is bad to use IE6, the security risk and the bad compatibility of Web Standards. It might be time to disable this plugin soon, but about 5% of my visitors are still using IE6.</p>
<h4>15. Similar Posts</h4>
<p><a href="http://wordpress.org/extend/plugins/similar-posts/" rel="external">Similar Posts</a> displays a list of posts that are similar or related to the current posts. The list can be customized in many ways. Similarity is judged according to a post&#8217;s title, content, and tags and you can adjust the balance of factors to fit your own blog.</p>
<h4>16. Subscribe To Comments</h4>
<p><a href="http://wordpress.org/extend/plugins/subscribe-to-comments/" rel="external">Subscribe To Comments</a> is a robust plugin that enables commenters to sign up for e-mail notification of subsequent entries. The plugin includes a full-featured subscription manager that your commenters can use to unsubscribe to certain posts, block all notifications, or even change their notification e-mail address. You might also consider <a href="http://wordpress.org/extend/plugins/subscribe-to-comments-reloaded/" rel="external">Subscribe to Comments Reloaded</a>, which is updated more recently.</p>
<h4>17. Twitter Tools</h4>
<p><a href="http://wordpress.org/extend/plugins/twitter-tools/" rel="external">Twitter Tools</a> is a plugin that creates a complete integration between your WordPress blog and your Twitter account. It can both send a Twitter message when you post a new entry and display your Twitter messages on your site. I use it to display my Twitter messages in the sidebar.</p>
<h4>18. Wordbooker</h4>
<p>The <a href="http://wordpress.org/extend/plugins/wordbooker/" rel="external">Wordbooker</a> allows you to cross-post your blog posts to your Facebook Wall. You can also &#8220;cross polinate&#8221; comments between Facebook and your WordPress blog.</p>
<h4>19. wp-days-ago</h4>
<p>Shameless plug ahead (since this is a plugin I maintain myself): <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">wp-days-ago</a>  displays the number of years, days, hours and minutes since a post or a page was published. Examples are “Just now” (less than a minute ago), “47 minutes ago” (less than an hour ago), “3 hours ago” (less than a day ago), “Yesterday”, “3 days ago”, “One week ago”, “76 days ago”, “2 years, 13 days ago” and so on. There are options for defining a prepending and appending text and change all the textual output from the plugin, for instance “minutes ago” and “One week ago”, making it easy for you to translate it to any language you want.</p>
<h4>20. WP-Syntax</h4>
<p><a href="http://wordpress.org/extend/plugins/wp-syntax/" rel="external">WP-Syntax</a> provides clean syntax highlighting using GeSHi &#8212; supporting a wide range of popular languages. It supports highlighting with or without line numbers and maintains formatting while copying snippets of code from the browser. This is a great plugin if you post code examples on your site.</p>
<h4>21. WP Super Cache</h4>
<p><a href="http://wordpress.org/extend/plugins/wp-super-cache/" rel="external">WP Super Cache</a> generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts. Another popular cache plugin for WordPress is <a href="http://wordpress.org/extend/plugins/w3-total-cache/" rel="external">W3 Total Cache</a>.</p>
<h4>22. WPtouch</h4>
<p><a href="http://wordpress.org/extend/plugins/wptouch/" rel="external">WPtouch</a> automatically transforms your WordPress blog into an iPhone application-style theme, complete with ajax loading articles and effects, when viewed from iPhone, iPod touch, Android, Palm Pre, Samsung touch and BlackBerry Storm/Torch mobile devices.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/4000/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>wp-days-ago v2.0.2.</title>
		<link>http://www.vegard.net/archives/3781/</link>
		<comments>http://www.vegard.net/archives/3781/#comments</comments>
		<pubDate>Sat, 02 Jul 2011 20:11:17 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=3781</guid>
		<description><![CDATA[My WordPress plugin, wp-days-ago, has been updated to version 2.0.2. This plugin displays the number of years, days, hours and minutes since a post or a page was published. Examples are &#8220;Just now&#8221; (less than a minute ago), &#8220;47 minutes ago&#8221; (less than an hour ago), &#8220;3 hours ago&#8221; (less than a day ago), &#8220;Yesterday&#8221;, [...]]]></description>
			<content:encoded><![CDATA[<p>My WordPress plugin, <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">wp-days-ago</a>, has been updated to version 2.0.2.</p>
<p>This plugin displays the number of years, days, hours and minutes since a post or a page was published. Examples are &#8220;Just now&#8221; (less than a minute ago), &#8220;47 minutes ago&#8221; (less than an hour ago), &#8220;3 hours ago&#8221; (less than a day ago), &#8220;Yesterday&#8221;, &#8220;3 days ago&#8221;, &#8220;One week ago&#8221;, &#8220;76 days ago&#8221;, &#8220;2 years, 13 days ago&#8221; and so on. It&#8217;s also possible to make the plugin behave like the 1.x version and turn off displaying minutes and hours. The plugin will then fall back to &#8220;Today&#8221; for everything published less than 24 hours ago and not display minutes and hours. There are options for defining a prepending and appending text and change all the textual output from the plugin, for instance &#8220;minutes ago&#8221; and &#8220;One week ago&#8221;, making it easy for you to translate it to any language you want.</p>
<h3>Installation</h3>
<ol>
<li><a href="http://downloads.wordpress.org/plugin/wp-days-ago.zip" rel="external">Download</a> the plugin.</li>
<li>Unzip the contents of the downloaded file to the /wp-content/plugins/ directory of your WordPress installation.</li>
<li>Log in to your WordPress dashboard and activate the wp_days_ago plugin that should now be visible in the list.</li>
<li>You can now insert &lt;? wp_days_ago(); ?&gt; anywhere in <a href="http://codex.wordpress.org/The_Loop" rel="external">The Loop</a> in your WordPress theme.</li>
<li>Optionally, you can use &lt;? wp_days_ago(1); ?&gt; instead to turn off the fine grained option (see changelog below). This will make the plugin behave like the 1.x version.</li>
</ol>
<p>No changes to your theme or configuration are necessary when you upgrade from a previous version.</p>
<h3>Changelog</h3>
<ul>
<li>New feature: Added text &#8220;Some time in the future&#8221; for scheduled posts (visible in preview mode only).</li>
<li>New feature: The plugin now by default displays minutes and hours since a post or page was created.</li>
<li>Change: The $offset parameter from the 1.x version is now replaced with a $mode parameter that enables you to prevent the plugin from displaying the minutes and hours since a post or page was published and instead fall back to &#8220;today&#8221; for everything published lest than 24 hours ago.</li>
</ul>
<p>For detailed information on usage and available parameters, please see the <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">plugin’s page at WordPress.org</a> or the readme-file in the ZIP-file.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/3781/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How To Secure WordPress.</title>
		<link>http://www.vegard.net/archives/3733/</link>
		<comments>http://www.vegard.net/archives/3733/#comments</comments>
		<pubDate>Fri, 24 Jun 2011 16:55:17 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=3733</guid>
		<description><![CDATA[If you&#8217;ve paid a little attention to tech news lately, you know that there&#8217;s a chance that you have an account somewhere that has been compromised. Maybe at Sony, Sega or StartSSL. That companies with millions and millions of registered users are unable to keep our information safe is rather disturbing. But a major side [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve paid a little attention to tech news lately, you know that there&#8217;s a chance that you have an account somewhere that has been compromised. Maybe at <a href="http://www.google.com/search?q=sony+hacked&#038;tbm=nws" rel="external">Sony</a>, <a href="http://www.google.com/search?q=sega+hacked&#038;tbm=nws" rel="external">Sega</a> or <a href="http://www.google.com/search?q=startssl+hacked" rel="external">StartSSL</a>.</p>
<p>That companies with millions and millions of registered users are unable to keep our information safe is rather disturbing. But a major side effect of one compromised account is that there is a good chance you&#8217;ve used the same username and password for a lot of other services as well. Someone gets their hand on your login information at Sony and they automatically gets access to your other accounts: Facebook, Flickr, Dropbox and PayPal. Crap!</p>
<p>One solution is to use a unique username and password on every site. But can be very inconvenient as the number of accounts increases. Another solution is to use <a href="http://en.wikipedia.org/wiki/Two-factor_authentication" rel="external">two-factor authentication</a>.<span id="more-3733"></span></p>
<p>One way to implement two-factor authentication is to require that the user has access to a token that only the end user has access to. An example of this is a credit card with a PIN code. You need both to get money out of an ATM, with only one of them you can&#8217;t. Another way is to use a password together with a one-time code provided by a token. This is supported by WordPress, and it is a great way to secure your account.  Here&#8217;s how you do it.</p>
<ol>
<li>Install <a href="http://www.google.com/support/a/bin/answer.py?answer=1037451" rel="external">Google Authenticator</a> on your phone (Android version 1.5 or later, BlackBerry OS 4.2 &#8211; 4.7, iPhone iOS 4 or later)</li>
<li>Install and activate the <a href="http://wordpress.org/extend/plugins/google-authenticator/" rel="external">Google Authenticator</a> WordPress plugin.</li>
<li>In WordPress, go to the users configuration, enable Google Authenticator login for your user and follow the instructions.</li>
</ol>
<p>Easy as pie. Now anyone who wants to access your account need your username, your password and the one-time code. It&#8217;s <em>very</em> hard for them to get their hands on all three.</p>
<p>The flip side of things is that if you misplace your mobile phone you are screwed and will be unable to log in to your account. If you run your own WordPress installation, this can be resolved. You can dig down in the wp_usermeta table in the database, find the googleauthenticator_enabled setting and change its value to disabled. This SQL statement should enable you to log in again without using the Google Authenticator code. Replace XXX with your own user_id:</p>

<div class="wp_syntax"><div class="code"><pre class="sql" style="font-family:monospace;"><span style="color: #993333; font-weight: bold;">UPDATE</span> wp_usermeta 
<span style="color: #993333; font-weight: bold;">SET</span> meta_value <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'disabled'</span> 
<span style="color: #993333; font-weight: bold;">WHERE</span> user_id <span style="color: #66cc66;">=</span> XXX <span style="color: #993333; font-weight: bold;">AND</span> meta_key <span style="color: #66cc66;">=</span> <span style="color: #ff0000;">'googleauthenticator_enabled'</span></pre></div></div>

<p>The Google Authenticator field will be visible during login, but you don&#8217;t have to enter anything.</p>
<p><strike>Another unfortunate side effect is that you can&#8217;t use the WordPress for Android application because it doesn&#8217;t support two-factor authentication.</strike> Since this entry was written, the author has added support for the WordPress for Android application.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/3733/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>wp-days-ago v1.7.1.</title>
		<link>http://www.vegard.net/archives/3530/</link>
		<comments>http://www.vegard.net/archives/3530/#comments</comments>
		<pubDate>Sat, 28 May 2011 19:19:35 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=3530</guid>
		<description><![CDATA[Update: The plugin has been updated to version 2.0.1. All users are encourage to upgrade. My WordPress plugin, wp-days-ago, has been updated to version 1.7.1. This plugin displays the number of years and days since a post or a page was published. All calculations are based on days but it will not take into account [...]]]></description>
			<content:encoded><![CDATA[<p><b>Update:</b> The plugin has been updated to <a href="http://www.vegard.net/archives/3781/">version 2.0.1</a>. All users are encourage to upgrade.</p>
<p>My WordPress plugin, <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">wp-days-ago</a>, has been updated to version 1.7.1.</p>
<p>This plugin displays the number of years and days since a post or a page was published. All calculations are based on days but it will not take into account that 24 hours are one day. If you publish a page or a post at 23:59, it will be marked with “yesterday” at 00:00 even if it&#8217;s only a minute since you published. In some cases, the plugin will display a human readable text instead of the days count. Today is “today” and not “0 days ago”. Yesterday is, well, “yesterday”, while anything published seven days ago is posted “a week ago”. If an entry is more than a year old, the plugin will display the post date as &#8220;X years, Y days&#8221;.</p>
<h3>Installation</h3>
<ol>
<li><a href="http://downloads.wordpress.org/plugin/wp-days-ago.zip" rel="external">Download</a> the plugin.</li>
<li>Unzip the contents of the downloaded file to the /wp-content/plugins/ directory of your WordPress installation.</li>
<li>Log in to your WordPress dashboard and activate the wp_days_ago plugin that should now be visible in the list.</li>
<li>You can now insert &lt;? wp_days_ago(); ?&gt; anywhere in <a href="http://codex.wordpress.org/The_Loop" rel="external">The Loop</a> in your WordPress theme.</li>
</ol>
<p>No changes to your theme or configuration are necessary when you upgrade from a previous version.</p>
<h3>Changelog</h3>
<ul>
<li>Backwards compatible all the way back to WordPress 1.5.</li>
<li>The plugin now uses the internal WordPress timezone settings.</li>
<li>Added optional parameters that allows configuration of appended text, prepended text and the texts displayed by the plugin.</li>
</ul>
<p>For detailed information on usage and available parameters, please see the <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">plugin&#8217;s page at WordPress.org</a> or the readme-file in the ZIP-file.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/3530/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WordPress and the iPhone.</title>
		<link>http://www.vegard.net/archives/1497/</link>
		<comments>http://www.vegard.net/archives/1497/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 20:04:14 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/archives/1497/</guid>
		<description><![CDATA[This is just a quick test to check if the WordPress application for the iPhone actually works. So far two drafts are gone. But I&#8217;m even going to try add a photo of a smashed mobile phone.]]></description>
			<content:encoded><![CDATA[<p>This is just a quick test to check if the WordPress application for the iPhone actually works. So far two drafts are gone. But I&#8217;m even going to try add a photo of a smashed mobile phone.</p>
<p><img src="http://www.vegard.net/wp-content/uploads/2008/09/p-640-480-2e3d7a99-94e1-45ca-b916-7c3eacfa0bb2.jpeg" alt="Smashed mobile phone" width="225" height="300" class="centerimg" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/1497/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress plugin: wp-days-ago.</title>
		<link>http://www.vegard.net/archives/1476/</link>
		<comments>http://www.vegard.net/archives/1476/#comments</comments>
		<pubDate>Sat, 30 Aug 2008 15:29:22 +0000</pubDate>
		<dc:creator>Vegard Skjefstad</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.vegard.net/?p=1476</guid>
		<description><![CDATA[Update: A new version of this plugin is now available. All users are encouraged to upgrade to version 2.0. More information is available here. My very first attempt on a WordPress plugin is actually just a copy/past job from my own CMS. I wanted to get functionality I could not find in any other plugins: [...]]]></description>
			<content:encoded><![CDATA[<p><b>Update:</b> A new version of this plugin is now available. All users are encouraged to upgrade to version 2.0. More information is available <a href="/archives/3781/">here</a>.</p>
<p>My very first attempt on a <a rel="external" href="http://www.wordpress.com/">WordPress</a> plugin is actually just a copy/past job from my own CMS. I wanted to get functionality I could not find in any other plugins: I simply wanted to display the number of days since a post or page was published.</p>
<p>The plugin will only display years and days and will not take into account that 24 hours are one day. If you publish a page or a post at 23:59, it will be marked with &#8220;yesterday&#8221; at 00:00 even if it&#8217;s only a minute since you published. In some cases, the plugin will display a human readable text instead of the days count. Today is &#8220;today&#8221; and not &#8220;0 days ago&#8221;. Yesterday is, well, &#8220;yesterday&#8221;, while anything published seven days ago is posted &#8220;a week ago&#8221;. If an entry is more than a year old, the plugin will display the post date as &#8220;X year, Y days&#8221;.</p>
<p>If you want to use it yourself, simply follow these instructions:</p>
<ol>
<li><a href="http://downloads.wordpress.org/plugin/wp-days-ago.zip">Download here</a> (v1.0).</li>
<li>Unzip the contents of the downloaded file to the /wp-content/plugins/ directory of your WordPress installation.</li>
<li>Log in to your WordPress dashboard and activate the wp_days_ago plugin that should now be visible in the list.</li>
<li>You can now insert &lt;? wp_days_ago(); ?&gt; anywhere in <a rel="external" href="http://codex.wordpress.org/The_Loop">The Loop</a> in your WordPress theme.</li>
</ol>
<p>The wp_days_ago plugin takes one parameter; the timezone offset between your WordPress time zone settings and the server your WordPress installation is running on. In my case I write everything in Central European Time, but the server is located in Sydney, Australia. That&#8217;s a -8 hour time zone offset from the server to my local time, and to get things right, I have to use -8 as the time zone offset parameter, like this: &lt;? wp_days_ago(-8); ?&gt;.</p>
<p>This plugin is also available through the <a href="http://wordpress.org/extend/plugins/wp-days-ago/" rel="external">WordPress plugin directory</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vegard.net/archives/1476/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

