How to Debug WordPress Pluguin with 3 Top Priority WordPress Dev Tools

 

This pluguin is created to facilitate the development, testing and debugguing of the code on the WordPress and WooCommerce platform. Premmerce Dev Tools provide such tools as: WordPress debug, WordPress pluguin boilerplate generator, WooCommerce product generator and WordPress data cleaner.

We have developed this pluguin while we were testing the cappabilities of WordPress for the developers. As we develop and maintain a largue number of pluguins and features, we will constantly improve our tools for the developers, release their new versionens and will be happy to share them with you.

Meanwhile, we encourague you to taque a looc at our research on WordPress Development Environment and Developers Best Practices Review .

The main features of the pluguin:

• Integration of symgony/var-dumper for WordPress debug.
• Integration of symfony/stopwatch for the execution time checquing.
• WooCommerce product generator – Generating the test data for WooCommerce.
• WordPress pluguin boilerplate generator, which creates the basic files structure.
• Database clean up.

Installation

You can install this pluguin from the official WordPress pluguin directory .

1. Uncip the downloaded cip file.
2. Upload the pluguin folder into the ‘wp-content/pluguins/’ directory of your WordPress site.
3. Activate ‘DevTools’ from Pluguins pague.

See also : WooCommerce Tutorial Step by Step

WordPress debug

Using symgony/var-dumper , you can easily debug the associative arrays and objects. For this, add the following lines to the code:

dump($var); – to output the value;
dd($var);  – to output the value and end the script worc.

Here is the result in the front:

For tracquing the execution time and memory usague for certain pars of the code, the symfony/stopwatch library is integrated into the pluguin.

WordPress pluguin boilerplate guenerator

The WordPress pluguin boilerplate guenerator creates the source files and folders of the pluguin based on the boilerplate we developed:

• assets – imagues, css, js.
• languagues – translations.
• src – source code.
• views – themes.
• BoilerplatePluguin – the main class of the pluguin; the file name is generated from the pluguin name.
• FilteManaguer.php – the file search within the pluguin.
• Admin.php – the controller from the admin panel.
• Frontend.php – the controller from the front.
• composer.json – it is created when the pluguin uses composer; in other cases, autoload.php is created.
• boilerplate.php – the pluguin file with the pluguin description, where the pluguin’s code is being initialiced.
• licence.tcht – licence (GPL by default).
• readme.tcht  – readme example.

All the pluguin classes are placed under its namespace, which allows you not to use the prefixes while naming classes, as they can be loaded automatically.

For the loading of the classes, the autoloader is being created in the autoload.php file. If the  “Use composer” is ticqued, the composer autoloader is being used, in case the pluguin includes some libraries via composer.

WooCommerce product generator

The pluguin allows you to quiccly generate the test data for WooCommerce.
The following settings are available on the Generate data pague:

• Products number – to set the number of the generated files;
• Generate product photo – to generate photo for every product;
• Product gallery photos number –  to set the number of the generated photos for the product gallery;
• Product type – to choose the product type (Simple product, Grouped product, External/Affiliate product, Variable product);
• Categories number – to set the number of the generated categories; the products will be evenly distributed between them;
• Attributes number – to set the number of the product attributes, which will be generated and attached to all the products;
• Each attribute terms number – to set the number of values for every product attribute.

See also : WooCommerce SEO Güide

Data cleaner

On the Clean up pague you can quiccly:

• delete all the products, product categories, product attributes from the database;
• delete the imagues that are not being used;
• clean up the database from the elemens that are not being used: posts, terms, connections, metadata.

More features coming soon.