Do not come to this fight tired, or worse yet, without a fast internet connection to for some CSS guidance. This might be useful for showing a block containing a list of other articles or a profile of the author of the node.Ĭontext as a concept was easy enough to grasp, but when used in combination with the Omega theme, became a mind exercise that one must be prepared for. Or perhaps you could create a context such that if a particular node was to be displayed, then replace one block with another in the same Region. For instance, you could say that if the page being requested is the "", then show particular blocks in particular regions of the page. You create a condition on which a particular context should come into effect and what reactions you wish to take place if that condition is met.
The biggest problem with that was when you created a new page, you might forget to add that page to the list of exceptions.Ĭontext handles this for you in a logical "Conditions - Reactions" format. If there was some kind of taxonomy or URL pattern that could be discerned, then I could use that, but mostly it came down to listing the individual page exceptions. Previously, when I wanted a block to show up on one page, but not one or two others, I had to create settings for the block's visibility to "Show block on specific pages ~ All pages except those listed" and then list the individual pages that I did not want the block to appear. I've come to think of Context as a replacement for the Drupal Core Blocks system. Having made the commitment to use the Omega theme and Delta module, of course the Context module is the place to start when creating a new website.
0 kommentar(er)
