Joe_Fitz

This plugins was designed to speed up and manage the process of creating a running migrations scripts. Migrations scripts are used to edit content on a blog to blog basis by running php files which manipulate your WordPress database. This could be adding or removing a page or post to certain blogs. Strategery Migrations also provides an interface to manage your migrations scripts. You can view a list of all migrations files and see a timestamp indicating when a migration file was created. You can see individual blogs’ migration state so that you can tell what files have been run or if a certain blog has been migrated. You can look at a list of all your blogs and see what their migration states are compared to each other.
This plugin was made for WordPress implementations using a multisite network with sub-directories.
<h3>Usage Instructions</h3>
<h4>Creating a Migration Script</h4>
<ol>
<li>Click on the Add New link in the Migrations admin options tab</li>
<li>Enter a the script’s filename using underscores instead of spaces (file_name)</li>
<li>Click Create File</li>
</ol>
You are then redirected to the list or migration files.
At this point the file has been generated and exists in the ‘/strategery-migrations/migrations/’ folder in your ‘plugins’ directory.
The filename is broken up into 2 parts. The first part before the dash(-) is the timestamp in YYYYMMDDHHMMSS format. This number is used to compare the sate of a blog compared to when this file was created. When a migration is run and completed, it will update the blog that ran the migration to reflect its new state. The sate for a blog is the same timestamp of the most recent migrations run on it. Only migrations with a later timestamp than the blog’s state timestamp will be run. The second part of the filename is the actual name of the migration script file. The format uses underscores as spaces and will be read by the plugin to create the classname in the file using camel case. 
Open the file that was created and start coding the migration script. You will notice that the file contains a class that extends the main migration class. Each migration script defines a new class with two methods. The up method is used for creating pages or posts. It is the creation method. The down method is used for undoing the up method. It Is a way to revert the migration. This method is optional. 
The methods are run on a blog to blog basis and work within the context of each blog. To get the ID of the current blog, for example, you can use the get_current_blog_id() function.
<h4>Models</h4>
Models are abstracts that are used to query your database. Models are used to save or delete that model type into your database. A model could be a post or a page, etc. To use models you need to make use of the getModel function.
$this->getModel( $type , $data );
$type – A string that picks wether the model is a page or a post, etc.
$data – An array that contains information related to the model type.
Example
$data = array(‘post_type’ => ‘page’ , ‘post_name’ => ‘menu-add’ , ‘post_title’ => ‘Add Menu Item’ );
$post = $this->getModel(‘Post’, $data );
You can also use the shortcut getPost($data).
The commands above query your database for existing posts that match the given data in the current blog and return an object of the post. You can then access that post’s information using the object. For example $post->ID will return the id of the post.
To create a page you use the same function call and add ->save() to the end.
$post = $this->getModel(‘Post’, array(‘post_type’ => ‘page’ , ‘post_name’ => ‘menu-add’ , ‘post_title’ => ‘Add Menu Item’ ))->save();
The command above queries your database for existing posts that match the given data in the current blog. If there is no match in the database it will create that post in the database and return an object of it. The save() command will not create duplicates.
If you want to delete a given post you simply need to replace save() with delete().
<h4>Your Database</h4>
To run queries on your database without using models you have to use $this->db(). It will return the WordPress database. To run an insert for example you would use the following code.
Example
$this->db()->insert($table, $data);
If you want to insert into each blog’s post table you would set the $table as $this->db()->posts
The command would then look like this
$this->db()->insert( $this->db()->posts , $data );
<h4>Excluding Pages</h4>
This migration plugin comes with a helper class that allows you to remove a page from the navigation menu. Pages that should not appear in your navigation menu can easily be excluded with one line of code. These pages are still reachable and still exist but they will not be seen by users with all your other navigation links.
This exclude functionality requires having another <a href="https://wordpress.org/extend/plugins/exclude-pages/" rel="ugc">plugin</a> active.
To use the helper function you need to pass it a path to helper class you are looking for.
$this->getHelper($path);
The getHelper function takes a string that contains the path to the specific helper class you are looking for.
$this->getHelper($path)->method($args);
This is the full call to a helper class method which has the helper function that takes the path to the class you are hooking into. getHelper returns an instance of that class and can be used to execute methods. All helper classes are contained in the ‘/lib/Helpers/Plugins/’ directory. It contains .php files with names in camel case. The class that is defined in each file is named the same as the file name except with underscores separating each word. For the exclude from navigation class, it is contained in the ExcludeFromNav.php file, but the class name is exclude_from_nav. This name is the one you need for the helper function.
Below is an example of how to call the exclude from navigation helper class.
Example
$this->getHelper(‘plugins/exclude_from_nav’)->exclude($post->ID);
exclude() takes the id of the page being excluded as an argument.
<h4>Logging</h4>
While the migration is running, there will be output in the migrations report showing you the progress of your migration. It will let you know if there was an error finding a specific post or if the migration was already done and it is already up to date.
You can add your own logging information inside your up and down methods for each migration script. This could be a simple message saying you did whatever you were trying to do. You do this by using the log() function. It simply echos the string passed to it.
$this->log($message , $nl);
Above is how it is called. It doesn’t format the string, so newlines and tabs must be added in as usual. $nl is an optional parameter that is of type bool which indicates whether to add a newline to the end of the $message string.
<h4>Running Migrations Scripts</h4>
There are several ways to run migrations scripts depending on how you want the migrations to be done.
The options are:
<ul>
<li>Run a single migration file a certain blog</li>
<li>Run all migration files for a single blog</li>
<li>Run all migration files for all blogs</li>
</ul>
To run a single migration file for a certain blog you can go to that blog in the WordPress backend and click on the Migrations link in the Migrations admin menu tab. Once you are at the migrations list there is a run button with to each list item on the right. Clicking this will run that script for the current blog.
To run all migration files for a certain blog you can either click the run all button at the top of that blog’s migrations list or click the migrate button that is in the blog list page. To get to this page you must be in the network administration panel and click on the Blog List link in the
Migrations admin menu tab. There is a migrate button for each blog in the list on the right side or the table.
To run all migrations for all blogs click the Migrate All button at the top of the Blog List page.

