<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wordpress on dennogumi.org</title>
    <link>https://www.dennogumi.org/tags/wordpress/</link>
    <description>Recent content in Wordpress on dennogumi.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2026 Einar under a CC-BY-SA 4.0 license. Some images are AI-generated. Header design by [Melissa Adkins](https://melissaadkins.com) with [assets from Freepik](https://freepik.com).</copyright>
    <lastBuildDate>Sat, 10 Jan 2009 21:02:59 +0000</lastBuildDate><atom:link href="https://www.dennogumi.org/tags/wordpress/feed/atom.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>New theme and 2.7</title>
      <link>https://www.dennogumi.org/2009/01/new-theme-and-2.7/</link>
      <pubDate>Sat, 10 Jan 2009 21:02:59 +0000</pubDate>
      
      <guid>https://www.dennogumi.org/2009/01/new-theme-and-2.7/</guid>
      <description>&lt;p&gt;As you have noticed, I have upgraded FailWordpress to version 2.7, getting also a new theme in the process. The header image is temporary, until I or &lt;a href=&#34;http://www.melissaakdins.com&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;someone else&lt;/a&gt; gets it fixed. The gallery has also changed: I ditched WPG2 and Gallery 2 because they kept on breaking every time I upgraded Wordpress (of course it&amp;rsquo;s probably Wordpress&amp;rsquo;s API and schema instability to blame).&lt;/p&gt;&#xA;&lt;p&gt;Therefore, the gallery had been organized and most likely older posts won&amp;rsquo;t show images anymore (I&amp;rsquo;ll get to fix those eventually).&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Wordpress SNAFU</title>
      <link>https://www.dennogumi.org/2008/05/wordpress-snafu/</link>
      <pubDate>Sun, 04 May 2008 07:35:07 +0000</pubDate>
      
      <guid>https://www.dennogumi.org/2008/05/wordpress-snafu/</guid>
      <description>&lt;p&gt;Yesterday I updated _&lt;a href=&#34;http://www.stealsaga.net&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;The S.T.E.A.L. Saga&lt;/a&gt; _to Wordpress 2.5.1. I thought the upgrade would be painless, but I was wrong. First of all, the auto plugin updater kind of confused between the various plugins, so it marked some as updateable although they weren&amp;rsquo;t. Then, some plugins (albeit incompatible), &lt;strong&gt;disappeared&lt;/strong&gt; from the plugin list (the fix was downloading a more recent version).&lt;/p&gt;&#xA;&lt;p&gt;The biggest issue was, however, the mangling of my .htaccess file due to a wrongly-generated permalink rule that was without a trailing slash (/). Such a badly done .htaccess would cause:&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Wordpress 2.5</title>
      <link>https://www.dennogumi.org/2008/03/wordpress-2.5/</link>
      <pubDate>Sun, 30 Mar 2008 09:21:13 +0000</pubDate>
      
      <guid>https://www.dennogumi.org/2008/03/wordpress-2.5/</guid>
      <description>&lt;p&gt;I have upgraded this blog to Wordpress 2.5. As a result, there are some functions, such as the image gallery, that have been disabled due to the annoying habit of the Wordpress developers of making core changes in very little time.&lt;/p&gt;&#xA;&lt;p&gt;Please report any problems you find, and notice that although the thumbnails look truncated in the new gallery, the full images are actually displayed correctly. I had to fiddle a bit wit the &amp;ldquo;new media manager&amp;rdquo;, not only because it&amp;rsquo;s in Flash, but because at least on Linux it gives odd results (apparently no one from the WP team bothered to check past Win and OSX?).&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>New theme</title>
      <link>https://www.dennogumi.org/2007/10/new-theme/</link>
      <pubDate>Thu, 11 Oct 2007 21:13:36 +0000</pubDate>
      
      <guid>https://www.dennogumi.org/2007/10/new-theme/</guid>
      <description>&lt;p&gt;After some thoughts, I switched dennogumi.org to &lt;a href=&#34;http://diekretzschmars.de/dkret-theme/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;the dKret theme&lt;/a&gt;. Please report any errors you may find. The header is the default image, but it will be changed soon (hint: Melissa, you already know what to do&amp;hellip;).&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Unimpressive management: Wordpress 2.3</title>
      <link>https://www.dennogumi.org/2007/10/unimpressive-management-wordpress-2.3/</link>
      <pubDate>Sun, 07 Oct 2007 19:01:33 +0000</pubDate>
      
      <guid>https://www.dennogumi.org/2007/10/unimpressive-management-wordpress-2.3/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve recently upgraded this blog to &lt;a href=&#34;http://wordpress.org&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Wordpress 2.3&lt;/a&gt;. While I&amp;rsquo;m interested in the new changes this release brings (like tagging support) I question the way the transition to the new version was handled.&lt;/p&gt;&#xA;&lt;p&gt;In particular, I am referring to the (questionable) &lt;a href=&#34;http://boren.nu/archives/2007/09/05/wordpress-23-database-schema-changes/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;idea of breaking the database schema  three weeks before the release&lt;/a&gt;. Given the amount of breakage that brought upon plugins, it should have been announced at the start of the 2.3 development cycle.  Right now, heavily customized installations are a pain to update (that&amp;rsquo;s why &lt;a href=&#34;http://www.stealsaga.net&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;&lt;em&gt;The S.T.E.A.L. Saga&lt;/em&gt;&lt;/a&gt; is staying on 2.2 for now).&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
