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:

function mytheme_links($links, $attributes = array()) {
// 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.

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

# Modify the RewriteBase if you are using Drupal in a subdirectory or in a
# 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:

SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options None
Options SymLinksIfOwnerMatch