Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • LOL. I’d rather not hack a hack, but thanks very much for your post–very useful info ??

    As a joke, I’m going to switch to serving application/xhtml+xml with no negotiation and let my site die for IE users. Obviously, my site isn’t mission critical ??

    Sorry to dig up such an old topic, but has anyone had any success with this? Might someone point me to exactly where I’d put the above function in my code? Thanks ??

    Thread Starter allanh

    (@allanh)

    Sorry I didn’t post back on this–been busy. I didn’t, actually, try to disable the cache through wp-settings.php, because I got a new server and I’ve been busy migrating all of my accounts over.

    The new server is running a more modern PHP (4.3.11) and the cache problem no longer exists for me. I would suggest that perhaps this issue effects installations running < 4.3 ?

    I’ll get around to testing this hypothesis in the near future and post back with results–unless someone already has discovered this?

    Thread Starter allanh

    (@allanh)

    YUP.

    So, I went into the Write area on Greenthink.net and tried to upload a picture. It tells me that wp-content needs to be writeable, so I chmod 777. I try again and the exact same thing happens.

    This time I notice that it’s created the /wp-content/cache/ directory, so I delete it and I get the site back.

    I go back to transreality and delete /wp-content/cache/ and it’s back now too.

    I saw this in another thread, but I believe it was unresolved. I’ll try to find that thread again and see what’s up.

    Thread Starter allanh

    (@allanh)

    I also have a 24 hour old install up here: https://www.greenthink.net/ on the same server that, even after a new (beta) template and hacks to it seems to be working ok.

    I’m going to start messing with it methodically and see if I can replicate the issue.

    Thread Starter allanh

    (@allanh)

    So, I tried repairing the tables, but they all checked out as good and if they were bad, I’d be getting some sort of error anyhow.

    I manually deleted the plugin’s from /wp-content/plugins/.

    The *only* other change I’ve made is to put the del.icio.us javascript in the sidebar, but after manually removing that I’m still no dice.

    Thread Starter allanh

    (@allanh)

    Tried it. Blank. ??

    Thread Starter allanh

    (@allanh)

    The database is fine. This is running on my own dedicated server with very minimal load and all the other sites on it are running fine.

    Thanks for the fast input peoples ??

    Thread Starter allanh

    (@allanh)

    Did I mention that I was also running the site successfully after the install for several hours? I did a test post and did some config changes and everything went smoothly.

    I’m also using Firefox 1.5 on OSX.4.3 and the same thing happens in Safari and IE on my winblows box.

    Thread Starter allanh

    (@allanh)

    Well, I would, but I don’t have an admin area to do so. Literally *everything* is blank–the admin area too ??

    I’m also not utilizing *any* plugin’s. I haven’t activated either the backup or akismet plugins and I’m using the stock template from the brand new install (I deleted *all* of the files from the old install (backed up of course)).

    None of the other threads seem to deal with this issue specifcally–not that I can read. I’m still digging around, but this isn’t just the home page after I’m logged in.

    Thread Starter allanh

    (@allanh)

    BTW I did search, but to no avail. If someone can point me to a thread that deals with this, I’ll apologize profusly for not searching hard enough to find it ??

    sadara wrote:

    the problem is solved by adding the function addslashes() to the sql statement at around line 49 of functions-post.php to read:

    Well, this solves the problem of the database error, but then, as the function would suggest, it would (did in my testing) add a slash in front of all the single quotes. This is not a solution as far as I’m concerned ??

    What I did that actually seems to have fixed the issue is to add the following bit just in front of the $sql=:
    $foo = addslashes($post_content);
    $bar = stripslashes($foo);

    And then replace $post_content in the query with $bar. Not perfect, but it works.

    Oh, and this was only an issue for me when posting from email.

    EDIT: thanks to sadara for pointing me in the right direction ??

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