Read more on the 1.0 release here.

Ok – it’s almost that easy but in the end it took me quite a while to find the proper solution for pages with very little content on it… So to save you the same hassle – here is a how to. I would suggest you add the CSS code to a custom style stylesheet rather than modifying the style.css to keep things easy when upgrading K2.

Step 1: footer.php
Before we start with the required CSS code we need to make a slight adjustment to the footer.php to ensure that the footer div is included in the page div which acts as the wrapper div.

Move this line:

</div> <!-- Close Page -->

Towards the bottom, right before this line:

<?php wp_footer(); ?>

Step 2: make html and body both 100% in height

html, body {
 height: 100%;
 }

Step 3: adjustments to #page

#page {
 padding-top: 0;
 border-bottom: none;
 height: auto !important;
 height: 100%;
 min-height: 100%;
 }

Step 4: adjustments to #header

#header {
 border-top:  20px solid #fff;
 }

Step 5: adjustments to .content

.content {
 padding: 0 20px 62px;
 }

Step 6: adjustments to #footer

#footer {
 padding: 10px 0 10px;
 position: absolute;
 bottom: 0;
 width: 100%;
 }

Final action

Ok, that’s basically it although you now need to check if some values need to be changed or not. I have changed the padding of the footer (see step 6) to 10px for both the top and the bottom. With these padding values I need a padding value of 62px for the bottom in the content div (see step 5).

Tip: to see how much you need for the bottom padding in step 5 is to add a background color to the footer and then make a screenshot. In, for example, Photoshop you can then easily get the height of the footer. Just a few more pixels to that as a spacing between the content and the footer and you are all set.

Tested with K2 r743 with FF3, IE6, and IE7.

For whoever needs a Dutch translation file for it – here it is. Just copy the code below to a newly created file called nl_NL.php in the /wp-content/plugins/db-cache/languages/ directory and you are ready to go.

<?php

$dbc_labels['configuration'] = "Configuratie";

$dbc_labels['activate'] = "Activeren";

$dbc_labels['timeout'] = "Laat een cached query verlopen na";
$dbc_labels['timeout_desc'] = "minuten. (Verlopen bestanden worden automatisch verwijderd.)";

$dbc_labels['tablesfilter'] = "Tabellen om te cachen";

$dbc_labels['saved'] = "Instellingen opgeslagen.";
$dbc_labels['cantsave'] = "De instellingen konden niet worden opgeslagen. &lt;a href=\"http://codex.wordpress.org/Changing_File_Permissions\" target=\"blank\"&gt;CHMOD 755&lt;/a&gt; bestand: &lt;u&gt;config.ini&lt;/u&gt;";
$dbc_labels['activated'] = "Caching geactiveerd.";
$dbc_labels['notactivated'] = "Caching kan niet worden geactiveerd. &lt;a href=\"http://codex.wordpress.org/Changing_File_Permissions\" target=\"blank\"&gt;CHMOD 755&lt;/a&gt; de folder: &lt;u&gt;wp-content&lt;/u&gt;";
$dbc_labels['deactivated'] = "Caching uitgeschakeld. Cache bestanden verwijderd.";
$dbc_labels['cleaned'] = "Cache bestanden verwijderd.";
$dbc_labels['expiredcleaned'] = "Verlopen cache bestanden verwijderd.";

$dbc_labels['save'] = "Opslaan";
$dbc_labels['clear'] = "Leeg de cache";
$dbc_labels['clearold'] = "Leeg de verlopen cache";

?>

Just have a look at the video to see the new features of 2.7 for yourself or go to:

• wordpress.org/development/2008/12/coltrane/
• codex.wordpress.org/Version_2.7

Simply uninstalling the plugin wasn’t good enough so after some research on the WordPress Support Forum I came across the following procedure to fix the issue:

1. Disable (and if needed remove) the plugin which causes the visual text editor of functioning normally.
2. Clear the browsers cache (in Firefox, use the Clear Private Data menu) and restart the browser.
3. Go to /wp-includes/js/tinymce/tiny_mce_config.php and find the following line:

   'compress' => true,

   and change the true value into false.

4. Log on to your WordPress admin area and now the visual text editor should be functional again.
5. If everything is working you can now undo the code change of step 3.

As you can see, the WP-Syntax plugin is still running and I can still use the visual text editor but that will take some modifications of the WP-Syntax code. I will post those changes later this week.

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/var/tmp//1220989448) is not within the allowed path(s): (/home/usr123/:/tmp:/usr/local/lib/php/) in /usr/home/usr123/../wp-includes/functions.php on line 1960

