Josh Crawford

Looks like this is a recent Neo update causing this, as I've just updated to 2.9.11 to find this issue (Previously on 2.8.14 where this was fine). The problem is...

Should be fixed for the next release. To get the fix early, change your `verbb/field-manager` requirement in `composer.json` to: ``` "require": { "verbb/field-manager": "dev-craft-3 as 2.2.4", "...": "..." } ```...

Yeah, interesting. I suppose it just depends on how far we want to run with this idea - not just limits, but other things related to field options. I'll have...

@themccallister It would likely be an additional model for Ratings - just because a rating has a few things associated with it (the actual rating, text, user, etc). This would...

@madebyshape Not in the slightest - you're more than welcome to build on-top of, or take anything from the Comments plugin. Its on our very long-term todo list, but this...

Are you able to provide the data that you're trying to import, so we can replicate it?

I wasn't able to replicate this sorry, even with the fields export. Possible related to this Super Table issue https://github.com/verbb/super-table/issues/474

@vieko Search would be a nice touch, but a reasonable amount of work to implement (not impossible), so its probably on the back-burner for the moment! @vaughn-taylor I'll consider this,...

This should be fixed in [3.0.0-beta.23](https://github.com/verbb/feed-me/releases/tag/3.0.0-beta.23).

For your first point, the current settings aren't overly useful in having a blacklist/whitelist setup. There's not much benefit to adding a string to the blacklist, then only to add...