1 tabard Feb 02, 2005 09:45
3 tabard Feb 07, 2005 00:58
Well, apparently, I'm still having this problem. First post edited to bump.
4 powerspike Feb 07, 2005 10:09
that appears to be a server side problem, so if you reciving the problem in one browser and not the other, would suggest clearing the cache in both of them, to see if the problem is still there or not, looking at the error - it's not chosing a skin to display ? maybe try changing the skin in the backend to see if that fixes the problem (if your still having it of course :P)
5 stk Feb 07, 2005 20:26
tabard ... I'm no expert, but the pathing looks very odd. First, my skins are located in "http://www.mysite.com/blogs/skins/myskin/_main.php" or locally it's "/home/username/public_html/blogs/skins/myskin/_main.php"
I'm not certain about the "/www/t/" (unless that's a local call because of your host). Or why the install is in htdocs, but not in a separate 'b2evo' or 'blog' directory.
But mostly, I'm confused by the double forward slash, (i.e. "skins//_main.php") That seems like a problem to me.
I checked your site in MSIE6 and FireFox1 ... both pull up your blog without errors.
6 graham Feb 07, 2005 20:57
No idea about the error, but having your install in htdocs is perfectly standard (like mine!).
[edit]
That line is the one that calls your _main.php from your skins folder. I suspect it's not been uploaded propperly, or is missing altogether.
7 tabard Feb 08, 2005 01:36
Well, I thought I posted a reply to this, but it looks like it got lost. Anyway...
Stk: that is Powweb's (my webhost) standard relative path layout. 'htdocs' is where my public files go. In-browser, it shows up as the base directory for my site.
As far as the "skins//_main.php" goes, I noticed that too, when I first started getting the error. I've checked my _config file, _blog_main, and even checked my skins directory to make sure everything is there. It looks like it's trying to call up a skin that's in a unnamed directory, but I've checked my default settings in the backend, and everything's normal.
I posted about the possible server-side issue on the Powweb forums. They did some balance loading upgrades in the last few months that slightly altered the way php includes work, so I'm wondering if that might be part of the problem. But that wouldn't make sense, since when it does work, all the includes are fine.
Ugh. Sorry about the rambling. This is a little frustrating, as you might imagine. Thanks for the replies guys :)
I wasn't able to figure out exactly what was wrong, so I backed up my website, deleted everything and reinstalled. I figure it must have had something to do with me installing in my base directory when there was already quite a bit of junk in there already. But it seems to be working fine now.
Thanks to the devs for putting together a great program! :)