tzkmx

Pros:

I’m currently migrating the separated blogs from some friends to a single network, I’m talking about 20 different blogs, every one with their own plugins, themes, and contents of course. It has been a PITA for me as technical support, and they as co-managers of their own sites, trying to get them to stay updating their plugins/themes, and keeping working things.

We choose to migrate every single blog to the network, since it has been a lot easier to me and another tech-savvy friend to update the whole network at once, and avoiding bugs introduced by our users while they were trying to “fix” things and ending with a real mess. Also if a bug shows up, we can handle it only one time and not again and again for every installation.

It has helped us to reduce the amount of files in the server, and since at bluehost we are limited to 200K i-nodes in our account, that limit is important to handle.

Contras:

Sometimes it’s a bit tricky to thing how a change in a theme, for example, could hit to every other blog using that theme with undesired changes. However following best practices like making child themes instead of hacking the themes themselves, has helped even to a couple of friends to learn to make changes to their themes.

However, since the requests for support from members of our network stills coming, but we need to fix it just one time, it’s really another pro ??

It would be useful to know what errors you are getting with FeedWordPress.

Have you tried to post to the support forum of that specific plugin? Maybe they could help you to find more useful that plugin you already know.

Hi!

I’m beginning with WP multisite with subdomains too, and I’ve found easier to set up a wildcard subdomain at your hosting provider, rather than configuring every single subdomain for every new blog you want to create.

All the subdomains should point to the same location as your main site. In example, in cpanel usually the main domain points to ~/public_html/ directory, all the subdomains managed from the same network should point to the same ~/public_html/, not to the subdirectories usually cpanel makes for every subdomain.

Later, if you need a certain specific subdomain not managed by your wordpress network, you can configure that subdomain to be served from another subdirectory.