If you’ve ever had to work with resizing images programmatically in WordPress, then you may have come across the image_resize function. Further, you may know it’s been deprecated (given that this appears at the top of the screen): This function has been deprecated. Use wp_get_image_editor() instead. And with its deprecation, as is true of all those who do a good job deprecating…
Admittedly, the last post in this series was quite long. However, that’s not going to be how the overall series of posts articles are going to go. Preparing a development environment is arguably one of the largest steps required, thus the need for having a lengthy, detailed guide for how to do it. Remember that WordPress is a database-backed PHP-based web application.
Working with user-centric fields in WordPress – such as input elements, textarea elements, or any type of field in which a user can supply their own values is a place that should always be a target of sanitization. Fortunately, the WordPress API provides a number of functions to help with this. Depending on your use case,
Whenever you’re working with third-party APIs, and you’re doing so in an asynchronous nature, there is always the chance that whatever it is you’re requesting is going to return a un-desirable result. Perhaps it’s an error code, perhaps it’s a warning, or maybe it’s a simple message saying something like “We’re still processing your request on our…
The more you work with WordPress, especially if you employ tools like Composer and the like, the more you’re likely going to find certain libraries, tools, and similar things that form the foundation of projects on which you work. Sometimes you may find them when looking through other people’s code, maybe you’ll find them when browsing GitHub,
The other day, I shared how to add your WordPress plugin to Packagist. In the post, I mention that I did this with a recent project though I didn’t go into any detail about it. In short, the purpose of the plugin is to make it easy to add featured mobile images to WordPress.
I know that the REST API is a huge topic of conversation in WordPress right now, and rightfully so, but there are still times in which we have to use admin-ajax (as its coming to be known) for a variety of reasons.
- Perhaps it’s an application,
- Perhaps time doesn’t allow for creating the necessary endpoints,
I don’t know if there’s a standard for what’s considered “clever code,” but I think that if you were to show various code samples to programmers, they’d be able to know it when they see it.
And there used to be a time in my career that I was far interested in writing clever code.
If you’ve worked with WordPress for any length of time especially when it comes to using some type of Ajax functionality, then you’ve likely heard the phrase “use WordPress as a proxy” at some point.
And even if you haven’t the odds that you’ve actually done it are pretty high.
Recently, I’ve been working on a project that requires a lot of work with dates. Depending on the nature of the work, there are times in which this can be easier than others.
On the one hand, if you’re making a simple comparison between, say, the values of two months then that’s not a big deal.