Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
AudioEye is causing problems in the community.
When I write posts (like this one) or comments, the "AudioEye Accessibility Helpdesk" window pops up every time I write a question mark: ?
Also, when posting this plugin adds data to the post. There are a lot of posts in the forum now where we can see text added at the bottom:
I don't know what causes this, and it's not all the time. A moment ago I made a post and I just couldn't remove that addition. I tried editing the post, but I still got the same error message as in the image above. I then switched from Chrome to Firefox, and then I could actually edit that text so that it disappeared.
There's a whole bunch of html being added to the post by the plugin:
AudioEye issue is reported as resolved! Thanks again, @Lech_Miszkiewicz for confirming fix.
Please feel free to send any additional feedback 😊
And of course, for some reason when I posted this particular post, that additional text that I'm talking about was not added... But it's not just me, it's easy to search the community to find problematic posts. Like this one: https://community.qlik.com/t5/App-Development/concat-works-randomly/td-p/2515921
When trying to post this comment (that I now apparently have managed to post at last since you are reading it, I at first couldn't because of an error message and the added strange text at the bottom. I just couldn't post the comment at all, no matter how I edited it. Had to change browser again.
Same happens to me, for example posting this reply.
This is so weird...
Thanks for bringing this to attention
Thanks @henrikalmen for bringing this up! I will be discussing with the team to correct the issue when posting.
I sent a private message, but adding here too.
"We updated some permissions and the issue should be resolved. Let me know if you are still seeing the html error message and additional content when submitting your post."
Thanks for the quick response. I'm using this reply as a test and I'm still seeing the error
According to posts made elsewhere, this has not been resolved yet. Just FYI for those following the thread.
Thanks @Or for keeping the post as up to date as possible with info.
We are still troubleshooting with AudioEye on the additional text/content added to posts for accessibility compliance.