Skip to main content
olimarrio
Gainsight Employee ⭐️
olimarrio
Gainsight Employee ⭐️
May 25, 2021 12:36 PM UTC

Grammarly Browser Extension Issues - Now Automatically Disabled - 3rd June

Hello everyone,

 

It has come to our attention that the Grammarly Extension has been causing an issue with some of our text editors across the platform. This occurs when text is typed into the editor and Grammarly is triggered to check spelling and grammar - causing the text to disappear and the rest of the text box functionality to break.

 

We have been in contact with Grammarly and they are aware of the issue. Their developers are currently analysing the cause of this issue and are working on a fix - however, no time-frame has been provided for a solution.

 

In the meantime, we suggest turning off the Grammarly extension whilst using your community platform. To do that, please click the G icon on your browser's toolbar and toggle Check for writing suggestions and Show definitions and synonyms via double clicks off.

 

We will keep in close contact with Grammarly and keep you updated once more information becomes available.

 

Thanks,

 

Oliver

 

 

    17 replies

    Show previous replies
    Ilan B
    Ilan B
    Contributor ⭐️⭐️⭐️⭐️
    Aug 10, 2021 2:10 PM UTC

    Hi @olimarrio,

    Are there any updates about fixing this? With Grammarly disabled, and my poor-spelling, a number of spelling and grammar mistakes are making it through :face_palm_tone1:. 

    Thanks,

    Ilan

    Translate
      Rudi
      Rudi
      Contributor ⭐️⭐️⭐️
      Aug 21, 2021 10:53 AM UTC

      Also looking for an update on this, guys!

      Translate
        olimarrio
        Gainsight Employee ⭐️
        olimarrioAuthor
        Gainsight Employee ⭐️
        Aug 24, 2021 2:14 PM UTC

        Hi @Ilan B & @Rudi,

         

        Unfortunately I don’t have good news to provide for this. :disappointed: We have been chasing Grammarly for a resolution but they have informed us they cannot find a quick fix and therefore they have closed our case.

         

        We are obviously very frustrated about this. We’ll discuss internally what our options are but they will be quite limited apart from a full change of our text editor.

         

        Apologies for not being able to provide you with a more positive update! 

        Translate
          Ilan B
          Ilan B
          Contributor ⭐️⭐️⭐️⭐️
          Apr 5, 2022 8:55 AM UTC

          Hi @olimarrio and co,

          Do we have any updates here? It’s a real pain point for me and other content creators using Insided. 

          Thanks,

          Ilan

          Translate
          Ilan B
          Ilan B
          Contributor ⭐️⭐️⭐️⭐️
          Apr 6, 2022 8:56 AM UTC

          FYI. If you install the desktop Grammarly software, it seems to work fine with Insided 😇

          Translate
            caultman
            Contributor ⭐️
            Jul 31, 2025 5:17 PM UTC

            Nudging an old thread - We’re getting reports from our users that the same issue seems to be occurring on the Enhancements Request form. Since it sounds like previous fields were set to disable Grammarly checking (which seems to still be the case), I’m wondering if that same code wasn’t deployed to the Enhancements request functionality? 

            When trying to enter text and Grammarly performs a check, it causes the Request form to try and close out. I assume that Grammarly hasn’t provided a fix for this, but is it possible to apply the Gainsight-side “disable code” to the Enhancements request form as well?

            Translate
            Kenneth R
            Kenneth R
            Expert ⭐️⭐️
            Aug 5, 2025 12:04 PM UTC

            Hi ​@caultman - Are you sure this question is related to our Gainsight CC platform?  It sounds like your question might be related to Zendesk - is that possible?

            Translate
            Terms & ConditionsAccessibility statement