Let me explain the context first. I have an HTTP site running that uses WB 2.8. I started some time ago to set up a new site in HTTPS. This site was set up with WB 2.10. While working on it, I wanted to have a new environment to do testing (partly so that I could get third-party help without risking my own site). My ISP gave me a second directory for this. I started by installing WB 2.11. I then copied over pages and other components from the first HTTPS site. I then had to work on another project (you know how it goes), and when I came back to the test site it was not loading correctly.
I just want it to work, at this point. After that, I can upgrade to WB 2.12.
I think some of the configuration is still incorrect. For example, the config.php file I found when I returned to this project included the line:
I changed it to:
In Chrome on the Mac I get part of the Home page (with the wrong formatting). On Windows I still get the under-construction page. But, this indicates that something about the magic constant __DIR__ isn't set correctly. I don't know where it is picking up the value for this, but really, it should be exactly the same because of the location of the config.php file.
It also indicates that the settings for the database in the config.php file are correct, because it wouldn't find and try to display content for the Home page if it wasn't accessing the database.
You said that the wb_settings table is important. I looked at this table in the new database (for the testing site, the one I'm getting based on the config.php file). I don't see any settings that directly apply, except that it still has the wb_version set to 2.10.0. Do you think the wb_settings table is different enough between 2.10 and 2.11 to cause this?
If necessary, I can start the upgrade over and go to WB 2.12. But if I could repair the wb_settings table so that it works with 2.11, then I can get started immediately and delay upgrading until I get to where I need that.
Thanks again for your help!