WordPress.org

1. doodlebee
   Member
   Posted 4 years ago #

   Hey all -

   I'm trying to install WordPress on a Verio IIS server. They have PHP run as CGI, and installing on a Windows server is a first for me.

   Right now, it's doing this weird thing where it seems to be running *part* of the PHP scripts, and "echoing" out other parts when I enter the admin areas (install or index - both do this). I have a wp-config.php file on one of them - the other is giving me a an error because it can't find it (not the typical WP error either) - but that's to be expected because I haven't done one yet.

   Anyway, it's really weird that only *parts* of the code are being run (or I think they are, anyway), which the rest is just echoed out. Putting phpinfo() on the server gives me a blank white page. I'm not familiar with IIS (I've done some stuff, but I'm mostly clueless) so would anyone know what I need to check for? I have access to php.ini (I needed o up the memory_limit, so they let me do that). Is it the CGI that's doing this? I just haven't a clue where, or what, to even look for to get me started, so a nudge in the right direction would be great.

2. doodlebee
   Member
   Posted 4 years ago #

   Found out what it was. I can't explain it fully, but in the end it was quasi the host's fault (the .htaccess file was messing with it) - if I renamed that file, I could get in and do my thing, then change it back and everything was fine.

3. doodlebee
   Member
   Posted 4 years ago #

   Sorry - I'm wrong on that one. That was the solution for a different site - also running on Verio, but the Unix server. The Windows IIS server is still being a turd.

   I found another thread that said if I installed an old version of WP and then upgraded, it would solve the issue. So I deleted everything, and uploaded the files for 2.0.11. now I have a totally new issue - it's finding the files just fine, but now I have the error of:

   PHP Fatal error: Call to undefined method stdClass::hide_errors() in ***\blog\wp-settings.php on line 121

   that line says this:

   $wpdb->hide_errors();

   Man, working on IIS sucks. Anyway, anyone have any ideas for me on how to get this running on Windows?

4. doodlebee
   Member
   Posted 4 years ago #

   Okay, I think I have it narrowed down. Line 121 comes after a few references to "WPINC". When i was trying to install 2.5.1, it didn't know what "WPINC" was. Changing relative paths for "ABSPATH" would solve some problems, but it would choke when it came to "WPINC" - so I'm guessing that's the issue here.

   Anyone know where "WPINC" is defined? Maybe I need to put in an absolute path to that?

5. Otto
   Tech Ninja
   Posted 4 years ago #

   WPINC is defined on line 176 of the wp-settings.php file.

6. doodlebee
   Member
   Posted 4 years ago #

   Thanks Otto. :)

7. doodlebee
   Member
   Posted 4 years ago #

   Blargh. So I removed everything and tried re-uploading the files, and ALL NEW errors showed up. So I re-uploaded/overwrote the files that were showing up in the new errors, and now an all-new wp-settings error is here, one I've never seen before, but of course, uploading the file again does nothing.

   This server is seriously whacked. It's gotta be that.

   Even funnier - if I upload the same file to the same area, using a PC, then I get a different error. Upload using my Mac, and the other error comes back. How weird is that?

8. doodlebee
   Member
   Posted 4 years ago #

   OMG - I *finally* got it.

   So, here's the deal. Thank to the wp-hackers lists, I removed ALL whitespace from the end of wp-settings.php. Apparently, my Mac puts in some different EOL characters than Windows does, so that was screwing with some things.

   I opened up the php.ini file, and looked for "cgi.fix_pathinfo". I found it, but it was commented out. I removed the leading ";" and set the "0" to "1". (While I was in there, I also set the memory_limit to 32 - might as well, right? LOL)

   Then - here's the biggie - when I started the installation, I typically go to sitename/wp-admin and let it do it's thing. but this time, when I'd enter in my blog name and email address, it would redirect to a 404 "Page Not Found". BUT - when I actually entered in the path to the installation file (in my case, it looked like so: sitename.com/blog/wp-admin/install.php) THEN IT WORKED!

   I had to change the settings to point to the correct location of the files - for some reason it only had "sitename.com" instead of "sitename.com/blog", so all the styles were lost - but now it works. Ahhh...took me two weeks to figure this out - but man, I'm glad it finally worked. Just thought I' pass this info along for anyone else who might need it.

Topic Closed

This topic has been closed to new replies.