WP Hive » Installation and Configuration

v0.5 and Subdirectory Installs

(26 posts)
  • Started 11 months ago by ikailo
  • Latest reply from ikailo
  • 4 Members Subscribed To Topic

No tags yet.


  1. ikailo
    Developer

    It has come to my attention that sites which are installed in a subdirectory are having issues accessing wp-admin. This affects you if you currently access your WordPress site like this:

    http://domain.com/blog

    and your WP Admin like this:

    http://domain.com/blog/wp-admin

    This is now fixed in the latest build, but it also requires that you to make one change in your WP Hive configuration after installation.

    Here are the steps:

    1. If you are being redirected to http://domain.com/wp-admin when you try to log-in, then you need to upgrade. Get the latest build from the download page and install it according steps # 2 and #3 in the documentation.

    2. *Important* Log-in to the WP Admin and go to WP Hive > Edit > domain.com/. Modify the Sub Directory for this site so that is reflects the correct path. It is likely set to '/' now, so change that to '/blog', or whatever is appropriate for your installation.

    Going forward, if you are adding subdomains or domain sites, then you must specify /blog (or appropriate) as the value for the Sub Directory.

    Eg: subdomain.domain.com/blog
    or: domain2.com/blog

    It is not possible to create sites as subdirectories to this install. (eg: domain.com/blog/anotherblog will not work).

    Posted 11 months ago #

  2. iconize
    Member

    I'm having this issue but i'm not using a subdirectory as indicated above. I download the files today. Installation went fine but after I create the subdirectory eg: (mysite.com/fl). Now the issue Im having is that it redirects back to the original login.

    How do I fix that?

    Posted 10 months ago #

  3. bridges
    Member

    "It is not possible to create sites as subdirectories to this install. (eg: domain.com/blog/anotherblog will not work)."

    Is this a permanent and/or inherent limitation of WP Hive?

    Posted 10 months ago #

  4. ikailo
    Developer

    It's not permanent.

    This, and the whole subdirectory feature in general will be getting a facelift in a future version of WP Hive.

    Posted 10 months ago #

  5. jebus
    Member

    I'm sorry to appear dense, but I need to clarify something. I have a main site set up to server from domain.com. The WP installation is in /wordpress. I added another site in a subdirectory, domain.com/subdirectory.

    The site itself seems to work fine, but the admin is still redirecting to domain.com/wp-admin. I upgraded wp-hive, but I can't do step 2 without breaking the main site. Is the problem that the domain.com main site is accessed at domain.com, but the actual Wordpress install is in /wordpress?

    Thanks for any help.

    Posted 10 months ago #

  6. ikailo
    Developer

    Please see this post. A resolution will be out ASAP.

    Thanks very much for your patience.

    Posted 10 months ago #

  7. gilliancs
    Member

    I have my blogs organised like this:

    http://www.mydomain.com/projects/08-09Lab1
    http://www.mydomain.com/projects/08-09Lab2, etc

    http://www.mydomain.com/courses/08-09Lab1
    http://www.mydomain.com/courses/08-09Lab2, etc

    So I would like to have wp installed in the directory /projects/ and in /courses/ and then to have subdirectories which hold each blog. I'm not clear from the documentation and discussion if this is possible or if not, what would be possible

    Posted 10 months ago #

  8. ikailo
    Developer

    gilliancs:

    Sorry, but this configuration won't be possible. WP Hive currently only looks at the very first directory, which in your case would be the same for each site ("courses").

    Posted 9 months ago #

  9. gilliancs
    Member

    So what would be possible?

    http://www.mydomain.com/blog1
    http://www.mydomain.com/blog2
    http://www.mydomain.com/blog3

    OR
    http://www.mydomain.com/sites/blog1
    http://www.mydomain.com/sites/blog2
    http://www.mydomain.com/sites/blog3

    My problem is that if in the future an upgrade of Wordpress breaks an old site, they become unusable.

    The reason I wanted to use subdirectories is so I could have a hive of all the sites of a particular year and not update them if they broke with a new update.
    Like this:

    http://www.mydomain.com/08-09/blog1
    http://www.mydomain.com/08-09/blog2

    http://www.mydomain.com/09-10/blog1
    http://www.mydomain.com/09-10/blog2

    Posted 9 months ago #

  10. ikailo
    Developer

    This configuration would work:

    http://www.mydomain.com/blog1
    http://www.mydomain.com/blog2
    http://www.mydomain.com/blog3

    I am planning to add support for the other configuration you are requesting within the next few releases.

    Posted 9 months ago #

  11. starapple
    Member

    Hi,

    Why not use the script to get the sever environment for the WP installation and use the full path info rather than relative paths or URLs, as I think is the case.

    My installation is in example.com/blog but my index.php is in my root directory. Adding a blog then using Hive creates example.com/blog/site1.

    In the WP Hive > Edit screen, by using the full path for Sub Directory, 'site1' could be created in the root (serverpath/blog/site1) so that I could keep example.com in the Domain Name field of the Edit form.

    The environment script could tell the plug-in where my wp-admin is so that it doesn not depend on the site URL in the form.

    Would site1 directory being at the same level as wp-content create a problem?

    Just my two cents worth before saying thanks for the great job you've done so far.

    Posted 9 months ago #

  12. starapple
    Member

    Please excuse the multiple posts. Firefox was preventing a redirection or reloading of the page and I switched to Explorer before realizing that the post had been submitted.

    Posted 9 months ago #

  13. starapple
    Member

    Posted 9 months ago #

  14. gilliancs
    Member

    Thanks ikailo: I'll wait for the release. As I run a main website and 8 blogs a year it helps to be able to keep them separate. Thanks for your great work.

    Posted 9 months ago #

  15. starapple
    Member

    Hi ikailo:

    I thought everything was fine with my installation of Hive until I was suddenly locked out of my site admin. Deleted wp-Hive and things are back to normal. It must be something to do with WP being installed in a directory of the domain root.

    In my previous post I was not clear in what I proposed. The suggestion was to get example.com/site1 created by Hive although the WP installation is at example.com/blog, and is accessed via example.com/index.php using .htaccess.

    In the WP Hive > Edit screen, by using the full server path for Sub Directory, 'site1' could be created in the root (serverroot/site1) and not be dependent on the Domain Name field, which would have the full url to the WP install example.com/blog.

    Hope this is clearer.

    Posted 9 months ago #

  16. bryon
    Member

    What happens if we already have subdomains setup with wp-hive, like sub1.site.com and sub2.site.com and everything is installed in a subdirectory like site.com/blog. Should we add the /blog to all the entries and it will work? I can't even get it to work with my main site with /blog (gets an direction loop)

    I think the problem for me is that I have it all installed into /blog but that subdirectory is there only to keep the folders tidy, when the site is actually viewed (maybe installed at?) it is site.com with no subdirectory.

    I am okay with having to delete db.php to get to my main site's dashboard. I might export all my posts and rebuild around wp-hive sometime in the future.

    Posted 9 months ago #

  17. bryon
    Member

    To be more clear, if you follow along in Dashboard > Settings > General

    My site is setup like this...
    Wordpress address (URL) = http://site.com/blog
    Blog address (URL) = http://site.com

    Posted 9 months ago #

  18. starapple
    Member

    That's my setup too, Byron. Are you saying that deleting or renaming db.php enables access to your admin, after which you reinstate db.php?

    Posted 9 months ago #

  19. bryon
    Member

    That is what I do starapple.

    Subsequently my subdomains are at http://sub1.site.com and so on.

    Posted 9 months ago #

  20. starapple
    Member

    Thanks Byron. Now another question, which I posed in another thread: exactly what does Hive do? Does it create an installation at the location to which you point it - that is, whether sub-domain or sub-directory?

    I see an "Install" button available after I've added a site but nothing happens. Well not really: either no subdirectory is created and I get a 404 after clicking "Install" or if I manually create one and click "Install" I'm directed to the empty directory.

    Do I need to place WP files in this directory? I was under the impression that Hive automates the creation of new blog instances under one installation of WP.

    Thanks again.

    Posted 9 months ago #

  21. ikailo
    Developer

    bryon: If you have installed WordPress in a subdirectory off the root and access your site(s) like this: domain.com/blog or sub1.domain.com/blog, then all your sites in the hive should be given a /blog path. WP Hive reads only the domain and the first path to determine which site to serve.

    starapple: Don't create any directories for the new sites. WP Hive uses Mod-Rewrite / Pretty Permalinks to determine which site is being requested. If you create a directory, then all you will see is a blank page because the webserver is serving the directory instead of WordPress.

    Posted 9 months ago #

  22. starapple
    Member

    Thanks John. Now just one more clarification. Is WP Hive creating a new (virtual) blog instance using the WP Installation and I could create domain.com/toronto, domain.com/kingston, domain.com/waterloo etc?

    Also, I'd wish to use the same favicon across all the blogs.

    Thanks again.

    Mark.

    Posted 9 months ago #

  23. bryon
    Member

    In wp-hive>edit when I change any entry with the values below, visiting returns "Unknown Host".

    Domain Name: sub1.site.com
    Sub Directory: /blog
    ... for all subdomains...

    and

    Domain Name: site.com
    Sub Directory: /blog
    ... returns Unknown Host for all pages...

    Also, thank you so much ikailo for your patience and help.

    Posted 9 months ago #

  24. bryon
    Member

    Also, something that may be note worthy. All my sub-domains can access their own dashboards via sub1.site.com/wp-admin

    Posted 9 months ago #

  25. drmwvrsquilts
    Member

    Sorry ikailo, but I'm really confused about this issue. I was already running v0.5.3, but all of a sudden having this redirection problem.

    I read this above:

    "This is now fixed in the latest build, but it also requires that you to make one change in your WP Hive configuration after installation."

    and I assume that the latest build IS in fact v0.5.3, right?

    So I did what you said would fix the problem, and added "/content" in the Subdirectory box, and it still doesn't fix the problem. My site is still redirecting to domain.com/wp-admin when I try to login.

    But then later you said this:

    "Please see this post. A resolution will be out ASAP.

    Thanks very much for your patience. "

    And when I look at that post, and it says that a resolution is coming. So first you said the problem is fixed, but you need to do thus and so after installation (which I did and it didn't help), but then a resolution is coming? Can you please clear this up?

    Posted 9 months ago #

  26. drmwvrsquilts
    Member

    Actually, it's even worse than I thought: If I put in "/content" in the Subdirectory box, the main site gives an unknown host error, so clearly that solution doesn't work at all. Is there any word on a timeline to make it all work again?

    Posted 9 months ago #

  27. ikailo
    Developer

    To be clear, regarding WP Hive v0.5.3.

    For WP Hive to work correctly, WordPress must be installed in the root. Giving WordPress its own directory eg: domain.com/blog still has outstanding issues, especially when trying to access WP Admin.

    WP Hive currently supports installs like this, as long as WordPress is installed as a regular site for domain.com:

    domain.com
    domain.com/blog1
    domain.com/blog2
    sub1.domain.com/blog1
    sub2.domain.com/blog3
    sub23.domain.com
    otherdomain.com

    Just make sure that when you access WordPress BEFORE installing WP Hive, that you access it using a domain name only, and not have to add a path. For Example: If you access it like this: domain.com/wp-admin, then it will work. If you access WordPress like this: domain.com/blog/wp-admin, WP Hive will NOT work.

    Posted 9 months ago #

  28. ikailo
    Developer

    My apologies if I haven't answered all the questions in this thread. There are a lot of questions that I'm not sure if they have been resolved or not yet.

    If there are outstanding issues, please start a new thread, as it will be easier for me to understand what needs to be addressed. Thanks!

    Posted 9 months ago #

RSS feed for this topic

Reply

You must log in to post.