* warning: Invalid argument supplied for foreach() in /var/www/modules/opencalais/calais.module on line 405.
* warning: implode() [function.implode]: Bad arguments. in /var/www/modules/opencalais/calais.module on line 431.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY v.weight, v.name' at line 4 query: SELECT v.vid, v.*, n.type FROM vocabulary v LEFT JOIN vocabulary_node_types n ON v.vid = n.vid WHERE n.type = 'page' and v.vid in () ORDER BY v.weight, v.name in /var/www/modules/opencalais/calais.module on line 440.
Took this from Forum post http://drupal.org/node/277724
Comments
Comment #1
buggyde commentedHi,
I get the same issues on the latest release of drupal and Calis.
warning: Invalid argument supplied for foreach() in /home/computer/public_html/modules/opencalais/calais.module on line 351.
I have tried 2.2 and 2.1 both give me the same error.
I am also unable to save any changes in the Node settings.
Comment #2
febbraro commentedWhat happens if you try to save the Calais Node Settings form?
Comment #3
buggyde commentedHi,
Nothing except all settings that I change reset to the default, like it is read only. It is very confusing, I am new to drupal so I thought it was something I was doing, but after a few days of setting up and configuring drupal, everything else is working but this.
Best Regards,
Comment #4
febbraro commentedAre there any messages in the watchdog log or your webserver's error log? This is strange behavior indeed! That settings form does nothing special except use standard Drupal functions to write to the variables table.
Comment #5
jjcheno commentedHi Frank, I upgraded a Beta test site to the new RDF version Alpha5 without thinking to remove /arc2 RDF is now looking for arc in: rdf/vendor/arc ,needless to say there were lots of errors
I got the same effect, losing the save in the Calais configurations 'node settings', but can save in the 'API'
also lost the 'save changes' in the sites overall 'blocks' I tried to revert to previous stable versions of both RDF and Calais but no joy
I think the damage has been done.
in addition to the same errors as Buggyde. I also got:
Unknown column 'v.prefix' in 'field list' query: SELECT v.prefix, v.uri FROM rdf_namespaces v in /home/public_html/1ana2.com/modules/rdf/rdf.db.inc on line 18.
Regards, Jim
Comment #6
febbraro commentedDo you have a backup of your site/db you can rollback to and attempt the upgrade again? I have not used RDF alpha 5 yet, I will test that out shortly and let you know if I run into any problems. I'm assuming you have run the update.php script after upgrading?
Comment #7
jjcheno commentedyes I was able to roll back and update to Calais 2.2 with RDF Alpha 5 and Arc from 11/18/2008. simply renaming the 'arc2' folder to 'arc'
I created a blog post, tags were generated as expected. Also the "CalaisDocumentCategory" entity in the Node settings was added, but thats where the weird part comes in. I cant save the newly created category, or any option in the Calais Node Settings. as buggyde reports in #3 above. options can be saved under Calias API Options (searching, distribution, API key) database has All privlegdes, clean 6.9 install. 1 user/admin
---------------------------side note-------------
the inabililtity to save is what caught my eye about this thread. I have 3 production sites, using 2.1 with RDF alpha3. these sites cant save blocks unlessall modules are disabled, I didnt think calais/rdf could be involved. to my knowledge these modules don't do anything with hook_block at all? I have been chasing this saving blocks issue for 2 months, so I am ready to try anything.
----------------
Regards, Jim
Comment #8
webchickI didn't initially realize I was supposed to go to a different screen and complete more configuration steps, so I got this as well on node/add/story:
This is coming from:
Is there a particular reason why these variables default to FALSE rather than array()?
Comment #9
webchickBumping version.
Comment #10
febbraro commentedThings are barfing in any case so array might be a better default, however I think the IN queries will still fail with an empty array.
To be honest, I need to do a much better job of defaulting the things I can on install and bullet proofing the rest of the processing to alert for unsaved configs, etc. I have put a "Requirements" warning that the config has not been saved, but the average user will never see it anyway and just start adding content. So b/c of that I need better initial configs.
Comment #11
febbraro commented@webchick Did you get this as part of OpenPublish, or simply using the module on a regular Drupal site?
Comment #12
webchickNah, this was the regular module on a clean 6.x site. I was dinking around with OpenPublish earlier that so I could have a reference example with everything already configured.
Comment #13
febbraro commentedThis was fixed a while back. array() are used instead of FALSE and a hook_requirement warning if that node setting page is not saved. Thanks for the suggestions.