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 xdebug.sh.


Our company got a new status: “Certified WPML contractor”. This is an international mark of quality of our web sites, developed on WordPress with the WPML internationalization plugin.

According to W3C survey, WordPress is used on 30% of all web sites in Internet. Many of them have content in several languages. Most widely used is WPML internationalization plugin, developed and supported by OnTheGoSystems.

In January, 2018 the OnTheGoSystems created the contractors club. This club joined approved by OnTheGoSystems freelancers and companies, who actively use WPML. Now there are 189 approved contractors in the club.

Finally, in March, clubs members received invitations to pass certification. At this moment, in the beginning of April, 2018, only 5 contractors, including KAGG Design, passed the certification process.


Code analysers as PHP Code Sniffer, and coding standards as WordPress Coding Standards, allow to create a modern, easily maintainable code, and avoid multiple errors even during writing of the code. They are indispensable for team development of a project. These tools are embedded into PhpStorm – modern powerful Integrated Development Environment (IDE).

At the same, many novice developers have troubles installing PHP Code Sniffer analyser and WordPress Coding Standards in PhpStorm on Windows. Information is dispersed by many articles in the Internet.

Below, we will join information on it in one place and show installation sequence step by step.


Is it possible to “squeeze out” a high performance from a WordPress site? Our answer is yes! In this article, we show how to set up a WordPress site configured to sustain high loads up to 10,000 clients per second, which equates to 800 million visits a day.

First, we need our own virtual private server (VPS). For testing we used a VPS leased from DigitalOcean (monthly rate USD 20) with the following parameters: 2GB of memory, 2 processors, 40GB on SSD. CentOS Linux release 7.3 has been chosen as the operating system.

The text below is almost a step-by-step instruction for experienced administrators. We will provide here only those parameters, which differs from default ones, and increase server performance. So, go ahead!


Website loading time is extremely important to attract and keep visitors. According to performed researches and opinion polls:

  • 47% of visitors expect that webpage will be loaded in 2 seconds;
  • 40% can leave website which is loaded for more than 3 seconds;
  • 75% of visitors went to competitors’ websites without waiting for the page to load;
  • 88% declared that unlikely will return to the website after unsuccessful attempt to open it.

What is more, the requirement to website speed grows constantly:

  • in 1999, one third of visitors left, if site was loading for more than 8 seconds;
  • in 2006, same one third left, if site was loading for more than 4 seconds;
  • last researches show that acceptable loading time is reduced to 2 seconds.

For an Internet shop, page loading time is even more significant factor. Amazon performed a number of tests, which showed: every 100 ms of increase in loading time of Amazon.com decrease sales by 1%. Google discovered that replacement of a page with 10 search results, loaded in 0.4 seconds, by a page with 30 search results, loaded in 0.9 seconds, decreased traffic and revenues from advertisement by 20%.

We put the highest attention to the speed of our sites, setting the task to provide loading time of any page of created website less than 1 second, and a page with the map – less than 2 seconds. To achieve this goal, we use only virtual private (VPS) and dedicated servers, last versions of nginx, mySQL and php 7 (which is twice faster than predecessor), caching systems, site structure optimization, minimal number of proven plugins.

Check out the results of page speed measurements for several websites created by us and compare with results of your site, which you can measure by the well-known service Pingdom. Do you have a slow site? Please contact us, we will make it “fly”!