Heres my initial port to 7.x

CommentFileSizeAuthor
0001-Initial-7.x-release.patch1.69 KBkylebrowning

Comments

brettbirschbach’s picture

brettbirschbach commented

If I grab the latest Services Views 2, and pull in the changes mentioned above, will it run with Drupal 7/Views 3/Services 3? I'm guessing not, or at best "maybe, but no one has extensively tested it". Just want to better understand what this "patch" represents, as I am considering a drupal site that is going to serve data to multiple other sites, and one requirement is to be able to serve data from complex queries touching multiple tables. I believe I need Services Views for this.

kylebrowning’s picture

kylebrowning commented

This patch supports views 2 AND views 3 and works for Drupal 7

brettbirschbach’s picture

brettbirschbach commented

Thanks Kyle. I followed your patch, and got Services Views successfully installed in my Drupal 7 site. However, whenever I retrieve a view via Services, all "fields" come back as the string "node". This is if my view is set up to return "Fields". If I change my view to return "Content", then when I retrieve it via Services, then the fields are all populated as array objects that I have to dig a few levels deep into to find values. Is this the expected functionality? In drupal 6, when I used Services Views that was embedded in Services 2, I fields showed up as simple values. I know, however, the data is structured differently by Drupal 7, so maybe there is no choice.

kylebrowning’s picture

kylebrowning commented

Unfortunately its a bug in views :( #1145770: Helper function for getting raw and rendered field data Im going to be attempting workarounds.

voxpelli’s picture

voxpelli commented
Status: Active » Fixed

This patch was mostly a port to Views 3 it seems - committed that to d6 and then did the change to the info file.

Seems to be working - please test it out! A dev-release will be built soon.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.