In-App Features

Please fix the restricted keyword feature

3y agoCompleted

For example: I want to restrict the EM in EM 2024, but this will be restrict Em in Emily or Emma as well. Please fix this problem.

5 comments

  1. You are right Hiền Lâm. As our filter triggers every time there is a new letter added on the text field, as soon as there is an M typed, our filter will detect it as a restricted keyword and delete it. We'll implement a delay so it works as you expect it. Thanks for letting us know

    1. Alejandro Lozdziejski Hi, so this doesn't work until now.

      For example this listing: https://famwalls.com/products/personalisiertes-herz-glowligh…

      My regex is : ^[^a-z]|[^a-zäöü]|[^a-z]$

      only a-z at the first character

      a-z and ä,ö,ü in the middle

      and a-z at the end.

      But when type läna, it deletes the ä right away as soon as I type l > ä , no chance to type the whole word.

      I have to type: lana and then replace the "a" with ä afterward. Really complicate

  2. Can be achieved using current functionality

  3. Please use \bEM\ as the regexp:

    Here's a breakdown of this regular expression:

    \b is a word boundary anchor. It asserts a position at the start or end of a word.

    EM is the literal string we want to match.

    \b again asserts a position at the end of the word.

    This pattern ensures that "EM" is matched only when it is a whole word, such as in "EM 2024", but not when it is part of another word, such as "Emily" or "Emma".

    1. Alejandro Lozdziejski Thank you for your reply, but unfortunately, whether it’s \bEM\ or \bEM\b, it’s still not working.

      When I use \bEM: I can type EM or anything including EM.

      When I use \bEM\b: I type E M and they disappear. Apparently, I don’t have any chance to type Emily or Emma because the characters will be gone when I type the second character.