• Download on WordPress.org
• Support Forums (post bug reports / requests here)

A quick screenshot:

In case you’re wondering if you will loose existing ads from the theme – no, they will be imported by the plugin.

For theme developers – to add “ad location” support in your theme, pass an action tag to the registerAdLocation() method. Example:

if(defined('AdManager::VERSION'))
  AdManager()->registerAdLocation('after_header', __('After theme header'));

dev.digitalnature.eu/atom

That demo installation uses sqlite (a portable file database-system), that’s why the slowness and high number of queries (I’m practically forced to do 20 queries just to get the database schema).

Nothing special on the surface because the API is far from complete. If you want to log in into the dashboard, use admin/admin credentials. There are no user access checks yet, so you can delete pretty much everything in there

To give you an idea of how far a developer can extend this application, take the dashboard as an example – it’s actually a plugin (here module).

Do you have any name suggestions for this application? Post them in the comments, I’m out of inspiration here. The “Atom” thing is just temporary…

2012

And some older 1 GB promo codes you probably already know:

I-LIKE-POLAND
SKYFISH-IS-COOL
CONNECT-WITH-SUPPORT

Don’t know what Wuala is? Most of you are probably familiar with Dropbox, a popular online file storage service. Wuala is one of its competitors, and in my opinion the best out there considering the features it provides.

If you want to get an account and start off with 3 GB, you can use my invite code when signing up

Why? The main reason is simply because I love WordPress, and I’m starting to feel its limits. Leaving aside the fact that you’re forced to work with outdated technology, there’s simply no way to implement certain functionality without resorting to all sorts of ugly hacks. These hacks can break compatibility with plugins, slow the site or just …be ugly. The second reason is my desire to learn PHP better.

Right now, less than 20% of the app is complete, which is:

• the database API, which uses the PDO abstraction layer, so multiple database types are supported by default, not just mysql; also all write operations are wrapped within transactions – that means no db inconsistency issues when dealing with heavy traffic. The table structure differs from the one in WP and seems to be much faster from a few quick tests I made so far.
• the option API (the same type of functionality as in WP)
• internationalization API, about 4-5 times faster than WP’s, even when reading messages from PO files; all translations are handled by a single “t()”-named function, including plurals.
• transient API (they get their own db table with an expiration column)
• a basic cache handler, for the moment it’s identical to WP’s object cache
• action / filter API, almost the same as in WP
• the User abstraction class (provides API for managing users)

The plugin system is replaced by modules, which are basically objects on which the developer can attach events, instead of hooking functions to actions. Also options are very easy to manage from inside them since you get add/update/getOption inherited methods…

There’s no graphic interface so far, so no demo yet

update: 08/02

Finished cron (fake, like the one in WP), taxonomy and asset dependency APIs, and added XCache and APC cache extensions. I’ll be opening a repository for the source soon

update: 17/02

Finished controller (mapping URL routes to actions), along with some basic theming API. I don’t think I even need to compare this to WP’s rewrite-template system… An early demo and a Github repository should be up next week.

What does it do:

• Allow your site users to rate posts (of any kind)
• Display the average post rating, vote count or weighted (bayesian) rating within your posts
• Display a widget with the top rated posts in your sidebar

A few screenshots:

• Download on WordPress.org
• Support forums

atom()->setContextArgs('primary_menu', array('walker' => new ThumbMenuWalker()));

class ThumbMenuWalker extends AtomWalkerNavMenu{

  // register the thumbnail size, 64 pixel square, cropped
  function __construct(){
    add_image_size('nav-thumb', 64, 64, true);
  }

  // override start_el
  function start_el(&$output, $item, $depth, $args) {

    $classes = empty($item->classes) ? array() : (array)$item->classes;

    $classes = join(' ', apply_filters('nav_menu_css_class', array_filter($classes), $item, $args));
    $classes = $classes ? ' class="'.esc_attr($classes).'"' : '';

    $output .= "\n<li{$classes}>";

    $attributes  = !empty($item->attr_title) ? ' title="'.esc_attr($item->attr_title).'"' : '';
    $attributes .= !empty($item->target) ? ' target="'.esc_attr($item->target).'"' : '';
    $attributes .= !empty($item->xfn) ? ' rel="'.esc_attr($item->xfn).'"' : '';
    $attributes .= !empty($item->url) ? ' href="'.esc_attr($item->url).'"' : '';

    $excerpt = $thumb = '';

    // 2nd level+
    if($depth > 0){
      $post = new AtomObjectPost($item->object_id);

      // thumbnail image
      if(post_type_supports($item->object, 'thumbnail'))
        $thumb = $post->getThumbnail('nav-thumb');

    if($thumb)
      $attributes .= ' class="clear-block"';

      // short description from the content, 100 is the max. character count
      $excerpt = $post->getContent(100, array(
        'cutoff'       => 'sentence',  // cut off just after the sentence ends
        'allowed_tags' => array(),     // no html
        'more'         => false,       // no 'more' text / link
      ));

      if($excerpt)
        $excerpt = "<small>{$excerpt}</small>";

      atom()->resetCurrentPost();
    }

    $content = $args->link_before.$thumb.'<span class="tt">'.apply_filters('the_title', $item->title, $item->ID).$excerpt.'</span>'.$args->link_after;
    $output .= apply_filters('walker_nav_menu_start_el', "{$args->before}<a{$attributes}>{$content}</a>{$args->after}", $item, $depth, $args);
  }

}

