Does not work with Context Breakpoint or Context Mobile Detect [#1859790]

Contextual View Modes does not seem to respond to conditions provided by the modules Context Mobile Detect and Context Breakpoint.

I've confirmed that Contextual View Modes works with the default conditions provided by context like Node Type, and I've confirmed Context Breakpoint and Context Mobile Detect to work in situations not involving Contextual View Modes. I'm not sure where the breakdown is, as everything seems to be failing silently, but this module seems to be the common factor in use with either of those modules.

Comment	File	Size	Author
#3	contextual_view_modes-add-context-mobile-detect-support-1859790-3.patch	954 bytes	steven.wichers

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

sherakama CreditAttribution: sherakama commented 12 December 2012 at 18:52

Thanks for this. I will take a look and see what it will take to make this work with those add on context modules. No promises :)

Comment #2

steven.wichers CreditAttribution: steven.wichers commented 11 January 2013 at 19:35

I just started looking in to this. First glance shows that contextual_view_modes_node_view_alter() is being called before any contexts are set via context_context().

Related issue? #1136270: block_view_alter

Comment #3

steven.wichers CreditAttribution: steven.wichers commented 11 January 2013 at 22:22

Status:

Active

» Needs review

File	Size
contextual_view_modes-add-context-mobile-detect-support-1859790-3.patch	954 bytes

Context does not currently provide a hook for modules to use that will fire early enough in the process to allow this module to function. I have created a patch that specifically looks for the context mobile module and then calls its condition function directly. I tested it on the current site I am developing and got different view modes based on mobile or not mobile.

Comment #4

steven.wichers CreditAttribution: steven.wichers commented 24 January 2013 at 16:37

Another, slightly more generic way to do this is to call module_invoke_all('context_page_reaction'); instead. This is what I wound up doing for a custom module that had a similar issue. This works, but isn't ideal because there really should be block specific hooks within Context.