Ryan Kanner

I am also having this issue on my foundation based sites. Would be happy to provide a patch if there’s a public repo somewhere. I’ll take a quick look around for one on github. For now I have reverted to version 3.1.1

ok, but in our case we have many sites running on a multisite install, so the error log has become completely unusable for any sort of monitoring. I’m also baffled why this query would be running on the front end of the site. It shouldn’t be looking for spam comments at all.

No, I switch to the blog 2 to retrieve information from the 2, but I want the permalink for each post reference to a single blog 1.

If I am understanding correctly you want ALL of the posts that you are grabbing from blog2 to link to the SAME url which is on blog1?

If that’s the case, just store the URL you want all of the posts to go to in a variable before you use switch_to_blog() and then just use your stored url variable in place of get_page_link()

You would have to do that with a separate query, or with a static link. You could also store a link location in a variable before you use the switch_to_blog function and use that, which could make it a bit more dynamic. Though I don’t know why you would want to link your read more to something other than the post.

You should be using get_permalink() instead of get_page_link()

You can also change the default path in your config file:

define( 'UPLOADS', 'wp-content/'.'newfolder' );

This will make the default path domain.com/wp-content/newfolder

You can change the upload path on a site by site basis in the network admin. Go to your site list in the network and hit the “edit” button for that site. Now hit the “settings” tab at the top and there is a field labeled “Upload Path”. You can specify a custom path here, or leave it blank to use the default path.

You sure can. Check out the documentation on setting up a network here Just select “sub-directories” when you are doing your setup.

Sounds like you are using the switch_to_blog function within a loop. You need to switch to the blog first and then start your loop.

Your response is a little confusing. Check to see if the posts are showing up on the page that you selected as the “posts page”. You can change that setting to whatever page you want the main blog to be on.

There’s no way to automate that then if they are all different values. If the content is coming from another part of the post object you can grab that and pass it to the update_post_meta function value.

Make sure your reading settings are set up correctly. Go to settings > reading and select the page you want to use as your blog page for the “posts page” dropdown. You could also try clearing the permalinks, just go to settings > permalinks and hit save (you don’t have to change any settings). That will clear your permalinks.

do you want to add the same value to all the field for all of the posts? The best way would probably be to add it through SQL if you have access to your database / comfortable with some light scripting.

UPDATE wp_postmeta SET meta_value='newValue' WHERE meta_key='myKey';

If not I guess you could just use the update_post_meta function inside a query that returns all of the posts.

Ideally your host should be located closest to wherever most of your visitors will be coming from. That combined with a CDN would make for some pretty solid performance.

The price of hosting is going to vary a lot depending on support, features & specs. I’m not sure what kind of bandwidth / storage you would need, so it’s tough to tell. I can tell you that grid hosting will not work for you. I would definitely put it on a cloud VPS that you could bump the specs up on as the network grows, and then you won’t have to worry about moving the network at any point.

The thing that is really going to start getting costly for you is the features & support. We are currently paying 6k+ for a dedicated box at a managed WP hosting company. Most of that money is really going to support. We could get a box with the same specs for about 1.5k if it wasn’t managed.

If you are looking to keep the price down, I would look into some unmanaged solutions such as AWS or digital ocean Just be warned that these solutions will require a lot more work on your part, and some more intimate knowledge of server configurations. Though if you are looking to spend under 250/month I don’t really see another way.

Be wary of some of the managed WP hosts out there. While they are great for scaling vertically ie. millions of page views / month, they often have serious issues scaling horizontally. Our team currently manages a cluster of 500+ sites on 1 multisite install with a premium managed hosting company, and we have been having a lot of issues. We plan on moving to a cloud hosted solution fairly soon.

I can tell you that any sort of grid hosting solution will not be enough for 300 sites. However; if your sites are built well (ie. no errors, no heavy database queries, functions only running when they need to be, using a CDN) you can really get away with a pretty inexpensive rock solid solution. For you, I would definitely recommend a cloud VPS solution that allows you to scale your resources as you add sites to your network.

Whatever you do, do your research. Talk to people, ask them if they have experience hosting networks of that size, and if their solution is capable of scaling horizontally.