It seems that new features introduced in Views 3 dev has broken this poor module. My guess is that it is the reworked pager settings, but I don't know.
Steps to reproduce:
* install dev versions of Views 3 and YQL Views Query Backend
* connect with twitter.search table (for example)
* output a field 'text' (tweet message)
* set a filter on field 'q' with value 'drupal' (or whatever)
* watch the error message instead of the expected preview
When I downgraded Views to a dev version a few months old (lying around on my local computer), the view started working fine again.
(This bug essentially renderes YQL Views Query Backend useless – hence the critical status. As far as I know it is not possible to run this module with the alpha3 release of Views 3, so there is no way at all if you don't have an old dev version.)
Comments
Comment #1
crizsubscribe
Comment #2
jvinci commentedSubscribe
Comment #3
kenorb commentedFixed one typo in 7.x, so 'Custom open tables' are not exported correctly.
Comment #4
kenorb commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.