If you use the default WP REST API, then you can try providing fields like they are implemented on the WordPress level. For example, listing is a custom post type āhp_listingā, and attributes (custom fields) are stored as meta fields with āhp_ā prefix.
For example, if you added an attribute with ācustom_fieldā name, then it can be saved as a post meta field āhp_custom_fieldā. For selectable attributes (of Select, Checkboxes, Radio Buttons types), values are stored as custom taxonomy terms, the taxonomy name would be āhp_listing_custom_fieldā in this case.
If youāre familiar with coding, I would recommend creating a custom REST API endpoint instead register_rest_route() ā Function | Developer.WordPress.org Then you can use the HivePress way of creating listings without the need to know how the fields are implemented:
Iāll try to explain a little more. I see the changes on the listing edit page. But when I go to the listing page as a user, some (this is important!) images are not listed.
I tested several media (videos and images) of different formats, such as png and jpeg/jpg, as well as media uploaded by different users on the site, but I could not find a pattern. Some media files are presented correctly, and some are not.
I tried another option for uploaded media posts by the author, but it did not help to solve the problem: