WP Hive » Installation and Configuration

Table Prefix broken?

(5 posts)

Tags:


  1. mpwalsh8
    Member

    This afternoon I got wp-hive working with a main blog and one new blog. I was poking around the database and noticed a couple of things:

    1) The wphive tables don't use the prefix I have setup for my primary WP installation. I think this needs to be fixed and is trivial to do so.

    2) The second blog I created which is managed by wp-hive has a 3 letter prefix based on the domain name - why not use the entire subdomain prefix? For the project I am thinking of using hive on, there will be 6-8 subdoamins which are all very similar and in each case, the first 3 letters are replicated across at least one other subdoamin.

    3) Like the wphive tables, the tables for the second blog do not make use of the database prefix either.

    Looking at the code, the wp-hive tables are hard coded which would prevent setting up more than one installation in a single database.

    I like the potential of this, but I'd like to see a couple things like this fixed before I commit it to a real project.

    Mike

    Posted 1 year ago #

  2. ikailo
    Developer

    Hi Mike,

    1. The wphive_host and wphive_config tables need to be shared between all the sites in the hive, hence the reason for the the hardcoding and no prefix (technically, the prefix is 'wphive_').

    2. We could use the whole subdomain name for the prefix if necessary. Might change that later. However, currently if multiple sites with the same first letters are added, it will generate a unique prefix eg: 'aa1_', 'aa2_', etc.. (note: there is a known bug when adding the third site automatically, so might have to do it manually)

    3. Not sure what you mean by the second blog not using the prefix. It's intended to use a unique prefix for each site. If it's not doing it, then it's a bug.. Can you send me more details about it?

    Never thought about having multiple hives in a single database before, but you bring up a valid point! Will most likely work that into a future version.

    Thanks for your feedback.. I am currently working on a new version, which I think you will find to your liking.

    Posted 1 year ago #

  3. mpwalsh8
    Member

    Thanks for the quick response, some more things to think about.

    1) If the hive tables need to be hardcoded, wouldn't that eliminate the possibility of having multiple hives reside in the same database? If the hives tables took on the prefix of the host (parent?) blog, is there anyway for the other blogs (children?) to know what their parent blog is? Isn't the prefix in the wp-config file?

    2) A generated name is better than a conflict but how can I correlate the tables with a blog? Having to look at the tables isn't something I do frequently but it does become necessary from time to time. What is the reason to shorten it in the first place?

    3) For my top level blog, I set the database prefix to be "abc_". When I created the second blog (demo), the tables were created with a prefix of "dem_", I would have expected them to also have the "abc_" prefix.

    Thanks,

    Mike

    Posted 1 year ago #

  4. ikailo
    Developer

    1. Yes. I never imagined that someone would install multiple hives on a single database. I think that will be changed one day.

    Currently, once the table prefix is set by wphive, the $table_prefix variable that is set in wp-config.php is lost forever. I guess we could store it somewhere, but I don't see the need for that. In actuality, it was not designed be a parent / child type relationship. More like brother / sister with a default prefix (the one stored in wp-config.php) in case WP Hive gets uninstalled.

    2. The wphive_hosts table lists the prefix / domain name pairs.

    The reason for the short prefix was that the default, wp_, was short, and I just followed suit.

    3. The prefix generation algorithm bases the prefix on the first few letters of the domain name, so if your names were subA.domain.com, subB.domain.com, subC.domain.com, etc.. then the prefixes should be sub_, su1_, su2_ etc...

    When WP Hive is first installed, it creates an entry in wphive_hosts for the prefix that is defined in wp-config.php, so the site can remain active and accessible.

    Posted 1 year ago #

  5. senlin09
    Member

    Hi John,
    I also struggled with this problem.

    I want to start using the hive plugin for different languages sites (once you have had the time for the update, that is) and typically people use 2 letter abbreviations for languages (conform WP_lang basically). That however results in a problem that can only be solved when you manually change the prefix for the subdomain in the wphive_hosts-table.

    To illustrate this:
    main domain: http://www.domain.com
    sub-domain: en.domain.com

    The plugin automatically makes the prefix for the subdomain en._ and that is not allowed.

    Solution:
    Manually change the prefix for the subdomain in for example en1_ and hopla, problem solved!

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.