I ran into a ugly little Drupal bug when I launched this site. I still don’t know the cause, but the solution is pretty easy to do.
After I launched I noticed a couple comments on the backend, but not the front. I tried looking all over the interface, and poured over my theme and even tried Drupal’s default Garland theme, but these comments never worked. I then looked directly in the MYSQL database and there they were, looking just fine.
So you write a lot of CSS, right? I used to be like you. I’ll bet you probably write enough CSS to see tons of possibilities in the code, but also maybe you pull your hair out over some of the limitations? It’s ok, you can admit it. Like when you have to copy/paste code all over your stylesheets, or when you try to remember the browser prefixes and divergent syntaxes for CSS3 techniques, or how there’s no help whatsoever in managing color values. Or maybe you’re one of us super nerds who actually has a use for programmatic loops and logic? If you nodded for even one of those, then let me introduce you to Sass.
Y’know, that was our best Drupaldelphia so far! From the perfect venue at Temple and the sessions, to the keynote and the attendees, it all came together really well.
I don’t know if this is why it worked so well, but I wasn’t as involved in the planning this year. Leading up to last Friday, I was very much in my own world, dealing with work and deadlines, and starting to stress over the two sessions I was involved in. It may have been late, but my panelmates and I sussed out our plan for the Themer’s Roundtable session, and shortly thereafter, I polished my Design in the Browser session as much as I could. Getting those pieces in place gave me enough mental space to see how well this event was going. We had a great mix of Drupal pros and newbies, and I’m happy to report that I saw both types in my sessions.
If you haven’t already heard, whitehouse.gov recently relaunched with Drupal as its new content management system. There’s nothing jumping off the screen screaming “Drupal” when you go there*, but you may have heard the global Drupal community’s shouts of “Woo-hoo” and “w00t!” last week when it launched. You see, aside from the benefits that the White House will receive from having a great open-source CMS, this is one of the loudest endorsements of our platform we’ve had to date.
if your location fields are not displaying in your view, you need to add a relationship to your view for the location. then have the location fields you are trying to display use that relationship.
then it should work. you may need the dev version unless this post is old.
Thanks to everyone who helped make yesterday’s DrupalCamp Philadelphia so much fun and a success. I was really feeling all kinds of Drupal love from all around. Hope so all of you an more the next time we do this.
As promised, I’m uploading my slides from my presentation.
from: http://mustardseedmedia.com/podcast/episode31
<?php
$args = $tids;
print views_embed_view('viewname', 'block_1', $tids);
?>Taxonomy pages have a default array of term ids that will work as views arguments.
Use the theme function on your template.php file
<?php
/**
<?php
$args = array();
print views_embed_view('viewname', 'block_1', $args);
?>By default when you group multiple cck values in a view each item just gets a single ‘field-item’ class. You can’t override this with a simple field formatter or any of the views tpl.php files. The theme function is in contributions/cck/includes/views/content.views.inc (http://drupalcontrib.org/api/function/theme_content_view_multiple_field/6)
My version adds an incremental class to each item that you can use to target specific items. This should go in template.php with “YOURTHEME_” replacing “theme_”
function theme_content_view_multiple_field($items, $field, $values) {
You can create custom formatters for CCK Fields. The code is pretty simple.
This doesn’t remove the extranious wrapper divs that cck creates by default, tho. To remove those I’m also using a modified content-field.tpl.php file.