I have this error

Fatal error: Cannot use assign-op operators with overloaded objects nor string offsets in /home/www/drupal/temp/echodespros/sites/all/modules/search_api/includes/processor.inc on line 288

It doesn't seem to affect anything from working.

Sorry for the brief description but I really don't have any more info on this. Just considered to post it in case it might help.

Comments

drunken monkey’s picture

A fatal error that doesn't affect anything? Very weird, and seems too good to be true …
Please see if the error is still there in the latest dev, and on which line!
(For me, line 288 only contains continue;.)

Also, which processors are you using? Any that aren't directly in the Search API module?

george.plescan’s picture

I updated to the latest dev and the error is gone.

I am using Search API for the Fuzzy Search module. As I said before the search was working fine, only that I got the error message when I opened the site.

Thank you for the module.

george.plescan’s picture

Status: Active » Closed (fixed)
george.plescan’s picture

Status: Closed (fixed) » Active

The error is back, I don't know why.

Fatal error: Cannot use assign-op operators with overloaded objects nor string offsets in /home/www/drupal/echodesprosdev/sites/all/modules/search_api/includes/processor.inc on line 294

else {
$token['score'] *= $score;
}

This is what's on that line.

Again the Fuzzy Search is still working on the site.

Sorry for closing and re-opening the issue. I tested and for the moment it was ok.

drunken monkey’s picture

Title: PHP error - processor.inc on line 288 » PHP error - processor.inc on line 294
Project: Search API » Fuzzy Search
Component: Miscellaneous » Search API integration

No problem. (Only please never set the status to „closed (fixed)“, just to „fixed“.)

However, then it seems the problem lies in the Fuzzy Search module. Moving this issue accordingly.

Please disable all processors but one of those from the Fuzzy Search module, and then all but the other, to find out which of those (or both, or none) is causing this problem. It might also help awolfey if you could find out what $token looks like before the fatal error occurs – but maybe he'll know that anyways. In that case he should either use normal arrays, or override normalizeTokens() in the processor.

awolfey’s picture

george.plescan, Could you please update your copy of fuzzysearch and let me know if this is still happening, and if so, the steps to repeat the error?

I just made a bunch of fixes to the module and it should be working again. Thanks

george.plescan’s picture

I did the updates of FuzzySearch and also Entity and SearchAPI.

I will report any changes in a future post, to be sure it doesn't reappear.

Thank you for the help.

awolfey’s picture

Status: Active » Closed (fixed)

Closing.