Open
Conversation
added 5 commits
June 17, 2013 11:29
* fixed issue where incorrect URL was displayed in domain change dialog. * added back buttons to launch different deployments * defaulted file checkboxes to off * changed date format in archive lister (previous commit)
Settings panes can now be made just by adding an 'add_meta_box()' function in the following format: add_meta_box( 'wpmove-NAME-settings', __( 'NAME Settings', 'WPMove' ), array($this, 'metabox_settings'), 'wpmove-settings',$context = 'advanced', $priority = 'default', $callback_args='NAME');
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background:
My company uses a 3 tier deployment strategy, and Wordpress Move has become an integral part of our workflow. The only thing that slows us down, is that after migrating a database, we have to reset the FTP settings at each step to promote content to the next level. Our solution is to store multiple FTP configurations in the database so they are always available. This facilitates simple pushing of content both up and down the chain.
Tiers (and how we use them):
Changes: