If the pager is turned on for a non-RDF view, the following error occurs at the top of the page:
•Notice: Undefined property: views_plugin_query_default::$endpoint in sparql_views_plugin_pager_full->execute_count_query() (line 15 of /www/ebremer/sites/all/modules/sparql_views/plugins/sparql_views_plugin_pager_full.inc).
•Notice: Trying to get property of non-object in _sparql_init_remote_store() (line 163 of /www/ebremer/sites/all/modules/sparql/sparql.module).
•User error: Could not properly handle "SELECT COUNT(*) AS expression " in ARC2_SPARQLPlusParser in _sparql_request() (line 92 of /www/ebremer/sites/all/modules/sparql/sparql.module).

CommentFileSizeAuthor
#5 1587546-pager-errors.patch2.13 KBlinclark

Comments

Anonymous’s picture

Anonymous (not verified) commented

Do you also have a SPARQL View displayed on this page?

ebremer’s picture

ebremer commented

No. The actual view is the view that mimics the frontpage (I like to tweak the default behaviors). If I navigate away from the page that contains the non-RDF view and say just go to a generic node, the error goes away. - E

Anonymous’s picture

Anonymous (not verified) commented

I was able to confirm this with testing. I haven't gotten a chance to look at the code, but I'm pretty certain it has to do with the way I'm overriding the pager, which is probably a silly way to do in hindsight.

ebremer’s picture

ebremer commented

Thanks Lin! I was looking for the sparql_views_related_resource which you had added with some drush slight-of-hand in the Part II demo video (http://www.youtube.com/watch?v=AsWPm0vpmoI). I thought given the time since the video that sparql_views_related_resource might have been rolled into the dev version which is when I decided to do the update and ran into the pager bug. I'm still looking for "sparql_views_related_resource", but I guess I should open another issue on that? :-) I'll hang tight for the pager bug fix. - Erich

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Needs review
StatusFileSize
new 1587546-pager-errors.patch2.13 KB

Yep, it was a silly mistake. I was only thinking of my client's particular use case and not thinking more generally.

Fortunately, I think it's a simple fix. Can you give this patch a try?

ebremer’s picture

ebremer commented

Working nicely now and I have the pager turned back on the "frontpage" view. Thanks!

jpstrikesback’s picture

jpstrikesback commented
Status: Needs review » Reviewed & tested by the community

Thanks, this fixes the issue.

ebremer’s picture

ebremer commented
Issue summary: View changes
Status: Reviewed & tested by the community » Closed (outdated)