WP Staging – DB & File Duplicator & Migration - Version 2.1.1

Version Description

  • New: Add link to tutorial explaining the process of pushing modification to the live site
Download this release

Release Info

Developer ReneHermi
Plugin Icon 128x128 WP Staging – DB & File Duplicator & Migration
Version 2.1.1
Comparing to
See all releases

Code changes from version 2.0.9 to 2.1.1

Files changed (5) hide show
  1. apps/Backend/Modules/Jobs/Data.php +1 -1
  2. apps/Backend/views/_includes/header.php +3 -0
  3. apps/Core/WPStaging.php +1 -1
  4. readme.txt +258 -249
  5. wp-staging.php +91 -78
apps/Backend/Modules/Jobs/Data.php CHANGED
@@ -341,7 +341,7 @@ class Data extends JobExecutable
341
  $content = str_replace('$table_prefix', '$table_prefix = \'' . $this->prefix . '\';//', $content);
342
 
343
  // Replace URLs
344
- $content = str_replace(get_home_url(), get_home_url() . $this->options->cloneDirectoryName, $content);
345
 
346
  if (false === @file_put_contents($path, $content))
347
  {
341
  $content = str_replace('$table_prefix', '$table_prefix = \'' . $this->prefix . '\';//', $content);
342
 
343
  // Replace URLs
344
+ $content = str_replace(get_home_url(), get_home_url() . '/' . $this->options->cloneDirectoryName, $content);
345
 
346
  if (false === @file_put_contents($path, $content))
347
  {
apps/Backend/views/_includes/header.php CHANGED
@@ -30,4 +30,7 @@
30
  </div>
31
  </div>
32
  </div>
 
 
 
33
  </div>
30
  </div>
31
  </div>
32
  </div>
33
+ <div style="font-size:14px;">
34
+ Tutorial: <a href="https://wp-staging.com/docs/copy-staging-site-to-live-site/" target="_blank">Learn how to push changes to live website</a>
35
+ </div>
36
  </div>
apps/Core/WPStaging.php CHANGED
@@ -29,7 +29,7 @@ final class WPStaging {
29
  /**
30
  * Plugin version
31
  */
32
- const VERSION = "2.0.9";
33
 
34
  /**
35
  * Plugin name
29
  /**
30
  * Plugin version
31
  */
32
+ const VERSION = "2.1.1";
33
 
34
  /**
35
  * Plugin name
readme.txt CHANGED
@@ -1,249 +1,258 @@
1
- === WP Staging - DB & File Duplicator & Migration ===
2
-
3
- Author URL: https://wordpress.org/plugins/wp-staging
4
- Plugin URL: https://wordpress.org/plugins/wp-staging
5
- Contributors: ReneHermi, WP-Staging
6
- Donate link: https://wordpress.org/plugins/wp-staging
7
- License: GPLv2 or later
8
- License URI: http://www.gnu.org/licenses/gpl-2.0.html
9
- Tags: staging, duplication, cloning, clone, migration, sandbox, test site, testing, backup, post, admin, administration, duplicate posts
10
- Requires at least: 3.6+
11
- Tested up to: 4.8
12
- Stable tag: 2.0.9
13
-
14
- A duplicator plugin! Clone, duplicate and migrate live sites to independent staging and development sites that are available only to administrators.
15
-
16
- == Description ==
17
-
18
- <strong>This cloning and staging plugin is well tested but work in progress. <br><br>
19
- If you find any issue, please open a [support ticket](https://wp-staging.com/support/ "support ticket").
20
- </strong>
21
- <br /><br />
22
- <strong>Note: </strong> For pushing plugins and theme files to live site, check out [https://wp-staging.com/](https://wp-staging.com/ "WP Staging Pro")
23
- <br /><br />
24
- <blockquote>
25
- <h4> WP Staging for WordPress Migration </h4>
26
- This duplicator plugin allows you to create an staging or development environment in seconds* <br /> <br />
27
- It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.
28
- This sounds pretty simple and yes it is! All the hard time-consumptive database and file copying stuff including url replacements is done in the background.
29
- <br /> <br />
30
- I created this plugin because all other solutions are way too complex, overloaded with dozens of options or having server requirements which are not available on most shared hosting solutions.
31
- All these reasons prevent user from testing new plugins and updates first before installing them on their live website, so its time to release a plugin which has the potential to be merged into everyone´s wordpress workflow.
32
- <br /><br />
33
- <p><small><em>* Time of creation depends on size of your database and file size</em></small></p>
34
- </blockquote>
35
-
36
- WP Staging helps you to prevent your website from being broken or unavailable because of installing untested plugin updates!
37
-
38
- [youtube https://www.youtube.com/watch?v=Ye3fC6cdB3A]
39
-
40
- = Main Features =
41
-
42
- * <strong>Easy: </strong> Staging migration applicable for everyone. No configuration needed!
43
- * <strong>Fast: </strong> Migration process lasts only a few seconds or minutes, depending on the site's size and server I/O power
44
- * <strong>Safe: </strong> Access to staging site is granted for administrators only.
45
- <br /><br />
46
- <strong>More safe:</strong>
47
- <br>
48
- * Admin bar reflects that you are working on a staging site
49
- * Extensive logging if duplication and migration process fails.
50
-
51
- = What does not work or is not tested when running wordpress migration? =
52
-
53
- * Wordpress migration of wordpress multisites (not tested)
54
- * WordPress duplicating process on windows server (not tested but will probably work)
55
- Edit: Duplication on windows server seems to be working well: [Read more](https://wordpress.org/support/topic/wont-copy-files?replies=5 "Read more")
56
-
57
-
58
- <strong>Change your workflow of updating themes and plugins data:</strong>
59
-
60
- 1. Use WP Staging for migration of a production website to a clone site for staging purposes
61
- 2. Customize theme, configuration and plugins or install new plugins
62
- 3. Test everything on your staging site first
63
- 4. Everything running as expected? You are on the save side for migration of all these modifications to your production site!
64
-
65
-
66
- <h3> Why should i use a staging website? </h3>
67
-
68
- Plugin updates and theme customizations should be tested on a staging platform first. Its recommended to have the staging platform on the same server where the production website is located.
69
- When you run a plugin update or plan to install a new one, it is a necessary task to check first the modifications on a clone of your production website.
70
- This makes sure that any modifications is working on your website without throwing unexpected errors or preventing your site from loading. (Better known as the wordpress blank page error)
71
-
72
- Testing a plugin update before installing it in live environment isn´t done very often by most user because existing staging solutions are too complex and need a lot of time to create a
73
- up-to-date copy of your website.
74
-
75
- Some people are also afraid of installing plugins updates because they follow the rule "never touch a running system" with having in mind that untested updates are increasing the risk of breaking their site.
76
- I totally understand this and i am guilty as well here, but unfortunately this leads to one of the main reasons why WordPress installations are often outdated, not updated at all and unsecure due to this non-update behavior.
77
-
78
- <strong> I think its time to change this, so i created "WP Staging" for WordPress migration of staging sites</strong>
79
-
80
- <h3> Can´t i just use my local wordpress development copy for testing like xampp / lampp? </h3>
81
-
82
- Nope! If your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect
83
- of your local copy is working on your live website exactely as you would expect it.
84
- There are some obvious things like differences in the config of php and the server you are running but even such non obvious settings like the amount of ram or the
85
- the cpu performance can lead to unexpected results on your production website.
86
- There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local staging platform.
87
-
88
- This is were WP Staging steps in... Site cloning and staging site creation simplified!
89
-
90
- <h3>I just want to migrate the database from one installation to another</h3>
91
- If you want to migrate your local database to a already existing production site you can use a tool like WP Migrate DB.
92
- WP Staging is only for creating a staging site with latest data from your production site. So it goes the opposite way of WP Migrate DB.
93
- Both tools are excellent cooperating eachother.
94
-
95
- <h3>What are the benefits compared to a plugin like Duplicator?</h3>
96
- At first, i love the [Duplicator plugin](https://wordpress.org/plugins/duplicator/ "Duplicator plugin"). Duplicator is a great tool for migrating from development site to production one or from production site to development one.
97
- The downside is that Duplicator needs adjustments, manually interventions and prerequirements for this. Duplicator also needs some skills to be able to create a development / staging site, where WP Staging does not need more than a click from you.
98
- However, Duplicator is best placed to be a tool for first-time creation of your production site. This is something where it is very handy and powerful.
99
-
100
- So, if you have created a local or webhosted development site and you need to migrate this site the first time to your production domain than you are doing nothing wrong with using
101
- the Duplicator plugin! If you need all you latest production data like posts, updated plugins, theme data and styles in a testing environment than i recommend to use WP Staging instead!
102
-
103
- = I need you feedback =
104
- This plugin has been done in hundreds of hours to work on even the smallest shared webhosting package but i am limited in testing this only on a handful of different server so i need your help:
105
- Please open a [support request](https://wordpress.org/support/plugin/wp-staging/ "support request") and describe your problem exactely. In wp-content/wp-staging/logs you find extended logfiles. Have a look at them and let me know the error-thrown lines.
106
-
107
-
108
- = Important =
109
-
110
- Per default the staging site will have permalinks disabled because the staging site will be cloned into a subfolder and regular permalinks are not working
111
- without doing changes to your .htaccess or nginx.conf.
112
- In the majority of cases this is abolutely fine for a staging platform and you still will be able to test new plugins and do some theme changes on your staging platform.
113
- If you need the same permalink stucture on your staging platform as you have in your prodcution website you have to create a custom .htaccess for apache webserver
114
- or to adjust your nginx.conf.
115
-
116
-
117
- = How to install and setup? =
118
- Install it via the admin dashboard and to 'Plugins', click 'Add New' and search the plugins for 'Staging'. Install the plugin with 'Install Now'.
119
- After installation goto the settings page 'Staging' and do your adjustments there.
120
-
121
-
122
- == Frequently Asked Questions ==
123
-
124
-
125
- == Official Site ==
126
- https://wp-staging.com
127
-
128
- == Installation ==
129
- 1. Download the file "wp-staging" , unzip and place it in your wp-content/plugins/wp-staging folder. You can alternatively upload and install it via the WordPress plugin backend.
130
- 2. Activate the plugin through the 'Plugins' menu in WordPress.
131
- 3. Start Plugins->Staging
132
-
133
- == Screenshots ==
134
-
135
- 1. Step 1. Create new WordPress staging site
136
- 2. Step 2. Scanning your website for files and database tables
137
- 3. Step 3. Wordpress Staging site creation in progress
138
- 4. Finish!
139
-
140
- == Changelog ==
141
-
142
-
143
-
144
- = 2.0.9 =
145
- * New: Exclude unneccessary files from cloning process: .tmp, .log, .htaccess, .git, .gitignore, desktop.ini, .DS_Store, .svn
146
- * New: More details for debugging in Tools->System Info
147
- * Fix: Check if tables in staging site exists before attempting to modify them
148
- * Fix: WordPress in sub directories were not opening
149
- * Tweak: Exclude wp-content/cache folder from copying process
150
-
151
- = 2.0.8 =
152
- * Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process. Still not fixed in 2.0.7
153
-
154
- = 2.0.7 =
155
- * Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process
156
-
157
-
158
- = 2.0.6 =
159
- * Fix: Cancel Cloning button not working
160
- * Fix: Limit max execution time to a maximum of 30sec to prevent high memory consumption and script timeouts
161
-
162
-
163
- = 2.0.5 =
164
- * New: Major version - Complete rewrite of the code base
165
- * New: Batch processing allows to clone even huge sites without any timeouts
166
- * New: Preparation for WP QUADS PRO with ability to copy file changes back to live site
167
- * New: Bypass (broken) third party plugins during wp staging related ajax requests to prevent processing errors. Use a mu plugin for this.
168
-
169
- = 1.1.6 =
170
- * New: Add download link to WP Staging Beta Version 2.0.1
171
-
172
- = 1.1.5 =
173
- * Fix: Admin notice is throwing a false positive write permission error
174
- * New: Move log folder to wp-content/uploads/wp-staging/logs
175
- * New: Tested up to WP 4.7.3
176
-
177
- = 1.1.4 =
178
- * Fix: Fatal error Unsupported operand types
179
-
180
- = 1.1.3 =
181
- * New: Tested up to wp 4.7.2
182
- * Fix: Arrows in drop down for folder selection are distorted
183
- * Tweak: Show working log as default to make debugging easier
184
-
185
- = 1.1.2 =
186
- * Fix: Settings are not deleted when plugin is removed
187
- * Fix: Staging site is available for non administrators
188
-
189
- = 1.1.1 =
190
- * Fix: Change rating url
191
-
192
- = 1.1.0 =
193
- * New: Tested up to WP 4.6
194
- * New: Create a poll and ask what feature is most required
195
-
196
- = 1.0.9 =
197
- * Fix: Undefined WPSTG() warning
198
- * Fix: Change compatibility version to wp 4.5.3
199
-
200
- = 1.0.8 =
201
- * Tested up to WP 4.5.2
202
-
203
- = 1.0.7 =
204
- * Fix: Activation hook is not fired and staging site is not working properly
205
- * Performance: Increase default query copy limit to 1000
206
-
207
- = 1.0.6 =
208
- * Fix: Uninstalling plugin throwing error
209
- * Fix: Error permission admin notice although permission issues are correct
210
-
211
-
212
- = 1.0.5 =
213
- * New: Tested up to WP 4.5
214
- * Fix: Download system log not working
215
- * Fix: Click on Optimizer "Select all | none | invert" links leads to jumping
216
- * Tweak: Make clear that unselecting a checkbox will exlude table or file from copy process
217
- * Tweak: Remove unnecessary text
218
- * Tweak: Change beta notice in dashboard. WP Staging is stable
219
- * Tweak: Change twitter handle to @wpstg
220
-
221
- = 1.0.3 =
222
- * Fix: Missing const MASHFS_VERSION
223
- * Fix: Remove error "table XY has been created, BUT inserting rows failed."
224
- * Fix: Not tested up to 4.4.2 message shown although it's tested up to WP 4.4.2
225
- * New: Disable either free or pro version and does not allow to have both version enabled at the same time
226
-
227
- = 1.0.2 =
228
- * Tweak: Change setting description of uninstall option
229
- * Tweak: Lower tags in readme.txt
230
-
231
- = 1.0.1 =
232
- * New: Orange colored admin bar on staging site for better visualization and comparision between production live site and staging site
233
- * Tweak: Remove contact link on multisite notification
234
-
235
- = 1.0.0 =
236
- * Fix: Do not follow symlinks during file copy process
237
- * Fix: css error
238
- * Fix: Show "not-compatible" notice only when blog version is higher than plugin tested version.
239
- * Fix: undefined var $size
240
- * Fix: Check if $path is null before writing to remaining_files.json
241
- * Fix: $db_helper undefined message
242
- * Fix: Skip non utf8 encoded files during copying process
243
-
244
- Complete changelog: [https://wp-staging.com/changelog.txt](https://wp-staging.com/changelog.txt)
245
-
246
- == Upgrade Notice ==
247
-
248
- = 2.0.2 =
249
- 2.0.2 * New: Batch processing allows to clone even huge sites without any timeouts
 
 
 
 
 
 
 
 
 
1
+ === WP Staging - DB & File Duplicator & Migration ===
2
+
3
+ Author URL: https://wordpress.org/plugins/wp-staging
4
+ Plugin URL: https://wordpress.org/plugins/wp-staging
5
+ Contributors: ReneHermi, WP-Staging
6
+ Donate link: https://wordpress.org/plugins/wp-staging
7
+ License: GPLv2 or later
8
+ License URI: http://www.gnu.org/licenses/gpl-2.0.html
9
+ Tags: staging, duplication, cloning, clone, migration, sandbox, test site, testing, backup, post, admin, administration, duplicate posts
10
+ Requires at least: 3.6+
11
+ Tested up to: 4.8
12
+ Stable tag: 2.1.1
13
+
14
+ A duplicator plugin! Clone, duplicate and migrate live sites to independent staging and development sites that are available only to administrators.
15
+
16
+ == Description ==
17
+
18
+ <strong>This cloning and staging plugin is well tested but work in progress. <br><br>
19
+ If you find any issue, please open a [support ticket](https://wp-staging.com/support/ "support ticket").
20
+ </strong>
21
+ <br /><br />
22
+ <strong>Note: </strong> For pushing plugins and theme files to live site, check out [https://wp-staging.com/](https://wp-staging.com/ "WP Staging Pro")
23
+ <br /><br />
24
+ <blockquote>
25
+ <h4> WP Staging for WordPress Migration </h4>
26
+ This duplicator plugin allows you to create an staging or development environment in seconds* <br /> <br />
27
+ It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.
28
+ This sounds pretty simple and yes it is! All the hard time-consumptive database and file copying stuff including url replacements is done in the background.
29
+ <br /> <br />
30
+ I created this plugin because all other solutions are way too complex, overloaded with dozens of options or having server requirements which are not available on most shared hosting solutions.
31
+ All these reasons prevent user from testing new plugins and updates first before installing them on their live website, so its time to release a plugin which has the potential to be merged into everyone´s wordpress workflow.
32
+ <br /><br />
33
+ <p><small><em>* Time of creation depends on size of your database and file size</em></small></p>
34
+ </blockquote>
35
+
36
+ WP Staging helps you to prevent your website from being broken or unavailable because of installing untested plugin updates!
37
+
38
+ [youtube https://www.youtube.com/watch?v=Ye3fC6cdB3A]
39
+
40
+ = Main Features =
41
+
42
+ * <strong>Easy: </strong> Staging migration applicable for everyone. No configuration needed!
43
+ * <strong>Fast: </strong> Migration process lasts only a few seconds or minutes, depending on the site's size and server I/O power
44
+ * <strong>Safe: </strong> Access to staging site is granted for administrators only.
45
+ <br /><br />
46
+ <strong>More safe:</strong>
47
+ <br>
48
+ * Admin bar reflects that you are working on a staging site
49
+ * Extensive logging if duplication and migration process fails.
50
+
51
+ = What does not work or is not tested when running wordpress migration? =
52
+
53
+ * Wordpress migration of wordpress multisites (not tested)
54
+ * WordPress duplicating process on windows server (not tested but will probably work)
55
+ Edit: Duplication on windows server seems to be working well: [Read more](https://wordpress.org/support/topic/wont-copy-files?replies=5 "Read more")
56
+
57
+
58
+ <strong>Change your workflow of updating themes and plugins data:</strong>
59
+
60
+ 1. Use WP Staging for migration of a production website to a clone site for staging purposes
61
+ 2. Customize theme, configuration and plugins or install new plugins
62
+ 3. Test everything on your staging site first
63
+ 4. Everything running as expected? You are on the save side for migration of all these modifications to your production site!
64
+
65
+
66
+ <h3> Why should i use a staging website? </h3>
67
+
68
+ Plugin updates and theme customizations should be tested on a staging platform first. Its recommended to have the staging platform on the same server where the production website is located.
69
+ When you run a plugin update or plan to install a new one, it is a necessary task to check first the modifications on a clone of your production website.
70
+ This makes sure that any modifications is working on your website without throwing unexpected errors or preventing your site from loading. (Better known as the wordpress blank page error)
71
+
72
+ Testing a plugin update before installing it in live environment isn´t done very often by most user because existing staging solutions are too complex and need a lot of time to create a
73
+ up-to-date copy of your website.
74
+
75
+ Some people are also afraid of installing plugins updates because they follow the rule "never touch a running system" with having in mind that untested updates are increasing the risk of breaking their site.
76
+ I totally understand this and i am guilty as well here, but unfortunately this leads to one of the main reasons why WordPress installations are often outdated, not updated at all and unsecure due to this non-update behavior.
77
+
78
+ <strong> I think its time to change this, so i created "WP Staging" for WordPress migration of staging sites</strong>
79
+
80
+ <h3> Can´t i just use my local wordpress development copy for testing like xampp / lampp? </h3>
81
+
82
+ Nope! If your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect
83
+ of your local copy is working on your live website exactely as you would expect it.
84
+ There are some obvious things like differences in the config of php and the server you are running but even such non obvious settings like the amount of ram or the
85
+ the cpu performance can lead to unexpected results on your production website.
86
+ There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local staging platform.
87
+
88
+ This is were WP Staging steps in... Site cloning and staging site creation simplified!
89
+
90
+ <h3>I just want to migrate the database from one installation to another</h3>
91
+ If you want to migrate your local database to a already existing production site you can use a tool like WP Migrate DB.
92
+ WP Staging is only for creating a staging site with latest data from your production site. So it goes the opposite way of WP Migrate DB.
93
+ Both tools are excellent cooperating eachother.
94
+
95
+ <h3>What are the benefits compared to a plugin like Duplicator?</h3>
96
+ At first, i love the [Duplicator plugin](https://wordpress.org/plugins/duplicator/ "Duplicator plugin"). Duplicator is a great tool for migrating from development site to production one or from production site to development one.
97
+ The downside is that Duplicator needs adjustments, manually interventions and prerequirements for this. Duplicator also needs some skills to be able to create a development / staging site, where WP Staging does not need more than a click from you.
98
+ However, Duplicator is best placed to be a tool for first-time creation of your production site. This is something where it is very handy and powerful.
99
+
100
+ So, if you have created a local or webhosted development site and you need to migrate this site the first time to your production domain than you are doing nothing wrong with using
101
+ the Duplicator plugin! If you need all you latest production data like posts, updated plugins, theme data and styles in a testing environment than i recommend to use WP Staging instead!
102
+
103
+ = I need you feedback =
104
+ This plugin has been done in hundreds of hours to work on even the smallest shared webhosting package but i am limited in testing this only on a handful of different server so i need your help:
105
+ Please open a [support request](https://wordpress.org/support/plugin/wp-staging/ "support request") and describe your problem exactely. In wp-content/wp-staging/logs you find extended logfiles. Have a look at them and let me know the error-thrown lines.
106
+
107
+
108
+ = Important =
109
+
110
+ Per default the staging site will have permalinks disabled because the staging site will be cloned into a subfolder and regular permalinks are not working
111
+ without doing changes to your .htaccess or nginx.conf.
112
+ In the majority of cases this is abolutely fine for a staging platform and you still will be able to test new plugins and do some theme changes on your staging platform.
113
+ If you need the same permalink stucture on your staging platform as you have in your prodcution website you have to create a custom .htaccess for apache webserver
114
+ or to adjust your nginx.conf.
115
+
116
+
117
+ = How to install and setup? =
118
+ Install it via the admin dashboard and to 'Plugins', click 'Add New' and search the plugins for 'Staging'. Install the plugin with 'Install Now'.
119
+ After installation goto the settings page 'Staging' and do your adjustments there.
120
+
121
+
122
+ == Frequently Asked Questions ==
123
+
124
+
125
+ == Official Site ==
126
+ https://wp-staging.com
127
+
128
+ == Installation ==
129
+ 1. Download the file "wp-staging" , unzip and place it in your wp-content/plugins/wp-staging folder. You can alternatively upload and install it via the WordPress plugin backend.
130
+ 2. Activate the plugin through the 'Plugins' menu in WordPress.
131
+ 3. Start Plugins->Staging
132
+
133
+ == Screenshots ==
134
+
135
+ 1. Step 1. Create new WordPress staging site
136
+ 2. Step 2. Scanning your website for files and database tables
137
+ 3. Step 3. Wordpress Staging site creation in progress
138
+ 4. Finish!
139
+
140
+ == Changelog ==
141
+
142
+
143
+
144
+ = 2.1.1 =
145
+ * New: Add link to tutorial explaining the process of pushing modification to the live site
146
+
147
+ = 2.1.0 =
148
+ * New: Exclude unneccessary files from cloning process: .tmp, .log, .htaccess, .git, .gitignore, desktop.ini, .DS_Store, .svn
149
+ * New: More details for debugging in Tools->System Info
150
+ * Fix: Check if tables in staging site exists before attempting to modify them
151
+ * Fix: WordPress in sub directories were not opening
152
+ * Fix: Nonce check not working if nonce life time is filtered by another plugin WP Bug: https://core.trac.wordpress.org/ticket/41617#comment:1
153
+ * Fix: Access to staging site not working, if WP_SITEURL and WP_HOME is defined in wp-config.php
154
+ * Tweak: Exclude wp-content/cache folder from copying process
155
+
156
+
157
+ = 2.0.9 =
158
+ * Skip Version
159
+
160
+ = 2.0.8 =
161
+ * Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process. Still not fixed in 2.0.7
162
+
163
+ = 2.0.7 =
164
+ * Fix: After update from wpstg 1.6.x to 2.x previous settings were not imported resulting in cancelation of cloning process
165
+
166
+
167
+ = 2.0.6 =
168
+ * Fix: Cancel Cloning button not working
169
+ * Fix: Limit max execution time to a maximum of 30sec to prevent high memory consumption and script timeouts
170
+
171
+
172
+ = 2.0.5 =
173
+ * New: Major version - Complete rewrite of the code base
174
+ * New: Batch processing allows to clone even huge sites without any timeouts
175
+ * New: Preparation for WP QUADS PRO with ability to copy file changes back to live site
176
+ * New: Bypass (broken) third party plugins during wp staging related ajax requests to prevent processing errors. Use a mu plugin for this.
177
+
178
+ = 1.1.6 =
179
+ * New: Add download link to WP Staging Beta Version 2.0.1
180
+
181
+ = 1.1.5 =
182
+ * Fix: Admin notice is throwing a false positive write permission error
183
+ * New: Move log folder to wp-content/uploads/wp-staging/logs
184
+ * New: Tested up to WP 4.7.3
185
+
186
+ = 1.1.4 =
187
+ * Fix: Fatal error Unsupported operand types
188
+
189
+ = 1.1.3 =
190
+ * New: Tested up to wp 4.7.2
191
+ * Fix: Arrows in drop down for folder selection are distorted
192
+ * Tweak: Show working log as default to make debugging easier
193
+
194
+ = 1.1.2 =
195
+ * Fix: Settings are not deleted when plugin is removed
196
+ * Fix: Staging site is available for non administrators
197
+
198
+ = 1.1.1 =
199
+ * Fix: Change rating url
200
+
201
+ = 1.1.0 =
202
+ * New: Tested up to WP 4.6
203
+ * New: Create a poll and ask what feature is most required
204
+
205
+ = 1.0.9 =
206
+ * Fix: Undefined WPSTG() warning
207
+ * Fix: Change compatibility version to wp 4.5.3
208
+
209
+ = 1.0.8 =
210
+ * Tested up to WP 4.5.2
211
+
212
+ = 1.0.7 =
213
+ * Fix: Activation hook is not fired and staging site is not working properly
214
+ * Performance: Increase default query copy limit to 1000
215
+
216
+ = 1.0.6 =
217
+ * Fix: Uninstalling plugin throwing error
218
+ * Fix: Error permission admin notice although permission issues are correct
219
+
220
+
221
+ = 1.0.5 =
222
+ * New: Tested up to WP 4.5
223
+ * Fix: Download system log not working
224
+ * Fix: Click on Optimizer "Select all | none | invert" links leads to jumping
225
+ * Tweak: Make clear that unselecting a checkbox will exlude table or file from copy process
226
+ * Tweak: Remove unnecessary text
227
+ * Tweak: Change beta notice in dashboard. WP Staging is stable
228
+ * Tweak: Change twitter handle to @wpstg
229
+
230
+ = 1.0.3 =
231
+ * Fix: Missing const MASHFS_VERSION
232
+ * Fix: Remove error "table XY has been created, BUT inserting rows failed."
233
+ * Fix: Not tested up to 4.4.2 message shown although it's tested up to WP 4.4.2
234
+ * New: Disable either free or pro version and does not allow to have both version enabled at the same time
235
+
236
+ = 1.0.2 =
237
+ * Tweak: Change setting description of uninstall option
238
+ * Tweak: Lower tags in readme.txt
239
+
240
+ = 1.0.1 =
241
+ * New: Orange colored admin bar on staging site for better visualization and comparision between production live site and staging site
242
+ * Tweak: Remove contact link on multisite notification
243
+
244
+ = 1.0.0 =
245
+ * Fix: Do not follow symlinks during file copy process
246
+ * Fix: css error
247
+ * Fix: Show "not-compatible" notice only when blog version is higher than plugin tested version.
248
+ * Fix: undefined var $size
249
+ * Fix: Check if $path is null before writing to remaining_files.json
250
+ * Fix: $db_helper undefined message
251
+ * Fix: Skip non utf8 encoded files during copying process
252
+
253
+ Complete changelog: [https://wp-staging.com/changelog.txt](https://wp-staging.com/changelog.txt)
254
+
255
+ == Upgrade Notice ==
256
+
257
+ = 2.0.2 =
258
+ 2.0.2 * New: Batch processing allows to clone even huge sites without any timeouts
wp-staging.php CHANGED
@@ -1,78 +1,91 @@
1
- <?php
2
-
3
- /**
4
- * Plugin Name: WP Staging
5
- * Plugin URI: https://wordpress.org/plugins/wp-staging
6
- * Description: Create a staging clone site for testing & developing
7
- * Author: WP-Staging, René Hermenau, Ilgıt Yıldırım
8
- * Author URI: https://wordpress.org/plugins/wp-staging
9
- * Version: 2.0.9
10
- * Text Domain: wpstg
11
- * Domain Path: /languages/
12
-
13
- *
14
- * WP-Staging is free software: you can redistribute it and/or modify
15
- * it under the terms of the GNU General Public License as published by
16
- * the Free Software Foundation, either version 2 of the License, or
17
- * any later version.
18
- *
19
- * WP-Staging is distributed in the hope that it will be useful,
20
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
21
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
22
- * GNU General Public License for more details.
23
- *
24
- * You should have received a copy of the GNU General Public License
25
- * along with Staging. If not, see <http://www.gnu.org/licenses/>.
26
- *
27
- * @package WPSTG
28
- * @category Core
29
- * @author René Hermenau, Ilgıt Yıldırım
30
- */
31
-
32
- // No Direct Access
33
- if (!defined("WPINC"))
34
- {
35
- die;
36
- }
37
-
38
- // Plugin Folder Path
39
- if( !defined( 'WPSTG_PLUGIN_DIR' ) ) {
40
- define( 'WPSTG_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
41
- }
42
- // Plugin Folder URL
43
- if( !defined( 'WPSTG_PLUGIN_URL' ) ) {
44
- define( 'WPSTG_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
45
- }
46
-
47
- /**
48
- * Path to main WP Staging class
49
- * Make sure to not redeclare class in case free version has been installed previosly
50
- */
51
- if (!class_exists( 'WPStaging\WPStaging' )){
52
- require_once plugin_dir_path(__FILE__) . "apps/Core/WPStaging.php";
53
- }
54
-
55
- $wpStaging = \WPStaging\WPStaging::getInstance();
56
-
57
- /**
58
- * Load a few important WP globals into WPStaging class to make them available via dependancy injection
59
- */
60
-
61
- // Wordpress DB Object
62
- if (isset($wpdb))
63
- {
64
- $wpStaging->set("wpdb", $wpdb);
65
- }
66
-
67
- // WordPress Filter Object
68
- if (isset($wp_filter))
69
- {
70
- $wpStaging->set("wp_filter", function() use(&$wp_filter) {
71
- return $wp_filter;
72
- });
73
- }
74
-
75
- /**
76
- * Inititalize WPStaging
77
- */
78
- $wpStaging->run();
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ <?php
2
+
3
+ /**
4
+ * Plugin Name: WP Staging
5
+ * Plugin URI: https://wordpress.org/plugins/wp-staging
6
+ * Description: Create a staging clone site for testing & developing
7
+ * Author: WP-Staging
8
+ * Author URI: https://wp-staging.com
9
+ * Contributors: ReneHermi, ilgityildirim
10
+ * Version: 2.1.1
11
+ * Text Domain: wpstg
12
+ * Domain Path: /languages/
13
+
14
+ *
15
+ * WP-Staging is free software: you can redistribute it and/or modify
16
+ * it under the terms of the GNU General Public License as published by
17
+ * the Free Software Foundation, either version 2 of the License, or
18
+ * any later version.
19
+ *
20
+ * WP-Staging is distributed in the hope that it will be useful,
21
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
22
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
23
+ * GNU General Public License for more details.
24
+ *
25
+ * You should have received a copy of the GNU General Public License
26
+ * along with Staging. If not, see <http://www.gnu.org/licenses/>.
27
+ *
28
+ * @package WPSTG
29
+ * @category Core
30
+ * @author René Hermenau, Ilgıt Yıldırım
31
+ */
32
+
33
+ // No Direct Access
34
+ if (!defined("WPINC"))
35
+ {
36
+ die;
37
+ }
38
+
39
+ // Plugin Folder Path
40
+ if( !defined( 'WPSTG_PLUGIN_DIR' ) ) {
41
+ define( 'WPSTG_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
42
+ }
43
+ // Plugin Folder URL
44
+ if( !defined( 'WPSTG_PLUGIN_URL' ) ) {
45
+ define( 'WPSTG_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
46
+ }
47
+
48
+
49
+ /**
50
+ * Fix nonce check
51
+ * https://core.trac.wordpress.org/ticket/41617#ticket
52
+ * @param int $seconds
53
+ * @return int
54
+ */
55
+ function wpstg_overwrite_nonce($seconds){
56
+ return 86400;
57
+ }
58
+ add_filter('nonce_life', 'wpstg_overwrite_nonce', 99999);
59
+
60
+ /**
61
+ * Path to main WP Staging class
62
+ * Make sure to not redeclare class in case free version has been installed previosly
63
+ */
64
+ if (!class_exists( 'WPStaging\WPStaging' )){
65
+ require_once plugin_dir_path(__FILE__) . "apps/Core/WPStaging.php";
66
+ }
67
+
68
+ $wpStaging = \WPStaging\WPStaging::getInstance();
69
+
70
+ /**
71
+ * Load a few important WP globals into WPStaging class to make them available via dependancy injection
72
+ */
73
+
74
+ // Wordpress DB Object
75
+ if (isset($wpdb))
76
+ {
77
+ $wpStaging->set("wpdb", $wpdb);
78
+ }
79
+
80
+ // WordPress Filter Object
81
+ if (isset($wp_filter))
82
+ {
83
+ $wpStaging->set("wp_filter", function() use(&$wp_filter) {
84
+ return $wp_filter;
85
+ });
86
+ }
87
+
88
+ /**
89
+ * Inititalize WPStaging
90
+ */
91
+ $wpStaging->run();