Welcome back to our series on creating custom blocks with the WordPress Gutenberg Block API. This tutorial is all about extending the random image block we created in the previous post. We got as far as adding a drop-down control to select an image category. We’ll continue with this by adding more block options to allow further customization.
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,
WordPress templates make it easier for developers to create dynamic content and apply a consistent style across multiple posts or pages. While this is a very useful feature, it’s been skipped over by many users due to the required degree of coding.
However, this is no longer the case. The new Elementor Theme Builder includes the ability to create custom single post templates without doing any coding whatsoever.
Do you want to set up WordPress error logs in wp-config file? The wp-config file in WordPress not only controls your WordPress site settings, it is also a very a useful debugging tool to help you find and fix errors.
The wp-config.php file is a WordPress configuration file that contains important WordPress settings.
Getting emails through your WordPress site is important. Whether someone is informing you there’s something wrong with your products, or just dropping by to say you’re doing a great job, you need to make sure you receive those emails.
Too often, our tests for if emails work on a WordPress site or in a WordPress plugin involve filling out a form,
If your client serves a non-English speaking audience, you may need to produce a website that works in multiple languages. Given that implementing multiple languages means a potential wealth of new custom, don’t let the fear of tackling a multilingual website stop you from working with these types of clients.
While handling multiple languages increases your project scope,
Are you seeing the 429 too many requests error on your WordPress site? This error can be extremely frustrating because it is hard to figure out what’s causing it.
The most common reason for the 429 too many requests error is when a user, bot, or a script tries to make too many requests to the servers.
Since the WordPress REST API was first proposed, we’ve talked a lot about how it will be involved in the future of wp-admin. Gutenberg, the new WordPress UI system that will be used for the new post editor in WordPress 5.0 is the first example we have of the REST API being used to communicate data between the server and a JavaScript-driven interface.
