Hello,

First of all, I love this module. I've been fiddling with content feeds for a client for a while and just pulling values into views has made things much simpler.

I've run into an issue when attempting to navigate to a field with depth, however. The API I'm calling attaches images as their own array within the primary feed. For example:

{
  "listing":4,
  "url":"http:\/\/path.to\/listing.html",
  "Images":[{
    "image_id":528,
    "url":"http:\/\/path.to\/image.jpg",
  }]
}

Entering 'Images/url' into the Key Chooser field returns no data (and no error). I saw some discussion during the development of this module about support for depth. Did that make it into the recommended release?

I'm primarily a front-end developer, so I'd prefer to do this with a minimum of back-end coding, but I'm open to all suggestions.

Once again, thank you for this module. Happy Holidays!

Comments

smokingmirror’s picture

smokingmirror commented
Issue summary: View changes
smokingmirror’s picture

smokingmirror commented
Issue summary: View changes
marcofernandes’s picture

marcofernandes commented

You should set on Query settings -> Apath=Images
And them on Key Chooser=url

Just a note: Probably you're going to have problems with the coma at the end of url field on the json:

"url":"http:\/\/path.to\/image.jpg",

Hope it helps.

eggersrj’s picture

eggersrj commented

I'm having the same issue. I'm sure I can force the services view I'm consuming to make the feed more flat (with no arrays), but it would be nice if the depth worked and I could just use the feeds as they are. I guess this issue is more of a deal breaker if one is trying to consume a feed where tweaking feeds isn't possible ...

If anyone has this working somewhere and can make a patch available that would be great. Or if anyone knows of a more robust module that enables views to consume json feeds please let me know...

Thanks in advance for any ideas!

marcofernandes’s picture

marcofernandes commented

@eggersrj, can you provide an example json?

I've tested @smokingmirror json and it worked fine (just removed the final comma on url property).

smokingmirror’s picture

smokingmirror commented

@marcofernandes:

I am very sorry for falling off the face of the earth for a while. My ISP accidentally severed a cable into my neighborhood and after weeks of back-and-forth I finally have a stable connection again.

I tried it again with your corrections and it worked, but I had to reconstruct the view in its entirety. I seem to be having some sort of persistent caching issue that prevents me from making changes to the default query after retrieving the JSON feed the first time. I'm pretty sure that's not the module's fault, though, so I consider my problem fixed.

Thanks for all of your help!

marcofernandes’s picture

marcofernandes commented
Status: Active » Closed (works as designed)