When choosing the 'analyze content' button on the Content Analysis tab of a node edit form the Content Analysis Results window pops and then hangs with the Analyzing Content bar on 0%. Taking a closer look at the http traffic during this request shows a server 500 error with a post request to /contentanalysis/analyze_js.

My php_error log also registered this error:

'PHP Fatal error: Class 'AlchemyAPI_NamedEntityParams' not found in sites/all/modules/contrib/alchemy/AlchemyAPI/module/AlchemyAPI_CURL.php on line 79

This is setup on local dev environment, using Curl and with the sdk installed into the alchemy modules folder.
As far as I can tell everything is configured correctly API key in place etc.

Finally another user register what seems to be the same error here: http://drupal.org/node/1404796

Thanks!

Comments

jamesrutherford’s picture

Not enough coffee this morning. Obviously that first issue is with the Content Analysis module. The second issue I believe is still relevant.

shareabread’s picture

same thing happen to me.. a window pops and then hangs with the Analyzing Content bar on 0%. has anyone able to look at this.. cheers

Buddharide’s picture

I'm getting a similar error, that AlchemyAPI_ConceptParams cannot be found on line 122 of AlchemyAPI_CURL.php.

Not sure how to fix it...

Anonymous’s picture

Same Problem, with #2, hangs with the Analyzing Content bar on 0%...

Anonymous’s picture

Version: 6.x-1.0-rc6 » 7.x-1.0-beta1

Same Problem, with #2, hangs with the Analyzing Content bar on 0%...

TomDude48’s picture

It will probably be a bit before i can look at this. It sounds like it is a problem with the Alchemy external library. For now uncheck the "Use CURL class" on the configure page.

phobosk’s picture

I had this problem too.
I fixed it as i changed the text format in the node (while editing) to be a format that doesn't have any html tags.

In my case i have two text formatters: 'Full HTML with tinymce' AND 'Full HTML with no editor' which is text only containing the raw html. When in 'Full HTML with no editor' format, alchemy behaves the way you have described... When i change the format to 'Full HTML with tinymce' (which shows a properly formatted text only) Alchemy works as expected....
I guess it is a problem of what is sent to the Alchemy API...

There is another bug when using Admin overlay in D7 too... after the results are loaded the dialog box is moved away from the browser visible area, but i guess this is a problem of the contentanalysis module's ajax....

brks’s picture

It seems broken.
After clicking "analyze content", a new window pops up, in it is the source code of the WAMP server homepage. This is strange, although I am using WAMP server.
After clicking OK to close the pop-up window, the "analyzing content" bar frozen at 0%.
I tried to change format as @phobosk advised above, but there is no difference. I also tried other stuff, such as ticking and un-ticking CURL class; but no difference.
I don't know where I am. Anybody using the module smoothly as @phobosk? Anybody still has issues?
----------------------------------------------------
update: it's working now. I don't know what happened, but it just recovered by itself. :-)

rphillipsfeynman’s picture

I'm having the same problem. Is there any progress on this? Thanks in advance

aasim_afridi44’s picture

I had same problem But for now you can uncheck this option 'Use CURL class'.

ThaJoa’s picture

I don't have that option checked by default and it's still not working

kyletaylored’s picture

Status: Active » Postponed (maintainer needs more info)

I built a fresh install, with the most recent version of AlchemyAPI, and I'm not getting this error. I see that some of you are on WAMP. Could anyone confirm this working on a non-WAMP installation?

b-reid’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Please refer to the following issue #2836254: Drupal Alchemy plugins no longer supported - resulting in "invalid-api-key" Error, after further research this module seems to be un-supported, and will be flagged for deprecation.