• I use PHP-thttpd instead of Apache. I can run WordPress local on my network with any problems. Everything looks great. As soon I ask a friend of mine to check it via the internet the whole page looks terrible..Just test and no graphics.

    Are there any ppl who use php-thttpd also is use WordPress without ant problems.

    I become crazy 🙂

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter whocaresg

    (@whocaresg)

    P.S. it’s about this blog:
    http://blog.vellema.com

    Why is the wordpress install in the cgi-bin? Is that something specific for your server setup?

    This is where your install wants to find the style.css file:

    http://192.168.0.20/cgi-bin/wordpress/wp-content/themes/default/style.css – is that where it actually resides?

    Thread Starter whocaresg

    (@whocaresg)

    It’s in the cgi-bin for no reason actually. The location is exactly where you gave it.

    A quote from the log:
    When I open blog.vellema.com (from my local network):

    “GET /cgi-bin/wordpress/ HTTP/1.1” 200 7008 “http://blog.vellema.com/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7”
    192.168.0.41 – – [03/Jan/2006:00:18:45 +0100] “GET /cgi-bin/wordpress/wp-content/themes/default/style.css HTTP/1.1” 304 0 “http://gvellema.dnsalias.org/cgi-bin/wordpress/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7”

    A quote from the log when you open blog.vellema.com
    63.18.87.58 – – [03/Jan/2006:00:19:43 +0100] “GET /cgi-bin/wordpress HTTP/1.1” 302 0 “http://blog.vellema.com/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5”
    63.18.87.58 – – [03/Jan/2006:00:19:49 +0100] “GET /cgi-bin/wordpress/ HTTP/1.1” 200 7008 “http://blog.vellema.com/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5”
    63.18.87.58 – – [03/Jan/2006:00:21:03 +0100] “GET /cgi-bin/wordpress HTTP/1.1” 302 0 “http://blog.vellema.com/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5”
    63.18.87.58 – – [03/Jan/2006:00:21:10 +0100] “GET /cgi-bin/wordpress/ HTTP/1.1” 200 7008 “http://blog.vellema.com/” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5”

    The difference is that the style.css does not show up at all..

    🙁

    In general, it’s neither necessary nor desirable for wp to live in the cgi-bin.

    Thread Starter whocaresg

    (@whocaresg)

    chmod’s on the dirs from /cgi-bin/wordpress till …default/ are all “755”

    Thread Starter whocaresg

    (@whocaresg)

    I can change the location ofcource….(move wordpress up 1 location)

    Thread Starter whocaresg

    (@whocaresg)

    But still why can I see everything without any problems and have external ppl no correct view?

    For troubleshooting purposes, please try installing (or moving, if you’re comfortable with that) wp in a normal subfolder.

    Thread Starter whocaresg

    (@whocaresg)

    I reinstalled everything and I saw i mistake (I hope). Can you check the blog now on http://gvellema.dnsalias.org/wordpress

    Thread Starter whocaresg

    (@whocaresg)

    I hope it works now!

    Thread Starter whocaresg

    (@whocaresg)

    In Admin, Options, General I hardcoded, by accident here:
    WordPress address (URI):
    Blog address (URI):

    both times 192.168.0.20 !!!!!!!

    I changed that now.

    I do not know why I did that but it seems 2 b correct now (I hope)

    Yup, there you are! No reason (unless to do with your server flavor of course!) to run wp in the cgi-bin, and every reason not to.

    Have fun!

    Thread Starter whocaresg

    (@whocaresg)

    Thanks for listening (I sound like a woman now)…but I’m sooooooooooo happy 🙂

    Great..

    Hmmm…. that’s a problem? I AM a woman… I’m happy for you too!

    Thread Starter whocaresg

    (@whocaresg)

    Hahaha….no 1 is perfect haha…just kidding..thanks vkaryl

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

The topic ‘how to for php-thttpd’ is closed to new replies.