Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter 4mostip

    (@4mostip)

    The plugin <WP HTTP Compression(version 1.0)> is the one causing the problem.

    Why it is a problem is as yet unknown, but it has not been updated since 2012-7-11 and compatibility has not been verified beyond WPv2.9.2

    Since original installation, I later implemented use of Cloudflare as Content Delivery Network, with compression option activated. I suppose this could perhaps be source of confusion for <WP HTTP Compression>. In any event, the latter is now redundant and can be suppressed.

    Topic Resolved
    Steve.

    Thread Starter 4mostip

    (@4mostip)

    @esmi – debug and error logs reveal nothing useful.

    However, researching the forum history turned up some old tips I had neglected to try before asking for help. Shame on me – sorry.

    • disable all plugins
    • swap themes
    • increase RAM allocation

    Disabling plugins fixed this issue.
    Now just remains to isolate the little monkey responsible.
    Steve

    Thread Starter 4mostip

    (@4mostip)

    PS Forgot to mention, this problem is NOT specific to WP version 3.8
    Steve

    Thread Starter 4mostip

    (@4mostip)

    PS I forgot to mention that the update itself usually completes OK, just does not report as such.

    Also sometimes leaves a .maintenance file behind.

    Hi Sheen,

    Firefox now displays your pages PERFECTLY when instructed to expect Windows-1252 as the character set!!

    What browser and operating system are you using to look at the site?
    I’ll try to take a peek “through your eyes” ….

    BTW – helping lovely ladies is classic nerd displacement activity.
    A pleasurable rosy glow for being a good neighbor – substitutes nicely for the guilt feelings over never taking exercise, not sleeping normal hours, eating junk, drinking junk, etc etc.

    LOL
    Steve

    On browsing through her site – it seems that the odd character still misbehaving is coded in Windows-1252 or ISO-8859-1 , so your db converter should fix any remaining problems nicely.

    Only concern is what the side-effects (if any) might be on the existing utf-8 coded records. Would it be safer to do a two stage conversion via ISO-8859-1 ?

    @kmessenger

    Isn’t wp-config the place to change the character set?
    If so, could you remind us of the command syntax, plz.

    Secondly, the existing mysql data base probably needs a clean-up, so she will need
    1) the SQL command to export all posts and comments,
    2) some text editor advice on how to batch convert utf-4 or UTF-4 to utf-8 (or UTF-8) , i.e. a case insensitive solution
    3) the SQL commands to import the updated posts and comments file to replace the originals.

    Steve

    <!DOCTYPE html>
    <html dir="ltr" lang="en-US" xmlns:og="https://opengraphprotocol.org/schema/">
    <head>
    <meta name="msvalidate.01" content="3234A16C79765EEE37D0A7874DE3FA3B" />
    <meta charset="UTF-4" />

    The problem lies right there in the meta charset which is set to UTF-4 when it should be UTF-8

    I’ve browsed your page with FF and it IS definitely UTF-8.
    It displays just fine for me – probably because I’ve set up my browser to scan for the ACTUAL charset (i.e. to ignore the announced one).

    Your problem is that your header section is announcing “utf-4”.
    (which I have never even heard of …)

    So – you need to get that line to read

    <meta charset=”UTF-8″ />`

    Over …………….

    Steve

    PS if you don”t want to publicly refer to the URL here, mail my user name at gmail dot com
    Steve

    Hi Sheen,

    I don’t know – my browser actually gives me names for character sets like UTF-8, Windows-1252 or ISO-8859-1 ……..

    Give me your URL expressed in text so the filters don’t mangle it, and I’ll have a look at the page for you.

    Skip the httxx.. stuff … I just need domain, directory, and page such as

    Domain is “My Domain name without TLD”
    My TLD is “com or org or net or whatever”
    My Directory is “root” or “directory path”
    Page name is “basename, i.e. without extension”
    Extension is “php or html or whatever”

    Capiche?

    Steve

    When I hit this issue it is usually a mismatch between the charset my website announced in it’s headers and the charset it actually output.

    There is an easy test – I only use Firefox so please bear with me – go to View tab and select character encoding. Try the different charset options given (it won’t do any damage!).

    If you can find a charset with which the page displays correctly then that is the charset you are actually using on the web page.

    So now it is just a matter of changing one or the other into agreement.
    Probably is easiest just to change the header section. If the params in your header section are different or missing, then just set charset to the charset FF says that you are actually transmitting!

    Steve

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