Changeset 2340021
- Timestamp:
- 07/14/2020 01:43:04 AM (5 years ago)
- File:
-
- 1 edited
-
wpsitesynccontent/trunk/readme.txt (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
wpsitesynccontent/trunk/readme.txt
r2340012 r2340021 14 14 == Description == 15 15 16 WPSiteSync for Content helps Designers, Developers and Content Creators Synchronize 17 SPECIFIC Content (i.e. Posts and Pages) between WordPress sites, AFTER a site has gone live. 18 You can do this in Real-Time, with a simple CLICK of a button! 16 WPSiteSync for Content helps Designers, Developers and Content Creators Synchronize SPECIFIC Content (i.e. Posts and Pages) between WordPress sites, AFTER a site has gone live. You can do this in Real-Time, with a simple CLICK of a button! 19 17 20 18 A typical development workflow looks like this: … … 25 23 4. Deploy Site to LIVE host 26 24 27 The challenge presented once you've deployed is that any future content changes must 28 either be done on the live site, or a full deployment is necessary if the changes were 29 made locally or on a staging site. 30 31 WPSiteSync is unique in that it solves this problem by offering the ability to only 32 deploy the CONTENT that has changed. This means ZERO down-time and ZERO data loss. 33 It is the missing piece of the development puzzle, allowing for a proper workflow 34 beyond the deployment and into its ongoing operation. 25 The challenge presented once you've deployed is that any future content changes must either be done on the live site, or a full deployment is necessary if the changes were made locally or on a staging site. 26 27 WPSiteSync is unique in that it solves this problem by offering the ability to only deploy the CONTENT that has changed. This means ZERO down-time and ZERO data loss. It is the missing piece of the development puzzle, allowing for a proper workflow beyond the deployment and into its ongoing operation. 35 28 36 29 With WPSiteSync, the new workflow looks like this: … … 43 36 6. Push New Additions/Changes from Local or Staging to Live Site 44 37 45 [](http://coderisk.com/wp/plugin/wpsitesynccontent/RIPS-kqglC-ykJe)46 47 38 Example use cases: 48 39 … … 54 45 * You only need to synchronize specific content (not the complete database) 55 46 56 You can use <em>WPSiteSync for Content</em> to synchronize your Posts and Pages between any two 57 WordPress sites, in any configuration. Some examples include: 47 You can use <em>WPSiteSync for Content</em> to synchronize your Posts and Pages between any two WordPress sites, in any configuration. Some examples include: 58 48 59 49 * Local -> Staging … … 64 54 [youtube https://www.youtube.com/watch?v=KpeiTMbdj_Y] 65 55 66 ><strong>Support Details:</strong> We are happy to provide support and help troubleshoot 67 issues. Visit our Support page at <a href="https://serverpress.com/contact/" target="_blank">https://serverpress.com/contact/</a>. 68 Users should know however, that we check the WordPress.org support forums once 69 a week on Wednesdays from 6pm to 8pm PST (UTC -8). 70 71 The <em>WPSiteSync for Content</em> plugin was specifically designed to simplify 72 your workflow when creating content between development, staging and live servers. 73 This tool removes the need to migrate an entire database, potentially overwriting 74 new content on your live site such as comments, reviews, purchases, etc. Now you 75 can update individual Pages or Posts as desired, leaving everything else intact. 76 The best part is that it's a simple click of a button, reducing errors and saving 77 you time. 78 79 WPSiteSync for Content is fully functional in any WordPress environment. We recommend 80 using DesktopServer for your Local Development Environment, but it is not a requirement. 56 ><strong>Support Details:</strong> We are happy to provide support and help troubleshoot issues. Visit our Support page at <a href="https://serverpress.com/contact/" target="_blank">https://serverpress.com/contact/</a>. Users should know however, that we check the WordPress.org support forums once a week on Wednesdays from 6pm to 8pm PST (UTC -8). 57 58 The <em>WPSiteSync for Content</em> plugin was specifically designed to simplify your workflow when creating content between development, staging and live servers. This tool removes the need to migrate an entire database, potentially overwriting new content on your live site such as comments, reviews, purchases, etc. Now you can update individual Pages or Posts as desired, leaving everything else intact. The best part is that it's a simple click of a button, reducing errors and saving you time. 59 60 WPSiteSync for Content is fully functional in any WordPress environment. We recommend using DesktopServer for your Local Development Environment, but it is not a requirement. 81 61 82 62 <strong>This benefits your Development Workflow in more ways than one:</strong> … … 115 95 * FULL access to ALL future Premium Extensions 116 96 117 <strong>For more perks such as Early Access</strong> and <strong>Exclusive Preview</strong> 118 of upcoming Features, please visit us at <a href="https://wpsitesync.com">WPSiteSync.com</a> 119 and join our newsletter. 120 121 <strong>ServerPress, LLC is not responsible for any loss of data that may occur as a result 122 of WPSiteSync for Content's use.</strong> Always backup your data before initial use of this 123 product. Should you experience such an issue, we want to know about it right away. Please 124 <a href="https://serverpress.com/contact/" target="_blank">contact our Support Team</a> 125 and we'll do everything we can to get you up and running. 97 <strong>For more perks such as Early Access</strong> and <strong>Exclusive Preview</strong> of upcoming Features, please visit us at <a href="https://wpsitesync.com">WPSiteSync.com</a> and join our newsletter. 98 99 <strong>ServerPress, LLC is not responsible for any loss of data that may occur as a result of WPSiteSync for Content's use.</strong> Always backup your data before initial use of this product. Should you experience such an issue, we want to know about it right away. Please <a href="https://serverpress.com/contact/" target="_blank">contact our Support Team</a> and we'll do everything we can to get you up and running. 126 100 127 101 == Installation == … … 141 115 2. Activate the plugin through the 'Plugins' menu in WordPress. 142 116 143 You will need to Install and Activate the WPSiteSync for Content plugin on your 144 development website (the Source) as well as the Target web site (where the Content 145 is being moved to). 146 147 Once activated, you can use the Configuration page found at Settings -> WPSiteSync, 148 on the Source website to set the URL of the Target site and enter the login credentials 149 to use when sending data. This will allow the WPSiteSync for Content plugin to 150 communicate with the Target website, authenticate, and then move the data between 151 the websites. You do not need to Configure WPSiteSync for Content on the Target 152 website as this will only be receiving Synchronization requests from the Source 153 site. 117 You will need to Install and Activate the WPSiteSync for Content plugin on your development website (the Source) as well as the Target web site (where the Content is being moved to). 118 119 Once activated, you can use the Configuration page found at Settings -> WPSiteSync, on the Source website to set the URL of the Target site and enter the login credentials to use when sending data. This will allow the WPSiteSync for Content plugin to communicate with the Target website, authenticate, and then move the data between the websites. You do not need to Configure WPSiteSync for Content on the Target website as this will only be receiving Synchronization requests from the Source site. 154 120 155 121 == Frequently Asked Questions == … … 157 123 = Do I need to Install WPSiteSync for Content on both sites? = 158 124 159 Yes! The WPSiteSync for Content needs to be installed on the local or Staging server 160 (the website you're moving the data from - the Source), as well as the Live server 161 (the website you're moving the data to - the Target). 125 Yes! The WPSiteSync for Content needs to be installed on the local or Staging server (the website you're moving the data from - the Source), as well as the Live server (the website you're moving the data to - the Target). 162 126 163 127 = Does this plugin Synchronize all of my content (Pages and Posts) at once? = 164 128 165 No. WPSiteSync for Content will only synchronize the one Page or Post content that 166 you are editing. And it will only Synchronize the content when you tell it to. This 167 allows you to control exactly what content is moved between sites and when it will 168 be moved. 129 No. WPSiteSync for Content will only synchronize the one Page or Post content that you are editing. And it will only Synchronize the content when you tell it to. This allows you to control exactly what content is moved between sites and when it will be moved. 169 130 170 131 = Will this overwrite data while I am editing? = 171 132 172 No. WPSiteSync checks to see if the Content is being edited by someone else on 173 the Target web site. If it is, it will not update the Content, allowing you to 174 coordinate with the users on the Target web site. 175 176 In addition, each time Content is updated or Synchronized on the Target web site, 177 a Post Revision is created (using the Post Revision settings). This allows you to 178 recover Content to a previous version if needed. 133 No. WPSiteSync checks to see if the Content is being edited by someone else on the Target web site. If it is, it will not update the Content, allowing you to coordinate with the users on the Target web site. 134 135 In addition, each time Content is updated or Synchronized on the Target web site, a Post Revision is created (using the Post Revision settings). This allows you to recover Content to a previous version if needed. 179 136 180 137 = Does WPSiteSync only update Page and Posts Content? = 181 138 182 Yes. However, support for synchronizing Custom Post Types is available with our 183 <a href="https://wpsitesync.com/downloads/wpsitesync-for-custom-post-types/" target="_blank">WPSiteSync 184 for Custom Post Types</a> add-on. Additional plugins for User Attribution, Synchronizing 185 Menus and Pulling content are available as well. 186 187 More complex data, such as WooCommerce products, Forms (like Gravity Forms or Ninja 188 Forms), and other plugins that use custom database tables are supported by 189 additional plugins that work with those products. 139 Yes. However, support for synchronizing Custom Post Types and Custom Taxonomies is available with our <a href="https://wpsitesync.com/downloads/wpsitesync-for-custom-post-types/" target="_blank">WPSiteSync for Custom Post Types</a> add-on. Additional plugins for User Attribution, Synchronizing Menus and Pulling content are available as well. 140 141 More complex data, such as WooCommerce products, Forms (like Gravity Forms or Ninja Forms), and other plugins that use custom database tables are supported by additional plugins that work with those products. 190 142 191 143 = Is WPSiteSync Gutenberg Compatible? = 192 144 193 Yes! The free version of <em>WPSiteSync for Content</em> supports all Gutenberg 194 blocks that are part of WordPress. There are many plugins that add more block types 195 than those available in WordPress, however. Our add-on product, <a href="https://wpsitesync.com/downloads/wpsitesync-for-gutenberg-blocks/" 196 target="_blank">WPSiteSync for Gutenberg Blocks</a> adds support for several of 197 the more popular third party Gutenberg add-ons. 198 199 If your favorite Gutenberg Block plugin is not currently supported, let us know 200 and we can add support for it. 201 145 Yes! The free version of <em>WPSiteSync for Content</em> supports all Gutenberg blocks that are part of WordPress. There are many plugins that add more block types than those available in WordPress, however. Our add-on product, <a href="https://wpsitesync.com/downloads/wpsitesync-for-gutenberg-blocks/" target="_blank">WPSiteSync for Gutenberg Blocks</a> adds support for several of the more popular third party Gutenberg add-ons. 146 147 If your favorite Gutenberg Block plugin is not currently supported, let us know and we can add support for it. 202 148 203 149 == Screenshots ==
Note: See TracChangeset
for help on using the changeset viewer.
