Yesterday, I shared a post on how to use wp_remote_get but I left out an alternative function: wp_safe_remote_get. The original goal was to use the first post to show:

1. What the original function accepts,
2. How to use the original function,
3. What the original function returns,
4. What an implementation make look like.

And then I was going to take a look at wp_safe_remote_get. But there’s a challenge: I have smart friends. Shortly after I published the post, I get a response from Roy:

wp_safe_remote_get***

— Mildly Spicy Salsa (@royboy789) January 10, 2017

Thanks, Roy! (Be sure to say “Hi!” to him. :)

But seriously, the follow-up to yesterday’s post is exactly that: wp_safe_remote_get. And it’s how to determine the difference in the two functions and when you’d use one over the other.

Continue reading

If you’re read any of my previous posts on retrieving remote files, then you know that old habits die hard as I often use file_get_contents rather than wp_remote_get.

So, as one does when blogging, I thought it would be helpful to share a simple example of how to use wp_remote_get in your day-to-day work.

The post below is merely a snippet of how to use it. That is, it won’t show how to designed, say, a class around it or a UI that allows users to upload a file. But this should be enough to get things started.

And I’ll include how to take the API documentation around it and understand how to leverage it when using a function like this.

Continue reading

A couple of days ago, I shared that I was looking to put some of my plugins up for adoption. I’ll go into a bit more details as to why later in this post, but I’m happy to say the WordPress plugins are adopted.

It’s funny to talk about little side projects as if they are your pets – then again, we do have the phrase “pet projects” so I suppose it makes sense in this context. ‍♂️

At any rate, as I said, they’ve all been adopted, and I couldn’t be more excited as to where they are going. Though it would have been fine for each one to go to a different developer, they’re all going to fall under Philip Arthur Moore’s ownership.

Continue reading