Forum Replies Created

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

    (@mcrebbe)

    Thanks Moshu.

    Thread Starter mcrebbe

    (@mcrebbe)

    CORRECTION:

    I was given the wrong link for voting. If you want to vote for me please use this link.

    Thanks,

    MC Rebbe

    Thread Starter mcrebbe

    (@mcrebbe)

    Yup, it worked perfectly. The site now validates. Thanks.

    If anyone else wants double check in their browsers, that would be cool, otherwise this is closed.

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    That’s weird. IE6 on Win XP is one of the setups I’m testing on and I’m not seeing any probs?

    So the question is if I open the relevant files and re-save them as UTF-8, is that likely to solve the problem, or do I actually need to remove/alter specific characters?

    Thanks,

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Thanks Otto. I’ve never seen those weird characters before, as they don’t show up in any of the 4 browsers the site has been tested with. But I take your point.

    BTW, which browser/version/platform are you using?

    Thanks,

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Moshu – Thanks, it appears that I may have been saving things as ANSI instead of UTF-8. If I open the relevant files and re-save them as UTF-8, is that likely to solve the problem, or do I actually need to remove/alter specific characters?

    Otto – To which characters are you refering?

    Haecceity – According to my edition of The Concise Oxford English Dictionary, “Although toothcomb and fine toothcomb arose from a misunderstanding of fine-tooth comb, they are now accepted as established expressions.”

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Funny you should mention that Moshu, it was only after placing those codes, that the problem first occurred.

    Having said that, those webring codes have since been cleaned up to be XHTML compatible. If they are still not, perhaps you could suggest what needs to be done to them?

    Thanks,

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Paul,

    Thanks, but I tried what was in that thread ages ago – it solved nothing. As I & others have already said above, it’s not a whitespace issue.

    Thread Starter mcrebbe

    (@mcrebbe)

    Thanks Podz.

    I already tried all of the above a couple of days ago:

    – The problem happens regardless of whether or not plug ins are activated.

    -The problem only happens when pinging. If pings are removed from the options/writing tab, the problem does not happen, with or without plug ins activated/deactivated.

    – Nevertheless I have tried this all again, with exactly the same results.

    – The exception is the ‘No Ping Wait’ plug in, which I started experimenting with a couple of days ago. When it is activated, the problem disapears.

    BTW: None of this was a problem on the old server, though thinking about it, I was running versions 1.5.2 (mcrebbe) & 2.0 (thetechnofile) on that server. I did upgrade both blogs to 2.0.2 on the old server (and everything seemed fine) before moving to the new one, but I didn’t actually post anything on the old server after that upgrade.

    – I thought it was the pinging too. However, I did a clean install of WP 2.0.2 on the new server (using fantastico), added the original very long list of pings to the options page, did a test posting and everything worked perfectly…then I imported my wordpress database and the problem appeared again?

    Thread Starter mcrebbe

    (@mcrebbe)

    Sorry Samboll. I misunderstood your original response. My bad. You were being constructive.

    However, I did check for whitespace in the files mentioned in the erro message + wp_config.php and the problem still persists.

    I also did a clean install, which worked perfectly until I imported my original database into it, at which point the problem replicated.

    ???

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Update:

    I have dramatically reduced the size of my pings list on https://www.mcrebbe.com by replacing it with list #2 suggested here:

    https://www.instant-info-online.com/wordpress-compressed-all-inclusive-ping-list.html

    I am still having the same problem regardless.

    Help!

    Thread Starter mcrebbe

    (@mcrebbe)

    OK, so I’ve spoken to my hosts and tried various things:

    I did a clean installation of WP 2.0.2 (using Fantastico) in a sub domian and editing/publishing posts worked perfectly…until I imported my existing database, after which I got exactly the same error again. We tried repairing the database and still get the same problem.

    My hosts suggest this means it is neither WordPress nor a hosting issue, but a database issue.

    HOWEVER, when I remove my largeish list of pings (or just try with a couple of pings) the problem disapears. Which makes me think that what is happening is that WordPress is timing out whilst trying to ping my long list?

    The only possibly illogical thing about that thought, is that with the clean fantastico install (before the databse was restored), WordPress would hapilly ping everything on the long list.

    Searching the Fora, I did find this plug-in https://somethingunpredictable.com/wp-no-ping-wait/
    Which seems to solve the problem (which would appear to support the idea that WP is timing out).

    However, I’m not convinced that any pinging is actually happening with that plug in activated, as pings don’t seem to show up on Technorati or elswehere, so I’m wondering if all it is actually doing with WP 2.0.2 is to switch off the pings, which is how it is solving the problem?

    My hosting company have suggested batting it back to the WP fora, so does anyone have any comments/suggestions?

    BTW it is not, as far as I can tell, a whitespace issue. I have doublechecked and reuploaded both files mentioned in the error message as well as the wp_config.php and it makes absolutely no difference whatsoever. I still get the same error messages.

    It has been suggested the database may be corrupted in some way. If that’s the case it means doing a clean install and manually copying everything across, which I’d rather avoid.

    On the other hand, if the DB has been compromised, I don’t want to use a quick fix like the plug in above or reducing my ping list, only to find somewhere down the line that I have to recreate the databse manually…by which time I may have added a couple of hundred more posts.

    Help please!

    Cheers,

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    Thank for that Podz. I’ll get onto them

    MC

    Thread Starter mcrebbe

    (@mcrebbe)

    I was not.

    Perhaps someone has something constructive to add?

    Thread Starter mcrebbe

    (@mcrebbe)

    OK, I’ve finally sorted this. Apparently the problem is a known issue that happens when a database is exported using PHPMyAdmin from a server running Ensim. The solution is to do a data dump at the command line.

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