Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted February 9, 20223 yr Hi there, I found out a very silly bug with the plataform, regarding the new feature that holds content for approval if an email adress is detected. If an image with an "@" symbol in its filename is inserted, the post is held for approval. We had old custom emoticons with file names such as: biggrin@2x.png ohmy@2x.png sad@2x.png tongue@2x.png happy@2x.png ph34r@2x.png sleep@2x.png wink@2x.png smile@2x.png Whenever any one of them was used, the post would be held for approval. I deleted these emoticons, but maybe this is something you want to take a look into. Thanks, Gabe.
February 9, 20223 yr Community Expert Before I look further into this, are you holding URLs with an @ in moderation? If so, thats what will be causing the problem. This images by the way are the retina versions of emoticons.
February 9, 20223 yr Author @Marc Stridgen are you holding URLs with an @ in moderation? I am not sure that I understood the question. I simply enabled the new feature below, available in the Word Filters section, Spam & E-mail tab: Quote Added the ability to moderate or replace posted email addresses with an obfuscated placeholder in content. So, I know that this is causing the issue, as explained in my original post. What I am reporting here is that, in my opinion, this filter should ignore filenames from images/emoticons. Cheers Edited February 9, 20223 yr by Gabriel Torres
February 9, 20223 yr Community Expert @Marc Stridgen I am not sure that I understood the question. I simply enabled the new feature below, available in the Word Filters section, Spam & E-mail tab: So, I know that this is causing the issue, as explained in my original post. What I am reporting here is that, in my opinion, this filter should ignore filenames from images/emoticons. Cheers I would suspect you are probably correct indeed 🙂 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
March 8, 20223 yr Community Expert Solution A new version (4.6.11) has now been released which resolves this issue. Please upgrade to the latest release in order to get this fix.