Has anybody been using the Bones API addon lately? We’ve been using our own custom JSON template implementation to allow Algolia/search engines to scrape an “endpoint.” We figured we might as well use Bones as that’s exactly what it does; output JSON with an API key and some query params. But unfortunately, I’m not getting it to present valid JSON. It appears to be breaking at the Wygwam field (“content”). To be honest, I’m not looking to invest a lot of time into fixing this as we already fixed the scraping feature with our own templates but it would be nice to have ALL the fields including some of the custom fields as described in the bones docs.
TLDR; Has anybody had good results with Bones + Wygwam? Wygwam appears to be causing “white spaces” that breaks the json
********* redacted json.
:null,"photo<em>filename":null,"photo</em>width":null,"photo<em>height":null,"site</em>id":1,"summary":"
The ECB will most likely cut 25bp, which is almost fully priced in by markets. W
<hr >
Redacted the json a bit (sorry, don’t wanne “spill” data) as you can see, the summary field has some white spaces, enters maybe?
Ok, can you do me a favor? Add an issue here. I’m in and out this week on a family emergency this week, but I can have a team member take a look and get a version out ASAP around this.
For the JSON and the channel info, go ahead and shoot that to [email protected], I’ll get Ashlie on our team a heads up it’s coming while I’m out. It’s a private channel, so you can send private info to that email. We’ll take care of this for you.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.