labs.dagensskiva.com

We know we’ve neglected you for a bit, and we’re sorry about that. We’ll try to step it up and do better.

Please try the new version of More Fields (1.4b1) before we submit it to the WordPress Plugin Repository.

Download: More Fields 1.4b1

Please note that support questions should be discussed in the support forum, not in this comment thread.

Changed in this version:

copy wp-admin/js/post.js to wp-content/plugins/more-fields/post.js
wp-content/plugins/more-fields/post.js: Comment out line 234
wp-content/plugins/more-fields/post.js: Comment out line 235
wp-content/plugins/more-fields/post.js: Comment out line 236
wp-content/plugins/more-fields/post.js: Comment out line 237

Update

New version (Beta 2) with more compatibility with legacy branches (2.8).

Download: More Fields 1.4b2

Update 2: Beta 3

Download: More Fields 1.4b3

Implemented $wp_query->add_rule in $more_fields->generate_rewrite_rules:754, so that php calamity is avoided.

An updated version of More Fields (1.3) is released for use with WordPress 2.8+.

It fixes problems with right column boxes and post types. For bugs and irregularities, please visit the forum.

It has gone a little un-noticed here, but we’ve quietly slipped out More Fields version 1.2, compatible with the new admin revealed in WordPress 2.7.

Whilst the changes in the admin layout (2.7 is different from 2.6 which is different from 2.5), together with the rapid release cycle that WordPress adheres to, have been frustrating, but we are very pleased with the way things now stand, and we intend to keep More Fields current with new releases of WordPress.

The plugin can be downloaded from here.

Enjoy!

And lastly, a bashful call for donations — if you find this plugin useful for your commercial WordPress projects, a donation will ensure future development, essentially buying my time from off other projects. And will keep me plied with delicious beverages.

Undeniably inspired by the iPod Touch, I put together a WordPress plugin that displays covers in the ‘Coverflow’ fashion. The actual animated browser comes from Weber Design Labs (open source and brilliant), but I hacked it slightly, adding parameters specifying what posts to get using query arguments sent to dymanically generated xml file. I also changed the colours, reflection, and changed the slider from being images to being vectors (so that we can change the colours and scale it).

This is currently being used for the advanced search.

Here’s what it looks like.

Pretty!

I thought I’d share my current and favorite, .screenrc settings:

vbell off
autodetach on
defscrollback 10000
startup_message off
pow_detach_msg "Screen session of \$LOGNAME \$:cr:\$:nl:ended."
caption always "%{= gk}%-Lw%{= rW}%50> %n%f* %t %{-}%+Lw%< %= %{= Gk} %H %{= rW} %l %{= Gk} %0c:%s %d/%m %{-}"
shell -$SHELL

Looking like:

From the bottom left to right:

• Screen name ‘tabs’: %-Lw%{= rW}%50> %n%f* %t %{-}%+Lw%<
• Server name: %H
• Server load: %l
• Date & time: %0c:%s %d/%m

I put this togehter a few years ago, back in London, when working at multimap, but I cannot remember where I sourced it from. So, I’m putting it here for posterity.

What is your favourite .screenrc configuration?

For the type of content written for dagensskiva.com the ‘code’ button in the editor has no use whatsoever. Instead we find much more use for a ‘cite’ button, a tag that is frequently added to posts, but there is no button for it. This JavaScript snippet will replace the code button with a functional cite button:

  index = edButtons.length;
  edButtons[index] = new edButton('ed_cite', 'cite', '<cite>', '<\/cite>','c');
  jQuery('#ed_code').attr('value', 'cite');
  jQuery('#ed_code').attr('onclick', 'edInsertTag(edCanvas, ' + index + ');');
  jQuery('#ed_code').attr('id', 'ed_cite');

This code registers the button, then changes the properties of the ‘code’ button to transform it into a ‘cite’ button. Works in both WordPress 2.3 and 2.5.

For some reason or other there are actions in WordPress that have translatable fields in them, so when these actions are used on other languages than English, they change. They are actions involving the $page_hook variable., e.g. admin_head-$page_hook. I ran into this problem when updating More Fields. The problem in the context of plugins is that the language is not loaded when the plugins are loaded, so that the needed translation is not available. To get around this, the actions requiring translation are called at the ‘admin_init’ action instead.

function mf_pre_queue_js () {
    add_action('load-' . sanitize_title(__('Settings')) . '_page_more-fields', 'mf_queue_js');
}
add_action('admin_init', 'mf_pre_queue_js');

I got help with this on the wp-hackers mailng list – a great source for WordPress insights.

>Try adding your actions on the init hook, I think that runs after
>the translatable stuff has been loaded and setup.

Correct.

Everything related to languages should be done at init or later, so that everything is loaded and any plugins that modify the content are loaded.

So, at the init/admin_init hook, we’re safe to assume that the appropriate language has been loaded.

I’ve just updated More Fields to version 0.6, compatible with WordPress 2.5.

New features:

• Compatible with the new admin introduced in WordPress 2.5
• Set default value in a select list.
• Enable right hand column boxes in WP 2.5.
• Option of removing the ‘Related’ links on the right hand side on the Write/Edit page.
• A new set of actions, enabling users to change the behavior of More Fields. The documentation has been updated to include an example on how to use these actions.

The plugin can be downloaded from wordpress.org.

Any feedback is always greatly appreciated.

We’ve had a confusing way of specifying the medium (physical, or virtual) and format (i.e. length) of a record release at dagensskiva.com. We have now restructured how this is represented, into two main components:

Formats:

• album
• single
• ep
• song
• box
• playlist

Media:

• cd
• 7”
• 10”
• 12”
• mp3
• aac
• wma
• myspace

In addition to this, we specify how mauy of the specified media constitutes the release, so that an album can be specified as, e.g. album (2×cd), song (mp3), box (10×12″), etc…

Did we miss anything?

I hashed together a plugin that enables authors to specify a specific template file to be used for a post (this functionality is already built in for pages, but not for posts).

<?php
/*
Plugin Name: Template for posts
Plugin URI: http://labs.dagensskiva.com
Description: Set the template file for a post by setting the Custom Field 'dsc_template' to the filename of the template
Version: 0.1
Author: Henrik
*/
?>

function dsc_post_template() {
  global $post, $wp_query;

  if (count($wp_query->posts) == 1) {
    $id = $wp_query->posts[0]->ID;
    if ($temp = get_post_meta($id, 'dsc_template', true)) {
      include( TEMPLATEPATH . '/' .$temp );
      exit(0);
    }
  }
}
add_filter('template_redirect', 'dsc_post_template', 9);

Usage: a Custom Field called ‘dsc_template’ is set to equal the basename of the file, e.g. ‘interview.php’, placed inside your theme folder. Simple as that. It only applies the template file if $wp_query contains only one post, i.e. where the template file ’single.php’ would normally be applied.