Support » Fixing WordPress » odd error in server logs

  • Cant figure it out 🙂

    File does not exist: my path/wp-content/themes/neat/none

    I tracked it down to something to do with css – possibly.. If I rename my CSS file on the server (breaking it), the error stops.. (Then I just get a file not found style.css, but nothing about “none”)

    Here’s the css (looks fine to me):

    Dont have many plugins installed — think the problem just started recently — the only plugin recently installed was “technotag” but I disabled it and still got the error.

    It’s not obviously breaking anything as the page still loads fine, but I dont want the error nonetheless..

    Can anyone shed some light?

Viewing 13 replies - 1 through 13 (of 13 total)
  • This is what should be at the top of a theme stylesheet:

    In the style.css:

    #sidebar ul li {

    That list-style-image is pointing to a url of ‘none’, which would seem to be the error.

    Now of all the files, how did you guess it was the css making the call?

    Beel — it was one of the few files I remember changing in the past few days, so I took it out of the equation and it fixed the issue 🙂

    Looks like I’ve solved it!!!!!

    By chopping pieces in and out of the css file and uploading / testing / checking logs (and repeating several painful times)

    I narrowed it down to this:


    from this section

    #sidebar ul li {

    the original css from the theme had this:

    list-style-image: none;

    I have absolutely no idea how it got changed to:


    Hey, thanks Kaf — I’m sure you figured that out in a fraction of the time it took me (i’m pretty new to CSS)….

    I’m still trying to figure out how that got changed though 🙂

    ok this is weird….. the


    reappeared again!! 🙂 i looked at the properties of my style.css on the server and it was modified at 10:00pm — while I was not home.

    what could possibly be changing it from list-style-image:none; to what it is above??



    Your dog is blogging in your absence?

    Seriously, I’ve never heard of such a thing. Would it hurt to CHMOD the stylesheet to 644 rather than 766?

    Actually, you don’t need to declare list-style-image: none; really, do you? Why don’t you try commenting that out of the stylesheet and see what happens. Put this line in place of the one you have:

    /* list-style-image: none; */

    server crash and reload from backup without telling you, or an unnoticed “oops” on your part.

    hmm maybe, but nothing else was missing — it couldn’t have been an oops as it was fine before I went out, time stamp showed modified while I *was* out, and broken when I came home 🙂

    no big deal, just interesting and odd

    If you actually needed to track this down, the date stamp coinciding with the time you were “out” isn’t mutually exclusive in and of itself. An “oops” would not be ruled out. Now I suppose if you shut off the computer before you left…

    yeah, my cat prolly unlocked my workstation (she’s great with CTRL-ALT-DEL) and haxored my .htaccess then uploaded it..

    🙂 Dunno — it’s fixed, and like i said, no big deal unless it happens again — then that’d be weird.

    I’ve had clients who were using an ftp program which did not immediately upload a file but held it in a queue, uploading it later – oops. But in your case, I am sure it couldn’t have been related to something on your end – more likely it was the cat.

    oh yeah, my ftp voyager software was closed also 🙂

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘odd error in server logs’ is closed to new replies.