The CSS:

.nav img, .nav .no-img{
  float:left;
  margin-right: 5px;
} 

.nav .tt{
  overflow:hidden;
  display:block;
  font-weight:bold;
}  

.nav small{
  font-size:11px;
  display:block;
  margin-top: 5px;
}

The result should be something like this:

First, define the maximum image sizes (note that we will only downsize, smaller images will get browser-resized):

define('MAX_AVATAR_WIDTH', 96);
define('MAX_AVATAR_HEIGHT', 96);

This goes in the child theme’s functions-user.php file.

Next, create the form which lets users upload the image. I chose the author.php template here, but you can easily add it inside the dashboard trough some hooks.

<?php if(is_user_logged_in() && get_current_user_id() === (int)get_query_var('author')): ?>
<form method="POST" enctype="multipart/form-data" action="">
  <input type="file" name="user_avatar" />
  <input type="hidden" name="action" value="wp_handle_upload" />
  <input type="submit" value="Upload new Avatar" />
</form>
<?php endif; ?>

The actual upload processing. You can have this in the same author template before get_header(), or inside the child theme’s functions:

if(is_user_logged_in() && isset($_FILES['user_avatar'])){

  // we need this for the wp_handle_upload function
  require_once ABSPATH.'wp-admin/includes/file.php';

  // ID of the current user
  $current_user_id = get_current_user_id();

  // just be aware that GIFs are annoying as fuck
  $allowed_image_types = array(
    'jpg|jpeg|jpe' => 'image/jpeg',
    'png'          => 'image/png',
    'gif'          => 'image/gif',
  );

  // let wp do the upload checks, file moving etc.
  $status = wp_handle_upload($_FILES['user_avatar'], array('mimes' => $allowed_image_types));

  // no errors? Get the uploaded file path and resize it
  if(empty($status['error'])){

    // resize it
    $resized = image_resize($status['file'], MAX_AVATAR_WIDTH, MAX_AVATAR_HEIGHT, $crop = true);

    // resize failed, display the reason
    if(is_wp_error($resized))
      wp_die($resized->get_error_message());

    // determine the resized file URL
    $uploads = wp_upload_dir();
    $resized_url = $uploads['url'].'/'.basename($resized);

    // insert the file URL into the current user meta
    update_user_meta($current_user_id, 'custom_avatar', $resized_url);

  // error, show it
  }else{
    wp_die(sprintf(__('Upload Error: %s'), $status['error']));

  }

}

Finally, hook into the avatar display function and get the avatar user meta field:

add_filter('get_avatar', 'custom_avatars', 10, 3);

function custom_avatars($avatar, $id_or_email, $size){
  if(is_user_logged_in()){
    $current_user = wp_get_current_user();
    $image_url = get_user_meta($current_user->ID, 'custom_avatar', true);
    if($user_avatar !== false)
      return '<img src="'.$image_url.'" class="avatar photo" width="'.$size.'" height="'.$size.'" alt="'.$current_user->display_name .'" />';
  }

  return $avatar;
}

Because get_the_excerpt() / the_excerpt() will call get_the_content() if the post doesn’t have an excerpt set, in many cases you get your filter applied on excerpts as well. This can lead to unwanted text inside them, like escaped javascript code.

If you don’t want your filter to be applied to excerpts, then remove it during the time in which the excerpt is being generated. Here’s one way to do it:

add_filter('the_content', 'my_plugin_filter');

// remove our filter, as early as possible
add_filter('get_the_excerpt', function($text){
  remove_filter('the_content', 'my_plugin_filter');
  return $text;
}, -999);

// add it back after wp_trim_excerpt was applied, in case the theme calls the_content after
add_filter('get_the_excerpt', function($text){
  add_filter('the_content', 'my_plugin_filter');
  return $text;
}, 999);

Another way is to check if the excerpt is being processed within your filter:

add_filter('the_content', 'my_plugin_filter');

function my_plugin_filter($text){
  if(in_array('get_the_excerpt', $GLOBALS['wp_current_filter'])) return $text;

  // not the excerpt, do your stuff here...
  return $text;
}

Your translation will become active just after you push the save button (.mo and .po files are created in your child theme folder).

Installation as usual, download the archive and copy the module in your child theme “mods” directory. (This is now included in the theme package)

I might port this to a plugin when I have the time, so that people can translate plugins or other themes too. Post your suggestions or encountered bugs in the comments.

Installation:
- download the module
- upload it into your child theme’s /mods/ folder, and activate it trough the theme settings

You can see a demo on the Mystique’s preview page

This will only work on browsers that support the new HTML 5 History API. That means all browsers, except Internet Explorer of course. IE users or users without javascript will navigate your site normally.

Known Issues:

• if you have any plugins that add javascript at some point in the page, then most likely they will not work well with this, because currently the module doesn’t inject javascript from the target page.
• back/forward is not yet implemented. I’m working on it

What’s the purpose of it? Apparently it decreases page load, by 20-40% from what I’ve seen so far…