Goes through the default content types of the Article and Page that are provided in Drupal 7, and shows the similarities and differences between the two. Also goes through some of the configuration options, which define the default settings whenever a new node is created.

Shows how to configure image styles for the uploaded headshot in order to resize the image to a more reasonable and standardized size.

Shows how to associate and create a relationship between two nodes with the node reference field type, and how to set up the node reference URL widget in order to auto-populate the node relationship via a link on the referring node.

Goes through the process of adding a role and then creating a user reference field, which autocompletes to users within that specified role.

Goes through the process of creating a hierarchical set of taxonomy terms, and then adding an autocomplete taxonomy term reference field to a content type.

Goes through the process of adding three new fields to the job posting content type including an integer text field for the salary, a select list of job type, and a checkbox as to whether or not telecommuting is allowed.

Provides an overview of the example job posting site that will be built over the remaining chapters of this video series. Joe gives a tour of the job posting content type as well as the job application content type.

Shows how to change the formatting and label display for fields, and how to control whether a field appears in the teaser, full mode, search results and other display mode contexts.

Goes through the process of creating a new content type of a job posting, and shows how to customize the Title and Body labels for this new content type.

Gives a high-level overview of the field configuration page and defines the field types, widget and display formatters. Also adds a simple text field as an example of extending an existing content type.

Goes through the process of creating a view of something other than content. In this case it's a view of users, and this chapter talks about other types of views of entities that are possible from different base tables.

This video series will continue the Job Board example from the Fields for Site Builders series where we will discover ways to display all of the job postings, allow people to find the one they are looking for and easily apply for it.

This screencast shows how you can use Rules to alter the presentation of your Drupal site, such as:

• Enabling, disabling and moving blocks around
• Setting HTML title element and also on-page titles
• Setting body classes
• Setting the active menu item (using Menu Position)

Some bigger questions about using Rules for altering presentation is also discussed:

• Using Rules for presentation altering is relatively heavy. (It consumes about 2.5 MB more PHP memory than Context, and has about the same loading times – judging from a first, rough comparison.)
• Using Rules for presentation altering gives a more complex UI than the interface use for modules made for more particular use cases.
• It is possible for modules to provide alternative user interfaces to Rules.
• Rules allows reusing actions in many different situations, between different modules.
• Rules (and Entity API) provides generalized data handling.

Additional resources

Rules guide (Drupal.org)

This screencast shows some more settings in the Rules Link module:

• How to use the visibility conditions in Rules Link.
• That the entity the link is attached to is always available as a parameter.
• That you can add more variables to the Rules Link by passing them in the URL – and that you need to set up the parameters settings to tell the link how to interpret the data.
• That each link is available as a field in Views.
• That you can add parameters to links displayed in Views.
• That there is a bug preventing links for non-node entities to be displayed in Views.

Additional resources

Rules guide (Drupal.org)

This screencast shows some functionality included in Rules Bonus Pack, as an example of how to make Rules integrate with other modules on your site. In particular it shows some Views and CTools/Page manager integration.

• Condition: Check the number of results from a view.
• Action: Load the sum of a Views column as a number. (Currently only D6!)
• Action: Load the first result in a view into Rules.
• Action: Clone a full node object.
• Action: Convert a number into a date
• Event: Trigger a rule when a custom page is rendered.
• Special: Allow Rules condition components to be used as CTools access plugins.

Additional resources

Rules guide (Drupal.org)

This screencasts presents some of the settings available when configuring a bulk operations view. It covers:

• Controlling access to your VBO, and why that is important.
• Showing actions as buttons rather than a select list.
• The new cool option for selecting all items on all view result pages.
• Turning check boxes into radio buttons.
• Showing or hiding the result of the bulk operations.
• Showing action configuration on the view page.
• How to skip the confirmation page.
• How to give your actions customized labels.

Additional resources

Views Bulk Operations (VBO) guide (Drupal.org)

This screencast introduces the awesome Views Bulk Operations (VBO) module, that can be used to perform actions on objects listed with Views. The screencast covers:

• How to add VBO fields to your views, to allow actions
• That these fields are displayed as check boxes (or possibly radio buttons) in your view
• That each VBO field is tied to one type of data in the view (such as nodes, node revisions or users)
• That some VBO actions have configuration pages

Additional resources

Views Bulk Operations (VBO) guide (Drupal.org)

This screencast shows how to repeat scheduled events – in this case sending repeated reminders to users who have not logged in for a month. The screencast covers:

• How to set up a component for scheduling (as seen before)
• The point of re-using an ID for scheduled tasks, to avoid duplicate reminders
• The trick of finding a good triggering event for scheduling (which is not always easy)
• The trick of having a component schedule itself upon completion, thereby repeating the scheduling
• How to delete scheduled tasks, and why that may be a good idea

Additional resources

Rules guide (Drupal.org)

This screencast shows “how you can use multiple-parameter Rules components in VBO and get the additional parameters as action configuration,” which translates to:

• If you have more than one parameter for a Rules component, you can still use it with VBO.
• Any additional parameters will be displayed as action configuration, meaning that the person executing the VBO gets to choose parameter value.
• Sadly, you can’t access data from the view item being actioned – you’ll have to stick with fixed input values. (If you want to use data from the processed item, you could actually do this inside the Rules component!) This is an issue being worked on.
• If you have complex parameters – such as taxonomy terms instead of just an integer – you can (mostly) use entity ID in the direct input mode.
• You can, by coding, change the form elements used for input. It is probably better to target the Rules data widget than doing a standard form_alter, but both will work.
• You could, for example, use this for changing comment settings on nodes, or adding selected tags to nodes. (Both examples shown in this screencast.) You could also use it for, say, sending customized messages or something. Or cloning existing nodes with changes specified in parameters.
• Bonus: If you add an entry to a multiple-value field in an entity, Rules won’t pick up that the entity has changed – make sure to add a “save entity” action in the rule.

Not mentioned in this screencast but still good to know:

• You can have Rules components without any parameters as well. No sweat.
• You can use Rules components without any parameters matching the View type too. In that case, you’ll have to specify all the parameters manually.
• If you have a component with several parameters matching the view type, the first one will be auto-populated by VBO – the rest you have to set manually.

Additional resources

Rules guide (Drupal.org)

This screencast shows how to start using Rules Scheduler. It does this by mimicking the Comment Closer module – closing the comments on articles two weeks after they are created. The screencast covers:

• Rules Scheduler needs components – you can only schedule prepared components
• Components can be scheduled as actions, for example from reaction rules
• The evaluation time for scheduled tasks is set with strtotime(), which means that you can use highly flexible expressions
• You can also use data selection, combined with offsets if you want to
• Every scheduled task should have a unique task ID, or it will replace existing tasks
• Scheduled tasks are displayed under the Schedule tab on the Rules admin pages
• You can delete tasks manually if you want to
• You can schedule tasks manually, without the need of reaction rules
• It is sometimes useful to execute rule components manually, to see that the scheduled tasks will work as expected

Additional resources

Rules guide (Drupal.org)

This screencast presents a way to help manage article promotions, separate content types used for promoting articles, providing more flexibility than standard teasers. The screencast shows how to have promotion nodes being published, unpublished and deleted in sync with the articles they belong to. Topics covered are:

• Reacting on the node deletion event.
• Using fetch entity by property to load a list of all relevant promotion nodes.
• How to have the loaded list unlimited in length.
• Using the delete entity action.
• How to call rule components from a reaction rule.
• Why it might be a good idea to have actions in separate components when acting on node updates.
• Cloning rule components.
• Publishing and unpublishing nodes.

Additional resources

Rules guide (Drupal.org)