I had a scenario at work where we wanted to style a link to a certain page differently than other links. In this particular use case, we wanted the link that directed to one particular path to look like a button, while all other links appear as text links.
To do something like this, try using attribute selectors in your CSS. Rather than rehash a really good explanation, and to give myself a reference when I need to go search for this info again, here's the source where I learned the ins and outs of this nifty trick:
The Skinny on CSS Attribute Selectors at the always awesome CSS-Tricks.
When creating my first responsive designs, I was dismayed to discover what happened to my text when I rotated my iPhone from portrait to landscape views. The body text grew huge, overtaking page titles, subheads, and any typographic hierarchy I had established for my page layouts.
This didn't happen on Android phones. The resizing of the body text was limited to Safari on iPhones.
Turns out this isn't an Apple bug; it's a feature. The CSS property -webkit-text-size-adjust specifies a size adjustment for displaying text content in Safari on iPhone.
To prevent my body copy from growing and overtaking other typographic elements on my page when viewed on an iPhone in landscape mode, I added the following to only the CSS that applied to my mobile viewports:
Now, be careful here. Using that bit of CSS will also affect Safari on larger tablet or desktop views. You'll want to also include this CSS in your media queries for your viewport sizes that are larger than mobile phone views, so that users can resize their text in their desktop browsers if they want to:
After wasting a bit of time trying to figure out how to enable Clean URLs with a Drupal installation on Bluehost, I found the answer here:
Drupal 7 - 'Clean URLs' problems with SimpleScripts
Worked like a charm.
On a non-work-related note, I just love how my recent fall plantings are thriving in my new garden.
Just registered for BADcamp 2011 in Berkeley, California from October 21-23. I've missed my own backyard camps the last time that DrupalCamp Dallas and DrupalCamp Austin rolled around due to family commitments. So I'm looking forward to this one. It's huge! 1100 peeps? It's a Con!
Flight booked. Room booked. Give me a shout if you're going and you want to hook up to talk theming and design for Drupal.
Just like a website, the world of website design and development is fluid. Trends change. New devices enter the marketplace to allow users to browse the web in ways not previously possible. Content management systems are constantly updated with new and improved features and bug fixes.
Which leads me to the decision to redesign my personal website.
When I created my old site three years ago, I was in the midst of making a change in my sitebuilding focus. I'd dabbled in a few content management systems, and built my old site in WordPress. Little did I know at the time that I'd never want to touch WordPress again. After I finished my site, I started building all my sites in Drupal. I never looked back. Well, except when I wanted to update the information on my personal site.
As a Drupal designer and sitebuilder, it's time to leave my old site and design behind.
My new site will be built on Drupal 7, and I plan to explore responsive web design as a solution to the changes in the way we browse sites.
So long, dragonfly. Maybe I'll see you soon on the new site.
On many websites I create for small businesses, the site owner wants (and should have) a blog. Drupal's blog tools are set up to be designed for multiple users by default. Many times, this is functionality I don't want or need.
One glaring element that I typically want to remove if a blog is by a single user is the "username's blog" link that appears in each blog post.
The following, found here, added to my theme's template.php file, did the trick:
// Hide username's blog
if (isset($links['blog_usernames_blog'])) {
unset($links['blog_usernames_blog']);
}
return theme_links($links, $attributes);
}
Change mytheme to the name of your theme, and remember to clear the cache after uploading the new template.php file.
A list of modules I commonly use on Drupal sites, with links to the project page for easy landing and downloading.
- Content Construction Kit (CCK)
- Views
- Views Slideshow
- View Cycle
- Administration menu
- Admin role
- Advanced help
- Devel
- Google Analytics
- Token
- ImageField
- FieldField
- ImageCache
- ImageAPI (required by ImageCache)
- Transliteration (required by ImageCache)
- jQuery plugins
- Pathauto
- Frequently Asked Questions
- SpamSpan
- Skinr
- Fusion (theme)
- Root Candy (admin theme)
This is one big "note to self" for me to reference as needed for current and future Drupal installs. If you found this through google, maybe it will help you, too.
Bluehost and Clean URLs
Problem: After basic install, system would not enable Clean URLs. Site is not live, but currently accessed through bluehost utility domain url.
Solution: First, make sure .htaccess file exists on server. Second, since Drupal is not on a production site, but rather on the utility domain, change the following in .htaccess:
# VirtualDocumentRoot and the rewrite rules are not working properly.
# For example if your site is at http://example.com/drupal uncomment and
# modify the following line:
RewriteBase /~username
Note: When site goes live, this line will need to be changed again.
Memory Limits in php.ini
Depending on the modules installed, the memory limit in the php.ini file will likely need to be increased. If php.ini is not already installed, install it through the control panel. Then open the file, and find the line memory_limit = . Increase the memory limit.
Bluehost change in February 2010 regarding uploaded images
On February 2, I and many others woke up, checked our Drupal sites and discovered that they were broken. After 45 minutes on the phone to tech support, conferring with another local Drupal user who turned out to be on Bluehost, and the twittervine, the following solution emerged and now needs to be implemented on Bluehost Drupal installs:
In /sites/default/files/, edit the .htaccess file, change the line that reads Options +FollowSymLinks to Options SymLinksIfOwnerMatch. So the new .htaccess file in the sites/default/files location should now read:
Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options None
Options SymLinksIfOwnerMatch