Fatal error: Call to undefined function db_fetch_object() in ../kwresearch.admin.inc on line 416

I get the same error, any solution yet?

I'm having the same issue, but I do not have taxonomy keywords synced.

The same error for bilingual site English- Russian:
Notice: Undefined property: stdClass::$taxonomy in kwresearch_node_update() (line 967 of /mysite/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined offset: 1 in kwresearch_node_update() (line 974 of /mysite/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined variable: page_keyword_obj in kwresearch_node_update() (line 980 of /mysite/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined offset: 1 in kwresearch_node_update() (line 974 of /mysite/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined variable: page_keyword_obj in kwresearch_node_update() (line 980 of /mysite/sites/all/modules/kwresearch/kwresearch.module).

***
When I edit keyword in a node with button "Keywords" > Operations > edit there is "Fatal error: Call to undefined function db_fetch_object() in mywebsite/sites/all/modules/kwresearch/kwresearch.admin.inc on line 416

***
The error "Error making API call: unsupported-text-language" appeared after editing articles. It relates to SEO: Content Analysis API, Meta tags, Keyword Research.

Same errors. Ended up disabling kwresearch. Will look forward to new version. This is certainly a much-needed module. Thank you.

Notice: Undefined property: stdClass::$taxonomy in kwresearch_node_update() (line 967 of /public_html/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined offset: 1 in kwresearch_node_update() (line 974 of /public_html/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined variable: page_keyword_obj in kwresearch_node_update() (line 980 of /public_html/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined offset: 1 in kwresearch_node_update() (line 974 of /public_html/sites/all/modules/kwresearch/kwresearch.module).
Notice: Undefined variable: page_keyword_obj in kwresearch_node_update() (line 980 of /public_html/sites/all/modules/kwresearch/kwresearch.module).

There are heaps of severe errors in this Module for D7. Even the dev build from Jan this year is full of errors.

My attempt to help kick this all back in to a working state attached.

This should fix the db_fetch_object error mentioned in the title of this thread and other that I think occurs when dealing with taxonomies.
(Apologies for the messy patches, my Sublime edit automatically removes redundant white space)

Patch rolled against 7.x-1.x-dev

This one includes more changes to try and clear the other errors and warnings that I could find away. This one replaces the one above and does more.

No auto testing? I guess not otherwise it wouldn't have ever been given a green release. Anyway - please test, comment and improve on these.

Hi marblegravy.
Testing out the patch in #7.
A lot of the errors do go away but as expected, behaviour changes and maybe you can dig deeper?

With the patch applied, adding page keywords now fails with a WSOD seemingly. Seemingly in that it really is not a white screen of death but just a blank page because no content is created by the form.
From:
/node/xxx/kwresearch
Then, clicking on 'Add page keyword' to admin/structure/kwresearch/page_keywords_edit/xxx?destination=node/xxx/kwresearch
leads to the blank page.
The page is blank if in context settings, everything is turned off. Turning on 'show all regions' and the context editor dialog results in the page now showing:

ContentAdd a block here.
HelpAdd a block here.
Dashboard (main)Add a block here.
Dashboard (sidebar)Add a block here.
Dashboard (inactive)Add a block here.

Now, going to admin/structure/kwresearch/page_keywords_edit/$pid/$kid?destination=node/55/kwresearch results in the error below:

Notice: Undefined variable: msgs in kwresearch_load_page_keyword() (line 641 of .... sites/all/modules/kwresearch/kwresearch.module).

Something to note is that now, unlike without the patch, the page url is correct (previously the site domain itself was missing from the path).
The keyword does get added on save and correct message is displayed. BUT, instead of updating the keyword on the page keyword tab (shown after save), the node now has the keyword added an extra time with the original staying intact.
See attached image at bottom:

At admin/structure/kwresearch/keyword_list/page Clicking on the keyword number at each page with a page keyword results in:

Recoverable fatal error: Argument 1 passed to drupal_http_build_query() must be an array, string given, called in /includes/common.inc on line 2267 and defined in drupal_http_build_query() (line 486 of includes/common.inc).

I presume $kid in the code is being called as a string instead of an array but I've no idea.
A test of the caller gives the following info:

#0 url(admin/structure/kwresearch/page_keywords/60, Array ([query] => destination=admin/structure/kwresearch/keywords_pages,[attributes] => Array (),[html] => )) called at [/includes/common.inc:2470] 
#1 l(keywords, admin/structure/kwresearch/page_keywords/60, Array ([query] => destination=admin/structure/kwresearch/keywords_pages)) called at [sites/all/modules/kwresearch/kwresearch.admin.inc:609] 
#2 kwresearch_keyword_pages_page(51) 
#3 call_user_func_array(kwresearch_keyword_pages_page, Array ([0] => 51)) called at [/includes/menu.inc:517] 
#4 menu_execute_active_handler() called at [/index.php:21]

Here, 51 is a keyword ($kid) and 60 is the node.

I guess this is already too much info and may be in the wrong direction to boot.

Thanks for the significant and well documented testing Kenyan, I'll have another look at this when I can find the time. Of course if the module maintainers wanted to pick it up, that might be nice too.

@marblegravy. It would be great if the changes you need to do to get the module into a working state would be in smaller patches and attached to different issues. Then I would happily test each small patch. But your patch has a lot of lines which seems to be the same before and after the patch, so it would probably not be committed anyway, when the module maintainers get som sparetime to work on the module again.

Might be somewhat related to #1620264: Numerous errors...

a note, comment, thought or any form of input from the maintainers would be great and quite appreciated. alternatively, i'm not certain that this module should be marked as "actively maintained" if close to 6,000 users are going to be left hanging on an issue like this (meaning one that is marked significant and has been known of for nearly one full year)

I cant get the last patch to work. I applied it manually and found that 90% of it is actualy replacing code with the same code. I now get a blank screen when accessing the keyword of a page.