Intermittent Issues - Not Copying Content For Some Sites

We seem to be experiencing irregular issues in regards to the WPMU Multisite Content Copier (https://premium.wpmudev.org/project/multisite-content-copier/). It doesn't copy content to a random handful of sites on our network.

When we try and copy a page or posts across all sites or even select sites on our Multisite Network, it appears to work on the frontend. But the actual content doesn't copy.

Replicate Issue:
1.) Navigate to Content Copier and select action, typically Pages or Posts
2.) Select Source Site (I've tried both by Blog ID and Site URL)
3.) Add Items To List
4.) Select Destination All Sites or Individual Sites
5.) Finishes with a "Your selected items have been copied." message. But checking some of the sites, the content did not actually copy.

Our Multisite Network has about 330 sites, so far we have a list of about a dozen websites that we've identified that refuse to accept the copied content for unknown reasons? This list can be provided in a private message or something.

Nothing peculiar pops up in the WordPress Debug Log, Apache Error Log or MySQL Error/General Logs. I've boosted the PHP memory limit and execution time thinking it may be timing out or exhausting memory but the dozen websites are sporadic throughout the network (blog ID #27, blog ID #99, etc...) and not toward the end of the list. There is nothing in the nginx logs either (which wouldn't make much sense anyway) [see below].

Our network operates via three virtual machines. Traffic is routed through an Nginx reverse proxy that connects to the web server which connects to the data server.
All in the Microsoft Azure Cloud running:
CentOS 7.2.1511
MySQL 5.6.28
PHP 5.4.16,
Nginx 1.6.3/Apache 2.4.6

Trying to provide whatever details may be helpful. Basically, we're stumped as to why some sites just don't work. Any help would be greatly appreciated, thank you!

  • joshuah

    Deactivated both Comet Cache & WordFence, the issue still persists. Specifically: I attempted copying content from source blog id #429 to blog id #99.

    define('WP_DEBUG', true);
    define('SAVEQUERIES', true);
    define( 'SCRIPT_DEBUG', true );
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', true);

    There were no errors displayed in the rendered HTML.

    A debug.log doesn't appear to be generating within the /wp-content/ folder like it previously used to do with debug mode enabled. Which is odd?

    The server is configured with proper file/folder permissions and the correct user:groups. Only thing different from a typical WordPress install is the /wp-content/uploads/ and /wp-content/cache/ are symbolic links to a separate storage drive.

    /var/log/httpd/error_log only contains enqueue, register style & undefined index errors, unrelated to this issue:

    [Fri Apr 01 13:24:13.050060 2016] [:error] [pid 3603] [client 192.168.21.6:43205] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:17.624499 2016] [:error] [pid 3500] [client 192.168.21.6:43221] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:17.692369 2016] [:error] [pid 3632] [client 192.168.21.6:43220] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:19.148054 2016] [:error] [pid 3792] [client 192.168.21.6:43229] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:20.241231 2016] [:error] [pid 3500] [client 192.168.21.6:43230] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:20.825512 2016] [:error] [pid 3731] [client 192.168.21.6:43233] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:21.890742 2016] [:error] [pid 3603] [client 192.168.21.6:43238] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:23.469808 2016] [:error] [pid 3792] [client 192.168.21.6:43250] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:23.470171 2016] [:error] [pid 3792] [client 192.168.21.6:43250] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:23.692120 2016] [:error] [pid 3603] [client 192.168.21.6:43249] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:23.910899 2016] [:error] [pid 3731] [client 192.168.21.6:43253] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:23.911321 2016] [:error] [pid 3731] [client 192.168.21.6:43253] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:24.312988 2016] [:error] [pid 3792] [client 192.168.21.6:43250] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:26.085131 2016] [:error] [pid 3704] [client 192.168.21.6:43255] PHP Notice:  Undefined index: second-center-fax in /var/www/html/public_html/wp-content/themes/{theme}/header.php on line 84, referer: {domain}
    [Fri Apr 01 13:24:27.802679 2016] [:error] [pid 3632] [client 192.168.21.6:43264] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:29.322880 2016] [:error] [pid 3504] [client 192.168.21.6:43265] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:29.323353 2016] [:error] [pid 3504] [client 192.168.21.6:43265] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:29.729297 2016] [:error] [pid 3704] [client 192.168.21.6:43268] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:29.729726 2016] [:error] [pid 3704] [client 192.168.21.6:43268] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:29.977709 2016] [:error] [pid 3704] [client 192.168.21.6:43268] PHP Notice:  Undefined index: footer-tagline in /var/www/html/public_html/wp-content/themes/{theme}/framework/classes/Utility.php on line 127
    [Fri Apr 01 13:24:32.788314 2016] [:error] [pid 3603] [client 192.168.21.6:43270] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:32.788702 2016] [:error] [pid 3603] [client 192.168.21.6:43270] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:33.645771 2016] [:error] [pid 3500] [client 192.168.21.6:43271] PHP Notice:  wp_register_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
    [Fri Apr 01 13:24:33.646179 2016] [:error] [pid 3500] [client 192.168.21.6:43271] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>login_enqueue_scripts</code> hooks. Please see <a href="https://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in /var/www/html/public_html/wp-includes/functions.php on line 3792
  • Michael Bissett

    Hey joshuah, Michael here, apologies for the delay on this one!

    I see that the Support Access has expired in the meantime, but from the sounds of it, this'll require a deeper look anyhow. Could you please send in the following via our secure contact form:

    - Mark to my attention, the subject line should contain only: ATTN: Michael Bissett
    - Do not include anything else in the subject line, doing so may delay our response due to how email filtering works.
    - Link back to this thread
    - Include WordPress network admin access details (login address, username & password)
    - Include FTP/SFTP log-in details (hostname, username & password)
    - Include the list of affected sites, and the examples, that you'd posted earlier in the support notes

    IMPORTANT: Please make sure you select "I have a different question" for your topic, so it doesn't go back to the forums - this and the subject line ensure that it gets assigned to me.

    https://premium.wpmudev.org/contact/

    Kind Regards,
    Michael

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.