The QueryPath module library no longer includes itself on every page request but only when a module explicitly asks for it. See #1781878: QueryPath is not always needed in hook_boot for details.

From a quick review it looks like this module uses querypath. It would be great if you could review your use of QueryPath to ensure that it will work when the next version is released.

Thanks!

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I'm planning to make a new release of querypath soon, so it would be great to get this fixed. If it's not fixed and there's a new release of querypath the result will be fatal errors for your users.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Issue tags: +QueryPath
tloudon’s picture

tloudon commented
Issue summary: View changes
Status: Active » Closed (won't fix)

Hi Greggles,

Thanks for the headsup, the module uses the querypath library directly in just a few spots not the Drupal module; so this is a non-issue here.

Thanks again!