- Betroffene Version
- WoltLab Suite 3.1
I use Grammarly when writing articles for other sites and it works on numerous other forums too, but not on WoltLab.
Is there a reason for this? How could I get it working or is it a Grammarly issue?
I use Grammarly when writing articles for other sites and it works on numerous other forums too, but not on WoltLab.
Is there a reason for this? How could I get it working or is it a Grammarly issue?
I asked about this some time back. I was told that support will come in new releases.
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.
You may also try https://languagetool.org/
I don't if it works with WSC, but i heard a lot good opinions about it (but not tried it myself yet)
Thanks for your replies and I'll contact them directly.
Edit:
Support ticket sent to Grammarly.
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.
I received a very swift response from Grammarly:
ZitatAlles anzeigen
Thanks for contacting Grammarly!
We don’t currently offer integration with WoltLab, but thank you for letting us know that it’s something you’d like to see. I’ve forwarded your request to our product team so that they can take it into account when making development plans.
To check whether a text field on your website (https://www.argentinaexpats.org) is compatible with Grammarly, please follow this link:
https://support.grammarly.com/hc/en-us/articles/115000090392
Please also note that our extension works only in a non-read-only text area, a non-read-only content editable, and an iframe with a content editable body. There are exceptions and conditions to this rule; for example, Draft.js fields are not supported either.
If Grammarly doesn’t work on your website, you can always use the Online Editor at https://app.grammarly.com.
I hope this helps, but please don’t hesitate to contact me for any further assistance. We apologize for any inconvenience.
Best wishes,
Julia
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?
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).
Nope
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?
I've replied to Grammarly asking them to look at it again, for whatever good that will do.
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.
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!
I hope WoltLab supports Grammarly in the future. Adios!
Wrong direction Hope Grammarly will support Redactor II (and Woltlab)
Wrong direction Hope Grammarly will support Redactor II (and Woltlab)
I suppose.
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.
At least they are helpful in replying to my emails:
Thank you for your message.
I have forwarded this information to our technical team; I will get back to you with their comments as soon as I hear back from them.
Thank you for your patience as we are looking into this!
Sincerely,
Julia
I will get back to you with their comments as soon as I hear back from them.
Did you heard something from them again?
Did they heard something from them again?
I doubt he did.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!