The content_type stub defines 'all contexts' for the plugin. Not entirely sure what it does, and have never used it. Only the custom content content type and the php access plugin use it.

I'll hazard a guess that it lets the content type see all contexts, but one should really use required contexts for input.

So. Please remove that. :-)

Comments

naxoc’s picture

naxoc commented

I am actually not quite sure what it does either. What I do remember though is that it stopped working when I removed it.

Do you have a use case where it is in the way?

xen’s picture

xen commented

When defining a content type that takes one required argument, the $context argument is that one argument. But with "all contexts", it is an array of all the contexts, which you'll then have to figure out how to dig out the one you want from.

Considering that in all of ctools and panels, only one use it (the 'custom' type, in order to do token replacement using all the contexts), I'd say it's not supposed to be used by standard, and shouldn't be part of the default CPS implementation.

naxoc’s picture

naxoc commented
Status: Active » Fixed

I took a look and you are right. I committed it to the 7.x-1.x branch.

Status: Fixed » Closed (fixed)

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