deliciousbrains / wp-migrate-db-pro-tweaks

Examples of using WP Migrate DB Pro's filters

WP Migrate DB Pro Tweaks

This is a WordPress plugin, meant as a starting point for developers to tweak WP Migrate DB Pro using WordPress filters.

Installation

Create a /wp-migrate-db-pro-tweaks/ folder in /wp-content/plugins/ and simply drop the wp-migrate-db-pro-tweaks.php file into it. Then go to the Plugins page in your WordPress dashboard and activate it.

Setup

Open the wp-migrate-db-pro-tweaks.php file and take a look at the init() function. You will notice that all the calls to add_filter() are commented out. So, at the moment the plugin does nothing even though it's activated. To enable a filter, simply uncomment the appropriate add_filter() line.

wp-migrate-db-pro-tweaks's Issues

Add details about intent to the `wpmdb_replace_custom_data` filter

Please see https://github.com/deliciousbrains/wp-migrate-db-pro/issues/767#issuecomment-64175824 for context.

Document new filters in the recursive_unserialize_replace() method

Add example for wpmdb_exclude_resized_media

returnng false for wpmdb_exclude_resized_media will skip migrating sizes.

Is there a filter for completely ignoring a table in all migrations.

I have a custom table in the database with the same prefix as all the other tables. All the data in that table is environment specific so I never want it to be included in migrations. I was hoping there would be a simple filter that would allow me to exclude specific tables regardless of profile settings but I haven't been able to track one down.

I know that migration profiles could be set up to exclude this table, but there's too much room for human error there.

I did find a wpmd_tables filter. It has a second parameter of $scope. During the finalization step this filter is used to figure out which tables to finalize using the temp scope.

$temp_tables = $this->table->get_tables('temp');

However, if I exclude the table using that filter, it leaves behind the temporary table.

The best I've been able to come up with is waiting for WPMDB to create the temp table and then delete it:

        add_action('wpmdb_post_process_table_data', function($table) {
            $prefix = \DeliciousBrains\WPMDB\Common\Properties\Properties::getInstance()->temp_prefix;
            $tableToIgnore = ActivityLog::getTableName();
            if ($table === $prefix . $tableToIgnore) {
                global $wpdb;
                $wpdb->query("DROP TABLE IF EXISTS $table");
            }
        });

It works but it definitely feels ridiculous.

Add example fix for when MariaDB uses TRANSACTIONAL in create table options

When migrating from MariaDB to MySQL and the Aria engine in MariaDB has the TRANSACTIONAL setting enabled it adds TRANSACTIONAL=1 to the CREATE TABLE options.

We should alter the example for wpmdb_create_table_query to show how to fix this.

It's not obvious whether the plugin should be installed locally or remotely for each function.

Sometimes the tweaks plugin should be installed locally, sometimes it should be installed on the remote, and sometimes it depends on whether it's an export (always local), push or pull as to where the tweaks plugin should be installed.

We should make it more obvious where the tweaks plugin should be installed for each use.

Add filter wpmdb_find_and_replace

Once wpmdbpro 1.4.3 goes out the door, we should add a filter example for wpmdb_find_and_replace.

Test/document the remaining hooks

Add wpmdb_preserved_sitemeta_options for Multisite options

Rework wpmdb_migration_complete example to simpler, more realistic example

I'd like to remove the current example and instead, show how to set WooCommerce Stripe addon to test mode.

Demonstrate new before and after filters for custom data

Two new filters will be available in WPMDB 1.5 to allow data to be 'massaged' before and after the recursive find and replace occurs. This is specifically geared towards base64 encoded data. deliciousbrains/wp-migrate-db-pro#1078

An example should be provided.

Add readme.md with a short blurb about what the plugin is and how it can be used

Tweaks init() method being hooked in too late

Was having an issue where I was unable to use a filter to change the temporary prefix used during a migration. Tracked it down to how we're hooking in the init() method for the tweaks plugin.

It being fired on the WordPress init action at a priority of 9. While the WPMDB class was being initialized on the same hook at priority of 5.

Changed it to instead be hooked in at a priority of 4 instead.

Is this okay?

Is there a list of attributes which we can use in our hook methods?

Hi,

I was wondering if there's a list with all object attributes we can call inside the action hooks?

In my case, I want to log some deployment with the migration_complete hook, like if the migration was a network to network migration or it was subsite to subsite and which of the subsite was migrated.
So I need some more information besides $migration_type and $connection_url.

Is there something I've missed?

Thanks!

Add new filter for multisite domain mapped subsite replaces

As per: https://github.com/deliciousbrains/wp-migrate-db-pro/issues/296