Grammarly

  • Affected App
    WoltLab Suite Core

    Grammarly is a free (and paid) service that allows you do to automatically spell and grammar checks within your browser. https://www.grammarly.com/


    For someone such as myself who does 'drive by posting' (time-consuming restraints from proofreading), it really is necessary. Surprisingly, our IT Staff even installed this for everyone at work.


    For whatever reason, it only seems to work when I switch the editor to HTML. If you could figure out what is suppressing it when I use the normal editor, that would be very much appreciated and help expedite our adaptation of your new software on our company forums. :)

    Edited 4 times, last by Abuse_and_Troll_Test ().

  • Probably because its not a textarea but a div. That's why the auto suggestion on Android phones is also not working in the non-html mode.

    Div alone would not be the issue (I do not think). How exactly it is being implemented here perhaps. There are other developments that use div without issue. I'm not doubting you, just confused by the standing differences.


    However the case, I would be very interested in seeing this resolved. :)

  • I understand this is not technically a bug, but I would hope this design flaw would at some point in the future is addressed. It really does come down to the simple fast that it works everywhere else except here. I would hate to think that WoltLab would intentionally ignore an issue that would exclude themselves from everyone else in a negative light.

    • Official Post

    I really appreciate your dedication, but this isn't something we're intentionally and/or accidentally prevent. As a matter of fact it is highly unclear what causes Grammarly to not attach itself to the editor, the expression that seems to be used to identify WYSIWYG editors (had to dig through the source to find it!), is clearly matching the editor - yet it won't do anything.


    All I can do at that point, is to get in touch with Imperavi to have them investigate the whole issue and possibly contact Grammarly themselves.


    Edit: Ticket sent, I'll let you know once I hear from them.

    Alexander Ebert
    Senior Developer WoltLab® GmbH

  • I really appreciate your dedication, but this isn't something we're intentionally and/or accidentally prevent. As a matter of fact it is highly unclear what causes Grammarly to not attach itself to the editor, the expression that seems to be used to identify WYSIWYG editors (had to dig through the source to find it!), is clearly matching the editor - yet it won't do anything.


    All I can do at that point, is to get in touch with Imperavi to have them investigate the whole issue and possibly contact Grammarly themselves.


    Edit: Ticket sent, I'll let you know once I hear from them.

    Thank you very much for your time, effort, and thoughtful consideration Alexander Ebert. :)

  • Code
            imperavi.com is Not Supported
            For technical reasons, we currently do not check your text on this version of imperavi.com

    On my professional grammarly plugin has issues as well.

    That's the what is shown in their website:

    https://imperavi.com/redactor/

    That is a generic message that automatically displays whenever it fails to load on a site. Hopefully, this can be resolved one way or the other so that I may incorporate the WoltLab forum software into a corporate environment.

  • I did not know about it ;)


    But since it is not working on imperariv official website, it is their issue to deal with ;)

    I hope they will resolve it .

    True which WoltLab pointing out here and we are still waiting for the follow up.

    Grammarly


    Still this will nevertheless be a strong deciding factor on our incorporation and purchase of forum software for our company forums.

  • Xenforo uses the exact same editor as WoltLab Burning Board. You're both using Redactor for your editor.


    Please look into this WoltLab



    Einstellungen_Benachrichtigungen - Einstellungen -_20130809-225542.png

    Files

  • No, XenForo uses Froala.

    Meine Beiträge stellen - sofern nicht ausdrücklich anders gekennzeichnet - ausschließlich meine subjektive und aus Erfahrung und / oder Reflexion gewonnene Meinung dar und sind nicht als Fakten zu verstehen. Meinungen sind persönliche Ansichten und benötigen keine Belege. In Deutschland gilt nach Artikel 5 des Grundgesetzes Meinungsfreiheit. Meine Beiträge stellen keine Rechtsberatung dar, hierzu bin ich nicht befugt.

  • No, XenForo uses Froala

    Yes, it does now in XenForo 2. But it uses Redactor 1 in XenForo 1 series


    I have noticed (same as WBB 4.1 using Redactor 1) that when switching to Plain Text mode there is no text style formatting displayed, not like it gets displayed with Redactor 2 because they went HTML with it (or whatever it is). Which is funny in a way, because with Redactor 2 switching to plain text HTML mode you can see all the badly nested empty tags left behind, e.t.c. Which you don't get to see with Redactor 1 or Froala using plain text mode.

  • No, XenForo uses Froala.

    Oh really? I stand corrected.


    I had not checked the code and the two really do look very simular (visually). So I was unaware that they had changed editors.

  • It seems to work pretty good as well in the Alpha version with XenForo 2 so far.

    I don't like xfv2. The overall design seems like a step backward or stuck 'as is' with no real advancement. The only thing I seem to like from it is that grammarly works and that they've finally adopted the new avatar system that other forums have finally come to accept.


    Letters avatars for members without profile photo


    Beyond that, I'm not impressed.

  • No, I'm not that keen on the new style changes either. Don't think many are to be honest reading comments about it past few days posted across different sites. But I do think the change in editor is an interesting one, maybe something WBB should have considered using instead of Redactor 2. I'm not a fan of how Redactor 2 shows all this formatting in HTML mode and appears to have been quite troublesome from the start getting things working right with it.

  • No, I'm not that keen on the new style changes either. Don't think many are to be honest reading comments about it past few days posted across different sites. But I do think the change in editor is an interesting one, maybe something WBB should have considered using instead of Redactor 2. I'm not a fan of how Redactor 2 shows all this formatting in HTML mode and appears to have been quiet troublesome from the start.

    I think sticking with Redactor 2 was a smart move. It allows for these to plug in easily


    https://imperavi.com/grafs/


    https://imperavi.com/kube/


    Imperavi has been busy and I've been enjoying their development.

  • I'm just saying that nobody had even heard of this Froala editor before, or at least it wasn't talked about until they posted a screenshot of the editor and (it was me actually) from that screenshot that found out it was Froala being used.


    I'm not saying WBB should switch to it also used. Guess I'm just a little curious what they think about it now that XenForo 2 demo site is out now live using it.

  • I'm just saying that nobody had even heard of this Froala editor before, or at least it wasn't talked about until they posted a screenshot of the editor and (it was me actually) from that screenshot that found out it was Froala being used.


    I'm not saying WBB should switch to it also used. Guess I'm just a little curious what they think about it now that XenForo 2 demo site is out now live using it.

    Well, I have encountered Froala before. They're not the 1st development to use it. It's very lightweight and while you do not usually see it in forum software it can be found in a few ticket software (support ticket type software).


    However, if they really did a little bit more research they'd know it's not known for being always mobile friendly, out of the box. Which means they'll be tweaking it themselves in order to keep "current" (which is important with mobile devices).


    Imperavi (developers of Redactor) are already planning on Redactor 3 and if you bought v2 early (as WoltLab did), you'll be getting v3 for free ;)

    https://imperavi.com/blog/marc…--get-next-redactor-free/


    So long term, WoltLab Burning Board will be well supported and business wise made the right investment.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!