Closed (fixed)
Project:
Search API Pages
Version:
8.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Sep 2018 at 10:59 UTC
Updated:
21 May 2019 at 12:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
anybodyChanging to major, because this breaks an important part of the functionality and makes the search blocks unusable.
Comment #3
anybodyThe problem just occured on a further page... reconfirming.
Comment #4
Snehal Brahmbhatt commented@Anybody,Please find my patch that works for the error that mentioned above. getConfigDependencyName function returns null because $search_api_page was empty. I have set the condition to check whether $search_api_page is empty or not. If $search_api_page is not empty then only it check for getConfigDependencyName function.
Please your view after using the attached patch.
Thanks!.
Comment #5
anybody@snehal.addweb: Thank you. That patch work, but I'd like the maintainer to have an eye on it, if $search_api_page will ever have a value... otherwise the whole function doesn't add value...
Comment #6
marcoweijenborg commentedI can't reproduce the issue when I install the latest stable version of Search API combined with the dev version of Search API Pages. However, the patch is ok, an extra check is always good.
Comment #7
marcoweijenborg commentedComment #8
legolasboThe
calculateDependencies()method should return an empty array if no dependencies could be determined. The attached patch fixes this.Comment #9
borisson_Yes, looks good.
Comment #11
borisson_Thanks!