Blog

In the previous tutorial we already discussed how to check if a specific coupon is applied to cart or to an order. But in this tutorial I will show you a different thing – how to find out programmatically if coupon with a specific code is actually created in WooCommerce admin.

In this tutorial I am going to cover different ways how you can check if a specific (or any) coupon has previously been added to WooCommerce cart or to a specific order.

The inspiration for this tutorial was another tutorial I found where it was recommended to create WooCommerce coupons using wp_insert_post() function and update_post_meta(). When working with WooCommerce data since 3.0 version it is always recommended to use CRUD objects. And coupons are not an exception.

In order to create a coupon programmatically in code we have to use WC_Coupon object. Once the object is created we are able to use its methods for coupon configuration.

Let’s do it and begin with something simple.

In this tutorial I am going to guide you through the process of creating products in WooCommerce in code.

It is the most correct way of creating products in latest WooCommerce versions. So, please forget about wp_insert_post() and update_post_meta() functions. Yes, I perfectly remember that products are WordPress custom post types and product prices are post meta but it doesn’t allow us to use those functions anyway, because there is a little more than that and it could cause bugs.

In this tutorial we are going to use CRUD objects that were introduced in WooCommerce 3.0 (CRUD is an abbreviation of Create, Read, Update, Delete). The CRUD objects we are interested in right now are:

• WC_Product_Simple – for simple products,
• WC_Product_External – for external products,
• WC_Product_Grouped – for grouped products,
• WC_Product_Variable – variable ones.

We are also going to use plenty of methods of these objects, that allow us to configure our product data.

Almost 7 years ago I created a tutorial about Stripe integration on a website. When I created it, it seemed quite difficult to me, but now it looks easy-breezy.

The thing is that it is obsolete right now. Well, it actually works for some cards, but mainly for those cards that are operating in North America. Today our goal is to implement it with brand new Stripe API which is called Payment Intents.

And I am going to guide your through it step by step.

I was eager to tell you about Full Site Editing, but I didn’t know where to start. It was just overwhelming. But not so far time ago I find out that the very first WordPress theme – “Kubrick” was rebuild for FSE, so, it is a block theme now.

My tutorial about configuring self-hosted plugin updates became quite popular so I decided to publish a similar tutorial related to WordPress themes.

The whole tutorial consists of two steps – in the first step we are going to configure our custom update server, in the second step – create a theme actually.