Strategery Migrations

Easily run and manage migration scripts to assist in updating blogs on your site.

migrate

nick843

Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/wp-clone-by-wp-academy" rel="nofollow ugc">https://tastewp.com/plugins/wp-clone-by-wp-academy</a>. 
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)
WP Clone is a great way to backup, migrate or clone a WordPress site to another domain or hosting server.
You can also use it to backup, migrate or clone your site to/from local server hosting, to create backup of your site for development or testing purposes, and to install pre-configured backups of WordPress.
WP Clone is a superior to other backup & migrate plugins for the following reasons:
<ul>
<li>It does not require FTP access to backup files you migrate or clone, neither the source or destination site; just install a new WordPress on the destination site, install our backup plugin, and follow the prompts to migrate or clone your site.</li>
<li>It does not backup or restore the WordPress system files (it just creates user content and database backups); reducing upload time for migration and improving security of your site</li>
<li>It fetches the site backup via your host’s direct http connection, which saves you from having to upload large backup files, making it easier to migrate.</li>
</ul>
<h4>What are today’s limitations?</h4>
Today:
<ul>
<li>90% of cases: Backups & migrations work flawlessly (we fixed some key bugs in the most recent version)</li>
<li>9% of cases: Backups or migrations fail due to your hoster’s configurations (most likely limits in up- and downloads) which is typically the case when you backup or migrate very large sites. However, there’s a workaround: simply do a “Database Only” backup (use “Advanced Settings”), transfer the wp-content directory over with FTP, and then restore new site. Then backup and migration also works.</li>
<li>1% of cases: Your site/hosting is abnormal (pardon our French) and backup or migration doesn’t work. However: that’s what we’ll now be working on, so that eventually backups and migrations will work in all cases.</li>
</ul>
The 1% case means:
<ul>
<li>Basic rule: DO NOT use it as your only backup solution! Only use it for migrations (so that if something fails, you still have the files on your old site as backup).</li>
<li>If you want to use it as backup, test it by restoring the backup file on a new site. If that works fine you should be safe.</li>
<li>In any case, we cannot take any responsibility if backup or migration fails.</li>
</ul>
Note: 
* There is never an issue in damaging the source installation (i.e. on the site where you create the backup). So backup sites at your pleasure. If your backup succeeds then chances are good that the migration (i.e. restore on another site) will also succeed. But don’t take any chances. 
* If backup or migration (restore) fails, just try it again. Often it works on second attempt.
<h4>Other tips how to backup and migrate</h4>
<ul>
<li>NEVER overwrite an installation for which you do not have an alternate backup source (e.g. a cPanel backup). Normally you would restore the backup onto a fresh WP installation on another host or on a subdomain. If the restore fails your destination site might become unusable, so be prepared to enter cPanel and then destroy / recreate the new installation if necessary.</li>
<li>DO NOT use our backup plugin on WP Engine or any hosting system with proprietary operating system. Instead, use their built-in backup tools.</li>
<li>Large sites (>2GB) might take as long as an hour to backup and migrate. Sites of 250 MB or less should take no more than a minute or two to backup, depending on your server.</li>
<li>We recommend you deactivate and delete page caching, security and maybe redirection plugins before you migrate, and re-install them on the new site, if necessary. In general, delete all unnecessary plugins and data from your site before you backup. You can also use the “Exclude directories” option if you have large media files, which you can then copy back to the new site with FTP.</li>
<li>How to copy from local server to your hosted website: Create a backup of the local site in the usual way, then save the backup file (right-click > Save) to your local disk. Upload this file to the root directory of your destination website and then use this url in the “Restore” dialog of the new site: http://yourdomain.com/.</li>
</ul>
<h4>Help Video</h4>
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/xN5Ffhyn4Ao?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h4>Credits</h4>
WP Clone uses functions from the “Safe Search and Replace on Database with Serialized Data” script first written by David Coveney of Interconnect IT Ltd (UK) http://www.davidcoveney.com or http://www.interconnectit.com and released under the WTFPL http://sam.zoy.org/wtfpl/. Partial script with full changelog is placed inside ‘lib/files’ directory.
This plugin is part of the Inisev product family – <a href="https://inisev.com" rel="nofollow ugc">check out our other products</a>.

Strategery Migrations vs Clone