Warning: touch() [function.touch]: open_basedir restriction in effect. File(/var/tmp/1220989448) is not within the allowed path(s): (/home/usr123/:/tmp:/usr/local/lib/php/) in /usr/home/usr123/../wp-admin/includes/file.php on line 122

Warning: fileowner() [function.fileowner]: open_basedir restriction in effect. File(/var/tmp/1220989448) is not within the allowed path(s): (/home/usr123/:/tmp:/usr/local/lib/php/) in /usr/home/usr123/../wp-admin/includes/file.php on line 487

Warning: unlink() [function.unlink]: open_basedir restriction in effect. File(/var/tmp/1220989448) is not within the allowed path(s): (/home/usr123/:/tmp:/usr/local/lib/php/) in /usr/home/usr123/../wp-admin/includes/file.php on line 489

This morning I finally found THE hint that has lead me to the solution to fix it and to be honest it was amazingly simple!!

WordPress is trying to use the wrong path, duhh, but the correct path is also provided in the error message. In my case I have to point WordPress to the /tmp path instead of the found /var/tmp path!!

When you follow the error messages you finally end up in the get_temp_dir function (/wp-admin/includes/file.php:97) which basically provides the answer straight away after you run a full source code search on WP_TEMP_DIR…

function get_temp_dir() {
 if ( defined('WP_TEMP_DIR') )
 return trailingslashit(WP_TEMP_DIR);

So the solution is to define WP_TEMP_DIR in the wp-config.php file:

define('WP_TEMP_DIR','/tmp');

Happy auto updating!

While writing the widget I also noticed some bugs and the need for some extra features.

Features:

1. Ship a widget with it – you can use my Agenda Widget for this, see source.
2. Show today’s and all day event’s until their end time.
3. Remove time notification when it’s a all day event.
4. Change $title_tag into to the $before and $after model for more template flexibility.
5. Localization by translation domain. Change:

   __('text')

   into:

   __('text', 'agenda')

   Have also used that in the plugin I have created.

6. Ship a .pot with it for translators. I will translate into Dutch when available.

Bugs:

1. When repeating on a daily basis the start time changes (looks like the function add (for example) 24 hours to the end time instead of the start time). )
2. Visual editor isn’t working.
3. Time droplists are out of sync with the input boxes (further to the right).
4. When using agenda_compromissos() the <a href> isn’t populated.
5. Add ‘no events’ message when there are no events to show, I’m now getting an error message.
6. Styling doesn’t fit in the (smaller) crazyhorse design of 2.7 and perhaps it’s an idea to keep in line with the default WP colors for the background.

Remarks:

1. The ‘Event’ page should not be registered as a menu item when you use 2.7 as the structure of the menu’s has changed. The Add New link on the Events page will follow the style WP is using on the Posts and Pages pages.

Questions:

1. How can you get the location and date(s)/time(s) visible in the post?

I will put some effort in this plugin as well as I really like it so I will start cracking the extra features and bugs as well and will make suggestions to DGMike.

• Word count! Never guess how many words are in your post anymore.
• Image captions, so you can add sweet captions like Political Ticker does under your images.
• Bulk management of plugins.
• A completely revamped image control to allow for easier inserting, floating, and resizing. It’s now fully integrated with the WYSIWYG.
• Drag-and-drop reordering of Galleries.
• Plugin update notification bubble.
• Customizable default avatars.
• You can now upload media when in full-screen mode.
• Remote publishing via XML-RPC and APP is now secure (off) by default, but you can turn it on easily through the options screen.
• Full SSL support in the core, and the ability to force SSL for security.
• You can now have many thousands of pages or categories with no interface issues.
• Ability to move your

  wp-config

  file and

  wp-content

  directories to a custom location, for “clean” SVN checkouts.

• Select a range of checkboxes with “shift-click.”
• You can toggle between the Flash uploader and the classic one.
• A number of proactive security enhancements, including cookies and database interactions.
• Stronger better faster versions of TinyMCE, jQuery, and jQuery UI.
• Version 2.6 fixes approximately 194 bugs.

Of all the improvements I really enjoy the new image system and the revision control as that where definitely points which needed improvement in previous versions of WordPress. If you want to see the new features in action, the WordPress guys have made a short video in which they explain the new features:

See wordpress.org/development/2008/07/wordpress-26-tyner/ for more background details on WordPress version 2.6.