Warning: unable to access

I’m having this same issue as well with WP 0.71-gold.
Warning: main(/home/ijsmorg/public_html//b2-include/wp-db.php): failed to open stream: No such file or directory in /home/ijsmorg/public_html/wordpress/b2config.php on line 337
Fatal error: main(): Failed opening required ‘/home/ijsmorg/public_html//b2-include/wp-db.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/ijsmorg/public_html/wordpress/b2config.php on line 337
The strangness appears, to me, to be with the b2-include directory. It’s within the wordpress directory created when you gunzip and tar -xvf the wget’d file … but it’s looking here:
/home/ijsmorg/public_html//b2-include/
‘wordpress’ should be within the two paired slashes, but I don’t see anything obvious to change, and the warning above the $b2inc var setting says to not include a / in there … so I’m stumped.
GFM

As a guess, I then went in and decided to be brave and change $b2inc to:
$b2inc=’wordpress/b2-include’
And I’ve gotten wp-install.php to connect to the db and start the install process. We’ll see if I break anything else in this process.

The install appears to have run, however … once I attempt to login at https://ijsm.org/wordpress/b2login.php, after auth it sends me to https://ijsm.org/b2login.php, which is certainly incorrect.
Now, I might be running at cross-purposes with WP here, but it seems to me as if WP is expecting to modify files within whatever root directory the b2*.php files are within, but … the tarball pushes you into /wordpress/ which is certainly cleaner in the long run.
Is this a case where $path and/or $relpath should be changed in b2config.php? And shouldn’t we as good developers want to push WP as an admin tool into its own directory so it’s not lost in the dreck of the root directory? ??

*cricket*

I think it has to do with your directory includes for your php.ini file. I *think* (and thats a long stretch coming from a person on the creative side…), you have to modify your “include_path” (see configuration in the php manual). I could be way off on this, but I think I’ve ran into similar problems in the past that seems like this is related…

Hmmmm … I’ll check php.ini and see what I can find out.

I saw nothing that jumped out at me.

Is the blog URL correct in the options? If the login redirect is going to the wrong place, that could be the reason.

Yes, it’s as I would like it to be, which is https://ijsm.org/
But then I’m weird and want the wordpress files in a separate directory. Call me strange, but I’m one for well-structured directories. When one wget’s the latest tarball, it unzips into its own directory–which is as it should be.
But why must it assume that you’re going run your log in that directory rather than the root directory? I know a ton of people who use Greymatter or Moveable Type that have the software that powers their logware in a directory separate from their content.

So you moved all of the files into the root directory then? Or they are still in the sub-directory? The blog URL setting must point to the URL that actually has the files in it. Trying to go to:
https://example.com/wp-admin/b2edit.php
is not going to work if the file is actually at:
https://example.com/wordpress/wp-admin/b2edit.php

Currently, my files are still in the subdir.
I guess I’m being pedantic here, but this is an option that should be pursued, especially because you could be clever about how you named the directory with wordpress files in it and limit access, etc.