[Plugin: Multisite Global Search] No widget and shortcodes do not work

Hi!

Function ms_global_search_install_multisite_notice shows a notice when Multisite option isn’t activated in config.php. I have an installation with that PHP version and MySQL version and I don’t get that warning so I don’t know why you get it…sorry.

When plugin is activated but you haven’t created a network the plugin doesn’t work. Check if your config.php has this line:

define(‘MULTISITE’, true);

If MULTISITE is false or isn’t define, the plugin will be deactivated automatically.

Great and thankyou for the reply,

I now know where the problem is.

My WordPress 3.0.1 install was originally WPMU and the upgrade to WordPress 3.0 does not require that defined (if you set it, it breaks the main site).

WordPress MultiSite makes use of the is_multisite() function which always returns true for any WordPress install with MultiSite enabled (Even upgraded WPMU networks).

See the top of https://codex.www.ads-software.com/Create_A_Network:

NOTE: If you are currently running a version of WordPress MU, you do not need to complete these steps. your network is already enabled. Once you upgrade to the 3.x branch, you will be prompted to update your .htaccess rules for MultiSite.

It would be great if you are willing to fix – or – when I get time, I could submit a patch and then we can mark this forum thread as fixed!

I have just had a quick play around with the code, this is indeed a WPMU to WP3.0(MS) upgrade issue.

Using is_multisite() fixes the initial problem but then open’s up a whole can of worms.

For the main blog in the new WP3.0, the $wpdb->prefix would be ‘wp_’ for the main site on a standard install where as networks upgraded from WPMU are $wpdb->prefix = ‘wp_1_’.

I can not promise I will have time to look further into a solution over the next few days, but I will try (It should be a simple case of tracking down the relevant sections within the code and making sure the plugin knows the difference between a new WP 3.0 install and an upgraded WPMU one).

NOTE TO OTHERS…

Confirmed, this plugin works unless you have upgraded from WPMU to WP3.0 MultiSite – so this bug will not effect everyone!

I will keep this thread alive until the issue is solved (and I am willing to submit a fix – when I have some spare time).

I’d love to use this plugin, but when I remember correctly, is requires PHP5 (which I have) and MySQL5 (which I don’t have), but I’d be happy to try your patched version when it’s ready.

I had the same issue with the notice.. Would be great to track that problem with MULTISITE, anyway i’ve commented the lines for now..

Also it would be great to put the widget in another file.. I mean, i personally don’t want users to use that widget, so i delete the code manually..

Thanks for this plugin!

New version available!
Fixed some problems with upgrades from WPMU to WP3.0 Multisite.
Using is_multisite() instead of MULTISITE constant.

@deadpan110 thanks! I use get_blogs_prefix to get correctly database prefix so if you have a multisite upgraded from WPMU the function return wp_1_ instead of wp_.

@roy Sorry, I can’t write a patched version because the plugin works with some features of MySQL5.

@kevinff Sorry, this new version have the widget in the same file. I’ll put it in another file for the next update.

@kevinff Version 1.2.5 have the widget in another file