Unsupported operand types in /all/modules/media_browser_plus/media_browser_plus.module on line 695. This is the operator +=; it is being used on arrays.

Comments

das-peter’s picture

Status: Active » Postponed (maintainer needs more info)

Unfortunately I don't have any +=; in /all/modules/media_browser_plus/media_browser_plus.module on line 695 in the latest dev version.
Please try latest dev or provide more information.
Thanks in advance.

norgo’s picture

just tried the latest dev (Oct1, 2012) and get the same error

Fatal error: Unsupported operand types in C:\xampp\htdocs\d7\sites\all\modules\media_browser_plus\media_browser_plus.module on line 695

Seems to happen after running update script.
flushed caches also, and problem persists.

das-peter’s picture

Assigned: Unassigned » das-peter
Status: Postponed (maintainer needs more info) » Needs work

Oh, I got it. I'll check that asap.

das-peter’s picture

Assigned: das-peter » Unassigned
Status: Needs work » Postponed (maintainer needs more info)

Unsupported operand types in /all/modules/media_browser_plus/media_browser_plus.module on line 695. This is the operator +=; it is being used on arrays.

This is absolutely valid: http://www.php.net/manual/en/language.operators.array.php

Could you check which version of file entity is used?
The latest dev defines the necessary menu item: file_entity.module line 117

norgo’s picture

I was using the Media 7.x-1.2 and should have read your README in the module folder first

After updating to Media 7.x.2.x-dev and added File entity 7.x-2.x-dev, error is gone.

one note to others though, if testing out media gallery, remove/uninstall that first. It was not easy to take out after installing the above first.

das-peter’s picture

Status: Postponed (maintainer needs more info) » Fixed

Okay, that makes sense.
Just to be clear for everyone reading this later on :) :
Do not use Media 1.x with Media Browser Plus 2.x

ANDiTKO’s picture

Status: Fixed » Needs work

I also got this issue after updating. This error completely crippled my website. I couldn't even go to my homepage. I tried on both Media 1.x and 2.x but still got that error.

My solution was to hack the "media_browser_plus.module" deleting all its contents just so i can go the the module administration and disable the module (drush was giving me the error and could not disable the module). Then i uninstalled it and deleted all its files.

This error still exists. Im going to do some more tesing and report back here.

Maintainer maybe enable error reporting on his server?

Thanks

ANDiTKO’s picture

Fresh and clean install and i still get this error.

Here are my module versions:

File entity 7.x-2.0-unstable6+12-dev
Media 7.x-2.0-unstable6
Media Browser Plus 7.x-2.x-dev
Media Field 7.x-2.0-unstable6

Before i was using the stable versions and still got this error :(

doublejosh’s picture

Fatal error: Unsupported operand types in /Users/jlind/Sites/upgrade.2/html/sites/all/modules/media_browser_plus/media_browser_plus.module on line 715

doublejosh’s picture

My problem was conflicting versions... Media 7.x-1.x and Media Browser Plus 7.x-2.x

das-peter’s picture

Status: Needs work » Fixed

I still think this is mostly caused by a version incompatibility.
Again: Do not use Media 1.x with Media Browser Plus 2.x
If you find conflicts with other versions please don't hesitate and post them here.

ANDiTKO’s picture

Comment #8 i had this error with Media 7.x-2.0 and Media Browser Plus 7.x-2.x. So is this fixed now?

das-peter’s picture

@ANDiTKO Hmm, I simply can't tell. We use it with Media 7.x-2.0-unstable3 and > Media 7.x-2.0-unstable6 without issues. So maybe Media 7.x-2.0-unstable6 has an issue that conflicts with the module that was later solved. I guess you best bet would be to try Media 7.x-2.0-unstable7.

kbasarab’s picture

I was running into this same issue as reported in #9.

The issue for me was a version conflict. I had 2.x dev versions of Media and Media Browser Plus but not file_entity module. Once I added file_entity module upgrade the error went away.

Status: Fixed » Closed (fixed)

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