The patch I posted about previously to improve the slash handling within WordPress for 3.5 (which fixes some core bugs and fixes tons of developer custom code bugs) is still looking promising. After setting up my unit testing environment a few days back and talking with a colleague to verify the proper approach, I began…
WordPress Archives
-
-
We’re still in the process of filling the three positions I posted about previously (technical project manager, front-end web developer and full-stack web developer), but we’ve just added another position that I’m really excited about. We are looking for someone to join our team specifically as a UI/UX lead for web applications. We do a…
-
For the last month or so I’ve been working on a patch to move the “stripslashes” functionality from the WordPress “model” API functions to the “controller” code (where it belongs). This change will mean that you don’t have to call add_magic_quotes() around your data when passing it to wp_insert_post(), wp_insert_user(), etc. As hardly any developers…
-
This past weekend I enjoyed my first trip to New Mexico to attend WordCamp Albuquerque. I’m not sure why it took me eight years after moving to Colorado to visit my neighboring state to the south, but WordCamp was a great excuse to get down for a visit. My thanks to the great folks in…
-
Carrington Core hasn’t changed much over the last few years. It’s stable, does what it’s supposed to do, and is extensible via standard WordPress APIs. Last night I merged in code to implement a new/overlooked feature for the first time in quite a while: support for sticky posts. This is part of the posts context,…
-
I feel like I’d be remiss if I didn’t add this to the conversation. I’ve seen some people indicating that calling plugin functions in themes is a bad idea (here’s an example comment to that effect). I think this is going too far – including a call to a plugin in a theme is fine…
-
Yesterday I released a version of Popularity Contest that removed all functionality and simply delivered a message that the plugin was discontinued and not recommended. It was the first time I’ve done this with a plugin, and it turns out I hadn’t thought through some of the ramifications of the changes I made. Here is…
-
As previously noted Popularity Contest had a good run but is no longer recommended. As such, I’ve gone ahead and disabled the default version in the plugin repository on WordPress.org, with an explanatory note. This post is part of the thread: Content Presentation – an ongoing story on this site. View the thread timeline for…
-
I recently posted about how to include a plugin in a WordPress theme properly. Here I will touch on the converse – how to make sure your plugin will work nicely if it is loaded by a theme. My general approach to development is to create discreet features that can interact with each other in…
-
When I was posting about our recent releases, I overlooked version 1.1 of RAMP. This is the first major feature release of RAMP, and we added a bunch of great features. Perhaps the most useful user feature is the “quick send” feature. Now when you publish or update a post, there is a “RAMP It”…
-
In our FavePersonal theme we integrated the excellent Social plugin from MailChimp and included an option to turn it on or off. Most importantly we did it in a way that still allows the Social plugin to be installed and updated independently. We made sure that we implemented this in a manner that: respected users’…
-
I really like the fullscreen editor in WordPress. I use it nearly all of the time when composing long-form content, often in conjunction with the excellent Markdown on Save plugin by Mark Jaquith. It has always bugged me that there wasn’t a Preview button in the fullscreen mode toolbar. Problem solved. Here’s the code. This…
-
We’ve released version 1.1 of our FavePersonal theme for WordPress (the theme you see on this site). This release includes the new 2.5 version of the Social plugin as well as updates to Carrington Core and other libraries and code changes to use new best practices added in WordPress 3.4. As a result, this release…
-
We recently updated Carrington Build for compatibility with WordPress 3.4. We also updated our pricing structure for Carrington Build, dropping the single site price from $499 to $299 and adding an unlimited site package1 at $999. Our Carrington Build packages include access to our developer support forums and developer documentation, along with example theme integrations…
-
We’ve gone ahead and merged in the global variables changes into version 3.4 of Carrington Core. We also stripped out the lightbox and color picker code so that Carrington Core is just a lightweight template selection engine. If you have a Carrington-based theme that relies on the lightbox or color picker, grab the code from…
