WSOD with some terms [#2247135]

I got the module to work with a test-vocabulary. but switching to a "live" vocabulary does result in a WSOD for a page.
I'm not sure what could cause this- i tried several vocabularies (with just a few and with lots of entries) that all work well
but one specific vocabulary does not. it did contain a few level 2 terms for testing so i thought it might be an issue with
more than one level- but after removing those term the problem still persists.
any idea how to narrow the problem? only fatal error I can find in log is "PHP Fatal error: Cannot access empty property in /var/www/sites/4-seasons.de/htdocs/modules/field/field.attach.inc on line 324"

Comments

Comment #1

david_garcia CreditAttribution: david_garcia commented 22 April 2014 at 13:46

I am not sure this is a filter's issue, anyways, to confirm get a full stack trace of the error, then in the call chain we can see if the module is involved.

I cannot replicate with the given information, neither surmise or get a hint onto what might be happening.

Greetings,

Comment #2

thommyboy CreditAttribution: thommyboy commented 28 April 2014 at 10:07

Hi,
some more testing. Found out it's not a specific vocabulary but a single TERM that results in the WSOD.
What I've got is a view with a contextual filter "has taxonoy term" to limit the results to a specific term.
Views Selective Filters is then used to further filter the result.
This works fine for all Terms but one. This one is of the same vocabulary (containing only 12 terms) and
there is nothing special about it as far as I can see. Using the non "(Selective)" version of the filter works
fine on that term- using the "(Selective") results in a WSOD (that's why I suppose a connection to this module)
with error log saying "Cannot access empty property in /.../htdocs/modules/field/field.attach.inc on line 324"

Comment #3

thommyboy CreditAttribution: thommyboy commented 28 April 2014 at 09:50

Title:

WSOD with some vocabularies

» WSOD with some terms

Comment #4

thommyboy CreditAttribution: thommyboy commented 28 April 2014 at 10:21

ok- #5 of https://drupal.org/node/1904788 helped me.
there was one node of a different content type tagged with the term that caused the wsod and my view contained fields not available in that content-type.
so this seems not to be related directly to views selective filters- but still seems to be an issue as the view works perfectly without a (Selective) Filter?