Wordpress 2.2 arrived a day ago.
Updating was no problem at all. Prominent new features are wigdet support without the need for an external plugin and a working atom 1.0 feed.
I could drop two plugins: the widget plugin and the atom10 plugin. Nice. All others work as before (some important to mention are UTW, WP-Cache and the nice extended live archive(*).
A really nice site effect of the update: the WP Team finally managed to put a “SET NAMES blah” into wp-db.php, so that setting “UTF-8″ i.e. in wp-admin really means UTF-8 in the database. I always hacked my wp-db(**) for my other blog planet-punk.de, since there are a lot of old posts from another legacy system that _are_ indeed UTF-8 but which where maltransformed by wp without that hack before 2.2.
I do have a local development system on my mac but i tend to test things twice or more often. Other people maybe don’t have or want that luxury and need to udate their blogs directly on the server. Either way, it’s a good idea, to put your blog to maintenance while updating your wp core files. This is easily accomplished with .htacess and mod_rewrite. First create a file “maintenance.html” for your visitors. Than look up your external ip and add the following to your .htaccess:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REMOTE_ADDR} !87.78.68.17 [NC]
RewriteRule ! maintenance.html$ maintenance.html [R=301,L]
</IfModule>and replace 87.78.68.17 with your external ip. Remember commenting these entries when you’re done.
(*) If you have any questions about my plugins, don’t hesitate to ask, i just don’t want a plugin list in case of bugs in any plugin.
(**) The hack was: Add the following to __construct in your wp-db.php (./wp-includes/) :
$this->select($dbname);
$this->query("SET NAMES 'utf8'");Share This
If you’re wordpress pingbacks or tracksbacks show everything but the post text it’s possible that you don’t have the right css class in your div. The div element that contains the entry text should be classed with “entry”.
Share This
Why on earth has my ‘post_type’ column on my wp 2.0.x based blog no default value? Ultimate Tag Warrior UTW3-14159265 will break and show no tags.
If anyone else has this problem, add
$typelimitsql = "(post_status = 'publish' OR post_status = 'static')"; // From previous version of utw
in ultimate-tag-warrior-core.php right before the class definition. It’s taken from the previous UTW Version.
Edit:
Upgrading to WP 2.1.x changed the table structure… A little hint would have been nice in the utw changelog.
Share This
Auch wenn ich allerortens lese, dass die meisten Suchmaschinen
<meta name="keywords" content="blah, und, blub" />
nicht mehr nutzen, halte ich diese Art von Metainformationen immer noch für sinnvoll. Und falls sie es nicht sein sollten, schaden können sie auch nicht.
Um sich die manuelle Tipparbeit zu sparen, kann man die Arbeit von Ultimate Tag Warrior erledigen lassen.
Folgende simpler Eintrag im entsprechenden Headertemplate des Themes erzeugt eine Liste aller Tags aller Posts:
<?php
if (function_exists('UTW_ShowWeightedTagSetAlphabetical')) {
print '<meta name="keywords" content="';
UTW_ShowWeightedTagSetAlphabetical(
'',
array(
'default' => '%tagdisplay%, ',
'last' => '%tagdisplay%'
)
);
print '" />';
}
?>Share This
Ein passender, erster seitenspezifischer Eintrag:
Nachdem ich gerade ohne Probleme WordPress 2.0.2 mit dem wundervollen Tiger Style Administration Panel von Steve Smith eingerichtet habe, muss ich mich direkt drüber ärgern, dass auch dort im Safari unter Mac OS X der Default Visual Rich Editor von WordPress nicht angezeigt wird.
Anscheinend führt der Visual Rich Editor im Safari direkt zu einem Totalabsturz. Leider funktionieren selbst die Quicktags nicht im Safari bzw. die Buttons erscheinen erst gar nicht.
Das allerdings kann man leicht ändern: Man braucht nur die Datei admin-functions.php im Verzeichnis wp-admin wie folgt anpassen:
More…
Share This