Author: Tom (Page 359 of 430)

One of the things that’s nice about the WordPress development community is that there’s no shortage of places to discuss what’s going on in the community.

Aside from chatting with people on Twitter, we can hop into IRC chats, listen in to other developer’s podcasts, and naturally read and respond to what other’s are writing on their blogs.

But late last week, I noticed the following tweet show up in my stream:

Are you a redditor? Love WordPress but think /r/wordpress is lacking? Come join us on the "Pro" WordPress subreddit http://t.co/LwHjYlnP

— Macho Pirate Mick Rackam (@tw2113) January 5, 2013

It’s been a long time since I’ve paid any attention to anything like Reddit – probably since college, but this particular subreddit caught my attention.

Continue reading

Comments are closed on this post. See the updated version for more information.

Last week, I was talking to a couple of developers on Twitter about some of the code that’s required to save custom post meta in WordPress when working with plugins or themes.

For the most part, good serialization functions are consistently formatted in the same way:

• First, we check for security. If the security check fails, then we exit the function.
• If security passes, then we proceed with our serialization functionality.

The thing is, the security checks are generally the same thing across the board so much so that you may even consider it somewhat of a boilerplate.

This seems like an opportunity to improve developer’s processes a bit by abstracting out some of the code that is used to save custom post meta data.

So let’s try this:

Continue reading