There are a couple of stray dpm()s in calais_batch_process(). D'oh. :(

CommentFileSizeAuthor
#1 calais-batch-dpm.patch1.01 KBfebbraro
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

febbraro’s picture

febbraro CreditAttribution: febbraro commented
FileSize
calais-batch-dpm.patch1.01 KB

At least you got the ones without profanity :)

Was this killing your bulk process? Here is a patch if it did.

Fixed in CVS

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented
Status: Active » Fixed

Haha. ;)

I just enabled Devel module, but figured this might trip someone else up. Thanks for the fix!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

DavidWhite’s picture

DavidWhite CreditAttribution: DavidWhite commented
Status: Closed (fixed) » Active

I applied the patch, and now when I go to do bulk processing, I don't get the fatal error, but I DO get the "An error occurred" message on the bulk processing page, when I'm such-and-such a percentage done.

Here's an example:

Calais Bulk Processing has encountered an error.
Please continue to the error page

An error occurred. /batch?id=52&op=do

We checked our error logs through Watchdog and some of our other log files and couldn't find anything. Apache is reporting this process as a POST, so I increased the max_input_time in our WHM from 1 minute to 2 minutes. Looks like we are still getting this "error" that isn't reporting any logs.

Edit: After reviewing the logs on this batch attempt (id=52) at this, I just found that dblog reported a 500 - Internal Server Error:

Message: Calais processing error: (500 - Internal Server Error)

Any ideas?

febbraro’s picture

febbraro CreditAttribution: febbraro commented
Status: Active » Closed (fixed)

Please open a new issue for this and don't open a previously closed one as your problem is different.

However the error you are seeing is actually an error from the Calais service itself and not from this module, it is just reporting the error returned. Could be a problem on their part. Try again and see if you still get the same problems? Dont forget to open a new issue too :)

reikiman’s picture

reikiman CreditAttribution: reikiman commented

I just want to point out this was fixed 3 months ago "in CVS" but the current release still has this error in it.

febbraro’s picture

febbraro CreditAttribution: febbraro commented

Thanks, I had forgotten. 3.2 is now released.