Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter wsmeets

    (@wsmeets)

    ah, the favicon is not an issue, almost none of my customers use it. It just doesn’t get uploaded. It is not a reason for failure. Favicon is what you see on this site for example, next to the url, there is a little W
    That is a favicon.

    But I have to say that my issue is resolved. I’ve downloaded the sources from here (I used a debian rep. first) and now it does work. I have no idea what is wrong with the debian package. I’m gonna do some tests with it in a virtual machine and report it to the debian maintainer. Anyway, should someone here get the same issues as I had, then this is the step-by-step solution

    apt-get remove wordpad
    rm -rf /usr/share/wordpress
    rm -rf /etc/wordpress
    rm -rf /var/www/directorywhereyouwantedtorunwordpress

    download it from this site
    untar/unzip

    Alter your config.php

    Fixed.

    Best regards,

    Wilbert Smeets

    Thread Starter wsmeets

    (@wsmeets)

    I don’t think this is server related really.
    My server works just fine. It hosts over 50 domains…
    Heck, I even support .net with mono 😉
    If a regular install of debian with the only added options apache2, php5, mysql 5 and mono is a serverissue then wordpress would not be running on many systems.

    The install.php script tries to access the wp-settings.php in /etc/wordpress which makes no sense, since the original file is in the www-root of this particulair domain. So your awsner is to me a bit like saying: “i have no clue, so it’s your fault.” That is not meant like a flame btw.

    My question is purely wordpress setup related, since the server is configured and running well.

    But let me rephrase my question.
    How can I get install.php to access the real wp-settings.php and not a symbolic linked version of it. I have a feeling that would resolve my issue.

    Thread Starter wsmeets

    (@wsmeets)

    A little more info I just found.
    In my blog directory I can access wp-settings.php just fine.
    However the install.php wants to access it in /etc/wordpress

    There is a symbolic link there, that also links to itself /etc/wordpress/wp-settings.php

    I think the whole issue can be resolved by letting install.php open the original wp-settings… I just don’t know how to do that.

    Thread Starter wsmeets

    (@wsmeets)

    Well the problem is. I am the host 🙂
    I have a production server in a datacentre for several websites I host. All works well. I’m using Apache2, PHP5 and mysql 5.0.41. All these things are tested and work.

    For one reason or another it looks like /etc/wordpress/wp-settings.php is symbolic linked to itself. I can’t even do a simple ‘cat /etc/wordpress/wp-settings.php’

    I have no idea why this is the case, I did a fresh install of wordpress with ‘apt-get install wordpress’ (I use debian).

    I searched the forums here, but it doesn’t seem to be a known issue.

    When opening install.php I get a blank page.

    Thread Starter wsmeets

    (@wsmeets)

    Lol…

    What is causing this and how can I resolve it.

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