Support » Plugin: WP Spell Check » Well-intended but misguided

  • benrock88

    (@benrock88)


    I really wanted to like this plugin.
    I am a writer. I learned spelling and grammar in school, but I am human, so I make mistakes. This sort of utility can be very useful to save time with editing. The spelling checker in Microsoft Word is a model of a spelling checker for me. I wished that this one were similar.
    I am developing a site with about twenty articles (posts and pages) and about 40,000 words.
    On one hand, it did catch two spelling mistakes in the first post, and I thank the developer for this.
    On the other hand, I tend to write in the active voice already, and it is NOT an error to write “to be” sometimes, contrary to what this program flagged.
    It also changed upper- to lower-case at the beginning of post, including the title and the first sentence. I could repeat this error of the plugin. I had earlier watched the video about how to use it and did nothing unusual.
    I am writing in English, but preparing for translation, so I started to use it post-by-post. (If you scan the whole site, even with one translated post, then all of the words in the other language are flagged as errors.)
    The most disappointing thing about this plugin to me is that it injects html code into my text, such as “<span>… hiddenSpellerror… </span>”. In other words, the buttons “Highlight spelling” and “Highlight grammar” do not only display what the developer considers errors (many of which were not errors, in my view), but pollutes my posts with their injected html code! Please do not hide anything in my posts.
    I de-activated and deleted the plugin, but only discovered the polluted posts after viewing them again.
    It took me hours to switch to text mode and to delete the injected code.
    I believe the the developer’s intentions were fine. I urge them to use Microsoft spell checker as model – and to let the writer keep control of their text, please, specifically to inject no html in the post or page.
    If you are not a writer, then perhaps this would be more useful to you.

    • This topic was modified 1 year ago by benrock88.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WP Spell Check

    (@wpspellcheck)

    Hi @benrock88
    Thanks for the thoughtful feedback and I apologize for the trouble you are going through.
    We have no intention of injecting code into your pages/post and messing up your writing.

    We have not been able to replicate this issue on our staging sites and testing environment, but we’d be happy to look into the issue and try to fix it asap.

    If you are open to that, please send us an email to support at wpspellcheck.com and we will look into it right away.

    Thank you

    Plugin Author WP Spell Check

    (@wpspellcheck)

    Hi there,
    We found the source of this issue and just released v7.1.11 with a fix for this specific issue.
    This happened when you tried to save the post as a DRAFT and we just put a fix for it.
    Please download and try the latest version and let us know if the issue persists.
    Thanks
    Moe

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Well-intended but misguided’ is closed to new replies.