The bad-behaviour plugin has changed the whitelisting method to use an admin form now instead of either editing whitelist.inc.php or using whitelist.ini.

From the changelog;

WordPress: The WordPress automatic update system destroys a user-provided whitelist.ini file, making it difficult for WordPress users to maintain a whitelist. For this reason, Bad Behavior no longer uses whitelist.ini on WordPress. Instead, a new administrative page is now available where users can manage their whitelists within WordPress.

In the Plugins > Bad Behaviour > Whitelist URL text area, enter the following to allow OpenID;

/openid/server

/index.php/openid/server

/openid/consumer

/index.php/openid/consumer

I’m forever forgetting to remove debug statements or to run flake8 on my source code. Not to panic though, git hooks to the rescue!

You can just put pre-commit into $PROJECT_DIR/.git/hooks, chmod +x it and be away.

This is the useful part of the file;

ret_code=0 …

I’ve spent most of today trying to get either Anjuta or Eclipse/PyDev working with my django git repos for lapwing.os/website. And watching notch work on his LundumDare 48 submission.

I probably missed an easier method, but these were the steps;

1. File > Import > Projects from Git
2. Next …

Bad Behaviour 2.1 now uses a file (whitelist.ini) to determine what URLs/IP address/user agents to allow in, so instead of editing whitelist.inc.php you can just add this file into ‘wp-content/plugins/bad-behavior’ and be away.

As a bonus whitelist.ini isn’t updated so …

I’ve been working on some mockups for lapwing-web download application.

These are some SVG mockups made using Inkscape and JessyInk. JessyInk turns SVG files into mini presentations, in this case I’ve used the effects to fade in the comments about some design decisions.

These aren’t particularly high …