WordPress.org

Support

Support » Plugins and Hacks » [Resolved] [Plugin: After the Deadline] Changes HTML Tags to Non-Compliant ALL-CAPS

[Resolved] [Plugin: After the Deadline] Changes HTML Tags to Non-Compliant ALL-CAPS

  • Chip Bennett

    @chipbennett

    Theme Review Admin

    Today I installed the After The Deadline plugin to test it out.

    I use the HTML editor by default. I opened a draft post, and clicked the [PROOFREAD] quicktag button. AtD scanned the draft and returned no errors. However, the plugin apparently changed all of my DOCTYPE-compliant lower-case HTML tags to non-compliant ALL-CAPS tags.

    I can find no way to modify this behavior. The plugin offered no option to ignore whatever “rule” modified my HTML tags, and there are no configurable options on either the AtD plugin options page or on my profile page.

    Why on earth would a modern proofreading plugin change HTML tags to a format that has not been standards-compliant for several years now?

    http://wordpress.org/extend/plugins/after-the-deadline/

Viewing 15 replies - 1 through 15 (of 32 total)
  • Hi Chip,
    I wrote After the Deadline. Here is what’s happening:

    When you click proofread (I presume you’re using the HTML editor), your text is transformed into the browsers representation of HTML. After you make your changes and click edit text, the browsers representation of the edited text is placed back into your editbox. The non-standard compliant representation coming back is courtesy of your browser.

    I tried a test post on Firefox 3.5.5 on MacOS X and it didn’t change the case of my tags.

    Here are some work-around ideas:

    – Use the visual editor to proofread your posts. AtD can be activated with the green checkmark button.

    – Try another browser or upgrade your current one (I can’t guarantee this will solve it).

    — Raphael

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Thanks, Raphael!

    The test I did was using IE8/WinXP. I will test later today using FF 3.5/Kubuntu.

    Why am I not surprised that IE is to blame?

    For various reasons, I both prefer and need to use the HTML editor. Hopefully FF won’t exhibit the same behavior.

    Since this problem only exists when using the HTML editor (and then, only because it has to render the HTML), yet when running AtD while using the visual editor, is there any way to have AtD render using WordPress’ visual editor rather than the browser, when using the HTML editor?

    (Hopefully that makes sense.)

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Raphael,

    I tried running AtD under FF 3.5 and Kubuntu 9.10, but the plugin threw an error about not being able to contact the spell check server (or something?), and quit.

    I’ll re-create again tonight, and give you the exact error message.

    In that case, though, none of my underlying HTML was touched – though that’s probably not a very meaningful observation.

    Ok, cool. Let me know what happens. I’m subscribed to the after-the-deadline tag so your response will go to my email.

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Here’s the error I get:

    There was an error communicating with the spell checking service.

    parsererror: undefined

    The plugin starts. I can see the display switch to visual editor, and then I get the dialogue with the above error message.

    When I click OK, the display returns to the HTML editor, with the content apparently unchanged.

    I think that’s the best I can give you, without perhaps some more specific questions.

    What does it do in the visual editor? If you could give me the text causing it that would help too. You can email it to me raffi at automattic dot com.

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Oh, that would require using the Visual Editor. 🙂

    I’ll try that this evening, and report back.

    (Sorry for the delay; weekend was spent preparing for hosting family for Thanksgiving.)

    p.s. glad to hear you’ll be on WPWeekly next week!

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Okay, so I tried using the visual editor, and don’t get any errors. The spell-checking works as expected.

    What I did:

    1) In profile, un-checked “disable visual editor”
    2) Opened a draft post (consisting of a raw URL)
    3) Clicked the proofread button
    4) Proofread/spellcheck ran
    5) In profile, checked “disable visual editor”
    6) Returned to draft post, refreshed page (to reload HTML editor)
    7) Clicked proofread button
    8) Same error as above was returned.

    There is no specific text that is causing the error, as far as I can tell. I created a new post, consisting of the text: “This is a test.”

    I still got the same error.

    There seems to be a problem invoking the spell-checker at all, when using the HTML editor.

    Hi Chip,
    Would you be willing to give me a contributor level account on your blog so I can look at what’s happening? Last time I had a tough to figure out issue, I learned that the user had an SSL enabled backend and I was able to update AtD to work with that.

    If you’re not comfortable with that, we can continue to troubleshoot this way. Do you have Firebug installed? It’d be helpful to know:

    – What (if any) errors are showing up in the console
    – What are the results of your request
    – What did your browser try to POST

    You can email me raffi at automattic dot com.

    — Raphael

    Oh, one other thing to consider. This will at least tell me if the problem is something in your WordPress (in which case an account would help) or the browser.

    Can you visit the AtD/jQuery demo and see if it works for you:

    http://www.polishmywriting.com/atd_jquery/demo2.html

    If it does, then we’ll move forward as above. If it doesn’t, I’ll get a Kubuntu live CD, FF 3.5, and see what happens.

    — Raphael

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Raphael,

    You’ve got email. Your contributor account is created.

    I’ll check the demo later this evening.

    Slick demo, btw!

    Chip

    Hi Chip,
    I haven’t received an email. Did you put two T’s into the automattic? After working here I can’t spell automatic without wanting to put two T’s into it.

    And thank you much Sir! I see the problem. The AtD/HTML Editor is trying to post to the wrong thing. The /wordpress/ directory trips it up. I don’t know why yet (both the visual editor and the HTML editor refer to admin_url()). Ideally both should be broken. Curiouser and curiouser said Alice.

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Raphael,

    I sent a separate email; not sure why the one out of WordPress didn’t send.

    Anyway, your demo works just fine for me with Kubuntu 9.10 and FF 3.5.

    Color me stumped…

    Chip Bennett

    @chipbennett

    Theme Review Admin

    Raphael,

    I noticed that you were able to poke around. Were you able to figure out anything?

Viewing 15 replies - 1 through 15 (of 32 total)
  • The topic ‘[Resolved] [Plugin: After the Deadline] Changes HTML Tags to Non-Compliant ALL-CAPS’ is closed to new replies.