Open valieand opened 8 years ago
The InputfieldPageAutocomplete is meant for matching text fields only. You might be able to get it to work if you change the operator to "=" (exact match), but there's a good chance that still won't work because this Inputfield was created specifically for text matching, not for numbers. Number indexes and text indexes are fundamentally different things at the database level.
Does it mean that problem should be resolved through CUSTOM inputfield (a-la InputfieldPageAutocomplete but that works on number indexes)? Or right solution is to have it in CORE (updated InputfieldPageAutocomplete or new inputfield)?
If you have thousands of pages and these pages do not have unique identifier other than page id, then it should be possible to use InputfieldPageAutocomplete (as other inputfields simply run out of memory) with query-able {id} field (as the only unique identifier).
But it doesn't work.