Show "reviews" of plugins of the official repository

For every plugin developer it is extremely important to be able to show the opinions of the users in the presentation site of their works, so that a possible client has an idea of ​​what they thought of the plugins, without having to go to the official repository.

To achieve this, there is the plugin Plugin Reviews (yes, I know it sounds redundant, but it's the name of it). It allows to insert the opinions of the plugin in any part of your active theme by means of shortcodes, easier impossible.

We can insert the reviews in the form of galleries or grid, very easily. The plugin's operation is very simple.

And it has a lot of shortcodes that we can take advantage of, in order to get the most out of its functionalities. Simple to use, I tried it at home and it worked perfect, I did not find any mistakes. What I did not find is something like that but for themes, since it would also come in handy for many developers and designed for 0 + 606s.

Do you want to help WordPress development?


WordPress is a CMS made by the community and for the community and without the support of themselves at this time it would not be the best CMS that there would be at present, we can all be part of this community that contributes to the development of this CMS that has helped us many times in daily life.

There are many forms of collaborate with the WordPress project the source code, testing errors in different environments, creating patches, functions, testing new versions, etc.

In this article we will recommend some ways you can collaborate with WordPress remains one of the best tools at the web level.

Trac is an open source software which uses WordPress to manage all types of errors, by generating tickets you can report any error What you have found, security problems, a bad update, you can also manage suggestions for the next versions of the CMS. In this way the community that is behind all WordPress will be able to analyze each of our opinions and give them a solution as soon as possible.

Work with the WordPress kernel

Since WordPress is created by the community, anyone can collaborate with the WordPress. base of the code, with this I do not mean that anyone can directly modify the base of all the source code, in order to make these changes it is necessary to create a patch file with the respective changes and send it for review. If these changes are accepted you will probably be in the next version of WordPress.

To collaborate with code changes and others it is necessary to use Subversion .

Publication of Plugins and Themes

To make the publication of some of these two the most indicated is to send them to the directory of plugins and themes that WordPress incorporates on your page, below are the links where they can be sent, in them are the indications of how to do it, just enough to have a account created on



Create the next documentation

Creating documentation is a little tedious and even boring but it is something we all need at some point in order to solve problem s, a good way to collaborate with the community is to update and create the documentation for the next version of WordPress, although it is true that in our Codex we still find outdated documentation of versions much earlier than the actual version and makes it necessary for someone to do this task especially for new users who are part of WordPress.

Another way to help and not only the community that develops WordPress but also the people who start in this world is collaborating and giving answers to the different topics that are created daily in the attendance forum, here I share the Spanish forum but in each language there is a different one.

If what you want is a little more agility when looking for solutions, WordPress also has very active chat rooms, to participate you only need to have an IRC client on your PC.

The main WordPress room is #wordpress [1 9459010]there is also the room dedicated to the development # wordpress-dev and as you can see the rest.

In the ideas section of WordPress, proposals for the next versions are compiled, here you can vote for the ones that most call your attention and think suitable for a next version, all these ideas are reviewed before beginning with the development of a new version to evaluate its implementation in WordPress.

These are the main ways to help the WordPress evolution, if you know others that also help, you can comment on them in our comments section.

NOTICE : this publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

10 basic skills of the WordPress plugin developer

 developer wordpress

The plugins are great part of the greatness and beauty of WordPress and create your own plugin will give you a knowledge and freedom that you will not find if you simply use what others create.

Now, if you throw yourself into the WordPress plugin development it does not hurt to keep this in mind ] 10 basic tips for creating plugins :

:: 1. Creating the plugin ::

The first step is to create the folder of your plugin in the directory / wp-content / plugins . Once you have created the folder you must place the files of your plugin in that folder. There must be a main plugin file, and the file names must have only letters and hyphens (-) if you want to separate words, do not use other punctuation marks or spaces.

A type name would be something like this: plugin-seo-sencillo.php

The main file of the plugin must have the following structure for WordPress to identify it as a plugin:

Once you save the changes , even if you do not have the plugin yet, you will see it on the WordPress plugins page.

:: 2. Activation and deactivation of the plugin ::

Plugins can be activated by clicking on the link " ] Activate "from the list of plugins. In a basic plugin you do not have to do anything when activating it. But an advanced plugin will require tasks such as launch the plugin settings, create tables, etc., so let's see how we can manage the activation and deactivation of a plugin.

Plugin activation hook

WordPress offers a function called register_activation_hook that is launched when a plugin is activated. We can add custom functions that are executed when activating the plugin using this method. An example would be the following:

You have to define the path of the file that contains the activation function as the first parameter and the name of the function as the second parameter.

If the activation function is inside the main plugin file you can use _FILE_ as in the previous example. Within the activation function you can also perform tasks such as validations, initializations and creation of tables

Plugin deactivation hook

We can manage the deactivation of a plugin with register_deactivation_hook using a similar syntax to that of activation. In the deactivation function you can also perform additional actions such as cleaning plugin resources, settings and tables.

:: 3. Creation of custom tables ::

The structure of the WordPress database and it is very flexible, and you can implement most of the custom features using the tables that are available.

However, sometimes you may prefer to include more advanced systems, such as shopping carts, task management systems , subscriptions, etc.

In these cases you should know how and when create custom tables . The first thing is to take into account the requirements of your project and try to use the table and meta tables wp_options to store the data specific to your project. If you consider that these tables do not have the necessary structure to implement the functionality you need then create custom tables using the following method:

First we check if the table exists before creating it. You can decide to create the table at the time of activation, depending on what you need. In the example you will see that {$ wpdb-> prefix} is used before creating the name of the table. This is because, normally, WordPress tables start with the prefix wp_ . This can be changed when you install WordPress, so it's better not to manually add the prefix wp_ since it could be another, and so we make sure it will adapt to what exists.

Using {$ wpdb -> prefix} you will get the prefix defined in the WordPress installation, so always use this syntax to create the tables.

Even if you use the function $ wpdb-> query to create the tables it is advisable to use the function dbDelta since it compares the current table structure. It is not loaded by default so you must include it at the beginning of the file.

:: 4. Including Scripts and styles ::

Even if you only echo scripts and styles it is recommended to add the scripts using the function wp_enqueue_script . This function checks whether files and dependencies are available with other scripts. The following example shows how to use the function wp_enque_script :

First you use wp_register_style to register the style file and wp_enqueue_style to include the file. You must also indicate the path and unique identifier of the style file. Then the scripts are included using the function wp_enqueue_script . If it depends on other scripts you can mention them in the third parameter. In the example, a dependency of jQuery has been added.

Finally, you can add data that will be used within specific scripts using the function wp_localize_script . You can include the scripts where you want but always use the functions wp_enqueue_scripts and wp_enqueue_styles .

Also make sure to use the action admin_enqueue_script instead of wp_enqueue_script for the admin part.

:: 5. Creating shortcodes ::

The shortcodes are predefined code blocks that you can use anywhere. It is essential to learn how to use shortcodes if you want to be a plugin developer since they add dynamic elements to custom pages.

You can create shortcodes using a syntax like the following: