IMPORTANT: RocketTheme Drupal Club is Sunsetting in 2012

Please be aware that the Drupal Club will be sunsetting this year, with new themes being released ONLY through June of 2012, and support ending in December of 2012. Please read the full post for further details.

Drupal FAQs

Drupal Frequently Asked Questions

My menu or layout doesn't work or I'm getting JavaScript errors.
As a first step, if you are using MooTools menus, make sure that you have JS COMPATIBILITY unchecked in the theme's configuration page. The jQuery in Drupal and the JavaScript in the MooTools library sometimes conflict with each other. (If you have modules using jQuery, you may also want to disable them temporarily to further identify the source of the problem.)

Leaving JS COMPATIBILITY checked is one of the top reasons for having difficulties with RocketTheme modules.

The JS COMPATIBILITY theme option is for users that are not using any RocketTheme modules and have no need to include the mootools library. By enabling this option, it EXCLUDES all mootools functionality.

My images aren't appearing (or only a broken icon is appearing) in RocketTheme modules, such as dRokStories and dRokNewsRotator or my module doesn't rotate or work the way it does in the demo.
There are two things you should always check if you are not seeing images or if the slider/rotator is not working correctly.

a. Check that the path in your dRokNewsRotator module or dRokStories module configuration is correct. Remember, it is "relative" to the theme directory itself. Don't be confused by the "files" directory here where you might normally put your image files in Drupal. It is NOT in the "sites/default/files" directory - but rather in the theme directory itself.

The location of your images must match the path on the configuration screen EXACTLY.

b. Double-check that the path you assign your images is terminated with a "/".

A forward slash must be appended to the end of your image file directory structure in order for the dRok modules to be able to find your images.

If you are not seeing your images at all or getting 404 errors, we suggest using Firebug or Web Developer Toolkit (free add-ons from the folks at Mozilla) to help you identify the source of the problem.

I've promoted my content to the Front Page area but it's not showing up?
On some themes, because of the use of blocks to provide a very dynamic front page layout, the "promoted" content area has been hidden. However, it is very easy to make this content display once more on your site. If you want a simple page to show, you will need to remove the if statement on the appropriate page.tpl.php file to allow it to display or "print". Look for the following code: 
  if($is_front){if($latest_news) {
  print $latest_news;
  }
  }
  else {
  print $content;
  }
Then remove the if statement. The altered code should look simply like this: 
print $content;
Your front page content that is promoted should now appear.

My (print, comment, feedback, etc) links don't show in my theme.
Open the node.tpl.php file and look for the following code: 
<?php //print $links; ?>
Remove the forward slashes so that the code looks like this: 
<?php print $links; ?>
Your links will now appear.

My thumbnails are not appearing in a dRokNewsRotator module or dRokStories module.
Thumbnails are not created automatically by the these modules. You will have to create the thumbnail and upload it to the same directory as your other image files.

dRokNewsRotator and dRokStories images are tied to the nid (Node ID) of the article - so if the nid of the article is 25, then the main image should be 25.jpg and the thumbnail should be 25_thumb.jpg.

I can't re-arrange or "drop" items once they are picked up in the Admin interface.
This is a known Drupal JavaScript issue. There is a patch that addresses this on the Drupal.org site.

http://drupal.org/files/issues/800968_tabledrag-for_2.patch

Troubleshooting Drupal Permissions
Although not specifically a RocketTheme issue, wrong permissions can cause problems throughout your Drupal installation. Here are some steps you can take to try and locate the source of the problem.

1. Check user access control and make sure that all users can "access content"
URL: mysite.com/admin/user/access.

Often, when installing a module, I accidentally change key permissions. Make certain that users that you want to have "access content" permission actually have them. It is easy to "get lost" in the Drupal permissions page.

Two Drupal modules that are extremely useful here are: Better Permissions and Filter Permissions.

These modules are essential for filtering permissions by role and/or module.

2. Check input filter roles
URL: mysite.com/admin/settings/filters

One problem with having a lot of input filters is that you can easily mess up the permissions of a particular filter. If a user does not have permission to use an input filter, then they cannot edit content that can only be edited with that input filter. To give a real-world example, say that there is a new input filter called "tinyMCE." Next, I set up my permissions for tinyMCE so that only my webmaster role can use the tinyMCE input filter. While doing this, I also set permissions so that only the webmaster can use my "Filtered HTML" and "Full HTML" input filters. Next, I set up a new role called "intern" and let the intern edit content. However, my intern reports that he cannot access any of the edit pages. Why? He needs to have access to the "tinyMCE" input filter.

3. Clear site cache and views cache
URL for Views Cache: mysite.com/admin/build/views/tools

Sometimes site cache and views cache can result in strange permissions problem. Site cache can be reset with the Developer module "Empty cache" menu option. To have this appear, you need to enable the Devel block. (You can also access this through the admin_menu module.) In addition to clearing the site cache, sometimes it helps to clear the Views cache. This is especially true if your permissions problems started after you edited a view. The option to clear views cache can be found in the Tools section of the Views administration page.

4. If all else fails, rebuild node permissions
URL: mysite.com/admin/content/node-settings/rebuild

Sometimes Drupal node permissions get corrupted. When this happens, rebuilding the node permissions can solve the problem. Please be advised that if you have a lot of nodes, this can take a very long time.

5. The Last Step: Looking for Module-Specific Issues
URL for Update Script: mysite.com/update.php

If none of the previous steps work, it's time to start disabling modules. First, if I recently installed a new version of a module, I make sure that I have run the update.php script. Next, I generally disable the module, and then repeat step three.

Enabling and disabling modules can be tedious and time-consuming. If you have shell access to your Drupal installation, you might want to install Drush which provides a quick command line interface to uploading, enabling and disabling modules in a Drupal installation.

Where can I find theme settings?
  • Login into the Drupal administrator
  • Go to Administer → Themes → theme_name → Configure
  • Change Settings
  • Save Changes