Josh Crawford

> Ah okay, so it does not matter if the captcha config is present in the json export for them to appear on the integration tab. That's good to know....

Fixed for the next release. To get this early, change your `verbb/formie` requirement in `composer.json` to: ``` "require": { "verbb/formie": "dev-craft-3 as 1.6.14", "...": "..." } ``` Then run `composer...

Have you refreshed the integration after the update?

Is it that exact same error? Support should allow for any label of a custom field to contain an emoji now. Your original example showed `Example Label 🔺` which I'll...

I'll require every use-case, yes - because we need to add specific handling for it. Option labels are a good point though, which I've just pushed an additional fix for...

Fixed in [1.6.15](https://github.com/verbb/formie/releases/tag/1.6.15)

Yeah, everything is escaped now, the entire string that's saved to the database is checked for emoji's and replaced. I did also check option labels just to be sure, but...

Looks like this is actually down to the [litemoji](https://github.com/elvanto/litemoji/issues/34) library (that both Craft and Formie use) not supporting these emoji's altogether. I've filed an issue there.

FYI, this will be fixed in Craft 4.4 https://github.com/craftcms/cms/discussions/12226

Right, so that's a fair point that if you're doing things like modifying the `form` variable, you'll need to pass that into the render function. I don't want to say...