• Anonymous

    I am using PHP 5.01, MySQL 4.0.20a, and Apache 1.3.31. I initially downloaded WordPress 1.2, and fumbled with the installation for two nights. First, I had nothing but problems with WordPress when loading PHP as a module rather than as CGI. I finally settled on loading PHP as CGI despite the security risks. I was able to get as far as Step 3 after having manually created the MySQL database. I didn’t know what privileges to give to my WordPress database account. After one complaint after another, I gave in and made the account a super-user. I still ended up with blank page renders. I’ve tried relocating php_mysql.dll to no avail.
    I discovered that WP 1.2 is best used on PHP4, and that I would need to downloaded a Nightly 1.3 release for use on PHP5. I recreated my database, downloaded and installed the latest WP 1.3. WordPress still gave me only blank pages. I found it necessary to reload PHP support as a module rather than as CGI. This made it possible for me to complete Step 3. But I am now stuck at my new WP login screen. If I attempt to login, I will get a CGI/FastCGI error, resulting in that horrible Internal Server Error. I know Apache is working. I am sure MySQL is working. I am pretty confident that PHP is configured correctly.
    Since WordPress is server friendly, I would feel selfish if I didn’t at least try it out. However, I found installing Greymatter to be far easier and quicker. I simply haven’t the time or patience left to try to make WP work. So I’ll instead focus the effort on GM, or try out MT. What would have helped me would have been a detailed installation guide that takes me through creating the MySQL database and account, setting up appropriate account privileges, and setting up PHP for use with Apache. It seems like all the focus is being put on customizing wp-config.php. Anyway, good luck WordPress, everyone. I’m hoping to try it out again someday.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator Matt Mullenweg

    (@matt)

    PHP 5.0 and 5.01 have problems with all versions of WordPress, however the CVS version of PHP does not. There’s nothing we can really do to fix that.

    Beel

    (@beel)

    Allusion: I tried out PHP 5.01 with WP 1.3 but Apache kept crashing at log-in, so I went back to PHP 4. Any idea as to what might be causing that??

    chuyskywalker

    (@chuyskywalker)

    What would have helped me would have been a detailed installation guide that takes me through creating the MySQL database and account, setting up appropriate account privileges, and setting up PHP for use with Apache.

    Unfortuneately, like the others pointed out, WP and PHP5 aren’t getting along nicely. Really sucks – but the truth is, none of that stuff I quoted is nessecary when doing installs under php4, because WP does it all very nicely, and very quickly without error.
    Best of luck with the other systems ๐Ÿ˜€

    Brak

    (@brak)

    Would be a lovely bit if someone found out just what is segfaulting Apache. Perhaps if I (ever) get some time I’ll work on it. Would be a function by function thing… narrowing it down to what’s doing it.
    Unfortunately I know exactly how time consuming and boring this is. And I also happen to know how little time developers have =/ ‘Tis a sucky thing, and I feel as though we shouldn’t blame Apache/PHP for this (just as we don’t blame IE for mis-interpreting our CSS) and just find a workaround.
    If anyone’s willing to work on this, I’m willing to contribute with what little time I have available.

    carthik

    (@carthik)

    Matt (allusion) knows the problem, and like he said, it is a bug that is fixed in the CVS version of PHP 5.

    Beel

    (@beel)

    Ahh, but is it? Re-read my post.

    Thread Starter Anonymous

    Hello. I made the original post. Since I’m not married to PHP5, I decided to give WordPress one more go using PHP4. I happily report that the installation was a success.
    My login immediately after the install completed no longer caused a CGI/Fast CGI error. Incidentally, I have PHP running as an Apache module. I did run into a login snag – the 403 Forbidden error. I checked my Apache error log:
    [Mon Aug 23 00:48:51 2004] [error] [client 127.0.0.1] Directory index forbidden by rule: c:/unix/websites/wordpress/wp-admin/
    I remembered that I have moved my DocumentRoot to another more manageable location outside of the Apache installation, but forgot to fully update httpd.conf. After doing, so I was able to login and make administrative changes. After updating my admin profile and logging out, I found I can no longer log back in. The password is correct, and there are no error messages.
    I’m still confused about whether wordpress installation location during setup refers to my domain or the directory beneath my domain where WP is installed:
    http://www.example.com vs. http://www.example.com/wordpress/
    I’m also still unsure what privileges the MySQL account needs.
    I can easily access any of the webpages within WordPress through my local httpd, and I’m worried about this.
    Yep. WordPress is still not working 100% for me. I’m still utterly confused, but I’m excited too. I’m looking forward to exploring WordPress more and making it work. I would appreciate an answer about WP and MySQL security though. ๐Ÿ™‚

    Moderator Matt Mullenweg

    (@matt)

    This article from the Linux Journal covers some of the MySQL setup:
    http://www.linuxjournal.com/article.php?sid=7624
    Hope that helps.

    Thread Starter Anonymous

    Thank you. In the article the author also gave all privileges to his WordPress user just as I did. Is that the best way to go however? I know nothing about PHP (having relied on CGI for years), so I’m concerned about there being a .php file storing the username and password to a database account with superuser privileges. Is this just how things are done now? Should I not be worried?

    Don’t be worried ๐Ÿ™‚

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘I give up :(’ is closed to new replies.