Eyecool

Yes… alive and well on Github. The current version is 2.4

https://github.com/stuttter/wp-multi-network

It’s an array, which isn’t supported (yet).

Did you get it sorted out?

The default is 30 minutes, which can seem like an eternity if you’re editing the json in real time.

Hi,

I tried and tried to get your array to display.

I only use this plugin with json objects, so I figured I’d be learning something new. 1 hour later, I realize that arrays aren’t supported in the plugin yet. But, the author has indicated that he might be adding array support in the future.

All I can say is keep checking back! ??

Yes. You can but it takes two steps:

1. add this filter to your theme’s functions.php
   add_filter('widget_text', 'do_shortcode');
2. add a text widget and use your JSON Data Shortcode inside that text widget

Basically, the filter allows the shortcode to execute within the text widget. The added bonus being that you can now use any/all shortcodes inside your text widgets.

Ron, that’s it. Works perfect.

Earlier I had tried

define( 'PLUGINDIR', $_SERVER['DOCUMENT_ROOT'] . '/content/plugins' );

Which didn’t work, and quickly abandoned the idea of using PLUGINSDIR (ticket #18772)

Summary for posterity
To move /wp-content to /content define the following in wp-config.php:

define( 'WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/content' );
define( 'WP_CONTENT_URL', 'https://' . $_SERVER['HTTP_HOST'] . '/content');
define( 'PLUGINDIR', 'content/plugins' );

Mapped domains will play nice throughout the install and work flawlessly with third party plugins like, Gravity Forms, and Network plugins.

Wheeew doggie.

Thanks Ron.

I couldn’t fix the function, but when I comment out the filter, it works as it should.

if ( defined( 'DOMAIN_MAPPING' ) ) {
//	add_filter( 'plugins_url', 'domain_mapping_plugins_uri', 1 );
	add_filter( 'theme_root_uri', 'domain_mapping_themes_uri', 1 );
	add_filter( 'pre_option_siteurl', 'domain_mapping_siteurl' );

Could that be it?

That does return the correct hostname for subdomains, but mapped domains are still borked.

<?php echo plugins_url();?>

on anymapped.com still returns https://anymapped.coms

I think the culprit might be function domain_mapping_plugins_uri

Sure! There’s a lot you can do. For example, automattic uses site_id=1 for all wordpress.com blogs and site_id=2 for self-hosted .org sites that use jetpack or stats.

It’s so simple, make it a rule of thumb and you’ll never forget. (remember you only have two thumbs!)

site_id = the network
blog_id = the sites (formerly known as blogs)

That’s it!

site_id=1 and blog_id=1 <– that’s your main domain. The one you installed WordPress on. By enabling multisite, it becomes the network and the site. This only happens once.

site_id=1 and blog_id=2 <– that’s your second site.
site_id=1 and blog_id=3 <– that’s your third site.

Take a peek at your wp_blogs table. It’s a cool place! ??

Mitch, with VPS’s, you’ve got lots of options!

You could stick with apache and move mysql on to a separate VPS. Apache really does make life simple. Control panels support it, all the major caching projects (for your projects) support it and there’s tons of info on how to tweak apache and php to handle heavy traffic.

Moving to nginx means no control panel. Limited information. Limited resources. A lot more work.

If you do put mysql on its own small vps, you can optimize it too.

+1 on the WordPress side, where you can use WP Super Cache (or that other one) to plug in to a CDN. Offloading your static files to a CDN lightens the load on your apache VPS.

See, I call W3TC “the other one”, because every time I’ve tried to use it with nginx and multisite, I end up pulling my hair. I’ve never got it to work right. Apparently it’s dead simple with apache.

Plus, with nginx, you also have to install/configure and run php-fpm…. Even if you hire someone to set it all up, it’s not entirely “set and forget”.

How did you upgrade to 3.2? SVN, Automatic Upgrade (through wp-admin) or manual ftp?

Did you back everything up? If you haven’t, back up now!

Depending on how you upgraded, I might try re-upgrading again. On most of my multisite upgrades to 3.2, it upgraded the database (and I got an ‘upgrading database’ message). On a few, I didn’t see that message and a few wonky things happened.

No problem Mitch!

There are all sorts of tips and tricks on nginx’s official website. Not sure if you’d been there before, but it never hurts to go straight to the source.

In regard to your questions, ideally you want to set up separate .conf files for each site. They usually go in the /sites-enabled directory, depending on which OS and how you installed nginx. Using your example, I do mine like this:
domain1.tld.conf
domain2.tld.conf
domain3.tld.conf

https://wiki.nginx.org/Wordpress

https://kbeezie.com/view/caching-wordpress/3/

You need to use try_files in your location block for security, performance and simplicity.

Here are two great resources: