Fatal error: Unsupported operand types in [path to drupal]/sites/all/modules/views/includes/handlers.inc on line 1032

Same problem, and problem exists only with taxonomy in glossary mode

Hi,

I solved the problem by replacing the code

        $placeholders = array(
          $placeholder => $value,
        ) + $this->placeholders;

by

        if(isset($this->placeholders)) {
          $placeholders = array(
            $placeholder => $value,
          ) + $this->placeholders;
        }
        else {
          $placeholders = array(
            $placeholder => $value,
          );
        }

in includes/handlers.inc file, in add_filter() function.

However, I don't know for the time if it causes collateral damage.
Everything seems to work for me for now ...

Hi, I was having an issue with contextual filters causing a HTTP 500 error and the PHP error which is listed in the bug report. After applying this patch the HTTP 500 and PHP errors / warnings stopped occuring.

http://redev.synapse.net.au/organisations/a-z/a

confirming that #6 works

Confirm patch from #6 helped me to solve the problem with latest Drupal 7.x-dev and latest views 3.5

I believe this patch will fix the issue in a more easy way.

Got 500 errors on an Ajax enabled views with taxonomy stuff, and this patch made it disappear.

Thanks.

Patch #11 worked for me, thanks.

Same problem ( taxonomy in glossary mode )
Patch #11 worked for me.
Thanks.

Thanks for testing! Committed this patch to d7.

This stuff is way to complicated...

Rerolled.

Patch in #11 fixes the problem for me, Drupal 7.

Thanks @fastangel!

NW now for some tests.

D7, Views 3.5 - view using attachments - patch in #11 worked for me

Thanks

@fastangel, tests? :)

I am trying reproduce this error on my local but I can't attach one display. I get a list empty in 'attach to'. I was seeing the code and in the options displays the list is always empty. Is other bug?

D7.15, Views 3.5 - using a clone of the default glossary view - patch in #11 worked for me. This problem appeared only after I updated Views from v3.3 to v3.5.

I get an error which I believe is the same issue. However, I am using the latest dev version of Views (2012-Nov-11), which is significantly newer than Views version 3.5 (2012-Aug-24) and newer than when these posts say the patch was rolled into Views.

When I put any incorrect path, e.g. "cats" or "dogs", after the View's url, I get a WSOD.

It appears the Contextual Filter for <(term) Taxonomy term: Name> that I have configured for this View seems to kick in and get stuck on not being able to find the specified filter criteria. Here's the PHP error I get (I also get server error logs, which I include in the post I link to below):

Notice: Undefined property: views_many_to_one_helper::$placeholders in views_many_to_one_helper->add_filter() (line 1032 of /path-to-drupal/sites/all/modules/views/includes/handlers.inc).

I had not found this issue last week, and so I posted my own issue for my situation at http://drupal.org/node/1836184

The effect of this problem is so bad, it often locks up my website!

Setting the version back to 8.x-dev - it looks like this was unset in comment 24.

Set to needs review. Not sure whether we want to have tests for that, though writing tests for many to one handler is less easy then you would expect it to be.

Patch in #11 fixes the problem for me to

Note to anyone who might come across this issue, to save you looking for it; the patch from #11 has been worked into the dev version.

(It does however not exist in 3.5 - the current stable version. You'll have to either apply the path, or use -dev, in other words.)

#18: views-1752062-18.patch queued for re-testing.

NW as per #20.

Cleaning up old issues.

This code changed a lot over the years, so there is a good chance that this got fixed, but since we have no steps to reproduce this on Drupal 8, that is hard to say for sure.

Please add some steps to reproduce this on D8 or move this back to the Drupal 7 queue if it is still relevant there.

Going to close since there hasn't been any activity after @Lendude's follow up.