As a rule, BLC can only check custom fields that contain HTML or nothing but a single URL. Based on the repeater field docs, it probably doesn’t match those requirements and can’t be checked.
Thread Starter
pascal.k
(@pascalklaeres)
But there is only HTML or single URL saved at wp_postmeta. When I search my wp_postmeta table to “repeaterfield_1_content” I only see HTML code.
Is there no solution I can use these meta_key to be checked by BLC?
My idea was to add these meta_keys to “BLC Settings > Custom fields”. But it’s not working. This is the setting I used:
html: repeaterfield_1_content
html: repeaterfield_2_content
html: repeaterfield_3_content
html: repeaterfield_4_content
html: repeaterfield_5_content
html: repeaterfield_7_content
html: repeaterfield_8_content
Are you sure it’s really HTML and not some XML-based format?
In any case, try the same settings but without the space after “html:”.
Thread Starter
pascal.k
(@pascalklaeres)
Yes. I fond the error. There was a space between “html:” and “repeater…“. This needs to be replaced. Then this is working fine. It’s surely not best practice, but it works fine.
Solution:
html:repeaterfieldname_fieldid_fieldname
html:repeaterfield_1_content
html:repeaterfield_2_content
html:repeaterfield_3_content
html:repeaterfield_4_content
html:repeaterfield_5_content
html:repeaterfield_7_content
html:repeaterfield_8_content
...
