I keep getting error message with this module installed that looks like this:

warning: Invalid argument supplied for foreach() in /home/mysite/public_html/mydomain/includes/form.inc on line 1211

Just installed your latest version and ran update.php but still see the error.

Comments

TomDude48’s picture

try the new beta version and see if you get the same error.

juankvillegas’s picture

Same problem

juankvillegas’s picture

Version: 6.x-1.0-alpha4 » 6.x-1.0-beta2

I forgot to change the version...

TomDude48’s picture

Which page(s) are you on when you get the error?

juankvillegas’s picture

I don't remember but I'm almost sure that it was in every page...

apmsooner’s picture

Just installed the latest version and still getting the following error at path admin/settings/kwresearch

warning: Invalid argument supplied for foreach() in /home/autop5/public_html/webmanager/includes/form.inc on line 1211.

FYI, I have no wordtracker api key entered for that field so don't know if that has something to do with it. I tried setting up account through your site and it appears an account never gets created so not sure how to obtain the demo key. Anyhow, don't even know if the error is related at all to that but it still exists nonetheless. The module appears to work just the same even with the error by the way but would like to resolve the issue.

apmsooner’s picture

Also, get an error on a node page like this:

warning: Invalid argument supplied for foreach() in /home/autop5/public_html/webmanager/sites/all/modules/kwresearch/kwresearch.module on line 750.

Looked up that line and it appears to relate to vocabulary terms. Okay so I went into kwresearch settings page thinking its looking for a vocabulary to save terms to and figured I should enable one. I have a couple of vocabularys setup however they aren't available as choices to save to in the settings page for the sync and tag vocabulary dropdown fields. Apparently theres a problem in the module code related to these particular fields.

apmsooner’s picture

Okay I think I figured something out here. I need to enable tagging on a vocabulary first. Then in kwresearch settings page, I can now see the vocabulary to attach. Once I attach a vocabulary, the error message goes away. I would suggest documentation to explain this requirement to prevent the error from appearing or remove the dependency thats causing the error... however it appears that in order for the module to be useful, a vocabulary must be configured and attached. Now that it seems to be working right... I think it will help me out tremendously so great work!

apmsooner’s picture

I'm still getting various errors throughout the site related to this module. I hope you can revise soon so I can use it.

apmsooner’s picture

Just installed your latest version dated 9/27. Still get this error when editing a node:
warning: Invalid argument supplied for foreach() in /home/autop5/public_html/webmanager/sites/all/modules/kwresearch/kwresearch.module on line 746.

TomDude48’s picture

apmsooner,

thanks for catching that issue. It occurs when you have no vocabs that are set to tag. It should be fixed in the latest release.

Tom

apmsooner’s picture

One more error... occurs when deleting nodes.

Fatal error: Call to undefined function kwreserach_load_page_keywords_by_page() in /home/autop5/public_html/webmanager/sites/all/modules/kwresearch/kwresearch.module on line 413

This is with latest update installed.

TomDude48’s picture

fixed, it will be in the dev release on 10/1

vrc3’s picture

Version: 6.x-1.0-beta2 » 6.x-1.x-dev

I am experiencing the "warning: Invalid argument supplied for foreach() in /usr/share/drupal6/includes/form.inc on line 1207" on every node edit page. I have tried enabling various settings with vocabularies with no success. The previous messages aren't very specific.

I have different vocabularies assigned to different node types, and some node types with no vocabularies. I have one set of tags for blogs, but none for general pages. What should I set in the keyword research settings page to get rid of this message for all node types?

vrc3’s picture

Okay, I figured this out... The error was actually from Content Analysis, which needed a default analyzer setting.

TomDude48’s picture

Status: Active » Closed (fixed)