Amanda Rodriguez blogs

[...] #62; <div class="field-type-image"> <?php print render($content['field_image'][0]); ?> </div> <?php else: ?> <!-- full [...]

[...] ;div class="field-type-image"> <?php print render($content['field_image'][0]); ?> </div> <?php else: ?> <!-- full node [...]

[...] function: <?php if ($node_region): ?> <div class="node_region"> <?php print render($node_region); ?> </div> <?php endif; ?> Block visibility based on node [...]

[...] to edit the node display settings. In Drupal 6 this is easy but not very straight forward. <?php print $node->content['body']; ?> In Drupal 7 this is even easier: <?php print render($ [...]

[...] t('Buy Now'); ?></a> <div class="field-type-image"> <?php print render($content['field_image'][0]); ?> </div> <?php else: ?> <!-- full node [...]

[...] in. Now onto the full node. <?php else: ?> <div class="image"> <?php print render($content['field_image'][1]); ?> </div> <div class="data"> <?php [...]

[...] . <?php print $node->content['body']; ?> In Drupal 7 this is even easier: <?php print render($content['body']); ?> A region within a node This is a very common need within Drupal [...]

[...] . <?php print $node->content['body']; ?> In Drupal 7 this is even easier: <?php print render($content['body']); ?> A region within a node This is a very common need within Drupal [...]

[...] me at the time, and surely can be improved. Nevertheless it might help someone! Creating the content type Entities probably would have been the better choice for me here since these nodes are never [...]

[...] me at the time, and surely can be improved. Nevertheless it might help someone! Creating the content type Entities probably would have been the better choice for me here since these nodes are never [...]

[...] settings for author information/post date and length of teasers options are now set within the content type edit form under display settings. Also its great that you can set a default parent menu item [...]

[...] is a rather simple implementation and might not be suitable for every project. Creating the content type First thing you'll need to do is create a content type (admin/structure/types/add). We're [...]

[...] image shows three blocks in the new region below the content that show the three list styles: As I stated before the primary links are no longer added by default, there is now a [...]

[...] styles over and over. Some examples of where you would use this is for layout, menus, list styles, font stacks, administration styles, etc. The great thing about skins is obviously that [...]

[...] use across every theme you do. Examples range from 960 Grid system, drop downs, font styles, list styles, etc. Having these available for your use cuts out the boring repetitious CSS and allows you to [...]

[...] with the id of your form: Now that we have our id we can add a switch case to our alter: <?php function mytheme_form_alter(&$form, &$form_state, $form_id) { switch ($form_id) { case ' [...]

[...] .php file, if there is not a preprocess_node() function then you'll need to add one. <?php function YOURTHEME_preprocess_node(&$vars) { // Check if the image field exists if(isset($vars[' [...]

[...] .php file, if there is not a preprocess_node() function then you'll need to add one. <?php function YOURTHEME_preprocess_node(&$vars) { // Check if the image field exists if(isset($vars[' [...]

[...] . Then assign a theme variable to the view preview. The next step is to print this in the node template, one thing to note is that when embedding a view in a template the title field does not get [...]

[...] exists, and if it does then we create the $addtl_images variable that we will print in our node template. Then we create a variable that is the length of the image array. Next we do a for loop, if [...]

[...] exists, and if it does then we create the $addtl_images variable that we will print in our node template. Then we create a variable that is the length of the image array. Next we do a for loop, if [...]

[...] . Then assign a theme variable to the view preview. The next step is to print this in the node template, one thing to note is that when embedding a view in a template the title field does not get [...]

[...] , if you're reading this you know CSS. :) The only thing I'll say is that I usually group my Skinr styles together at the bottom of my file, but obviously you can do whatever you prefer! Page styles [...]

[...] and should not be used on client work yet). Skins consist of a .info file declaring all Skinr styles associated with it, and any additional files needed for those styles. The skins folder sits in [...]

[...] skin Before starting to write I always open up documentation so that I can reference it. Skinr documentation is located at: http://drupal.org/node/578574. Setting up the files for a skin is similar to [...]

[...] needed to use this but I'm sure someone out there is grateful for it! If you look at the Skinr documentation you can also see there is the option to add template files. However, they cannot be applied [...]