theantichris

icc97

This plugin is aimed at developers that need to migrate their databases from 
production to test or local domains.
This is the simplest way I’ve found to migrate databases quickly.
You only have to set the <code>WP_HOME</code> 
(<a href="https://codex.wordpress.org/Editing_wp-config.php#WordPress_address_.28URL.29" rel="nofollow ugc">WordPress address URL</a>) 
and <code>WP_SITEURL</code> 
(<a href="https://codex.wordpress.org/Editing_wp-config.php#Blog_address_.28URL.29" rel="nofollow ugc">Blog address URL</a>) 
constants once for each environment and then the database is automatically 
upgraded when you import a database and login to the admin area.
This stands on the shoulders of the constants and fills the hole for when 
plugins don’t follow the rules and use the database directly.
This plugin is designed to be the most lightweight way to migrate your database 
and stay out the way of your own processes.
It works with WordPress to use WordPress’ own constants to update the database 
using the 
<a href="https://codex.wordpress.org/Class_Reference/wpdb" rel="nofollow ugc">WordPress Database Object</a>. 
It avoids search and replaces in text files. It uses database queries to update 
the database as should be done.
Most developers have their own methods for exporting/importing the database – 
if you can use <code>mysqldump</code> then you probably don’t want a WordPress plugin to 
do it for you.
It makes no assumptions about your database and it’s cross platform.
P.S. Pitta is taken from the start of an <a href="http://wordpress.stackexchange.com/a/182/5433" rel="nofollow ugc">answer from WordPress SE</a>:
<blockquote>
Deployment of a WordPress site from one box to another has been a PITA since 
 day one I started working with WordPress. (Truth-be-told it was a PITA with 
 Drupal for 2 years before I started with WordPress so the problem is 
 certainly not exclusively with WordPress.)
</blockquote>
So this plugin aims to make things less PITA and more yummy Pitta (pedants will 
mention that Pitta can also be spelled pita).
Its inspiration actually comes from the <a href="http://wordpress.stackexchange.com/q/119/5433" rel="nofollow ugc">second answer</a> 
from the same <a href="http://wordpress.stackexchange.com/q/119/5433" rel="nofollow ugc">WordPress SE question</a>.
Coincidentally there is a migratory bird called a <a href="https://en.wikipedia.org/wiki/Pitta" rel="nofollow ugc">Pitta</a>:
<blockquote>
The fairy pitta migrates from Korea, Japan, Taiwan and coastal China to Borneo.
</blockquote>
P.P.S. This plugin is based off the excellent <a href="https://github.com/theantichris/WordPress-Plugin-Boilerplate" rel="nofollow ugc">WordPress Plugin Boilerplate</a> from antichris on Github

Pitta Migration

Migrate WordPress databases using WP_HOME and WP_SITEURL constants.

Dion

UsageDD allows administrators to monitor the resource usage of their WordPress installation. It will add a small box at the bottom center of each page, only visible to administrators, that displays the number of MySQL queries, the amount of memory used by the page’s code, and if you are using a compatible webserver (most are compatible), the “time to first byte” (TTFB) and the time required to generate the full page. TTFB is used by Google for page-ranking purposes, and it will be the first of the two displayed.
You can use the display to determine if your site has too many plugins loaded, if your theme is too “heavy”, or if something is wrong on your server. The plugin itself uses virtually no resources and should be compatible with every theme and plugin that outputs HTML.
Support is available in our <a href="https://forum.dion-designs.com/f35/usagedd-support/" rel="nofollow ugc">dedicated support area</a>. Support questions posted on wordpress.org may go unanswered for an extended period of time.

UsageDD

UsageDD allows administrators to monitor the resource usage of their WordPress installation.

Pitta Migration vs UsageDD