Views is a fantastic module that allows you to build complex database queries through configuration. However, I've found that a weird variation of the 80/20 rule applies to views: 80% of the time, the configuration will get you 100% of what you want, but 20% of the time, it will only get you 80% of what you want. That's where the views hooks are handy, especially hook_views_query_alter. I've used this many times - adding a where clause, modifying a field, etc.
$rosie = new RoseBush; $rosie->plant(); $rosie->shred_flesh(); $rosie->fertilize(); $rosie->weed(); $rosie->water();
Okay, so it's no D7CX or anything, but I just spent the weekend upgrading my three little modules to Drupal 7:
I've been trying out the managed Aegir mini offering by Omega8.cc, and been quite happy with it. A few days ago I got a message that I needed to migrate them over to another platform because they weren't on a Pressflow-based Drupal 6 platform. These are sites that I haven't touched for a long time - apparently, in fact, since before I started using Pressflow. So then: how to migrate the sites without spending a lot of time on them? I decided to just move all the code into each site's folder and then migrate. Here's how to do it:
My wife just started using a freshly-installed Acquia Drupal 7.2.2 site. She's very web savvy, but not familiar with Drupal. Here are some quotes:
(reading) "'Step 1. Start at the beginning. Visit the administration section for a task-based or module-based overview of the options available to configure your website.' Which one do I want? Task-based or module based? Well, I can't do task based, because the link doesn't work! I guess I'll do module-based. Let's see... Acquia Network - do I want to do that? I don't know what any of these things are...."
One of the things that annoys me about all ticket management systems is the amount of time that it takes to add a new ticket. Click the project; click for a new ticket; wait for the page to load; enter a title; select a priority; assign to a user; select other options; enter a longer description; click "Save"; wait for the page to load; rinse and repeat. That's a lot of overhead just for adding a ticket! I've tried unfuddle, basecamp, jira, and openatrium, all with the same complaint.
I often use the calendar module for my Drupal sites, and I often want to put holiday information in them without making a whole bunch of events or doing weird stuff with Javascript. With a very small patch to add a date class to table cells generated by calendar module, this is possible with pure css. Since every day of the year has a distinct class in the format Dec-3, you can simply address each one through css:
Ever want to make a nine-pointed star using spyrogimp? Unless you're better at straight math than me, it's a little tough to figure out the numbers. Here are some that work:
A ratio of 7:1 (for example, 84 teeth on the outer wheel, and 12 on the inner) will get you a regular nonagon. For something with a nicer weave to it, try 120 outer and 48 inner. I've found that a hole ratio of about .23 works well on that last one. By varying the settings, combining different figures, applying selective shading, and removing extraneous lines, you can get some really nice figures.
So, there are probably many reasons you might be getting a page like this one, with no CSS whatsoever. I've discovered a few. My most recent surprise was drush cc.
At least in my case, it looks like clearing that "css and js" cache is a bad idea on a site with page caching turned on, because anonymous users will see the WSOC (white screen of confusion - just a little shy of the WSOD).
Kudos to the Aegir project for Aegir's alpha15 release, and especially Miguel for the contribution of a long-anticipated (by me at least) upgrade script. As before, you must read and carefully follow the version-specific upgrade notes at the bottom of the Aegir upgrade instructions, but after that the script automated everything.
