Recently, I put openSUSE on my laptop, with the kde4 windows manager, and it was (kind of) love at first sight. A couple of days ago, however, I played around with some vpn related packages to login to my work’s vpn. Using Yast, I installed a couple of packages and Yast automatically installed some dependencies with them (of course). Little did I know, that I was breaking my wifi…
After I was done, I noticed that while knetworkmanager still showed the available wireless networks, I couldn’t connect to any of them. Clicking on a connection that had been set up before, didn’t seem to do anything. Never underestimate the power of Linux, however. (OK, it shouldn’t have broken in the first place, but well…) What did I find in /var/log/NetworkManager? This:
Not being a Linux-guru myself, this didn’t mean a whole lot to me, but it provided me with the necessary seeds to sow in the google-field, and true enough, after a couple of minutes, google bore a nice ripe peace of fruit: the answer. A short synopsis for the not so adventurous: I had to remove the (inadvertently installed) package “NetworkManager-kde4″, which worked perfectly.
Now openSUSE and I are on friendly terms again.

Drupal: Invoke comments using contemplate
The Contemplate module (or Content Templates module) is a bless when you want to give a certain node type a specific layout. It’s easier than using node-type.tpl.php from an administrative point of view because you don’t need to upload new css-files, and from a designing point of view because the module provides a convenient list of available variables.
What wasn’t immediately clear to me, however, was how to include the commenting section in a node using Contemplate (or node-type.tpl.php for that matter). A search on drupal.org eventually leaded me to using this:
if (function_exists(‘comment_render’) && user_access(‘post comments’)) {
print “<div class=’cscomment’>”;
print “<h3 class=’field-label’>Comments</h3>”;
print comment_render($node);
$node->comment = NULL;
print “</div>”;
}?>
which works fine at the moment.
Note that this is working for Drupal 5, but in the same thread, solutions for Drupal 6 have been suggested.