Submitting plugin to wordpress.org repository is a cautious as well as watchful process. Before submitting, one must have readme.txt and license (GPL 2 or later) in the plugin folder.
The plugin folder structure depends upon the coding style of the developer so it can be of different type. But, an important thing to note is that there must be the two files: readme.txt and license.txt. A standard readme.txt file can be seen in:
As we all know, flexibility and customization is possible in WordPress because of action and filter. We can add as many actions and filters and remove them as well.
Lets take a look how we can remove an action from theme that is added via plugin.
Lets say, we have a class Wte_Paypal_Gateway:
class Wte_Paypal_Gateway
This class has a global object instance called $plugin_public.
global $plugin_public;
An action wte_paypal_submit_btn is hooked in a tag called
Settings API
It is the back-bone of plugin development. It was first added in WordPress 2.7 and allows semi-automatic management of admin pages containing settings forms to be managed. It lets you define settings pages, where sections can be defined within those pages and fields within those sections.
Let’s take an example:
A function ‘wp_travel_engine_settings_page‘ is created where a sub-menu page ‘WP Travel Engine Admin Settings‘ is defined. This submenu page is added to a
Step 1: Exporting Local WordPress Database
For this, just go to http://localhost/phpmyadmin/ and (choose) click on your WordPress database. Next, click on the Export button at the top. While exporting choose custom, which will provide you with more options to export your database. Select all tables to export and gzipped for compression. Now, scroll down to press the Go button to download your database in the compressed zipped format.
Step 2: Uploading WordPress Files
Now
Strategies:
Strategies are the steps which we follow during the plugin development process. Below are some of the steps to be undertaken so that the process becomes more effective as well as faster.
Planning
Planning is the blue-print of a process. Before we directly go to the development of a plugin, we plan the road-map as well as the strategies we will be following. It includes all the processes from naming of the plugin to
