I discovered that this module didn't fire correctly if I tried to use it with a context 'sitewide global' trigger. (7.x-1.2, not tried -dev yet sorry)
I believe this may be hard/impossible to fix in the current code as :
At the point that the node is being rendered (and thus decides which display to use) the 'sitewide' context flag has not yet been set. In my site anyway.
So it just failed.
My workaround was to use a different context trigger : node type is X : and that worked OK, and was semantically similar enough for my needs at the time.
I can't see a good way around that (it's deep in context internal order of operation), so I thought I'd just raise a warning that
"this may be incompatible with the 'sitewide' context trigger"
It may be that switching the processing to a context reaction as in this issue could resolve it.
Comments
Comment #1
dman commentedRelated by title (though not by task)
I discovered that this module didn't fire correctly if I tried to use it with a context 'sitewide global' trigger. (7.x-1.2, not tried -dev yet sorry)
I believe this may be hard/impossible to fix in the current code as :
At the point that the node is being rendered (and thus decides which display to use) the 'sitewide' context flag has not yet been set. In my site anyway.
So it just failed.
My workaround was to use a different context trigger : node type is X : and that worked OK, and was semantically similar enough for my needs at the time.
I can't see a good way around that (it's deep in context internal order of operation), so I thought I'd just raise a warning that
"this may be incompatible with the 'sitewide' context trigger"
It may be that switching the processing to a context reaction as in this issue could resolve it.
Comment #2
sherakama commentedComment #3
sherakama commentedThis re-factor work has been finished in the 3.x branch.
A review would be helpful.
Thanks.
Comment #4
sherakama commentedComment #5
sherakama commented