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][] by simply […]
-
Recent Posts
Categories
Recent Comments
- Anton on A class needed by class <…> cannot be found: org/apache/tools/ant/Task
- raaaj on A class needed by class <…> cannot be found: org/apache/tools/ant/Task
- Kijana Woodard on WordPress OpenID v3.3
- Ajaxian » Safari self replicates itself…. for fun on iTunes 9, now with more WebKit
- OpenID: Redirects and Delegation » Code Nomad on Challenges in changing my OpenID
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 this by […]