Version Description
- New: Compatible up to WordPress 5.4.2
- Fix: Remove beta notice
- Fix: Error if views are cloned
- Fix: Fatal error if WordPress is older than 4.5
- Fix: Merge pro/free version
- Fix: Step switching logic does not work properly
- Fix: Fix progress bar when certains steps are skipped
- Fix: Change german translation for REPORT ISSUE
Download this release
Release Info
Developer | ReneHermi |
Plugin | WP Staging – DB & File Duplicator & Migration |
Version | 2.7.5 |
Comparing to | |
See all releases |
Code changes from version 2.7.4 to 2.7.5
- Backend/views/notices/wp-version-compatible-message.php +4 -5
- readme.txt +51 -44
- vendor/autoload.php +1 -1
- vendor/composer/autoload_real.php +4 -4
- vendor/composer/autoload_static.php +3 -3
- wp-staging.php +2 -2
Backend/views/notices/wp-version-compatible-message.php
CHANGED
@@ -2,11 +2,10 @@
|
|
2 |
<p>
|
3 |
<?php
|
4 |
echo sprintf( __(
|
5 |
-
|
6 |
-
|
7 |
-
|
8 |
-
|
9 |
-
'<p><a href="%1$s" target="_blank"><strong>Get the latest version Now</strong></a>.', 'wp-staging'), 'https://wp-staging.com', get_bloginfo( 'version' )
|
10 |
);
|
11 |
?>
|
12 |
</p>
|
2 |
<p>
|
3 |
<?php
|
4 |
echo sprintf( __(
|
5 |
+
'Your version of WP Staging has not been tested with WordPress %2$s.' .
|
6 |
+
'<br/><br/>WP STAGING has an enterprise-level quality control that performs a compatibility audit on every new WordPress release.' .
|
7 |
+
'<br/>We prioritize testing the Pro version of the plugin first, which receives the compatibility audit earlier than the Free version. If you are in a rush, upgrade to Pro today to get the latest version of WPSTAGING.' .
|
8 |
+
'<p><a href="%1$s" target="_blank"><strong>Get the latest version Now</strong></a>.', 'wp-staging'), 'https://wp-staging.com', get_bloginfo( 'version' )
|
|
|
9 |
);
|
10 |
?>
|
11 |
</p>
|
readme.txt
CHANGED
@@ -6,10 +6,10 @@ 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,
|
10 |
Requires at least: 3.6+
|
11 |
-
Tested up to: 5.
|
12 |
-
Stable tag: 2.7.
|
13 |
Requires PHP: 5.5
|
14 |
|
15 |
A duplicator plugin - clone/move, duplicate & migrate live websites to independent staging and development sites that are accessible by authorized users only.
|
@@ -17,18 +17,18 @@ A duplicator plugin - clone/move, duplicate & migrate live websites to independe
|
|
17 |
== Description ==
|
18 |
|
19 |
<h3>WP Staging for WordPress Migration & Cloning </h3>
|
20 |
-
This duplicator plugin allows you to create an exact copy of your entire website for staging or development purposes in seconds.
|
21 |
-
(Exact time depends on the size of your website)<br /><br />
|
22 |
It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.
|
23 |
<br /> <br />
|
24 |
-
<strong>Note: </strong> For pushing & migrating plugins and theme files to
|
25 |
<br /><br />
|
26 |
All the time-consumptive database and file copying operations are done in the background. The plugin even automatically does an entire search & replace of all serialized links and paths.
|
27 |
<br /><br />
|
28 |
-
This plugin works even on the smallest shared hosting servers.
|
29 |
<br /><br />
|
30 |
<br /><br />
|
31 |
-
WP Staging can
|
32 |
|
33 |
[youtube https://www.youtube.com/watch?v=Ye3fC6cdB3A]
|
34 |
|
@@ -36,29 +36,28 @@ WP Staging can help you to protect your website from being broken or unavailable
|
|
36 |
|
37 |
= Main Features =
|
38 |
|
|
|
39 |
* No SASS service. All data belongs to you and stays on your server.
|
40 |
-
* Easy to use!
|
41 |
* No server timeouts on huge websites or/and small hosting servers
|
42 |
-
* Staging website will be available from example.com/staging-site
|
43 |
* Very fast - Migration process takes only a few seconds or minutes, depending on the website's size and server I/O power.
|
44 |
-
* Only administrators can access the staging website. Login with the same credentials you use on your production site
|
45 |
* SEO friendly: The staging website is unavailable to search engines due to a custom login prompt and no-index header.
|
46 |
-
* The admin bar on the staging website
|
47 |
-
* All database tables
|
48 |
-
* As default the staging website will be copied into a subfolder.
|
49 |
* Extensive logging features
|
50 |
* Supports all main web servers including Apache, Nginx, and Microsoft IIS
|
51 |
* <strong>[Premium]: </strong>Choose a separate database and select a custom directory for cloning
|
52 |
* <strong>[Premium]: </strong>Make the staging website available from a subdomain like dev.example.com
|
53 |
-
* <strong>[Premium]: </strong>Push & migrate plugins and
|
54 |
-
* <strong>[Premium]: </strong>Define user roles that
|
55 |
* <strong>[Premium]: </strong>Migration and cloning of WordPress multisites
|
56 |
|
57 |
> Note: Some features are Premium. Which means you need WP Staging Pro to use those features. You can [get WP Staging Premium here](https://wp-staging.com)!
|
58 |
|
59 |
* New: Compatible with WordFence & All In One WP Security & Firewall
|
60 |
|
61 |
-
= Additional Features WP
|
62 |
|
63 |
* Cloning and migration of WordPress multisites
|
64 |
* Define a separate database and a custom directory for cloning
|
@@ -71,10 +70,10 @@ WP Staging can help you to protect your website from being broken or unavailable
|
|
71 |
1. Use WP Staging to clone a production website for staging, testing or backup purposes
|
72 |
2. Create a backup of your website
|
73 |
3. Customize theme, configuration, update or install new plugins
|
74 |
-
4. Test everything on your staging site
|
75 |
5. If everything works on the staging site start the migration and copy all modifications to your production site!
|
76 |
|
77 |
-
<h3> Why should I
|
78 |
|
79 |
Plugin updates and theme customizations should be tested on a staging platform first before they are done on your production website.
|
80 |
It's recommended having the staging platform on the same server where the production website is located to use the same hardware and software environment for your test website and to catch all possible errors during testing.
|
@@ -82,56 +81,61 @@ It's recommended having the staging platform on the same server where the produc
|
|
82 |
Before you update a plugin or going to install a new one, it is highly recommended to check out the modifications on a clone of your production website.
|
83 |
This makes sure that any modifications work on your production website without throwing unexpected errors or preventing your site from loading. Better known as the "WordPress blank page error".
|
84 |
|
85 |
-
Testing a plugin update before installing it in a
|
86 |
an up-to-date copy of your website.
|
87 |
|
88 |
-
Some
|
89 |
This is one of the main reasons why WordPress installations are often outdated, not updated at all and insecure because of this non-update behavior.
|
90 |
|
91 |
-
<strong> It's time to change this, so use "WP Staging" for cloning and migration of WordPress websites</strong>
|
92 |
|
93 |
-
<h3> Can´t I just use my local wordpress development system like xampp / lampp for testing purposes? </h3>
|
94 |
|
95 |
You can test your website locally but if your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect of your local copy is working on your production website exactly as you expect it.
|
96 |
-
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
|
97 |
-
There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local platform only.
|
98 |
|
99 |
-
This is were WP Staging jumps in... Site cloning and staging site creation simplified!
|
100 |
|
101 |
<h3>I just want to migrate the database from one installation to another</h3>
|
102 |
If you want to migrate your local database to an already existing production site you can use a tool like WP Migrate DB.
|
103 |
-
WP Staging is
|
104 |
Both tools are excellent cooperating each other.
|
105 |
|
106 |
<h3>What are the benefits compared to a plugin like Duplicator?</h3>
|
107 |
-
|
108 |
-
The downside is that
|
109 |
-
|
|
|
110 |
|
111 |
-
|
112 |
-
the Duplicator plugin! If you need all your latest production data like posts, updated plugins, theme data and styles in a testing environment than I recommend to use WP
|
113 |
|
114 |
-
= I
|
115 |
-
This plugin has been
|
116 |
-
|
|
|
|
|
|
|
|
|
117 |
|
118 |
|
119 |
= Important =
|
120 |
|
121 |
-
Permalinks are disabled on the staging
|
122 |
-
without doing changes to the .htaccess (Apache server) or nginx.conf (Nginx Server).
|
123 |
[Read here](https://wp-staging.com/docs/activate-permalinks-staging-site/ "activate permalinks on staging site") how to activate permalinks on the staging site.
|
124 |
|
|
|
125 |
|
126 |
= How to install and setup? =
|
127 |
-
Install it via the admin dashboard and to 'Plugins', click 'Add New' and search the plugins for '
|
128 |
After installation, go to the settings page 'Staging' and do your adjustments there.
|
129 |
|
130 |
|
131 |
== Frequently Asked Questions ==
|
132 |
|
133 |
-
* I can not log in to the staging site
|
134 |
-
If you are using a security plugin like All In One WP Security & Firewall you need to install the latest version of WP
|
135 |
Go to WP Staging > Settings and add the slug to the custom login page which you set up in All In One WP Security & Firewall plugin.
|
136 |
|
137 |
|
@@ -146,14 +150,14 @@ https://wp-staging.com
|
|
146 |
|
147 |
== Screenshots ==
|
148 |
|
149 |
-
1. Step 1. Create a new WordPress staging site
|
150 |
2. Step 2. Scanning your website for files and database tables
|
151 |
-
3. Step 3. Wordpress
|
152 |
-
4. Finish
|
153 |
|
154 |
== Changelog ==
|
155 |
|
156 |
-
= 2.7.
|
157 |
* New: Compatible up to WordPress 5.4.2
|
158 |
* Fix: Remove beta notice
|
159 |
* Fix: Error if views are cloned
|
@@ -163,6 +167,9 @@ https://wp-staging.com
|
|
163 |
* Fix: Fix progress bar when certains steps are skipped
|
164 |
* Fix: Change german translation for REPORT ISSUE
|
165 |
|
|
|
|
|
|
|
166 |
= 2.7.3 =
|
167 |
* New: Compatible up to WordPress 5.4.1
|
168 |
* New: Allow filtering of staging site title
|
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: backup, staging, duplication, clone, migration
|
10 |
Requires at least: 3.6+
|
11 |
+
Tested up to: 5.5
|
12 |
+
Stable tag: 2.7.5
|
13 |
Requires PHP: 5.5
|
14 |
|
15 |
A duplicator plugin - clone/move, duplicate & migrate live websites to independent staging and development sites that are accessible by authorized users only.
|
17 |
== Description ==
|
18 |
|
19 |
<h3>WP Staging for WordPress Migration & Cloning </h3>
|
20 |
+
This duplicator plugin allows you to create an exact copy of your entire website for staging, backup or development purposes in seconds.
|
21 |
+
(Exact backup time depends on the size of your website)<br /><br />
|
22 |
It creates a clone of your website into a subfolder of your main WordPress installation including an entire copy of your database.
|
23 |
<br /> <br />
|
24 |
+
<strong>Note: </strong> For pushing & migrating plugins and theme files to production site, check out the pro edition [https://wp-staging.com/](https://wp-staging.com/ "WP Staging Pro")
|
25 |
<br /><br />
|
26 |
All the time-consumptive database and file copying operations are done in the background. The plugin even automatically does an entire search & replace of all serialized links and paths.
|
27 |
<br /><br />
|
28 |
+
This staging and backup plugin works even on the smallest shared hosting servers.
|
29 |
<br /><br />
|
30 |
<br /><br />
|
31 |
+
WP Staging can protect your website from being broken or unavailable because of installing untested plugin updates!
|
32 |
|
33 |
[youtube https://www.youtube.com/watch?v=Ye3fC6cdB3A]
|
34 |
|
36 |
|
37 |
= Main Features =
|
38 |
|
39 |
+
* WP STAGING creates the staging website into a subfolder of your production site like example.com/staging-site.
|
40 |
* No SASS service. All data belongs to you and stays on your server.
|
41 |
+
* Easy to use! Create a clone of your site by clicking one button "CREATE NEW STAGING SITE".
|
42 |
* No server timeouts on huge websites or/and small hosting servers
|
|
|
43 |
* Very fast - Migration process takes only a few seconds or minutes, depending on the website's size and server I/O power.
|
44 |
+
* Only administrators can access the staging website. (Login with the same credentials you use on your production site)
|
45 |
* SEO friendly: The staging website is unavailable to search engines due to a custom login prompt and no-index header.
|
46 |
+
* The admin bar on the staging website is orange colored and shows clearly when you work on the staging site.
|
47 |
+
* All duplicated database tables get a new prefix beginning with wpstg(int)_.
|
|
|
48 |
* Extensive logging features
|
49 |
* Supports all main web servers including Apache, Nginx, and Microsoft IIS
|
50 |
* <strong>[Premium]: </strong>Choose a separate database and select a custom directory for cloning
|
51 |
* <strong>[Premium]: </strong>Make the staging website available from a subdomain like dev.example.com
|
52 |
+
* <strong>[Premium]: </strong>Push & migrate entire staging site inc. all plugins, themes, and media files to production website.
|
53 |
+
* <strong>[Premium]: </strong>Define user roles that get access to the staging site only. For instance, clients or external developers.
|
54 |
* <strong>[Premium]: </strong>Migration and cloning of WordPress multisites
|
55 |
|
56 |
> Note: Some features are Premium. Which means you need WP Staging Pro to use those features. You can [get WP Staging Premium here](https://wp-staging.com)!
|
57 |
|
58 |
* New: Compatible with WordFence & All In One WP Security & Firewall
|
59 |
|
60 |
+
= Additional Features WP STAGING PRO Edition =
|
61 |
|
62 |
* Cloning and migration of WordPress multisites
|
63 |
* Define a separate database and a custom directory for cloning
|
70 |
1. Use WP Staging to clone a production website for staging, testing or backup purposes
|
71 |
2. Create a backup of your website
|
72 |
3. Customize theme, configuration, update or install new plugins
|
73 |
+
4. Test everything on your staging site and keep a backup of the original site
|
74 |
5. If everything works on the staging site start the migration and copy all modifications to your production site!
|
75 |
|
76 |
+
<h3> Why should I Use a Staging Website? </h3>
|
77 |
|
78 |
Plugin updates and theme customizations should be tested on a staging platform first before they are done on your production website.
|
79 |
It's recommended having the staging platform on the same server where the production website is located to use the same hardware and software environment for your test website and to catch all possible errors during testing.
|
81 |
Before you update a plugin or going to install a new one, it is highly recommended to check out the modifications on a clone of your production website.
|
82 |
This makes sure that any modifications work on your production website without throwing unexpected errors or preventing your site from loading. Better known as the "WordPress blank page error".
|
83 |
|
84 |
+
Testing a plugin update before installing it in a production environment isn´t done very often by most users because existing staging solutions are too complex and need a lot of time to create a
|
85 |
an up-to-date copy of your website.
|
86 |
|
87 |
+
Some of you might be afraid of installing plugins updates because Your follow the rule "never touch a running system" with having in mind that untested updates are increasing the risk of breaking Your site.
|
88 |
This is one of the main reasons why WordPress installations are often outdated, not updated at all and insecure because of this non-update behavior.
|
89 |
|
90 |
+
<strong> It's time to change this, so use "WP Staging" for cloning, backup and migration of WordPress websites</strong>
|
91 |
|
92 |
+
<h3> Can´t I just use my local wordpress development system like xampp / lampp for testing and backup purposes? </h3>
|
93 |
|
94 |
You can test your website locally but if your local hardware and software environment is not a 100% exact clone of your production server there is NO guarantee that every aspect of your local copy is working on your production website exactly as you expect it.
|
95 |
+
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 CPU performance can lead to unexpected results on your production website.
|
96 |
+
There are dozens of other possible cause of failure which can not be handled well when you are testing your changes on a local platform only without creating a backup staging site.
|
97 |
|
98 |
+
This is were WP Staging jumps in... Site cloning, backup and staging site creation simplified!
|
99 |
|
100 |
<h3>I just want to migrate the database from one installation to another</h3>
|
101 |
If you want to migrate your local database to an already existing production site you can use a tool like WP Migrate DB.
|
102 |
+
WP Staging is intended for creating a staging site with latest data from your production site or creating a backup of it. So it goes the opposite way of WP Migrate DB.
|
103 |
Both tools are excellent cooperating each other.
|
104 |
|
105 |
<h3>What are the benefits compared to a plugin like Duplicator?</h3>
|
106 |
+
I really the Duplicator plugin. It is a great tool for migrating from a development site to production one or from production site to development one and a good tool to create a backup of your WordPress website.
|
107 |
+
The downside is that before you can even create an export or backup file with Duplicator a lot of adjustments, manually interventions and requirements are needed before you can start the backup process.
|
108 |
+
Duplicator also needs some skills to be able to create a backup and development/staging site, where WP Staging does not need more than a click from you.
|
109 |
+
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.
|
110 |
|
111 |
+
If you have created a local or web-hosted development site and you need to migrate this site the first time to your production domain than you are doing nothing wrong with using
|
112 |
+
the Duplicator plugin! If you need all your latest production data like posts, updated plugins, theme data and styles in a testing environment or want to create a quick backup before testing out omething than I recommend to use WP STAGING instead!
|
113 |
|
114 |
+
= Can I give You some Feedback? =
|
115 |
+
This plugin has been created in thousands of hours and works even with the smallest shared web hosting package.
|
116 |
+
We also use enterprise level approved testing coding structures to make sure that the plugin runs rock solid on your system.
|
117 |
+
If you are a developer you will probably like to hear that we use Codeception and PHPUnit for our software.
|
118 |
+
|
119 |
+
As there are infinite numbers of possible server constellations it still might happen that something does not work for you 100%. In that case,
|
120 |
+
please open a [support request](https://wp-staging.com/support/ "support request") and describe your issue.
|
121 |
|
122 |
|
123 |
= Important =
|
124 |
|
125 |
+
Permalinks are disabled on the staging / backup site after first time cloning / backup creation
|
|
|
126 |
[Read here](https://wp-staging.com/docs/activate-permalinks-staging-site/ "activate permalinks on staging site") how to activate permalinks on the staging site.
|
127 |
|
128 |
+
|
129 |
|
130 |
= How to install and setup? =
|
131 |
+
Install it via the admin dashboard and to 'Plugins', click 'Add New' and search the plugins for 'WP STAGING'. Install the plugin with 'Install Now'.
|
132 |
After installation, go to the settings page 'Staging' and do your adjustments there.
|
133 |
|
134 |
|
135 |
== Frequently Asked Questions ==
|
136 |
|
137 |
+
* I can not log in to the staging / backup site
|
138 |
+
If you are using a security plugin like All In One WP Security & Firewall you need to install the latest version of WP STAGING to access your cloned backup site.
|
139 |
Go to WP Staging > Settings and add the slug to the custom login page which you set up in All In One WP Security & Firewall plugin.
|
140 |
|
141 |
|
150 |
|
151 |
== Screenshots ==
|
152 |
|
153 |
+
1. Step 1. Create a new WordPress staging / backup site
|
154 |
2. Step 2. Scanning your website for files and database tables
|
155 |
+
3. Step 3. Wordpress staging site creation in progress
|
156 |
+
4. Finish - Access your backup / staging site
|
157 |
|
158 |
== Changelog ==
|
159 |
|
160 |
+
= 2.7.5 =
|
161 |
* New: Compatible up to WordPress 5.4.2
|
162 |
* Fix: Remove beta notice
|
163 |
* Fix: Error if views are cloned
|
167 |
* Fix: Fix progress bar when certains steps are skipped
|
168 |
* Fix: Change german translation for REPORT ISSUE
|
169 |
|
170 |
+
= 2.7.4 =
|
171 |
+
SKIP VERSION
|
172 |
+
|
173 |
= 2.7.3 =
|
174 |
* New: Compatible up to WordPress 5.4.1
|
175 |
* New: Allow filtering of staging site title
|
vendor/autoload.php
CHANGED
@@ -4,4 +4,4 @@
|
|
4 |
|
5 |
require_once __DIR__ . '/composer/autoload_real.php';
|
6 |
|
7 |
-
return
|
4 |
|
5 |
require_once __DIR__ . '/composer/autoload_real.php';
|
6 |
|
7 |
+
return ComposerAutoloaderInit33d851adfa7d97fe992146265e7c3b4d::getLoader();
|
vendor/composer/autoload_real.php
CHANGED
@@ -2,7 +2,7 @@
|
|
2 |
|
3 |
// autoload_real.php @generated by Composer
|
4 |
|
5 |
-
class
|
6 |
{
|
7 |
private static $loader;
|
8 |
|
@@ -22,15 +22,15 @@ class ComposerAutoloaderInitb9bb895dff0feeace986bca17666d0d0
|
|
22 |
return self::$loader;
|
23 |
}
|
24 |
|
25 |
-
spl_autoload_register(array('
|
26 |
self::$loader = $loader = new \Composer\Autoload\ClassLoader();
|
27 |
-
spl_autoload_unregister(array('
|
28 |
|
29 |
$useStaticLoader = PHP_VERSION_ID >= 50600 && !defined('HHVM_VERSION') && (!function_exists('zend_loader_file_encoded') || !zend_loader_file_encoded());
|
30 |
if ($useStaticLoader) {
|
31 |
require_once __DIR__ . '/autoload_static.php';
|
32 |
|
33 |
-
call_user_func(\Composer\Autoload\
|
34 |
} else {
|
35 |
$map = require __DIR__ . '/autoload_namespaces.php';
|
36 |
foreach ($map as $namespace => $path) {
|
2 |
|
3 |
// autoload_real.php @generated by Composer
|
4 |
|
5 |
+
class ComposerAutoloaderInit33d851adfa7d97fe992146265e7c3b4d
|
6 |
{
|
7 |
private static $loader;
|
8 |
|
22 |
return self::$loader;
|
23 |
}
|
24 |
|
25 |
+
spl_autoload_register(array('ComposerAutoloaderInit33d851adfa7d97fe992146265e7c3b4d', 'loadClassLoader'), true, true);
|
26 |
self::$loader = $loader = new \Composer\Autoload\ClassLoader();
|
27 |
+
spl_autoload_unregister(array('ComposerAutoloaderInit33d851adfa7d97fe992146265e7c3b4d', 'loadClassLoader'));
|
28 |
|
29 |
$useStaticLoader = PHP_VERSION_ID >= 50600 && !defined('HHVM_VERSION') && (!function_exists('zend_loader_file_encoded') || !zend_loader_file_encoded());
|
30 |
if ($useStaticLoader) {
|
31 |
require_once __DIR__ . '/autoload_static.php';
|
32 |
|
33 |
+
call_user_func(\Composer\Autoload\ComposerStaticInit33d851adfa7d97fe992146265e7c3b4d::getInitializer($loader));
|
34 |
} else {
|
35 |
$map = require __DIR__ . '/autoload_namespaces.php';
|
36 |
foreach ($map as $namespace => $path) {
|
vendor/composer/autoload_static.php
CHANGED
@@ -4,7 +4,7 @@
|
|
4 |
|
5 |
namespace Composer\Autoload;
|
6 |
|
7 |
-
class
|
8 |
{
|
9 |
public static $prefixLengthsPsr4 = array (
|
10 |
'W' =>
|
@@ -36,8 +36,8 @@ class ComposerStaticInitb9bb895dff0feeace986bca17666d0d0
|
|
36 |
public static function getInitializer(ClassLoader $loader)
|
37 |
{
|
38 |
return \Closure::bind(function () use ($loader) {
|
39 |
-
$loader->prefixLengthsPsr4 =
|
40 |
-
$loader->prefixDirsPsr4 =
|
41 |
|
42 |
}, null, ClassLoader::class);
|
43 |
}
|
4 |
|
5 |
namespace Composer\Autoload;
|
6 |
|
7 |
+
class ComposerStaticInit33d851adfa7d97fe992146265e7c3b4d
|
8 |
{
|
9 |
public static $prefixLengthsPsr4 = array (
|
10 |
'W' =>
|
36 |
public static function getInitializer(ClassLoader $loader)
|
37 |
{
|
38 |
return \Closure::bind(function () use ($loader) {
|
39 |
+
$loader->prefixLengthsPsr4 = ComposerStaticInit33d851adfa7d97fe992146265e7c3b4d::$prefixLengthsPsr4;
|
40 |
+
$loader->prefixDirsPsr4 = ComposerStaticInit33d851adfa7d97fe992146265e7c3b4d::$prefixDirsPsr4;
|
41 |
|
42 |
}, null, ClassLoader::class);
|
43 |
}
|
wp-staging.php
CHANGED
@@ -7,7 +7,7 @@
|
|
7 |
* Author: WP-Staging
|
8 |
* Author URI: https://wp-staging.com
|
9 |
* Contributors: ReneHermi, ilgityildirim
|
10 |
-
* Version: 2.7.
|
11 |
* Text Domain: wp-staging
|
12 |
* Domain Path: /languages/
|
13 |
*
|
@@ -39,7 +39,7 @@ if (!defined('WPSTG_PLUGIN_SLUG')) {
|
|
39 |
|
40 |
// Plugin Version
|
41 |
if (!defined('WPSTG_VERSION')) {
|
42 |
-
define('WPSTG_VERSION', '2.7.
|
43 |
}
|
44 |
|
45 |
// Compatible up to WordPress Version
|
7 |
* Author: WP-Staging
|
8 |
* Author URI: https://wp-staging.com
|
9 |
* Contributors: ReneHermi, ilgityildirim
|
10 |
+
* Version: 2.7.5
|
11 |
* Text Domain: wp-staging
|
12 |
* Domain Path: /languages/
|
13 |
*
|
39 |
|
40 |
// Plugin Version
|
41 |
if (!defined('WPSTG_VERSION')) {
|
42 |
+
define('WPSTG_VERSION', '2.7.5');
|
43 |
}
|
44 |
|
45 |
// Compatible up to WordPress Version
|