<?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/"
	xmlns:georss="http://www.georss.org/georss" >

<channel>
	<title>[&#124;] m.tacker.org &#187; PHP</title>
	<atom:link href="http://m.tacker.org/blog/tag/php/feed" rel="self" type="application/rss+xml" />
	<link>http://m.tacker.org/blog</link>
	<description>Aus meinem Alltag.</description>
	<lastBuildDate>Sat, 21 Jan 2012 21:42:44 +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>File_Bittorrent 2.2.0 release</title>
		<link>http://m.tacker.org/blog/1168.file_bittorrent-220-release.html</link>
		<comments>http://m.tacker.org/blog/1168.file_bittorrent-220-release.html#comments</comments>
		<pubDate>Thu, 12 Jun 2008 18:25:20 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[Bittorrent]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/?p=1168</guid>
		<description><![CDATA[Today I&#8217;ve release version 2.2 of PEAR&#8217;s File_Bittorrent. Changes include the support for the &#8220;private&#8221; Flag which was requested by William Booth. The flag is used to tell Bittorrent Clients not to consider other trackers besides the ones stated in the torrent file. See the Azureus Wiki for further information on this topic.]]></description>
			<content:encoded><![CDATA[<p><img src="http://m.tacker.org/blog/wp-content/uploads/2006/07/file_bittorrent.gif" alt="PEAR::File_Bittorrent" class="right" />Today I&#8217;ve release version 2.2 of PEAR&#8217;s <a href="http://pear.php.net/package/File_Bittorrent2/">File_Bittorrent</a>.</p>
<p>Changes include the support for the &#8220;private&#8221; Flag which was requested by <a href="http://pear.php.net/bugs/bug.php?id=14013">William Booth</a>.</p>
<p>The flag is used to tell Bittorrent Clients not to consider other trackers besides the ones stated in the torrent file. See the <a href="http://www.azureuswiki.com/index.php/Secure_Torrents">Azureus Wiki</a> for further information on this topic.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/1168.file_bittorrent-220-release.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PEAR Cache_Lite 1.7.3 release</title>
		<link>http://m.tacker.org/blog/1118.pear-cache_lite-173-release.html</link>
		<comments>http://m.tacker.org/blog/1118.pear-cache_lite-173-release.html#comments</comments>
		<pubDate>Mon, 14 Apr 2008 17:58:40 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PEAR Cache_Lite]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Projekte]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/?p=1118</guid>
		<description><![CDATA[This is my first release for PEAR Cache_Lite. In March I took over the vacant developer position for this package as I am using it for many projects. After some initial hesitation, David nudged me to use cvs. I did &#8212; and 1.7.3 is the result. It&#8217;s just a bugfix release but after nearly two [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://m.tacker.org/blog/wp-content/uploads/2008/04/pear-cache_lite.gif" alt="" title="PEAR Cache_Lite" width="199" height="46" class="alignright size-medium wp-image-1119" />This is my first release for <a href="http://pear.php.net/package/Cache_Lite">PEAR Cache_Lite</a>. In March I took over the vacant developer position for this package as I am using it for many projects. After some initial hesitation, <a href="http://blog.agoraproduction.com/">David</a> nudged me to use cvs. I did &mdash; and <a href="http://pear.php.net/package/Cache_Lite/download/1.7.3">1.7.3</a> is the result. It&#8217;s just a bugfix release but after nearly two years finally something to talk about for Cache_Lite.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/1118.pear-cache_lite-173-release.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>File_Bittorrent 2.1.0 release</title>
		<link>http://m.tacker.org/blog/862.file_bittorrent-210-release.html</link>
		<comments>http://m.tacker.org/blog/862.file_bittorrent-210-release.html#comments</comments>
		<pubDate>Sat, 12 Jan 2008 10:56:41 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PEAR File_Bittorrent]]></category>
		<category><![CDATA[Projekte]]></category>
		<category><![CDATA[Bittorrent]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/862.file_bittorrent-210-release.html</guid>
		<description><![CDATA[I&#8217;ve just released File_Bittorrent 2.1.0. This is the stable release of the PHP5 only version of File_Bittorrent. New features include the ability to add a specific list of files while making a torrent. This feature has been implemented by Barry Hunter.]]></description>
			<content:encoded><![CDATA[<p><img src="http://m.tacker.org/blog/wp-content/uploads/2006/07/file_bittorrent.gif" alt="PEAR::File_Bittorrent" class="right" />I&#8217;ve just released <a href="http://pear.php.net/package/File_Bittorrent2/">File_Bittorrent 2.1.0</a>. This is the stable release of the PHP5 only version of <a href="http://pear.php.net/package/File_Bittorrent/">File_Bittorrent</a>. New features include the ability to add a specific list of files while making a torrent. This feature has been implemented by <a href="http://barryhunter.co.uk">Barry Hunter</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/862.file_bittorrent-210-release.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>File_Bittorrent2 released</title>
		<link>http://m.tacker.org/blog/773.file_bittorrent2-released.html</link>
		<comments>http://m.tacker.org/blog/773.file_bittorrent2-released.html#comments</comments>
		<pubDate>Sun, 26 Aug 2007 11:11:23 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PEAR File_Bittorrent]]></category>
		<category><![CDATA[Projekte]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/773.file_bittorrent2-released.html</guid>
		<description><![CDATA[I&#8217;ve just released File_Bittorrent2. This is the PHP5 only version of File_Bittorrent &#8212; no new features were added, even the API is the same. Only the error handling has been changed according to PEAR&#8217;s new error handling guidelines «Error Signaling in PHP 5 PEAR packages».]]></description>
			<content:encoded><![CDATA[<p><img src="http://m.tacker.org/blog/wp-content/uploads/2006/07/file_bittorrent.gif" alt="PEAR::File_Bittorrent" class="right" />I&#8217;ve just released <a href="http://pear.php.net/package/File_Bittorrent2/">File_Bittorrent2</a>. This is the PHP5 only version of <a href="http://pear.php.net/package/File_Bittorrent/">File_Bittorrent</a> &mdash; no new features were added, even the API is the same.</p>
<p>Only the error handling has been changed according to <a href="http://www.go-pear.org/manual/en/standards.errors.php">PEAR&#8217;s new error handling guidelines</a> «Error Signaling in PHP 5 PEAR packages».</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/773.file_bittorrent2-released.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>__autoload vs. require_once</title>
		<link>http://m.tacker.org/blog/599.__autoload-vs-require_once.html</link>
		<comments>http://m.tacker.org/blog/599.__autoload-vs-require_once.html#comments</comments>
		<pubDate>Wed, 06 Dec 2006 15:13:54 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/599.__autoload-vs-require_once.html</guid>
		<description><![CDATA[Yesterday I read in Lukas Blog that __autoload is bad for bytecode caches. As I am currently in the optimizing phase of a project I gave it try. I used __autoload for everything until now. I then removed __autoload and added the &#8220;old style&#8221; require_once calls. I testet the app by fetching the start page [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday I read in <a href="http://pooteeweet.org/blog/">Lukas Blog</a> that <a href="http://pooteeweet.org/blog/538"><code>__autoload</code> is bad for bytecode caches</a>. As I am currently in the optimizing phase of a project I gave it try.</p>
<p>I used <code>__autoload</code> for everything until now. I then removed <code>__autoload</code> and added the &#8220;old style&#8221; <code>require_once</code> calls.</p>
<p>I testet the app by fetching the start page 100 times on a freshly started apache 2.2 with mod_php 5.2.0 and apc 3.0.12.</p>
<p><strong>The speed increase was about 4%.</strong></p>
<p>For me the speed gain does not legitimate the loss in code quality.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/599.__autoload-vs-require_once.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AlbumEmbed / PicasaEmbed</title>
		<link>http://m.tacker.org/blog/1056.albumembed-picasaembed.html</link>
		<comments>http://m.tacker.org/blog/1056.albumembed-picasaembed.html#comments</comments>
		<pubDate>Thu, 30 Nov 2006 20:23:40 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/1056.albumembed-picasaembed.html</guid>
		<description><![CDATA[AlbumEmbed / PicasaEmbed PicasaEmbed, bzw. inzwischen AlbumEmbed ist ein universelle PHP5-Bibliothek und Fotos aus Bilder-Galerien, die einen RSS-Feed anbieten, in eine Webseite einzubinden. Grundsätzlich geschieht das Blättern mittels Ajax, es steht jedoch auch eine Fallback-Lösung zur Verfügung, falls JavaScript deaktiviert ist. Weitere Details finden sich (auf Englisch) in meinem Blog. Ausgehen von PicasaEmbed ist AlbumEmbed [...]]]></description>
			<content:encoded><![CDATA[<dl class="foto" style="width: 200px">
<dt><img src="http://tacker.org/wp-content/uploads/2007/02/resized_2007-02-28_212600.png" alt="AlbumEmbed / PicasaEmbed" /></dt>
<dd>AlbumEmbed / PicasaEmbed</dd>
</dl>
<p><a href="http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html">PicasaEmbed</a>, bzw. inzwischen <em>AlbumEmbed</em> ist ein universelle PHP5-Bibliothek und Fotos aus Bilder-Galerien, die einen RSS-Feed anbieten, in eine Webseite einzubinden.</p>
<p>Grundsätzlich geschieht das Blättern mittels Ajax, es steht jedoch auch eine Fallback-Lösung zur Verfügung, falls JavaScript deaktiviert ist. Weitere Details finden sich (auf Englisch) <a href="http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html">in meinem Blog</a>.</p>
<p>Ausgehen von <em>PicasaEmbed</em> ist <em>AlbumEmbed</em> verallgemeinert und lässt sich für alle Arten von Bilder-Galerien einsetzen. Zur Zeit wird <a href="http://picasaweb.google.com/">Picasa</a> und <a href="http://gallery.menalto.com/">Gallery</a> unterstützt. Ein Beispiel für den Einsatz von <em>AlbumEmbed</em> findet sich <a href="http://m.tacker.org/blog/652.bad-noch-mehr-moglichkeiten.html">hier</a>.</p>
<h3>Quellcode</h3>
<ul>
<li><a href="http://versions.tacker.org/svn/smallprojects/albumembed">SVN</a></li>
<li><a href="http://projects.clyre.net/picasaembed/example.phps">Beispiel</a></li>
<li><a href="http://versions.tacker.org/trac/smallprojects/browser/albumembed/">Quellcode-Browser</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/1056.albumembed-picasaembed.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Picasaembed: Embed and browse your Picasa Web Albums</title>
		<link>http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html</link>
		<comments>http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html#comments</comments>
		<pubDate>Thu, 30 Nov 2006 17:00:02 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Projekte]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html</guid>
		<description><![CDATA[Yesterday evening I discovered that Google&#8217;s Picasa Web Albums have RSS feeds. This led me to a script in PHP5, which enables you to embed the thumbnails of a whole album in any site &#8212; you may even browse through them. The browsing is done with Ajax to give a fast experience but there is [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday evening I discovered that <a href="http://picasaweb.google.com/">Google&#8217;s Picasa Web Albums</a> have RSS feeds. This led me to a script in PHP5, which enables you to embed the thumbnails of a whole album in any site &mdash; you may even browse through them. The browsing is done with Ajax to give a fast experience but there is a fallback solution which works without javascript.</p>
<p>Multiple embedded albums per page are also supported.</p>
<p>The usage of Picasaembed is not limited to WordPress &mdash; it&#8217;s designed as a standalone library.</p>
<h2>Download</h2>
<ul>
<li><a href="http://versions.tacker.org/svn/smallprojects/picasaembed">via SVN</a></li>
<li><a href="http://projects.clyre.net/download/picasaembed.tgz">Tar-Archive</a></li>
<li><a href="http://projects.clyre.net/download/picasaembed.zip">Zip-Archive</a></li>
</ul>
<h2>Example</h2>
<p>You are just seeing an example. You may also check out the <a href="http://projects.clyre.net/picasaembed/example.php">example</a> (<a href="http://projects.clyre.net/picasaembed/example.phps">source code</a>) which is provided with the script.</p>
<h2>Installation</h2>
<p>Let&#8217;s assume that you want Picasaembed in your WordPress blog.</p>
<p>Copy the files to a new folder named <code>picasaembed</code> in WordPress&#8217; plugins folder and make sure that the webserver has write permission to the <code>cache</code> folder.</p>
<p>Just make sure that the prototype.js is loaded somewhere. You would add it to your <code>header.php</code> file.</p>
<blockquote><p><code>&lt;script type=&quot;text/javascript&quot; src=&quot;/blog/wp-content/plugins/picasaembed/prototype-1.4.0.js&quot;&gt;&lt;/script&gt;</code></p></blockquote>
<p>As Picasaembed requires a RSS-URL to display the album we need set up a <a href="http://codex.wordpress.org/Using_Custom_Fields">custom field</a> for our post. Let&#8217;s assume that we name it <code>picasaembed_rss_url</code>.</p>
<p>In the theme files <code>index.php</code> and <code>single.php</code> (which display the post) we have to add these lines before the <code>the_content()</code> tag to display the album:</p>
<blockquote><p><code>&lt;?php<br />
 $picasaembed = (get_post_meta($post-&gt;ID, 'picasaembed_rss_url', true)) ? get_post_meta($post-&gt;ID, 'picasaembed_rss_url', true) : false;<br />
 if ($picasaembed) {<br />
 require_once './wp-content/plugins/picasaembed/Picasaembed.php';<br />
 Picasaembed::$location = './wp-content/plugins/picasaembed/Picasaembed.php';<br />
 echo Picasaembed::getContainer($picasaembed);<br />
 }<br />
?&gt;</code></p></blockquote>
<p>That&#8217;s it. Now everytime a post has the custom field <code>picasaembed_rss_url</code> the value will be used as a RSS-URL for Picasaembed. Happy time!</p>
<h2>Uses</h2>
<ul>
<li><a href="http://pear.php.net/package/XML_RSS">PEAR XML_RSS</a> for parsing the rss feed. (not included)</li>
<li><a href="http://pear.php.net/package/Cache_Lite">PEAR Cache_Lite</a> for caching the parsed rss feed. (not included)</li>
<li><a href="http://prototype.conio.net/">The prototype JavaScript Framework</a> for the ajax browsing.</li>
<li><a href="http://pear.php.net/package/HTML_Page2">PEAR HTML_Page2</a> &mdash; optional &mdash; for the <a href="http://projects.clyre.net/picasaembed/example.php">example</a>. (not included)</li>
</ul>
<h2>License</h2>
<p>Released under the <a href="http://www.gnu.org/licenses/lgpl.html">LGPL</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/595.picasaembed-embed-and-browse-your-picasa-web-albums.html/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Sicherheitseinstellungen von PHP prüfen</title>
		<link>http://m.tacker.org/blog/566.sicherheitseinstellungen-von-php-prufen.html</link>
		<comments>http://m.tacker.org/blog/566.sicherheitseinstellungen-von-php-prufen.html#comments</comments>
		<pubDate>Mon, 23 Oct 2006 09:29:25 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/566.sicherheitseinstellungen-von-php-prufen.html</guid>
		<description><![CDATA[Mit PHPSecInfo vom PHP Security Consortium kann man die Konfiguration einer PHP-Installation auf mögliche Schwachstellen überprüfen. PHPSecInfo möchte unerfahrene Server-Admins und Entwicklern einen leichten Überblick über die sicherheitsrelevanten Konfigurationseinstellungen von PHP bieten. Anhand farbiger Markierung ist auf den ersten Blick zu erkennen, ob eine Einstellung ein Sicherheitsrisiko birgt (rot und orange) oder sicher ist (grün). [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://m.tacker.org/blog/wp-content/uploads/2006/10/2006-10-23_103027_250.png' alt='PHP Security Consortium: PHPSecInfo' class="right" />Mit <a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo</a> vom PHP Security Consortium kann man die Konfiguration einer PHP-Installation auf mögliche Schwachstellen überprüfen.</p>
<p>PHPSecInfo möchte unerfahrene Server-Admins und Entwicklern einen leichten Überblick über die sicherheitsrelevanten Konfigurationseinstellungen von PHP bieten.</p>
<p>Anhand farbiger Markierung ist auf den ersten Blick zu erkennen, ob eine Einstellung ein Sicherheitsrisiko birgt (rot und orange) oder sicher ist (grün). Neben der farblichen Markierung gibt eine Erklärung, zur Zeit nur auf Englisch, darüber Aufschluss, was diese Einstellung gefährlich macht, und hinterfragt, ob die aktuelle Einstellung wirklich benötigt wird.</p>
<p>Diese Einstellungen werden in der aktuellen Version geprüft:</p>
<ul>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.cgi.force-redirect">cgi.force_redirect</a></li>
<li><a href="http://de.php.net/manual/en/ref.filesystem.php#ini.allow-url-fopen">allow_url_fopen</a></li>
<li><a href="http://de.php.net/manual/en/ref.errorfunc.php#ini.display-errors">display_errors</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.expose-php">expose_php</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.file-uploads">file_uploads</a></li>
<li><a href="http://de.php.net/manual/en/ref.info.php#ini.magic-quotes-gpc">magic_quotes_gpc</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.memory-limit">memory_limit</a></li>
<li><a href="http://de.php.net/manual/en/features.safe-mode.php#ini.open-basedir">open_basedir</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.post-max-size">post_max_size</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.register-globals">register_globals</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.upload-max-filesize">upload_max_filesize</a></li>
<li><a href="http://de.php.net/manual/en/ini.core.php#ini.upload-tmp-dir">upload_tmp_dir</a></li>
<li><a href="http://de.php.net/manual/en/ref.session.php#ini.session.use-trans-sid">session.use_trans_sid</a></li>
<li>sowie der User und die Gruppe unter dem PHP ausgeführt wird.</li>
</ul>
<p>PHPsecInfo ist modular aufgebaut und kann von jedem durch weitere Tests ergänzt werden. Informationen dazu, wie auch die Mailingliste finden sich auf der Internetseite des Projekts: <a href="http://phpsec.org/projects/phpsecinfo/">http://phpsec.org/projects/phpsecinfo/</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/566.sicherheitseinstellungen-von-php-prufen.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mit PEAR ebay-Auktionen auf der eigenen Homepage anzeigen</title>
		<link>http://m.tacker.org/blog/446.mit-pear-ebay-auktionen-auf-der-eigenen-homepage-anzeigen.html</link>
		<comments>http://m.tacker.org/blog/446.mit-pear-ebay-auktionen-auf-der-eigenen-homepage-anzeigen.html#comments</comments>
		<pubDate>Thu, 14 Sep 2006 11:40:41 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/446.mit-pear-ebay-auktionen-auf-der-eigenen-homepage-anzeigen.html</guid>
		<description><![CDATA[Für Eva habe ich das vor einigen Tagen gemacht, und hier ist nun auch das Script dazu.]]></description>
			<content:encoded><![CDATA[<p>Für <a href="http://www.evejay.de">Eva</a> habe ich das vor einigen Tagen gemacht, und <a href="http://m.tacker.org/blog/wp-content/uploads/2006/09/ebay.phps">hier ist nun auch das Script dazu</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/446.mit-pear-ebay-auktionen-auf-der-eigenen-homepage-anzeigen.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ViewLevel-Plugin fixed</title>
		<link>http://m.tacker.org/blog/389.viewlevel-plugin-fixed.html</link>
		<comments>http://m.tacker.org/blog/389.viewlevel-plugin-fixed.html#comments</comments>
		<pubDate>Wed, 05 Jul 2006 11:32:33 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/389.viewlevel-plugin-fixed.html</guid>
		<description><![CDATA[Changeset 3951 of WordPress finally removed the old table variables. This broke the ViewLevel-Plugin I was using. You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near &#8216;WHERE meta_key=&#8217;viewlevel&#8217; AND meta_value &#62; 10&#8242; at line 1 I&#8217;ve fixed the plugin [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://trac.wordpress.org/changeset/3951">Changeset 3951</a> of <a href="http://www.wordpress.org/">WordPress</a> finally removed the old table variables. This broke the <a href="http://blog.firetree.net/2005/08/25/viewlevel-20/">ViewLevel-Plugin</a> I was using.</p>
<blockquote><p>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near &#8216;WHERE meta_key=&#8217;viewlevel&#8217; AND meta_value &gt; 10&#8242; at line 1</p></blockquote>
<p>I&#8217;ve fixed the plugin so it&#8217;s now using the right variables.</p>
<p>You can download it here: <a href="http://m.tacker.org/blog/wp-content/uploads/2006/07/viewlevel21.zip" id="p388">ViewLevel 2.1</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/389.viewlevel-plugin-fixed.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>File_Bittorrent 1.0.1 released</title>
		<link>http://m.tacker.org/blog/383.file_bittorrent-101-released.html</link>
		<comments>http://m.tacker.org/blog/383.file_bittorrent-101-released.html#comments</comments>
		<pubDate>Mon, 03 Jul 2006 08:20:31 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PEAR File_Bittorrent]]></category>
		<category><![CDATA[Projekte]]></category>
		<category><![CDATA[Bittorrent]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/383.file_bittorrent-101-released.html</guid>
		<description><![CDATA[Yesterday I have released File_Bittorrent 1.0.1 with some minor bug fixes and enhancements. The complete changelog can be found here. There are currently two open bugs. Bug #5836 (Support for files &#62; 2GB) is a pain in the ass to test, so no progress there. I appreciate every help here. Bug #5880 (Support UTF-8 encoding) [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://m.tacker.org/blog/wp-content/uploads/2006/07/file_bittorrent.gif" id="image381" alt="PEAR File_Bittorrent" class="right" />Yesterday I have released File_Bittorrent 1.0.1 with some minor bug fixes and enhancements. The complete changelog can be found <a href="http://versions.tacker.org/trac/File_Bittorrent/log/trunk?action=stop_on_copy&amp;rev=61&amp;stop_rev=55&amp;mode=stop_on_copy">here</a>.</p>
<p>There are currently two open bugs. <a href="http://pear.php.net/bugs/5836">Bug #5836</a> (Support for files &gt; 2GB) is a pain in the ass to test, so no progress there. I appreciate every help here. <a href="http://pear.php.net/bugs/5880">Bug #5880</a> (Support UTF-8 encoding) is a two sided sword. Of course, UTF-8 is the only future proof way to go but unless the original bittorrent programs do not work with UTF-8, File_Bittorrent won&#8217;t either. Even if other clients do the original bittorrent programs are the reference implementation.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/383.file_bittorrent-101-released.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PHP Bug #37578</title>
		<link>http://m.tacker.org/blog/364.php-bug-37578.html</link>
		<comments>http://m.tacker.org/blog/364.php-bug-37578.html#comments</comments>
		<pubDate>Wed, 24 May 2006 14:07:05 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/364.php-bug-37578.html</guid>
		<description><![CDATA[This is the test for PHP Bug #37578: unserialize_callback_func in htaccess has no effect.]]></description>
			<content:encoded><![CDATA[<p><a href="http://m.tacker.org/blog/wp-content/uploads/2006/05/bug_37578.tgz" id="p362">This is the test</a> for <a href="http://bugs.php.net/bug.php?id=37578">PHP Bug #37578: unserialize_callback_func in htaccess has no effect</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/364.php-bug-37578.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Script to switch svn:externals</title>
		<link>http://m.tacker.org/blog/312.script-to-switch-svnexternals.html</link>
		<comments>http://m.tacker.org/blog/312.script-to-switch-svnexternals.html#comments</comments>
		<pubDate>Fri, 28 Apr 2006 11:20:17 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/312.script-to-switch-svnexternals.html</guid>
		<description><![CDATA[As svn switch does not update URLs in svn:externals I have created this little helper script which does the job. The formatted source is here.]]></description>
			<content:encoded><![CDATA[<p>As svn switch does not update URLs in svn:externals I have created this little helper script which does the job.</p>
<p>The formatted source is <a href="http://m.tacker.org/projects/php/scripts/switch-svn-externals.phps">here</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/312.script-to-switch-svnexternals.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PDODataObject</title>
		<link>http://m.tacker.org/blog/1045.pdodataobject.html</link>
		<comments>http://m.tacker.org/blog/1045.pdodataobject.html#comments</comments>
		<pubDate>Tue, 18 Apr 2006 10:59:06 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/1045.pdodataobject.html</guid>
		<description><![CDATA[PDODataObject ist eine Portierung von PEAR DB_DataObject auf PHP5 und PDO. Zusätzlich zu den bekannten Features von DB_DataObject habe ich noch eine automatische Formulargenerierung sowie die automatische Validierung von Datenbank-Referenzen integriert. Eine stabiles Release liegt zur noch nicht vor, steht aber kurz bevor. Ein Großteil des Codes wird bereits durch Unit-Tests mit PHPUnit geprüft. Quellcode [...]]]></description>
			<content:encoded><![CDATA[<p>PDODataObject ist eine Portierung von <a href="http://pear.php.net/package/DB_DataObject">PEAR DB_DataObject</a> auf PHP5 und <a href="http://de.php.net/pdo">PDO</a>.</p>
<p>Zusätzlich zu den bekannten Features von DB_DataObject habe ich noch eine automatische Formulargenerierung sowie die automatische Validierung von Datenbank-Referenzen integriert.</p>
<p>Eine stabiles Release liegt zur noch nicht vor, steht aber kurz bevor. Ein Großteil des Codes wird bereits durch Unit-Tests mit <a href="http://www.phpunit.de">PHPUnit</a> geprüft.</p>
<h3>Quellcode</h3>
<ul>
<li><a href="http://tacker.org/svn/smallprojects/php/packages/PDODataObject/trunk/">SVN</a></li>
<li><a href="http://tacker.org/trac/smallprojects/browser/php/packages/PDODataObject/trunk/">Quellcode-Browser</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/1045.pdodataobject.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL update on Gentoo broke my WordPress blog</title>
		<link>http://m.tacker.org/blog/277.mysql-update-on-gentoo-broke-my-wordpress-blog.html</link>
		<comments>http://m.tacker.org/blog/277.mysql-update-on-gentoo-broke-my-wordpress-blog.html#comments</comments>
		<pubDate>Thu, 13 Apr 2006 12:59:13 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/277.mysql-update-on-gentoo-broke-my-wordpress-blog.html</guid>
		<description><![CDATA[This weeks update of MySQL on Gentoo introduced UTF-8 as the default character set. This is without doubt the right decision. But it caused some trouble with wordpress. Basically, the title fields of WordPress posts were stored utf8 encoded in the database, this caused them to be displayed like Hersteller von Heizkesseln f&#195;&#188;r Holz So, [...]]]></description>
			<content:encoded><![CDATA[<p>This weeks update of MySQL on <a href="http://m.tacker.org/blog/">Gentoo</a> introduced UTF-8 as the default character set. This is without doubt the right decision. But it caused some trouble with wordpress.</p>
<p>Basically, the title fields of WordPress posts were stored utf8 encoded in the database, this caused them to be displayed like</p>
<blockquote><p>Hersteller von Heizkesseln f&Atilde;&frac14;r Holz</p></blockquote>
<p>So, I&#39;ve update my <a href="http://m.tacker.org/blog/64.script-to-convert-wordpress-content-encoding.html">Script to convert WordPress&rsquo; content encoding</a> to cope with that. It updates the table and fields to use UTF-8 as encoding and collation and optionally decodes utf8 encoded content. Se the <a href="http://m.tacker.org/trac/smallprojects/changeset?new=wordpress%2Fconvert-encoding.php%4023&amp;old=trunk%2Fconvert-encoding.php%4020">change log</a> for details.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/277.mysql-update-on-gentoo-broke-my-wordpress-blog.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOWTO Convert an OpenOffice document into a trac wiki page</title>
		<link>http://m.tacker.org/blog/152.howto-convert-an-openoffice-document-into-a-trac-wiki-page.html</link>
		<comments>http://m.tacker.org/blog/152.howto-convert-an-openoffice-document-into-a-trac-wiki-page.html#comments</comments>
		<pubDate>Tue, 28 Mar 2006 12:37:17 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Projekte]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[trac]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/152.howto-convert-an-openoffice-document-into-a-trac-wiki-page.html</guid>
		<description><![CDATA[I just wrote a small PHP script which helps in converting an OpenOffice document into a trac wiki page. Details on the usage and download is located here: OpenOffice2TracWiki.]]></description>
			<content:encoded><![CDATA[<p>I just wrote a small PHP script which helps in converting an OpenOffice document into a trac wiki page.</p>
<p>Details on the usage and download is located here: <a href="http://m.tacker.org/trac/smallprojects/wiki/Projects/OpenOffice2TracWiki">OpenOffice2TracWiki</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/152.howto-convert-an-openoffice-document-into-a-trac-wiki-page.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Discontinued: WikkaTodo for Wikka Wiki</title>
		<link>http://m.tacker.org/blog/75.discontinued-wikkatodo-for-wikka-wiki.html</link>
		<comments>http://m.tacker.org/blog/75.discontinued-wikkatodo-for-wikka-wiki.html#comments</comments>
		<pubDate>Fri, 27 Jan 2006 11:49:29 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[English]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/75.discontinued-wikkatodo-for-wikka-wiki.html</guid>
		<description><![CDATA[I am no longer working on WikkaTodo (task management in Wikka Wiki) as I have moved the project it was needed for to Trac. The source code can be downloaded via SVN from here. Any one interested in taking over the project?]]></description>
			<content:encoded><![CDATA[<p>I am no longer working on <b>WikkaTodo</b> (task management in <a href="http://wikkawiki.org/HomePage">Wikka Wiki</a>) as I have moved the project it was needed for to <a href="http://projects.edgewall.com/trac/">Trac</a>.</p>
<p>The source code can be downloaded via SVN from <a href="http://versions.tacker.org/svn/wikkawiki/trunk">here</a>.</p>
<p>Any one interested in taking over the project?</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/75.discontinued-wikkatodo-for-wikka-wiki.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Script to convert WordPress&#8217; content encoding</title>
		<link>http://m.tacker.org/blog/64.script-to-convert-wordpress-content-encoding.html</link>
		<comments>http://m.tacker.org/blog/64.script-to-convert-wordpress-content-encoding.html#comments</comments>
		<pubDate>Mon, 12 Dec 2005 21:18:13 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[most visited]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/?p=64</guid>
		<description><![CDATA[This script converts the encoding of all database entries of wordpress into another encoding.]]></description>
			<content:encoded><![CDATA[<p>I&#39;ve just created a script which converts the encoding of all database entries of wordpress into another encoding.<br />
In most cases you would convert into UTF-8.</p>
<p><b>IMPORTANT!</b><br />
Remember to dumpy your database first</p>
<p><code>mysqldump --opt DB_NAME</code></p>
<p>Or use phpMyAdmin:<br />
<a href="http://www.zerokspot.com/docs/howto.phpmyadmin.backup_and_restore/">http://www.zerokspot.com/docs/howto.phpmyadmin.backup_and_restore/</a><br />
<a href="http://www.phpmyadmin.net/documentation/#faq6_3">http://www.phpmyadmin.net/documentation/#faq6_3</a></p>
<p>Do NOT run this script more then once</p>
<p>Place this script inside the wp-content folder of your blog and access it via the browser, e.g. http://yoursite.com/blog/wp-content/convert-encoding.php</p>
<ul>
<li><a href="http://code.coderbyheart.de/svn/wordpress/convert-encoding.php">convert-encoding.php</a></li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/64.script-to-convert-wordpress-content-encoding.html/feed</wfw:commentRss>
		<slash:comments>43</slash:comments>
		</item>
		<item>
		<title>Mehrsprachige Seiten nicht aus der Datenbank füttern</title>
		<link>http://m.tacker.org/blog/63.mehrsprachige-seiten-nicht-aus-der-datenbank-futtern.html</link>
		<comments>http://m.tacker.org/blog/63.mehrsprachige-seiten-nicht-aus-der-datenbank-futtern.html#comments</comments>
		<pubDate>Mon, 12 Dec 2005 13:54:14 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[Erkenntnisse]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/63.mehrsprachige-seiten-nicht-aus-der-datenbank-futtern.html</guid>
		<description><![CDATA[Notiz an mich]]></description>
			<content:encoded><![CDATA[<p>Denn, wenn die Datenbank ausfällt, kann man dem Nutzer immer noch eine schöne mehrsprachige Fehlerseite anzeigen. Daher immer gecachte Includes verwenden.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/63.mehrsprachige-seiten-nicht-aus-der-datenbank-futtern.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP 5.1.0 RC6 breaks backward compatibility with PEAR Date</title>
		<link>http://m.tacker.org/blog/52.php-510-rc6-breaks-backward-compatibility-with-pear-date.html</link>
		<comments>http://m.tacker.org/blog/52.php-510-rc6-breaks-backward-compatibility-with-pear-date.html#comments</comments>
		<pubDate>Thu, 24 Nov 2005 15:35:53 +0000</pubDate>
		<dc:creator>Markus Tacker</dc:creator>
				<category><![CDATA[Allgemeines]]></category>
		<category><![CDATA[English]]></category>
		<category><![CDATA[PEAR]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://m.tacker.org/blog/52.php-510-rc6-breaks-backward-compatibility-with-pear-date.html</guid>
		<description><![CDATA[This is a good example, why we need namespaces in PHP.]]></description>
			<content:encoded><![CDATA[<p>The latest release of PHP [1] will cause great problems as there is a new object available with the name &#8220;Date&#8221; [2]. This will break many existing applications, which rely on PEAR Date [3].</p>
<p>Solution: Run with PHP4 or rename the Date class.</p>
<ul>
<li>[1] <a href="http://www.zend.com/zend/week/week244.php#Heading3">Discussion of ext/date</a></li>
<li>[2] <a href="http://www.tacker.org/date.phps">Code</a> and <a href="http://www.tacker.org/date.php">Result</a></li>
<li>[3] <a href="http://pear.php.net/package/Date">PEAR Date</a></li>
</ul>
<p><em>Update</em><br />
This issue has been fixed in PHP 5.1.1 by removing the Date class.</p>]]></content:encoded>
			<wfw:commentRss>http://m.tacker.org/blog/52.php-510-rc6-breaks-backward-compatibility-with-pear-date.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

