Hello. In this article, we will learn how to read data from the WordPress Media Manager via API. The distinguishing feature of today’s post is that we’ll use native PHP CURL functions instead of the WP wrapper “wp_remote_get(...)”.

Order website or plugin development for WordPress, website development on the Laravel, Symfony, or Yii2 framework…

Hello. In this article, we will learn how to read data from the WordPress Media Manager via API. The distinguishing feature of today’s post is that we’ll use native PHP CURL functions instead of the WP wrapper “wp_remote_get(...)”.

Hello. In today’s article, we’ll cover the topic of comments. Specifically, how to add a custom column to the comment list table and display custom (non-standard) values in it.

Hello. In today’s article, we’ll look at uploading images to the WordPress media manager using the API and its core functions.
Today we’ll add some complexity by using a cron job. Our code will need to execute every 10 seconds.
Let’s get started. First, we’ll create a custom time interval for the cron job using the WordPress “cron_schedules” filter:

When developing your own plugin or addon, due to some technical requirements, WordPress template files sometimes need to be placed inside the plugin directory (i.e., not in the theme folder). What is needed for this?
As an example, take the WooCommerce or bbPress plugin. By default, plugin templates are stored inside the plugin folder. For Woo, it’s “/wp-content/plugins/woocommerce/templates”, and for bbPress — “/wp-content/plugins/bbpress/templates/default/bbpress”. This article describes how to partially implement similar functionality, but in a simplified form (we’ll cover full implementation in upcoming posts).

Today we’ll take a look at another useful feature — how to work with post or term meta data via the API. Just like with creating data via the API, WordPress by default doesn’t support meta field interaction. To enable it, we’ll need to install a third-party plugin. Unfortunately, I couldn’t find it on GitHub — maybe it was moved or merged into the WordPress plugin repository. However, since I still have the plugin archive locally, we’ll use it for this article (you can download the plugin via the provided link). I’m sure you can also find a similar plugin in the WP repository with good reviews.