This page should hopefully help out with the most common questions people have. I will be adding to this page as time goes on. If you don’t find answers here or in the readme, please feel free to ask questions. 
- Are my plugins compatible with Virtual Multiblog?
- Why are all of the blog addresses showing the same blog?
- Okay, I’ve made a directory for a second blog. Now what do I put in it?
- Does Virtual Multiblog work with WordPress version x.x?
- The new version is missing the plugin folder. What happened? Do I still need it?
- Can the blogs have different themes and plugins?
- What is a “symbolic link” (symlink) and how do I make one?
- I’ve redirected different domains to my site, and set up the config files, but the domains all show the same blog. What’s going wrong?
- How do I upgrade from version 2.1 to version 2.2?
- Is there a way to make it so that when you log on to one blog you’re logged on to them all?
- Q: Are my plugins compatible with Virtual Multiblog?
-
A: Almost all plugins are completely compatible with this system. The only known exceptions are plugins that alter the .htaccess file; this mostly comprises caching plugins such as WP Super Cache.
- Q: Why are all of the blog addresses showing the same blog?
-
A: Most likely, the system can’t figure out the VUSER for some reason. When that happens, it uses the autoconfig info, or if you’ve set up a $vusers[] list, the first entry on that list. To confirm that it’s just defaulting to the first thing on $vusers[], move something else to the top of the list.
Similar problems can be caused if a config file has an incorrect name, so check that as well.
- Q: Okay, I’ve made a folder for a second blog. Now what do I put in it?
-
A: Nothing. In fact, get rid of the folder. If you want a “virtual” blog in a subdirectory, that subdirectory isn’t going to actually be a folder, it’s going to be a symbolic link. (See more on Symbolic Links.)
If you’re making a virtual blog in a subdomain (e.g. newblog.example.com ) you don’t even need the symlink. Simply point the subdomain to the same location as your primary domain.
The whole point of this exercise is that all your blogs will run off a single set of WordPress files. You should never have to have multiple copies of the files in different places.
- Q: Does Virtual Multiblog work with WordPress version x.x?
-
A: As of this writing, Virtual Multiblog 2.6 has been tested through WordPress 2.8. Because of the nature of the VMB system, I do not anticipate basic functionality breaking in future versions, unless WordPress radically changes the way it works.
Although people tend to refer to VMB as a “plugin” for WordPress, it really isn’t: Virtual Multiblog doesn’t run on top of WordPress, WordPress runs on top of Virtual Multiblog! (This is why I consistently refer to it as a “system” rather than a “plugin”.) Because of this, there is very little in the basic function that depends on how WordPress works. That makes it pretty future proof.
It does have some “plugin-like” functions that are more dependent on WordPress, and thus may change or break over time. At this time that code adds no major functionality beyond a diagnostic page in Admin.
- Q: The new version is missing the plugin folder. What happened? Do I still need it?
-
A: Sorry, that’s two questions. The plugin is no longer needed as of VMB version 2.4. Before upgrading, you should deactivate the “Virtual Multiblog Support” plugin in all blogs. The easiest way to do that is to delete the file. The functions formerly handled by the plugin are still there; I just got rid of the plugin, which was acting as a bootstrap.
- Q: Can the blogs have different themes and plugins?
-
A: Yes. Each blog runs as a completely separate install of WordPress. As such, they have separate Admin sections, separate Users, and separate settings (including which themes or plugins are active).
- Q: What is a “symbolic link” (symlink) and how do I make one?
-
A: A symbolic link, or “symlink” is a type of shortcut originating in Unix-like operating systems. Basically, it is a second representation of a particular file (or in this case, directory). A symbolic link basically acts as though it is the target file or folder. In the case of this system, you can put WordPress files in one folder and make a symlink pointing to that first folder. The symlink acts as a second folder that has all the contents of the original.
As for making them, that’s a huge topic, and too big for this page. It totally depends on your system, your OS, settings within your OS, and so forth, though I can say that they can be made in Unix or Linux; I have personally made them in Mac OS X (using Cocktail); and I am informed by commenters that you can make them in Windows.
If you don’t know much about them, it might be best to ask your hosting company to make them for you. That’s what I do.
For further information, you might find the page at Wikipedia useful.
- Q: I’ve redirected different domains to my site, and set up the config files, but the domains all show the same blog. What’s going wrong?
-
A: It could be many things. First off, a URL redirect will not work; the domains must all point directly to the server (or name server). Next, the server must have those domains pointing to the same directory with the install of WordPress. (In Apache the server admin would most likely set up “Virtual Hosts” that all point to the same place.)
A bit of info that might help with troubleshooting: if the system can’t figure out what VUSER to use, it will try to use the default. (If you’ve set up the
$vusers[]list, the default is the first on the list.) Thus, problems determining VUSER can result in different virtual blogs displaying the same content. - Q: How do I upgrade to a new version?
-
Step 1: Set your configuration files aside.
Step 2: Delete the existing
/wp-content/multiblog/folder. Replace it with the new copy. Put your existing config files back into the/config/folder.Step 3: In the root WordPress folder, replace the old wp-config.php with the new one.
Step 4: If you have the
multiblog-supportplugin installed in your plugins folder, delete it. You don’t need it anymore.NOTE: If you previously had to do strange things to your
$vusers[]or table-prefixes relating to double-slashes, I think that’s fixed as of in 2.2. So if you’re having trouble, you may try undoing whatever you had to tweak in the old version. (I was never able to reproduce that error, so I don’t know what exactly caused it, but I’m hearing that it’s fixed now.) - Q: Is there a way to make it so that when you log on to one blog you’re logged on to them all?
-
A: Not at present. Somewhere down the line I would like to implement this, but I don’t expect it any time soon.
86 Comments
Pages: « 1 2 3 4 [5] Show All
UPDATE: line 897 in pluggable.php is a 302 header redirect part of the the function wp_redirect.php. I should also point out that the blog works fine when I use the original WordPress wp-config.php, but the above issue happens only when VMB is enabled with the VMB wp-config.php file. (wp-config.php File is in the root, but WP install is in /blog. I have added the correct path info as per your instructions). Thanks.
As you may have guessed, the “headers already sent” error is caused by the “Hello filename” string you’re echoing. PHP throws that error if you try to set headers when something has already been sent to the browser — headers have to be first. So by the time pluggable.php tries to set headers you’ve already sent the “Hello” and it bugs out.
Beyond that I’m not sure what might be causing the redirect problem, other than something wrong with the config file.
Well, yes, the echo string is only for troubleshooting to see which page is the one that it stops/bugs at. The header error then tells me what is the next file in the chain. After that, I put the echo string in the next file to troubleshoot & so on.
However the “Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects. The webpage at http://wealthandsuccess.org/wp-admin/install.php has resulted in too many redirects.” error only occurs through the use of the VMB version of wp-config.php. When I replace it with the original wordpress wp-config.php file, my blog works fine (abeit not a multi-site blog). When I put the VMB file back, the error occurs again.
The only line I have changed in the wp-config.php is the following:
//define( ‘VMB_CONFIG_DIR’, ‘../../../config/’ ); //=>Not Working
//define( ‘VMB_CONFIG_DIR’, ‘/home/content/f/o/r/forcomcanada/html/config/’ ); //=>Works.
define( ‘VMB_CONFIG_DIR’, ‘config’ ); //=>Works.
My structure is:
Root
|_index.php (=>contains require(‘./blog/wp-blog-header.php’);)
|_config (VMB config folder)
|_blog
|_wp-content
|_multiblog
Thanks.
Sorry, the spaces were removed when I posted. Structure=:
Root
..|_index.php (=>contains require(‘./blog/wp-blog-header.php’);)
..|_config (VMB config folder/directory)
..|_blog
….|_wp-content
……|_multiblog
Thanks.
Is it possible to domain map the virtual blogs as well as assign specific IP:s to specific blogs?
Blogs can be on different domains if the different domains all point to the same directory on your server.
I don’t know about mapping different IP addresses, but I think if they’re all pointing to that same directory, it should work.
Pages: « 1 2 3 4 [5] Show All