The good news is that b2evo index.php is our homepage :D
The bad news is that I'm picky about keeping directories neat and don't want b2evo installed directly into root. :(
What I usually do, is install b2evo into /root/b2evolution, get everything working and then move index.php (and stubs) up one directory (into root). Then I change the $baseurl from 'http://mysite.com/b2evolution/' to 'http://mysite.com/' (in _basic_config.php) and fix up all of the "$[loc]_subdir" (relative to base) variables in "advanced.php".
Sounds simple enough and it has been.
But I ran into a bit of a problem with the admin_skins path construction. Seems that 1.8 picks up the URL fine (so I can get the skin in the back office OKAY), but the path name it constructs has got a double "b2evolution" in it. :(
(I noticed it failing when I went into the Users Tab in the back office, as it didn't correctly populate the admin-skins drop down menu and spit out some complaining error message) .
One can hardwire a fix for it in the /b2evolution/_header.php file (I just backed up a directory to correct the file path).
<?php
require_once dirname(__FILE__).'/'.$adminskins_subdir.$admin_skin.'/_adminUI.class.php';
/* became */
require_once dirname(__FILE__).'/../'.$adminskins_subdir.$admin_skin.'/_adminUI.class.php';
?>
( Two lines changed ... around line 25 and 89 )
(A similar problem occurred with the GoogleSpell plugin, although instead of two "b2evolution" dir names, it didn't have ANY. A similar hardwired fix remedies the problem ... around line 215 of _googlespell.plugin.php ).
Seems like these are mildly obfuscating and unecessary, shall I call them "insects"? Shouldn't one be able to put some distance between the index.php/stub files and the install directory without any hacks?
I wonder if specifying a $base_path (e.g., /home/yoursite/public_html/) in addition to a $base_url in config and utilizing them consistently ( along with the relative URL information in _advanced.php) wouldn't alleviate these problems?
If there's a better way to achieve what I'm doing, I'm all ears. But I thought I'd relay the information, in case anyone else runs into this problem.
General Support
b2evolution CMS Support Forums
Seems there's problems finding admin.php too, which it thinks should be in the root directory. This is easily discovered when I try to edit an existing post and get a 404 error instead. :(
The temporary fix, has been to modify the line in the advanced file that points to admin, correctly adding the "b2evolution/" directory tree (that line says nothing about it being "relative to base" ... but again, it's inconsistent.
Why? Because adding the "b2evolution/" dir allows me to edit my posts (it correctly finds http://mysite.com/b2evolution/admin.php?blah&blah but it fails in other areas, tossing out a http://myside.com/b2evolution/b2evolution/admin.php&blah&blah )
Seems the internal pathing and URLs need some sorting out and consistency.