How can I get Grammarly to work?

  • I asked about this some time back. I was told that support will come in new releases.

    Smile , it's good for health

  • Grammarly randomly enables and disables support for various editors as they feel comfortable. It did work for quite a long time until they decided to stop supporting the editor for an unknown reason, refusing to explain anything to us. We did make efforts in the past to work around their block, but because of the way their detection works, this is a battle we cannot win.


    If you want to use Grammarly, then please contact their support and ask them, maybe they'll listen to their customers at least.

    Alexander Ebert
    Senior Developer WoltLab® GmbH

  • I tweeted tagging Woltlab and Grammarly in last July. There was no response to that Tweet. I hope this time there will be some difference.

    Smile , it's good for health

  • I received a very swift response from Grammarly:

    I don't understand all that to be honest.

  • We did make efforts in the past to work around their block


    Isn't WSC 5.2 using Redactor 3? Because from what i know, Redactor 3 has Grammarly support (and an option to disable it since 3.0.7).


    What about BeyondGrammar as alternative for Grammarly?

    Roses are red, Violets are blue Unexpected '{' on line 32

  • Isn't WSC 5.2 using Redactor 3? Because from what i know, Redactor 3 has Grammarly support (and an option to disable it since 3.0.7).

    No, Redactor 3 is a complete rewrite using vanilla JS, breaking with all existing APIs, therefore WSC 5.2 will use an enhanced and optimized version of Redactor II instead.


    Fun fact: Grammarly was supported in Old Redactor, Redactor II and Redactor II with an update (renamed .redactor-editor to .redactor-layer). At some point, Grammarly silently dropped support by blocking it without giving any sort of explanation. Cool, eh?

    Alexander Ebert
    Senior Developer WoltLab® GmbH

  • Perhaps you should also mention that they should support Redactor II, not (just) Woltlab. Because WSC is using the Redactor II Editor along many other applications.

    Viele Grüsse aus Stuttgart, Kind Regards from Stuttgart
    TheSonic

  • Interesting. I use Grammarly all the time while using Google Chrome, so this is a bummer. ?(


    I haven't posted in this site on years. I do lurk the forums even once in a blue moon to keep up to date. I have an expired license with branding-free and want to renew it. I'll wait until WoltLab Suite 5.2 is released. In my opinion, WoltLab is a hidden gem!


    Anyway, I felt like posting in this thread. Hopefully, I hope WoltLab supports Grammarly in the future. Adios! :)

  • Perhaps you should also mention that they should support Redactor II, not (just) Woltlab. Because WSC is using the Redactor II Editor along many other applications.

    However, especially since Imperavi (the maker behind Redactor) dropped support for Redactor II, WSC is using a heavily modified/hacked version of it. It is pretty far away from "vanilla" Redactor II with all of its extensions and bogus hacks, so there are (perhaps) certain differences the Grammarly extension has to take into consideration.

  • with all of its extensions and bogus hacks, so there are (perhaps) certain differences the Grammarly extension has to take into consideration.

    You are right, but we will nevere know that, because Grammarly dropped support for Redactor itself - even for vanilla (exactly what Alex Ebert wrote).

    Fun fact: Grammarly was supported in Old Redactor, Redactor II and Redactor II with an update (renamed .redactor-editor to .redactor-layer). At some point, Grammarly silently dropped support by blocking it without giving any sort of explanation.

    Viele Grüsse aus Stuttgart, Kind Regards from Stuttgart
    TheSonic