Category Archives: technology
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][] [...]
Deciphering Twitter @replies
So I’ve been as confused as anyone as to what the current Twitter reply system is actually doing, so I decided to try a quick experiment. Just like email replies (which I recently ranted about), there are two ways to designate a reply in Twitter. Akin to the subject of an email, you [...]
Posted in technology 3 Comments
HTTP Client Library for PHP
As I mentioned in my last post, I’m currently spending a lot of time thinking about and coding PHP libraries for the various Open Stack protocols. I’ve recently hit a common roadblock with a couple of the libraries, and wanted to solicit some feedback from the community. Ironically enough, I’m stuck with regards [...]
WordPress Plugin Pet Peeve #3: Not being extensible
Possibly related posts: