greenredbrownell

Podz, you are tireless. I commend you heartily. Thanks for keepin’ it friendly. 😉

Pathing for your whole WordPress site is done in two rows of your data base. If you know how to open up your WP mySQL data base (if you are on a hosted server, there is usually a management console of some sort), then go browse the rows of the “wp-options’ table. The two entries (option_name column) you want to look at are called “siteurl” and “home”. See if there’s anything in there that will help point you at the right URL. If you change these options, do so carefully, and remember the old contents, so you can get back to what it was again if it doesn’t work.

When I installed in a sub-folder of the root, I had to change my “home” value before all the internal WP links on the various pages would work (and so the default theme would show up). After install, the value of “home” was something like “www.mysite.com”, and I had to change it to something like “www.mysite.com/baseballblog, which is where I had WP installed.

Good luck.

Lloyd, you should really start another thread. However, go look at my last reply here

http://wordpress.org/support/topic.php?id=14126

I describe how I got rid of your error. I was using a GoDaddy Windows hosted server, but I have seen reports of this error on other servers as well. Hope it works…

I was successful on a GoDaddy Windows-based server. Are you on a Windows or Linux server?

I can’t help with the “foreach” error, but the problem with it not finding tables is a chicken/egg kind of thing that happens to lots of people on their first install. You can usually IGNORE those warnings if you haven’t actually done the install yet!!!

It took me days to figure out that the tables do not get created until you go through Steps 1 and 2 of the install process. So, if at the bottom of the page you see the standard text to start Step 1, just try it. Very often, it sets up the data base just fine, and you’re on your way… if it doesn’t work, you may have to delete your data base and start over, but that shouldn’t be so hard, eh??

Good luck….

— Green

Ya, it took me *days* to figure out to ignore all those errors and just go install the damn thing, so it could set up the data base tables….

Glad to hear it’s solved…

I had the same problem. Check this thread for my last post.

http://wordpress.org/support/topic.php?id=14126

In my case, I was on a GoDaddy server using Windows. If I commented out the lines that were producing the error you mentioned, I was able to get the installation to succeed. In other words, the server *did* support the “mysql” extension, but the extension_loaded() call was saying that it wasn’t supported.

If you want to check your server for the mysql extension the way I did, follow the link above to the other thread. You can add one line (get_loaded_extensions, or something like that), just before the “die” statement, which will print out a list of the supported extensions. Then, re-upload your “diagnostic” script and start over with install.php, and it’ll display.

I’ll bet you’ll find “mysql” on there, and can comment out the lines, the same as me. If ‘mysql” isn’t on the list, you’ll have to get in touch with your hosting provider….

I finally figured out the issue here, and the issue is that the WordPress script and GoDaddy Windows web hosting don’t quite get along.

Specifically, the lines that produce the error that everyone is mentioning above are these, from wp-settings.php:

if ( !extension_loaded(‘mysql’) ) {
die( ‘Your PHP installation appears to be missing the MySQL which is required for WordPress.’ );
}

Well, to debug the issue, I inserted the folling line immediately before the “die” statement:

print_r(get_loaded_extensions());

and guess what?? GoDaddy does indeed have “mysql” loaded. I understand that the extension name is case-sensitie, and all, but it matched exactly!!! And still, the “extension_loaded” call above failed. My solution was to simply comment out all the lines listed above in wp-settings.php, like this:

//if ( !extension_loaded(‘mysql’) ) {
// die( ‘Your PHP installation appears to be missing //the MySQL which is required for WordPress.’ );
//}

Then I re-uploaded, tried install.php again, and things just worked. Well, I’m lying… it gave me a bunch of “table not found” errors before displaying the Step 1 text, and it took me *days* to figure out that I should just ignore those errors… Step 1 (or was it Step 2?) will create the tables in the data base, and then all will work fine.

I should emphasize that this was a Windows GoDaddy host, not a Linux one, so YMMV if you chose a Linux host.

Hope this helps someone get past this particular error.

Coders and PHP mavens, why would this statement error out on GoDaddy’s host, when “mysql” was in fact installed???

Thanks a lot,

Green