All-in-One WP Migration - Version 5.55

Version Description

  • Fix an issue with resolving URL on export/import when using non-blocking streams client
Download this release

Release Info

Developer yani.iliev
Plugin Icon 128x128 All-in-One WP Migration
Version 5.55
Comparing to
See all releases

Code changes from version 5.54 to 5.55

all-in-one-wp-migration.php CHANGED
@@ -5,7 +5,7 @@
5
  * Description: Migration tool for all your blog data. Import or Export your blog content with a single click.
6
  * Author: ServMask
7
  * Author URI: https://servmask.com/
8
- * Version: 5.54
9
  * Text Domain: all-in-one-wp-migration
10
  * Domain Path: /languages
11
  * Network: True
5
  * Description: Migration tool for all your blog data. Import or Export your blog content with a single click.
6
  * Author: ServMask
7
  * Author URI: https://servmask.com/
8
+ * Version: 5.55
9
  * Text Domain: all-in-one-wp-migration
10
  * Domain Path: /languages
11
  * Network: True
constants.php CHANGED
@@ -38,7 +38,7 @@ if ( function_exists( 'gethostname' ) && in_array( gethostname(), $local ) ) {
38
  // ==================
39
  // = Plugin Version =
40
  // ==================
41
- define( 'AI1WM_VERSION', '5.54' );
42
 
43
  // ===============
44
  // = Plugin Name =
38
  // ==================
39
  // = Plugin Version =
40
  // ==================
41
+ define( 'AI1WM_VERSION', '5.55' );
42
 
43
  // ===============
44
  // = Plugin Name =
lib/model/http/class-ai1wm-http-stream.php CHANGED
@@ -98,6 +98,10 @@ class Ai1wm_Http_Stream extends Ai1wm_Http_Abstract {
98
  fread( $handle, 1024 );
99
  } else {
100
  stream_set_blocking( $handle, 0 );
 
 
 
 
101
  }
102
 
103
  // Close stream handle
98
  fread( $handle, 1024 );
99
  } else {
100
  stream_set_blocking( $handle, 0 );
101
+ // What we observed is that when the stream is non-blocking, it takes time for the webserver to start a new php thread.
102
+ // By sleeping for 3s, we give some time for the webserver to start a new php process to process the request.
103
+ // This is a temporary solution and a new one will be addressed in WM-651
104
+ sleep( 3 );
105
  }
106
 
107
  // Close stream handle
lib/view/assets/javascript/import.min.js CHANGED
@@ -2721,13 +2721,74 @@
2721
  /***/ function(module, exports) {
2722
 
2723
  // shim for using process in browser
2724
-
2725
  var process = module.exports = {};
2726
 
2727
- // cached from whatever global is present so that test runners that stub it don't break things.
2728
- var cachedSetTimeout = setTimeout;
2729
- var cachedClearTimeout = clearTimeout;
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2730
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2731
  var queue = [];
2732
  var draining = false;
2733
  var currentQueue;
@@ -2752,7 +2813,7 @@
2752
  if (draining) {
2753
  return;
2754
  }
2755
- var timeout = cachedSetTimeout(cleanUpNextTick);
2756
  draining = true;
2757
 
2758
  var len = queue.length;
@@ -2769,7 +2830,7 @@
2769
  }
2770
  currentQueue = null;
2771
  draining = false;
2772
- cachedClearTimeout(timeout);
2773
  }
2774
 
2775
  process.nextTick = function (fun) {
@@ -2781,7 +2842,7 @@
2781
  }
2782
  queue.push(new Item(fun, args));
2783
  if (queue.length === 1 && !draining) {
2784
- cachedSetTimeout(drainQueue, 0);
2785
  }
2786
  };
2787
 
