MagicStick

Thanks dan. I really appreciate your post. To answer your questions:

1. To remove the error add the following temporary hacky fix to your functions.php file.

function remove_annoying_subdomain_message(){
    ?>
    <script>
        jQuery(document).ready(function($) {
            target = jQuery("div.error p:contains('Subdomain configurations')").parent().hide();
        });
    </script>

    <?php
}
add_action('admin_footer', 'remove_annoying_subdomain_message');

2. There have been no changes to the plugin core at all but I’ve had a few bug reports that turned out were because of subdomain installations. My thoughts on this were to add a notice to indicate subdomain issues. It’s interesting to me that you are not having issues! I know for a fact that the there would be issues with Images copying over in the post content? Have you experienced this? Perhaps in light of your comments I might pull back on the severity of my wording in the error message in a future release and will definitely add a button to dismiss the message. That was a slip up on my part. Sorry about that.

• This reply was modified 9 years, 7 months ago by MagicStick.

Fixed in 0.9.3 🙂

Hi Adrian. I’m about to release an update which supports wordpress’ new WP_Site_Query() class.

https://developer.wordpress.org/reference/functions/get_sites/

I think this will solve your problem as the limit $args['number'] on the query is defaulted to null (no limit). After my update can you have a wee check and confirm for me?

Many thanks.

Mario

can someone confirm to me if these PHP warnings disappeared for you in v0.9.2? Thanks!

Hi aotyehel. Sorry for the late reply. I’ve been up to my eyes in it!

You can achieve this by adding the following code into your functions.php file:

PLEASE NOTE: In order for this to work you have to have the default destination post status set to publish. I have added the code in the snippet below to auto set this ‘publish’ behaviour:

function get_published_date($mpd_process_info){

  $mpd_process_info['post_date'] = get_post_field('post_date', $mpd_process_info['source_id']);
 
  return $mpd_process_info;
}

add_filter('mpd_source_data', 'get_published_date');

function set_published_date($mdp_post, $mpd_process_info){

  $mdp_post['post_date'] = $mpd_process_info['post_date'];
  $mdp_post['post_status'] = 'publish';
 
  return $mdp_post;

}

add_filter('mpd_setup_destination_data', 'set_published_date', 10,2);

hey joedev91. Thanks for looking into that. I’ll include your improvement in a future update! Thanks!

• This reply was modified 9 years, 8 months ago by MagicStick.

Hi AlpDmr. Unfortunately WooCommerce uses a system out-with WordPress’ core database tables so this is what is causing the issue. My plugin is fully extendable so hoping someone might develop an addon to support WooCommerce one day!

With regard to your default post status, yes you can set the default status in the settings page 🙂

Ah. There may be further configuration on the network required. If you go into the media library of the destination site you might see the images there but my guess is that the file size says 0bytes? If so It will be restrictions on your host and would again say to speak to them 🙁 sorry man.