Version 0.6.0 RC1

I am pleased to announce that WP Hive version 0.6.0 is now available as a release candidate.

Download Here:

This version addresses:

*    Fully compatible with WordPress v 3.0
*    Complete Support for Subdirectory Sites
*    Premier Add-on now Available: Single Sign On

Upgrade Instructions:

Just overwrite the contents of /wp-content/plugins/wp-hive/ with the contents in the zip file.

After the upgrade, you should re-save your permalinks on your root site (wp-admin -> settings -> permalinks) and then set the permissions on .htaccess to read-only (CHMOD 555), so that it doesn’t get re-written by any other site in the hive.

Don’t forget to get your WP Hive Pro-Subscription now because it won’t stay at this price for much longer. If you have a pro subscription and would like the Single-Sign-On Add-on, please email me.

Finally, please take a look at I am offering my services and booking contracts for unique and interesting projects a couple of months in advance, so please let me know if you have an upcoming project that I could help with.


  1. Carlos Pedraza says:

    This is great news! I’m curious, before I install this new version, exactly how it will play with WP 3.0. What does “fully compatible” mean, exactly? For example, can you create a set of multiple Hive sites overseen by a single administrator, and another set of WP 3.0 sites each with their own admins?

    I’m looking forward to seeing what I’ll be gaining by sticking with wp-Hive in the face of the new WordPress.

  2. Michael says:

    Congratulations on the new release.

    And yes, I agree with Carlos. Could you please write out a very lengthy and detailed blog post explaining why Hive is still valuable, and then after that, why Hive Pro is needed, and what the differences are between all 3 levels…. starting with the base Wp3.0?

    That would be extremely helpful, to see the overall picture, and also the details about what the value is in paying the monthly or annual fee for your Pro plugin.

    Thanks very much!

  3. mmtrav says:

    Hi there, I think the above comments are really valid as well. Also, now that WP3.0 is going multisite, what’s the benefit of Hive over what is now becoming a built-in wordpress function?

  4. ikailo says:

    Yes, this WP 3.0 issue is going to be a concern, but I would not have continued working on this project if I hadn’t been convinced myself that there was enough difference to warrant the work. I trust these differences will become more apparent over time.

    First, I will clarify: WP Hive is fully compatible with WP 3.0 (NORMAL) only.
    It will *not* work if WP 3.0 is set up in multisite mode.

    As I see it, the simple difference is this:

    WP Hive is targeted to individual entities who maintain a network of sites who are administered by a fixed group of trusted individuals. Some examples of users are: companies maintaining sites for multiple brands, web service providers managing sites for multiple clients, or another group of sites all controlled by a particular entity. This type of system usually has a fixed or known number of sites.

    WordPress 3.0 Multisite appears to be targeted towards entities maintaining a network of sites administered by many anonymous individuals. Usually outside users have an option to create a new site within the network and have some level of control over it. This type of system could have an infinite or unknown number of sites.

    Of course, there are instances where the suggestion above won’t work, but I would say this is a good starting point.

    There are a multitude of differences up for discussion. I could (and will) document many of them, but also would welcome user input as well.

  5. Amanda Youngblood says:

    From what I’ve seen, WP3.0 Multisite only lets you set up your sites as subdomains ( or subdirectories (… I couldn’t find a way to set it so that I can have different domains on the network. From what I can tell, WP Hive allows you to have different domains in the hive… which for me is the whole point. I’m a bit of a WP noob, so if I’m wrong, sorry! But, that was enough for me to decide to purchase a pro subscription for Hive. 🙂

  6. Michael says:

    I see Multisite differently. The example given by WordPress designers was one person (I don’t know why you use “entity”) running 6 blogs.

    That could also be 60 or 600.

    And Amanda, yes it does work on multiple domains. You were mistaken.

  7. Wordskill says:

    @Michael, I don’t think @Amanda was mistaken, she simply didn’t know about the Domain Mapping plugin that allows you to use a different domain for each WP 3.0 Multisite site. The plugin does make it very easy but, all the same, multiple domains is not YET a standard part of WP’s multisite functionality.

    @ikailo, if I understand you correctly, you are saying that the WP Hive is better for creating many sites that one person will control i.e. that administering these sites will be simpler than creating the same sites using the native WP Multisite feature + the Domain Mapping plugin BECAUSE WP Hive networks are more geared towards the joint administration of a portfolio of individual websites rather than the blogging networks that Multisite is geared towards?

    Will WP Hive really save me enough time to justify paying $50 per year? As others have suggested above, you will maintain the interest of more potential customers if you write a detailed blog post explaining exactly what the advantages are. Also, from the posts you have written so far, it is unclear if people paying so much for pro accounts will also have to pay for the add-ons, or if all add-ons are included in that price.

  8. Cathy says:

    I wanted to add a user’s perspective as to why I decided to stay with WP Hive and was willing to pay the $50.

    I already have 13 blogs as part of my WP Hive group. What WP Hive allowed me to do, when I had 13 separate installations, was combine all 13 under the same install. This means I kept everything that the original blogs had. There was work on the back/admin end certainly, but from the front, everything stayed looking the same.

    WP Hive made it very easy to add new sites to the hive. You just enter the wp database table prefix, click done, and you are good to go. I then had to do a bit of changing with my host and add on domains, but it was really easy (part of which may be that my host, HostGator, made the process simple).

    Before I decided to purchase the subscription to WP Hive I looked into how I would do the same thing under WP 3.0. There was lots of information about setting up blogs under WP 3.0, but it was all talking about *new* blogs.

    What about existing blogs? The best I could find (and I looked for at least an hour) was a couple of notes about copying the content into a new blog set up by WP 3.0 and the blog was the same as before. Maybe I missed something in that explanation, but to me that meant you didn’t copy over the options table. So, any widgets that I set up, or settings on plugins would have to be redone. Times 13. No thank you!

    I consider myself pretty smart and able to figure out complex directions. But the directions for setting up a WP 3.0 multiblog group (site, or network or whatever) made my head spin.

    Then there was the domain mapping plugin. Again, I would have had to spend quite a bit of time to figure out how that worked. Now, there was a learning curve for me with WP Hive, but it was all stuff you did through WP or your host.

    With WP Hive: There was no changes to the WP Config file. There was no need to create/amend an .htaccess file (which some hosts don’t even let you have anyway).

    The final thing that clinched WP Hive for me was this comment: “Yep, multi-site *is* complicated and gets you to look at things differently. 😀 It helps to understand the why things are like that though – it was written to set up a site like, where other users are signing up for blogs.

    Now in core, with the current userbase, I’m fairly certain the biggest use-case is managing multiple blogs by one owner. Huge difference there.” comment on this post: by Andrea_r, an WP developer.

    As noted above by John and others, WP 3.0/the original WP MU just wasn’t designed for what WP Hive is designed for. It can be used that way, but that wasn’t the original intention. WP Hive was built from the ground up specifically to make it easy for 1 person to administer multiple blogs.

    Finally, I will admit that I took a couple of days to decide to pay for the plugin and ultimately I did. Because:
    1. it is very, very helpful to me;
    2. given all the reasons above I didn’t want it to be discontinued;
    3. I would get the feature of a single sign on, which is one feature the base plugin doesn’t have but WP 3.0 does;
    4. the little bit of tweaking I’ve done with WP themes and plugins was enough to put me in awe of people that write from scratch, therefore, John deserves to be compensated for his work; and finally
    5. I had decided a while ago that I was going to donate anyway, so I just upped my “donation” into official subscription service. This lets John know that I’m committed to seeing this plugin continued, not just that I’m saying “thank you” for a job already done.

    I realize this comment has gone on for quite awhile, but I hope that it helps others to see how WP Hive (even the free version) is an easier solution than WP 3.0’s multi-site function.


  9. Wordskill says:

    @Cathy – thanks a lot for taking the time to explain why you decided to take the plunge. I guess the main thing holding me back is that the developer himself often appears to be quite unresponsive, although it might just be that he doesn’t read comments.

  10. ikailo says:

    I truly appreciate Cathy’s comment, as it does shed a lot of light on the differences and is quite accurate as far as I am concerned.

    Clearly there is a debate as to whether or not WP Hive is appropriate in light of the WP 3.0 release. This was to be expected, and to be honest I would rather you decide for yourself. Anyone has the option to try it, since the free version is perfectly functional with the exception of the add-ons, of which the only existing one is the Single-Sign-On.

    However, whether or not you want to justify supporting or subscribing is up to you. WP Hive was originally developed because I needed it for a particular purpose (as previously discussed). As it turns out, others wanted it too, and I have continued to develop it only because some users can see the potential and have provided support and/or encouragement. It is this support, and ONLY this support that keeps WP Hive alive.

    I respect and acknowledge the fact that I have at times appeared to be unresponsive. Please bear in mind that I am: A) Much more responsive to people who have supported or subscribed and B) Very busy providing food and shelter for my family through other full-time commitments. I am only one person.

    Most plugin developers will agree with me when I say that the amount being collected / donated / subscribed etc.. (even at $50/year) nowhere near covers the invested time and development costs. Very few plugin developers have been able to convert the hobby into a viable business, and there are many examples available online to confirm this. I would love to turn this into my livelihood, and there is a good chance that one day it will be. In the meantime, I will do what I can, when I can. And, for those that have supported me in this effort I thank you very, very much.

  11. adouer says:

    hi,I have already read the upgrades insturctions,but i do not know how to set the permissions on .htaccess to read-only (CHMOD 555), could you tell me more in detail?

  12. Wordskill says:

    @ikailo – I appreciate that you took the time to respond.

    I am not querying the time and effort you have invested into WP Hive, I am not querying the amount you have chosen to charge and you don’t have to tell me that I am free to purchase or not purchase, I already know that.

    The only thing I, and probably many other potential subscribers, are trying to do is to get some clarity on what the actual differences are, IN USE, between a WP Hive network and a WP multisite network. What are the actual practical differences, how is it going to make my life easier or save me time? We want to know this because we are INTERESTED in becoming subscribers.

    For instance, does the Single Sign-On add-on, which your site describes as allowing “users to remain logged in when traversing sites in the Hive” actually make it easier to jump from one site’s administrative dashboard to another?

    Again, I am not asking you to justify the right of your product to exist, the only reason I am asking questions is because I am INTERESTED but I have not been able, despite reading your website carefully, to work out exactly what a WP Hive network and, in particular WP Hive Pro, does differently. If it saves me trouble and time, of course I will subscribe.

    I don’t believe that people subscribe simply to support, they pay money because they believe that certain features will be useful to them and, frankly, they don’t care about how long it took you to develop, all they care about is how useful the plugin will be to them. In order to work that out, they need to understand exactly what it does and, if the premium version adds extra functionality that the free version does not demonstrate, they need to have those premium features described most carefully of all.

    As for responsiveness, firstly thanks for responding so quickly in this case. You say, though, that you are “much more responsive to people who have supported or subscribed”; may I politely suggest that it would make sense to remain just as responsive towards people who are TRYING to become subscribers but who have questions that your website failed to answer – those people, once their questions are answered, are likely to become your most ardent subscribers.

  13. Wordskill says:

    In short, I am saying that you should stop being defensive about the whole WP multisite overlap and, instead, put that energy towards explaining how WP Hive will help us, we are only holding back on purchasing because that advantage is not yet clear but we are definitely open to having it explaining to us, perhaps in a new blog post.

  14. A4D says:

    Hi ikailo, one area I do believe that wp-hive will have a future is via the sub-directory structure even with WP3 multi-site

    so if we were to create WP3 multi in subdomains and run wp-hive in sub-directories without conflict you would fully justify wp-hive (for me)

    the sub-domain multi use would be for the public and wp-hive would be used for 1 admin control

    not sure whether there is a write around this but it would make for interesting thought

    many thanks for your work and I would love to hear your thoughts


  15. Pablo says:


    Very interesting discussion. However, after reading everything, I’m not sure what to use: either “WP mapping plugin” or “WP Hive”.

    My needs are:

    – Multiple domains in same WP instance
    – Same database (if possible same tables … although having a prefix for each domain is an option)
    – I will be the only one administering the WP
    – My clients should have access to write posts. Each client should only be able to access her blog and not the rest (my clients do not know each other in fact)
    – I control the DNS and the apache server.
    – Either using the option of subdomains or subdirectories is not valid for me. Each client needs her own domain to work.

    My gut feeling says that using WP native plugins or software is a better idea for the future (compatibility issues, maintenance, etc.). I used WordPress mu with very little success (quite cumbersome and not very oriented to administrators)

    I will try to test bot options, but any feedback would be appreciated.

    Thanks for your help in advance.



  16. Jonathan says:

    Hooray for Wordskills comments above. Exactly what I was thinking!

    Spelling out features, benefits, differences is not the same as saying “try them both”. Some of us are not that technical.


  17. Sanjay Arora says:

    I am looking for something that will allow me to have several specialized blogs/groups of posts and one or more general blogs which will contain posts from two or more specialized blogs, maybe defined as groups of posts/subjects. All using one database and single sign-on for users/commenters.

    Don’t mind paying but does wp-hive fill this requirement? If not, can someone suggest something that would accomplish this?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.