Get Firefox 2
Hover 0.7.3 available
July 20th, 2014 :: Permalink :: Trackback

Besides a couple of minor bugs this release fixes one major bug with php >= 5.4

*Warning: Creating default object from empty value in…/wp-content/plugins/hover/hover.php on line 182*
by bd in wordpress
  Comments Off

Mojolicious and sprintf loggin
February 27th, 2013 :: Permalink :: Trackback

Don’t want to write things like

app->log->debug("foo $config->{foo} versus ".stat->mtime." seconds");

but rather

app->log->debug("foo %s versus %d seconds", $config->{foo}, stat->mtime);

but Mojo::Log does not support that directly. You could use this:

app->log->debug(sprintf("foo %s  versus %d seconds", $config->{foo}, stat->mtime));

with the downside that sprintf() is called even if the message would not be logged due to your app’s log level being higher than that of the call.

Alternatively you could base your own logger class on Mojo::Log:


package My::Log;
use base Mojo::Log;

sub format {
        my ($self, $level, $format, @parameters) = @_;

        return $self->SUPER::format($level, sprintf($format, @parameters));

package main;

use Mojolicious::Lite;

app->log->error("this string %s printf %s", 'uses', 'stuff');
app->log->warn('decimal: %d hex: %x', 16, 16);
app->log->info('pi: %.2f', 3.14159265359);

And it’s output:

[Wed Feb 27 17:24:34 2013] [error] this string uses printf stuff
[Wed Feb 27 17:24:34 2013] [warn] decimal: 16 hex: 10
[Wed Feb 27 17:24:34 2013] [info] pi: 3.14
by bd in Mojolicious
  Comments Off

Mojolicious behind Apache with mod_proxy
February 27th, 2013 :: Permalink :: Trackback

This is the only way I got an Mojolicious application to work behind an apache2 web server using mod_proxy.

Setting the base will make sure that your routes match the incoming URLs and that the right URL is used in redirects:

my $base = 'http://localhost:3000/app1';

hook 'before_dispatch' => sub {

When using the style sheet or JavaScript helper a leading slash is important, else the path will be wrong:

%= stylesheet '/css/foo.css'

And this is the apache config snippet:

ProxyPass /app1 http://localhost:3000
ProxyPassReverse /app1 http://localhost:3000/app1

Note the missing /app1 at the end of the ProxyPass line.

The complete Mojolicious code:

#!/usr/bin/env perl
use Mojolicious::Lite;

use Time::HiRes qw/gettimeofday/;

my $base = 'http://localhost:3000/app1';

hook 'before_dispatch' => sub {

under sub {
        shift->stash(now => join('.', gettimeofday()));

get '/' => sub {
        my $self = shift;
} => 'index';

get '/foo' => sub {
        my $self = shift;

get '/redirect' => sub {
        my $self = shift;


@@ foo.html.ep
% layout 'default';
% title 'Foo';

@@ index.html.ep
% layout 'default';
% title 'index';

@@ layouts/default.html.ep
<!DOCTYPE html>
    %= stylesheet '/css/foo.css'
    <title><%= title %></title>
    <h1>Welcome to <%= title %></h1>
    <p>Now: <%= stash('now') %></p>
    <%= content %>
     <li><%= link_to 'Index' => 'index' %></li>
     <li><%= link_to 'Foo' => 'foo' %></li>
     <li><%= link_to 'Redirect' => 'redirect' %>: Will redirect to foo</li>


by bd in Mojolicious
  Comments Off

Mojolicious and Linux::Inotify2
February 26th, 2013 :: Permalink :: Trackback

This is a tiny example on how to use Linux::Inotify2 from within a Mojolicious application to watch a file for modification. Note: this will not work with morbo, as no inotify will be delivered to the app. Update: it works with morbo if you use our $io = … instead of my $io = …. The reason for that is, my $io goes out of scope as app->start() does not block.

You will need these modules:

  • Linux::Inotify2 - scalable directory/file change notification
  • EV – perl interface to libev, a high performance full-featured event loop
  • AnyEvent – the DBI of event loop programming
  • And of course Mojolicious

Steps to see the magic happen:

  1. Save the code below to /tmp/
  2. Create file to be watched: touch /tmp/foo
  3. Run your app (again, morbo will not work): /tmp/ daemon
  4. In another shell, update the watched file: touch /tmp/foo

This is what Mojolicious should log:

[Tue Feb 26 21:22:09 2013] [info] Listening at “http://*:3000″.
Server available at
[Tue Feb 26 21:22:13 2013] [debug] file changed
[Tue Feb 26 21:22:13 2013] [debug] file changed
[Tue Feb 26 21:22:13 2013] [debug] file changed



use Mojolicious::Lite;

use Linux::Inotify2;
use EV;
use AnyEvent;

sub file_changed {
        app->log->debug("file changed");

sub setup_notify {
        my $inotify = new Linux::Inotify2;
        $inotify->watch('/tmp/foo', IN_ALL_EVENTS, 

        my $io = AnyEvent->io(
                fh => $inotify->{fd},
                poll => 'r',
                cb => sub { $inotify->poll }

        return $io;

get '/' => sub { shift->render_text('index') };

our $io = setup_notify();

by bd in Mojolicious
  Comments Off

Hover 0.7.2 available
October 8th, 2011 :: Permalink :: Trackback

This release fixes an interoperability issue with the Events Manager plugin. Thanks to Marcus Sykes for helping me narrow down the problem.

by bd in wordpress
  Comments Off

Hover 0.7.1 available
September 15th, 2011 :: Permalink :: Trackback

This release fixes undefined constant/variable warnings, an error during checks triggerd by a missing table, the has_cap deprecation warning and a bug where the activation hook may not be run.

Also Maintenance options have been added.

by bd in Foo
  Comments Off

Hover 0.7.0 available
September 9th, 2011 :: Permalink :: Trackback

This release fixes the hidden screen options problem, updates the included xajax
to the latest stable version and disables websnapr support.

Also the script has been split up in smaller pieces, so that only what is needed
is loaded.

by bd in wordpress
  Comments Off

hostapd, ath9k (AR9287) and Could not set interface mon.wlan0 flags: Unknown error 132
August 20th, 2011 :: Permalink :: Trackback

Turns out this error message meant, wireless radio is hard blocked by BIOS. So after enabling wireless radio in the BIOS, I now have a working access point.

by bd in debian
  Comments Off

Hover 0.6.13 available
September 17th, 2010 :: Permalink :: Trackback

Hover 0.6.13 adds support for predefined image popups and fixes a couple of bugs.

Image Popups

In the past hover could generate popups for all HTML tags (including <img>) from their title attribute. To have the same popup for an image you had to enter the same text every time you inserted that image. While this worked, it was tedious, error prone and hard to change later on.

Hover 0.6.13 now let’s you define a popup for an image once and every time you use that image, it will get the same popup. Popups are assigned to Images by their absolut URL.

Bugs fixed

  • cleanup and fixed plugin activation error detection, table creation and database checks
  • correctly set database schema version on first time install
  • HTML encode aposthrophe in popups, fixing possible javascript error
by bd in wordpress
  Comments Off

Hover and Images in Tag Popups
June 25th, 2010 :: Permalink :: Trackback

It is possible to add images to popups generated for tags, e.g. for links. Just hover over the “wordpress” category listed on the right.

What you need to do is to partially HTML encode your, well, HTML.

In order to display the image as shown in the category, enter this in the category’s description.

&lt;img src=\"images/powered/wordpress\" /&gt;

Be sure to amend the image path to your setup/image.

by bd in wordpress
  Comments Off

Too Cool for Internet Explorer