2721
  /***/ function(module, exports) {
2722
 
2723
  // shim for using process in browser
 
2724
  var process = module.exports = {};
2725
 
2726
+ // cached from whatever global is present so that test runners that stub it
2727
+ // don't break things. But we need to wrap it in a try catch in case it is
2728
+ // wrapped in strict mode code which doesn't define any globals. It's inside a
2729
+ // function because try/catches deoptimize in certain engines.
2730
+
2731
+ var cachedSetTimeout;
2732
+ var cachedClearTimeout;
2733
+
2734
+ (function () {
2735
+ try {
2736
+ cachedSetTimeout = setTimeout;
2737
+ } catch (e) {
2738
+ cachedSetTimeout = function () {
2739
+ throw new Error('setTimeout is not defined');
2740
+ }
2741
+ }
2742
+ try {
2743
+ cachedClearTimeout = clearTimeout;
2744
+ } catch (e) {
2745
+ cachedClearTimeout = function () {
2746
+ throw new Error('clearTimeout is not defined');
2747
+ }
2748
+ }
2749
+ } ())
2750
+ function runTimeout(fun) {
2751
+ if (cachedSetTimeout === setTimeout) {
2752
+ //normal enviroments in sane situations
2753
+ return setTimeout(fun, 0);
2754
+ }
2755
+ try {
2756
+ // when when somebody has screwed with setTimeout but no I.E. maddness
2757
+ return cachedSetTimeout(fun, 0);
2758
+ } catch(e){
2759
+ try {
2760
+ // When we are in I.E. but the script has been evaled so I.E. doesn't trust the global object when called normally
2761
+ return cachedSetTimeout.call(null, fun, 0);
2762
+ } catch(e){
2763
+ // same as above but when it's a version of I.E. that must have the global object for 'this', hopfully our context correct otherwise it will throw a global error
2764
+ return cachedSetTimeout.call(this, fun, 0);
2765
+ }
2766
+ }
2767
 
2768
+
2769
+ }
2770
+ function runClearTimeout(marker) {
2771
+ if (cachedClearTimeout === clearTimeout) {
2772
+ //normal enviroments in sane situations
2773
+ return clearTimeout(marker);
2774
+ }
2775
+ try {
2776
+ // when when somebody has screwed with setTimeout but no I.E. maddness
2777
+ return cachedClearTimeout(marker);
2778
+ } catch (e){
2779
+ try {
2780
+ // When we are in I.E. but the script has been evaled so I.E. doesn't trust the global object when called normally
2781
+ return cachedClearTimeout.call(null, marker);
2782
+ } catch (e){
2783
+ // same as above but when it's a version of I.E. that must have the global object for 'this', hopfully our context correct otherwise it will throw a global error.
2784
+ // Some versions of I.E. have different rules for clearTimeout vs setTimeout
2785
+ return cachedClearTimeout.call(this, marker);
2786
+ }
2787
+ }
2788
+
2789
+
2790
+
2791
+ }
2792
  var queue = [];
2793
  var draining = false;
2794
  var currentQueue;
2813
  if (draining) {
2814
  return;
2815
  }
2816
+ var timeout = runTimeout(cleanUpNextTick);
2817
  draining = true;
2818
 
2819
  var len = queue.length;
2830
  }
2831
  currentQueue = null;
2832
  draining = false;
2833
+ runClearTimeout(timeout);
2834
  }
2835
 
2836
  process.nextTick = function (fun) {
2842
  }
2843
  queue.push(new Item(fun, args));
2844
  if (queue.length === 1 && !draining) {
2845
+ runTimeout(drainQueue);
2846
  }
2847
  };
2848
 
readme.txt CHANGED
@@ -3,7 +3,7 @@ Contributors: yani.iliev, bangelov, pimjitsawang
3
  Tags: db migration, migration, wordpress migration, db backup, db restore, website backup, website restore, website migration, website deploy, wordpress deploy, db backup, database export, database serialization, database find replace
4
  Requires at least: 3.3
5
  Tested up to: 4.6
6
- Stable tag: 5.54
7
  License: GPLv2 or later
8
 
9
  All-in-One WP Migration is the only tool that you will ever need to migrate a WordPress site.
@@ -78,6 +78,9 @@ All in One WP Plugin is the first plugin to offer true mobile experience on Word
78
  3. Plugin Menu
79
 
80
  == Changelog ==
 
 
 
81
  = 5.54 =
82
  * Fix an issue with resolving URL on export/import
83
 
3
  Tags: db migration, migration, wordpress migration, db backup, db restore, website backup, website restore, website migration, website deploy, wordpress deploy, db backup, database export, database serialization, database find replace
4
  Requires at least: 3.3
5
  Tested up to: 4.6
6
+ Stable tag: 5.55
7
  License: GPLv2 or later
8
 
9
  All-in-One WP Migration is the only tool that you will ever need to migrate a WordPress site.
78
  3. Plugin Menu
79
 
80
  == Changelog ==
81
+ = 5.55 =
82
+ * Fix an issue with resolving URL on export/import when using non-blocking streams client
83
+
84
  = 5.54 =
85
  * Fix an issue with resolving URL on export/import
86