This plugin may already be obsolete by the time you read this, but I found a couple of functions that weren’t provided by the default WordPress-MU API that you may find useful in your own WordPress-MU development.
Tag Archive for 'development'
The underlying architecture of the WordPress content storage and retrieval systems provide a flexible and powerful way of creating all manner of sites.
This talk is an overview of that capability and stern reminder that its not about the WordPress plugins you install, but the Information Architecture you implement that will make your site a success or not.
How Not To Build a Plugin by Will Norris
Spotted on WordPress TV. Lots of examples of how to make your plugin less flexible, less secure, and more prone to misbehaving.
Video After The Jump
I started moving my open source code over to GitHub, since it supports working with contributors in a natural, but controlled manner. However, for many of my WordPress plugins I already have a local working copy, since they are hosted in the WordPress plugin repository to support auto-update. I didn’t want to disrupt my svn working copy, nor did I want to start fresh in github.
Continue reading ‘One working copy to rule them all (Git + SVN)’
Installing ImageMagick with MacPorts couldn’t be easier:
sudo port install ImageMagick
But getting it to work with your PHP installation is a bit harder. If you’ve installed PHP via MacPorts with the pear variant you can install the imagick extension via pecl:
sudo pecl install imagick
The trick to getting it to stop complaining about the Wand-config path, is by passing it the proper prefix for ImageMagick. When prompted, hit 1, then enter in:
/opt/local
Now just add this to the end of your php.ini file, and reboot apache:
[imagemagick]
extension=imagick.so
comments