You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pardon me for asking, because this might be a stupid question, but:
Is there a way to target only a subsite (on a wordpress multisite install) with grunt-wordpress-deploy? We're working with 100+ live sites on the production environment and would like to prevent accidental overwrites.
Also it would be faster to just push and pull only the targeted subsite. Would love to hear from you, and thanks for a wonderful plugin!
The text was updated successfully, but these errors were encountered:
Hello,
I have to look better at how the multisite installation works in Wordpress. The plugin was originally intended for single wordpress installation but, why not?
Let me me look if it's possibile and how much effort is needed.
In the meantime, thank you!
Cool thanks! For clarity: there is an answer on SO, where someone explains the DB structure for WP multisite, and there's also docs explaining it on wordpress.org.
Also, someone explained in detail here what steps are needed to migrate a WP subsite on a multisite install.
I don't know what the best solution would be for the plugin. You could allow the user to specify the necessary db queries one by one (which would ask more of the user but be easier to build), or you could have something like a "multisite" flag in the options (which would be more difficult to code but easier for the user)..
Pardon me for asking, because this might be a stupid question, but:
Is there a way to target only a subsite (on a wordpress multisite install) with grunt-wordpress-deploy? We're working with 100+ live sites on the production environment and would like to prevent accidental overwrites.
Also it would be faster to just push and pull only the targeted subsite. Would love to hear from you, and thanks for a wonderful plugin!
The text was updated successfully, but these errors were encountered: