<?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>Philaeum - Strategic Internet Solutions</title>
	<atom:link href="http://www.philaeum.nl/blog/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.philaeum.nl/blog</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Tue, 18 Dec 2012 11:14:26 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
		<item>
		<title>Google now also reports about old versions of software</title>
		<link>http://www.philaeum.nl/blog/index.php/google-now-also-reports-about-old-versions-of-software/</link>
		<comments>http://www.philaeum.nl/blog/index.php/google-now-also-reports-about-old-versions-of-software/#comments</comments>
		<pubDate>Tue, 18 Dec 2012 11:14:26 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=66</guid>
		<description><![CDATA[When I logged in to Google Webmastertools today I was presented with a message that I&#8217;m using an old version of Vbulletin on one of my websites. Vbulletin is currently in the 4.x.x. version but in the 3.x.x versions there &#8230; <a href="http://www.philaeum.nl/blog/index.php/google-now-also-reports-about-old-versions-of-software/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>When I logged in to Google Webmastertools today I was presented with a message that I&#8217;m using an old version of Vbulletin on one of my websites. Vbulletin is currently in the 4.x.x. version but in the 3.x.x versions there is still a maintained one, which we&#8217;re using. But it&#8217;s probably good that Google monitors for it as many outdated versions come with security vulnerabilities. I hope to update to the 4.x.x. branch soon but as our forum is rather large this is more than simply running the update script.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/google-now-also-reports-about-old-versions-of-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress wp_list_comments callback explanation</title>
		<link>http://www.philaeum.nl/blog/index.php/wordpress-wp_list_comments-callback-explanation/</link>
		<comments>http://www.philaeum.nl/blog/index.php/wordpress-wp_list_comments-callback-explanation/#comments</comments>
		<pubDate>Tue, 24 May 2011 15:57:47 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=58</guid>
		<description><![CDATA[When working with comments you might want to drastically change the appearance of the comments. You can use a new comment template with which you call from the template where you want to list the comments. But if you want &#8230; <a href="http://www.philaeum.nl/blog/index.php/wordpress-wp_list_comments-callback-explanation/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>When working with comments you might want to drastically change the appearance of the comments. You can use a new comment template with
<pre class="brush: php; title: ; notranslate">comments_template( '/my-comments.php', true )</pre>
<p> which you call from the template where you want to list the comments. But if you want each single comment to be different, you can use the callback function of wp_list_comments.</p>
<p>You use wp_list_comments in your comments template. Default is comments.php in your theme function, but if you used the comments_template function from above, you have to look for that file (of course). You should see wp_list_comments like the The Loop on it&#8217;s own. It goes through all of the comments and lists them. With the callback you can modify The Comment Loop and totally make it to your own likings.</p>
<pre class="brush: php; title: ; notranslate">

&lt;?php 
global $my_object;
wp_list_comments(array('type' =&gt; 'all', 'callback', array($my_object, 'my_custom_comments'));
?&gt;
</pre>
<p>I&#8217;m using classes in my plugins, hence the inclusion of the global, you can also put the function in your functions.php and simply remove the references to the object. Then you can create a function in your class or functions.php and start the fun:</p>
<pre class="brush: php; title: ; notranslate">

function my_custom_comments($comment, $args, $depth){
        
        $GLOBALS['comment'] = $comment;
    
        comment_text();
        
    }

</pre>
<p>In it, you can use the <a href="http://codex.wordpress.org/Template_Tags#Comment Tags">Comments Tags</a> which are listed <a href="http://codex.wordpress.org/Template_Tags#Comment Tags">here</a>. Questions? I&#8217;m happy to help you a little further, so don&#8217;t hesitate to post!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/wordpress-wp_list_comments-callback-explanation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress get_comment_meta and update_comment_meta</title>
		<link>http://www.philaeum.nl/blog/index.php/wordpress-get_comment_meta-and-update_comment_meta/</link>
		<comments>http://www.philaeum.nl/blog/index.php/wordpress-get_comment_meta-and-update_comment_meta/#comments</comments>
		<pubDate>Tue, 24 May 2011 15:33:01 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=55</guid>
		<description><![CDATA[WordPress now features a function to allow you to store meta data for each comment. Just like it&#8217;s able to do so for posts. It seems that, under the hood, WordPress has functionality that potentially prepares it for metadata on &#8230; <a href="http://www.philaeum.nl/blog/index.php/wordpress-get_comment_meta-and-update_comment_meta/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>WordPress now features a function to allow you to store meta data for each comment. Just like it&#8217;s able to do so for posts. It seems that, under the hood, WordPress has functionality that potentially prepares it for metadata on whatever you want. As get_comment_meta is nothing but a call to update_meta with the first parameter prefilled with &#8216;comment&#8217;.</p>
<p>Anyway, when you are reading this you are probably looking for a way to get get_comment_meta working. It&#8217;s not documented in the Codex (yet) and other information on the web is not always easy to understand or complete. So here&#8217;s my try to make you understand get_comment_meta and with it comes update_comment_meta.</p>
<ul>
<li>update_comment_meta -&gt; will allow us to update a comment meta entry and is also used to create a meta entry</li>
<li>get_comment_meta -&gt; will alows us to retreive the meta entry for each comment</li>
</ul>
<p><span style="font-size: medium;">The metadata for the comments is stored in the database in its own table and the comment ID is required to link the comment to its metadata.</span></p>
<p>To add comment metadata, a simple call to it like this will make it work:</p>
<pre class="brush: php; title: ; notranslate">
update_comment_meta($comment_id, 'key', 'value');
</pre>
<p>If you save the data when someone is adding a new comment, you would probably receive the $comment_id from a call to e.g. wp_new_comment.</p>
<p>Retrieving the comment metadata is a little different than expected, it has a small (and simple) twist. The trick is in the third parameter here:</p>
<pre class="brush: php; title: ; notranslate">
get_comment_meta($comment_id, 'key', true);
</pre>
<p>This will return a single result (e.g. string) while the following will result in returing an array:</p>
<pre class="brush: php; title: ; notranslate">
get_comment_meta($comment_id, 'key');
</pre>
<p>It&#8217;s as simple as this! In case you want the comment ID while retrieving comments, you can replace $comment_id with get_comment_ID();</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/wordpress-get_comment_meta-and-update_comment_meta/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Features to expect in WordPress 3.2 (to be released Q2/Q3 2011)</title>
		<link>http://www.philaeum.nl/blog/index.php/features-to-expect-in-wordpress-3-2/</link>
		<comments>http://www.philaeum.nl/blog/index.php/features-to-expect-in-wordpress-3-2/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 21:13:01 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=47</guid>
		<description><![CDATA[WordPress 3.1 has just been released and I, as a WordPress addict, am already searching for information on WordPress 3.2. This release is scheduled for the first half of 2011. One thing seems to be sure, WordPress 3.2 will no &#8230; <a href="http://www.philaeum.nl/blog/index.php/features-to-expect-in-wordpress-3-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>WordPress 3.1 has just been released and I, as a WordPress addict, am already searching for information on WordPress 3.2. This release is scheduled for the first half of 2011. One thing seems to be sure, WordPress 3.2 will no longer support PHP4 and MySQL4. Besides that I found other features that are scheduled to appear in WordPress 3.2. Here is a list of features that affect end-users:</p>
<ul>
<li>Minimum version for PHP: 5.2</li>
<li>Minimum version for MySQL: 5.0.15</li>
<li>Download required translations from <a href="http://blog.glotpress.org/">GlotPress</a> &#8211; This means that WordPress itself, themes and plugins are able to download translations from one, group a collaborative, web-based software translation tool. This would help getting translations automatically without any manual searching and downloading .mo files</li>
<li>Administration menu revamp &#8211; For plugin developers the current setup of the administration menu is a lot of hassle. With a rewrite/restructuring of the code this is improved</li>
<li>User can register/login with e-mail address, no username required anymore, functionality currently available in <a href="http://wordpress.org/extend/plugins/wp-email-login/">this plugin</a></li>
<li>Timezone suggestion, based on IP address</li>
<li>To be updated when more comes available, tips are very welcome!</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/features-to-expect-in-wordpress-3-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to make WPML compatible with W3C Total Cache</title>
		<link>http://www.philaeum.nl/blog/index.php/how-to-make-wpml-compatible-with-w3c-total-cache/</link>
		<comments>http://www.philaeum.nl/blog/index.php/how-to-make-wpml-compatible-with-w3c-total-cache/#comments</comments>
		<pubDate>Tue, 15 Feb 2011 16:03:54 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=40</guid>
		<description><![CDATA[If you&#8217;re a heavy user of WordPress and use WMPL together with W3C Total Cache then you might have found out that it doesn&#8217;t work properly when using alias domains for each language. The language switcher doesn&#8217;t work correctly anymore. &#8230; <a href="http://www.philaeum.nl/blog/index.php/how-to-make-wpml-compatible-with-w3c-total-cache/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>If you&#8217;re a heavy user of WordPress and use <a href="http://www.wmpl.org">WMPL</a> together with <a href="http://wordpress.org/extend/plugins/w3-total-cache/">W3C Total Cache</a> then you might have found out that it doesn&#8217;t work properly when using alias domains for each language. The language switcher doesn&#8217;t work correctly anymore. It seems that it switches to the first cached page and/or sometimes a random page. It might work for all pages except the home, but can also affect all pages on the website.</p>
<p>The default setting for the disk cache on W3C Total Cache is enhanced. Simply by changing this option to basic, both plugins will work together flawlessly. In enhanced mode the caching plugin fiddles with the headers of the HTTP request, in basic mode it keeps them as they are.</p>
<p><strong>Update:</strong> Added clarifications as per the comment of Richard</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/how-to-make-wpml-compatible-with-w3c-total-cache/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Retrieve server/host Windows version</title>
		<link>http://www.philaeum.nl/blog/index.php/retrieve-serverhost-windows-version/</link>
		<comments>http://www.philaeum.nl/blog/index.php/retrieve-serverhost-windows-version/#comments</comments>
		<pubDate>Tue, 04 Jan 2011 14:15:46 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=33</guid>
		<description><![CDATA[Not one of the easiest jobs, is retrieving the version information of your Windows computer with PHP. Other methods are available, but they don&#8217;t show you the exact version, usually just report WINNT or similair strings. The code below will &#8230; <a href="http://www.philaeum.nl/blog/index.php/retrieve-serverhost-windows-version/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Not one of the easiest jobs, is retrieving the version information of your Windows computer with PHP. Other methods are available, but they don&#8217;t show you the exact version, usually just report WINNT or similair strings. The code below will print the full information on your computer, easy as that&#8230;</p>
<pre class="brush: php; title: ; notranslate">
    $com_object = new COM ( 'winmgmts://localhost/root/CIMV2' );
    $os =  $com_object-&gt;ExecQuery(&quot;Select * from Win32_OperatingSystem&quot;);

    foreach ($os as $os_data )
    {
                //  Windows version information e.g. 6.1.7600  for Windows 7
		$windows_version = $os_data-&gt;Version; 
                // Full name of Windows version e.g. Microsoft Windows 7 Professional 
		$windows_caption = $os_data-&gt;Caption; 
                // Major Service Pack version (0 if not available)
		$windows_sp = $os_data-&gt;ServicePackMajorVersion; 
    }
   

</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/retrieve-serverhost-windows-version/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress shortcode output buffer versus appending to string</title>
		<link>http://www.philaeum.nl/blog/index.php/wordpress-shortcode-output-buffer-versus-returning-string/</link>
		<comments>http://www.philaeum.nl/blog/index.php/wordpress-shortcode-output-buffer-versus-returning-string/#comments</comments>
		<pubDate>Mon, 27 Dec 2010 13:12:53 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=19</guid>
		<description><![CDATA[When your develop a Wordpress plugin there is a big chance that you will need to include a shortcode. If you simply <code>echo</code> each line, you will notice that your output will not appear on the right place. This is because Wordpress will output your code as soon as it encounters the <code>echo</code>. Therefore you should use a different way to get your output on the page. This will ensure that the output will appear on the place where you've added the shortcode. <a href="http://www.philaeum.nl/blog/index.php/wordpress-shortcode-output-buffer-versus-returning-string/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>When your develop a WordPress plugin there is a big chance that you will need to include a shortcode. If you simply <code>echo</code> each line, you will notice that your output will not appear on the right place. This is because WordPress will output your code as soon as it encounters the <code>echo</code>. Therefore you should use a different way to get your output on the page. This will ensure that the output will appear on the place where you&#8217;ve added the shortcode.</p>
<p>1) You can use the output buffer of PHP, by starting it with <code>ob_start()</code>. Then simply use <code>echo</code> to output your lines. Once you&#8217;ve defined your output you can collect your output to a variable, with <code>ob_get_contents()</code> and return this:</p>
<pre class="brush: php; title: ; notranslate">
function my_shortcode() {
ob_start();
echo 'hello world';
echo 'This is a WordPress shortcode';
$output_string = ob_get_contents();
ob_end_clean();
return $output_string;
}
</pre>
<p>This will ensure that all your output will be catched by the output buffer and returned. When using multiple shortcodes on a page, this can cause conflicts. </p>
<p>2) Another option is to append strings, this would mean we would rewrite the code above to:</p>
<pre class="brush: php; title: ; notranslate">
function my_shortcode() {
$output_string = 'hello world';
$output_string .= 'This is a WordPress shortcode';
return $output_string;
}
</pre>
<p>This should solve any problems with the output of your WordPress shortcode appearing on the wrong place.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/wordpress-shortcode-output-buffer-versus-returning-string/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WordPress footer no longer appearing</title>
		<link>http://www.philaeum.nl/blog/index.php/wordpress-footer-no-longer-appearing/</link>
		<comments>http://www.philaeum.nl/blog/index.php/wordpress-footer-no-longer-appearing/#comments</comments>
		<pubDate>Thu, 23 Dec 2010 20:58:41 +0000</pubDate>
		<dc:creator>Jan Willem</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://www.philaeum.nl/blog/?p=4</guid>
		<description><![CDATA[All of a sudden, the code included by WordPress Plugins dissapeared, the solution was easier than expected but took a lot of work to finally find out put before the body closing tag. Without the tag, the code won&#8217;t be &#8230; <a href="http://www.philaeum.nl/blog/index.php/wordpress-footer-no-longer-appearing/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>All of a sudden, the code included by WordPress Plugins dissapeared, the solution was easier than expected but took a lot of work to finally find out put
<pre class="brush: php; title: ; notranslate">&lt;?php wp_footer()?&gt;
&lt;/body&gt;</pre>
<p> before the body closing tag. Without the tag, the code won&#8217;t be inserted. Ofcourse the body tag should be in your HTML page anyway, but if you somehow removed it, this can save you some work.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philaeum.nl/blog/index.php/wordpress-footer-no-longer-appearing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
