Tag Archives: wordpress
WordPress Plugin Pet Peeve #2: Direct Calls to Plugin Files
This is actually very similar to my first pet peeve of [hardcoding the path to wp-content][pet-peeve-1], in that it makes assumptions about where files are placed on the filesystem. Oftentimes, plugins need to handle certain kinds of requests, maybe for some specific protocol, or to handle an AJAX request. Some plugins will do [...]
WordPress Plugin Pet Peeve #1: Hardcoding wp-content
Perhaps my biggest pet peeves I run across with WordPress plugins is when developers hardcode the URL or path to the WordPress content folder. By default this folder is named ‘wp-content’, and resides at the root of the primary WordPress folder. However, since WordPress 2.6 (released July 2008), this location [can be moved][] [...]
Authentication in WordPress 2.8
Use Case
I’ve spent a lot of time working with the WordPress authentication system. I took over the OpenID plugin for WordPress two years ago, and was hired by Vidoop last May to work on the DiSo Project full time. Last summer, Matt Mullenweg invited me to talk at WordCamp SF 2008 about OAuth. [...]
Challenges in changing my OpenID
I recently decided to combine two personal websites I had (this one, willnorris.com, and will.norris.name) so that I had a single web presence. I chose to use willnorris.com as my canonical URL, but this presented two problems:
I have been listing will.norris.name as my homepage in my various social networks profiles and on blog comments. [...]
WordPress Plugin Pet Peeve #3: Not being extensible
Possibly related posts: