Posted by dominikb1888 on September 2, 2010 at 3:03pm
Jump to:
| Project: | SPARQL Views |
| Version: | 6.x-1.1-alpha1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
After Installing the module, upgrading views to 3.0-alpha3 and applying the patch, I received the above error message in the views ui filter pane.
I tried tackling the error myself by putting the sparql_views_handler_filter_where.inc file back into the handlers directory assuming the missing handler has something to do with the missing file. I couldn't get it to work though.
Can anyone else report this behaviour? I am using Drupal 6.19.
Best regards,
Dominik
Comments
#1
I haven't tried the module against alpha 3. I know that last week, during DrupalCon, Views alpha was broken. Try against the Views dev release.
#2
Thanks for the quick reply!
I added the handlers in the to the implementation of hook_views_handlers and can now see the filter form with subject, predicat and object.
Was this code change on github intentional: http://github.com/linclark/sparql_views/commit/e970d7738483654b8032d3ce3... ?
BTW I couldn't get it to work against the views-3.x-dev version in the first place and was then glad to find the tutorial on your blog where you mention alpha3.
#3
#4
Yes, the code change on GitHub was intentional. The code on GitHub is not compatible with the code on Drupal.org... I completely reworked the way that SPARQL Views works on the backend.
A new version will be up on GitHub within the next week.
#5
Great module!
(Not just the functionality, but nicely put together, too.)
I'm afraid I don't follow this thread of discussion, or why the issue is now closed. I installed everything as per the instructions, and everything worked fine running a query against an end-point.
However, the moment I tried to add a filter in the view I got the "Broken/missing handler: sparql_ep > where" error message that Dominik referred to.
Dominik asked in comment #2 whether you intentionally removed the 'where' handler from the handlers directory, and you said yes -- so it sounds like you're expecting this to work, Lin. But what I'm not understanding is why Dominik had to add the handler back in.
I'd really appreciate it if you could clarify whether the module should work 'as is', or whether that handler does indeed need to be added in to get filters to work.
Thanks!
#6
Hi Mark,
I closed the issue because I tried following the instructions from the video on lin's blog, which belong to the CVS version of the code from here which is not up to date. You're post reads like you did that as well.
The Github Version has got a different UI. There still is the query settings entry in the views UI advanced settings section. You can insert Prefixes and your full Sparql Query there. Every "?" Prefixed variable will turn into a field you can use in your view once you submit the "query settings" form. In addition you will find a link called "Build Query" which will assist users with a concept import from the respective enpoint and a graphical query builder.
I could get this to work with Lin's help. At the moment I believe that not all required modules and their correct versions are in the drush-make file. I will file a separate issue as soon as I can confirm this to be really correct.
Yet when the errors were resolved the module worked like a charm. A great start definitely.
#7
Thanks for updating dominik :)
I posted the video with the Alpha1 version of SPARQL Views. Since then, I have completely reworked the backend. I've been holding off on making a new release on Drupal.org in the hopes that the Git migration would take place, but I may just need to read up on Maintaining a Drupal module using Git in the meantime.
The new version of the module takes a query in the Settings section in the left hand column.
I'm currently focusing on getting unit tests working, but will debug the make file after that.
In the meantime, let me know if you want to Skype and get the module working, Mark. I sent a starter site to Dominik which worked well.
#8
After talking with Mark, his issue was an unrelated one. Once I clean up the code, it should be clearer that I'm not using filters anymore.