The new editor called Gutenberg is here as plugin in 4.9, and as core functionality called Block Editor, in 5.0. Regarding to it, it is often needed to determine programmatically which editor is used to edit post or page in the site console.

There are several variants:

  • WordPress 4.9, Gutenberg plugin is not active
  • WordPress 4.9, Gutenberg plugin is active
  • WordPress 5.0, Block Editor by default
  • WordPress 5.0, Classic Editor plugin is active
  • WordPress 5.0, Classic Editor plugin is active, but in site console in “Settings > Writing” the option “Use the Block editor by default…” is selected

All the mentioned variants can be processed by the following code:

New version 2.0.0 of the plugin WOOF by Category is published. Now plugin is compatible with WPML.

WOOF by Category is a WooCommerce Product Filter (WOOF) extension, which allows user to set up different WOOF filters in different categories. Plugin has options page on the backend, to setup relationships between any WooCommerce product category and any set of WOOF filters. Only selected filters will be shown on the selected category page and its children.

In the new version of the plugin, settings are saved separately for each WPML language. This allows to have different sets of pairs “category->filters” in different languages, and work with categories, translated by WooCommerce Multilingual (this plugin is a part of WPML).

xDebug is great development tool, but is slows down a web site significantly. During development cycle, it is desirable to turn on xDebug only when it is really needed. Let us show how to turn xDebug on, off, and set profiling modes in Laragon development environment. Also, we will show how to add buttons for these actions to phpStorm toolbar.

This is what final result will be (4 rightmost buttons).

First, let us create a command file to switch xDebug. We assume that we work on Windows 10 with Linux Bash Shell installed. In some folder, which is in Windows PATH, let us create two files: xdebug.bat and