Jump to content

Community

Davyc

Grammarly will it come back to IPS

Recommended Posts

4.4.4 Sees Grammarly disabled - I must admit I never had any problems or issues using Grammarly in any iterations of the IPS suite nor in any of the apps.  Since it is now disabled it has compelled me to use another called Ginger, which whilst good, it is not as good as Grammarly.  I can only say thank goodness that I did not upgrade to the paid version or I would have been out of pocket as I only use it on IPS sites.  With this in mind, is there not an opportunity to discover what issues are prevalent with Grammarly and can they be surmounted?  I would love to see this come back.

With thanks

:happy:

Share this post


Link to post
Share on other sites

Grammarly and CKEditor do not play well, and we received several bug reports about the same issue(s) related to how Grammarly modifies the DOM within an editor. In short = yes, there was an issue (or a couple of very related issues), and there was no way for us to resolve this outside of disabling Grammarly in the editor.

It may return when we reach a point where we can upgrade to CKEditor 5. It is my understanding that the CKEditor devs and the Grammarly devs are working together on maximum compatibility, but won't be backporting that to CKEditor 4.

Share this post


Link to post
Share on other sites
6 hours ago, bfarber said:

Grammarly and CKEditor do not play well, and we received several bug reports about the same issue(s) related to how Grammarly modifies the DOM within an editor.

Thanks for the info, though most of it goes above my head lol.  I have to say that I used Grammarly for a good while (along with a few others) and never had an issue with it.  At present I have moved to another Grammarly type spell checker called Ginger and there are no problems with that either.  Having said all of that, I do understand that if there are technical issues then I accept that.  Hopefully, when you can upgrade to 5 Grammarly can come back into the fold.

Much appreciate the response and explanation :biggrin:

Share this post


Link to post
Share on other sites

I only found an issue when I went back to read an old topic and noticed side scrolling going on. After nailing the post and grammarly user which caused it, went back through the members post history to find multiple pages effected by it. 

Was an easy fix in the end, I told him I would ban him if he didn’t stop using it. He stopped. 😄

Share this post


Link to post
Share on other sites
3 hours ago, day_ said:

Was an easy fix in the end, I told him I would ban him if he didn’t stop using it. He stopped.

I would have tried this, but it would have been somewhat counterproductive to ban myself lol.

I honestly had no idea that a spell checker could cause such problems - just goes to show that you never know.

:biggrin:

Share this post


Link to post
Share on other sites

The majority of reports we get were along the lines of "I can't click the Quote/Edit/Options links below this post". We'd investigate and find that Grammarly had inserted a large div into the post which was basically sitting on top of those links, making them unclickable. The issue mostly manifested when editing posts which had quotes in them, but this was not a sole factor.

In any event, as we have no control over Grammarly's behavior or CKEditor's behavior in this context, the best we could do to prevent issues for our clients was to prevent Grammarly from inspecting the post content. You can still of course use their standalone app to write up posts, and then copy/paste those posts into the editor afterwards.

Share this post


Link to post
Share on other sites

Yeah I have seen the Grammarly problems first hand.

One thing that concerns me though, if grammarly can insert its div and its accepted into the post what is there to stop a user being a PITA and doing it/worse themselves with chrome dev tools?

Share this post


Link to post
Share on other sites
2 hours ago, sudo said:

...... what is there to stop a user being a PITA and doing it/worse themselves with chrome dev tools?

I believe that should be addressed by "Moderation", up to and including the step which @day_ mentioned.

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...