Author: Tom (Page 350 of 427)

The Ethics of WordPress Developer Responsibilities

February 8, 2013 / Tom / 0 Comments

Earlier this week, I shared a post on You Can’t Ask Users To Upgrade WordPress To Fix Their Problems. In the post, I shared a few reasons as to why it’s dangerous to expect and/or trust your customers to upgrade WordPress.

You can read the full article for my reasons why, but Mike brought up an interesting statement in the comment feed that got me thinking about the ethics of our responsibilities a developers for building projects for clients.

Though ethics are subjective and that you’ll rarely hear me talk about them on this particular blog, I think that there is room for discussion as to what constitutes the ethics of programmers in the case of building, releasing, and maintaing software for others, and, in this case, within the WordPress space.

WordPress For Application Development

February 7, 2013 / Tom

Several times now, I discussed the potential and feasability of building web using WordPress for Application Development.

For those of you who haven’t read, I’ve written:

And today, I’m continuing the discussion with a post on WP Daily.

How To Use Sequel Pro with MAMP For Local Development

February 7, 2013 / Tom / 0 Comments

For those of you who have read my previous blog posts, you know that my local development environment consistents of using MAMP for Apache, PHP, and MySQL.

Though I’m not particularly hardcore about any given IDE, I’ve been using Coda 2 since it was released and have enjoyed it especially because of its integrated database environment.

But with the need to work with several other remote databases outside the context of an IDE, and the recent release of Sequel Pro 1.0, I thought it may be useful to share how I’ve also been using Sequel Pro with MAMP.

You Can’t Ask Users To Upgrade WordPress To Fix Their Problems

February 6, 2013 / Tom / 0 Comments

I think one of the major characteristics of anyone who’s a digital native – that is, anyone who spends a vast amount of time on the Internet and that has a certain level of proficiency – has no problem upgrading their apps to the latest version and tinkering around with the new features and/or looking for new bugs.

I mean, we can always roll back, right?

And when it comes to WordPress – especially for those who build things for the platform – it’s not at all uncommon to see us urging our users and others to upgrade, as well.

I love updates as the next geek, but we can’t blame others for wanting to wait to upgrade WordPress immediately, nor can we expect everyone to upgrade WordPress as quickly as we do.

Save Custom Post Meta – Revisited, Refactored, Refined.

February 5, 2013 / Tom / 0 Comments

About a month ago, I shared a post that discussed the code that’s required to save custom post meta data. Generally speaking, this is a lot of boilerplate that’s required to make sure that the data being saved is permitted and that the author has permissions to do so.

Of course, depending on the nature of your project, the code will vary a little, but for the majority of the cases, it’s all the same.

But thanks to several commenters and contributors, the code has been completely refactored, and I’ve actually been using it in a recent project.