Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have been searching for a while, I cannot figure out how to create sidebar blocks like the default "Weekly Meeting Times"
http://i.imgur.com/E9D2j.png
Comments
Comment #1
Code Monkey CreditAttribution: Code Monkey commentedThose could be created as a view or a standard html block. The visibility of the blocks are controlled through the context module.
Does that help?
Comment #2
linwiz CreditAttribution: linwiz commentedIt helps a little, but I'll be honest in saying that I am used to D6. D7 is foreign to me, and I've never understood views period. could you provide more info and direct links?
Comment #3
Code Monkey CreditAttribution: Code Monkey commentedI'm assuming you know how to create a static html block with these instructions. If not, you can start by looking on the Structure page to create Blocks. I am also using a 7.x-1.x branch of OpenChurch for these instructions.
Since OpenChurch is using the Context module. You can view the README.txt of this module for additional information. You get to the Context UI by visiting the /admin/structure/context url.
From here, you will see the default contexts provided by OpenChurch. For now, there is only one, "openchurch-all-sitewide", and it is listed as a "Global" context. The "Global" label is actually arbitrary as it is only a tag listed in this particular context as you will see when you select to Edit it (admin/structure/context/list/openchurch-all-sitewide/edit).
From the edit page, you will see three sections. The first section is the general information of the context. This contains the unique name of the context, a tag (this is that arbitrary label mentioned above), and the description. The next section is the Conditions on when to show this context. And the last section is the Reactions that occur when the previously defined conditions are met.
Let's check out the assigned Conditions for this context. In this section you will see a drop down list and then a predefined condition called "Path". The drop down list allows you to add additional conditions. Clicking the "Path" link will bring up a list of path conditions in the right column of the page that are already assigned to this condition. Each path must be on its' own line.
The first condition, "*", means to show this condition on all pages. The second condition, being that it is prefixed with the tilde character "~", means do not show this condition on the following pages, which would be any administrative pages "~admin*". So, this context will show on all pages except for the administrative pages.
Now that we have covered the conditions on when to show this context, let's move on to what reactions should occur. In the Reactions section, you will see a similar drop down list and a predefined reaction called "Blocks". Again, the drop down list allows you to add another reaction to this context.
Click on the "Blocks" link. This will update the right column to show the different regions within your current template and then the list of blocks that are unassigned to any regions. You can only have one block listed in one region.
You can only modify one region at a time. This means you can only add to, remove from, or rearrange one region at a time. To move a block from one region to another, you must remove it from the region it assigned and then add it to the desired region.
Any blocks you want to add to a region must already be created.
I hope this helps.
Comment #4
linwiz CreditAttribution: linwiz commentedThat helped tremendously. I now know how to make blocks show up with no problem! thank you so much!!
Comment #5
drupalninja99 CreditAttribution: drupalninja99 commentedChanging to fixed, we probably need to add this to the documentation site. @Code Monkey do you want access to add book pages to http://openchurchsite.com/documentation?
Comment #6
Code Monkey CreditAttribution: Code Monkey commentedI can or you can copy this over. It is up to you. I see that I need to do a little rewording on this to make a little more sense out of it, though.
Comment #8
drupalninja99 CreditAttribution: drupalninja99 commentedTagging as documentation