Drupal

It appears that loading the JStools tabs CSS @import derictive before the default line for CSS styles in a Drupal theme prevents the default styles from being applies in IE browsers (yes, including IE7 and IE8).

<style type="text/css" media="all">@import "/modules/jstools/tabs/tabs.css"</style>

I was able to zero-in on this particular line (above) by commenting out the &amp;lt;?php print $styles; ?&amp;gt; directive in the Drupal theme and instead hard-coded the tyle @import lines (you can get these by copying the source of your pages before you comment out $styles in our theme).

Armed with the @import directives in the source, I applied them all and then removed one by one and in blocks until I was able to isolate the line causing the problem.

Solution
Writing the default style file (style.css) before the tabs.css call will solve the problem. The simples way to implement this is to hard-code a link to styles.css before the

<?php print $styles; ?> call in the drupal theme. The only down-side to ths approach is the fact that you will end up with two calls t the style.css file, but that does not have visible effects visually, or in markup validity.

Drupal was selected as the ideal CMS infrastructure by the Recreational Services Department of Indiana University. The design team for this department had a clear vision, and an approved set of mock designs for the proposed website. The In-house content manager for Indiana University described the vision to include available functionality in Drupal, as well as customizations of existing modules to fit the specific website needs of the student, staff and alumni community. The presentation of content in this CMS setup was to be based on the already approved mocks (Adobe Photoshop files) with reasonable enhancements and accommodation for the specific needs of a CMS website.

iDonny Productions created a custom Drupal theme based on the approved designs provided by the client; with multiple content regions to enable the dynamic placement of content blocks depending on a predetermined logical relevance matching system.

NB: Although we always recommend the use of semantic XHTML markup without using tables for layout, the scope requirements for this site required the use of tables for basic layout to avoid differences in browser implementation of CSS-P positioning box models.

Indiana University Recreational Services Website

As the name of this module suggests, it finds and presents entries (documents or nodes) that are similar to the current document. The similarities can be in any field of the node (Title and Body fields). Unlike a previous module that required modifying one of the mode tables to add a column that would be populated with keywords and association data, this module does not modify the existing table structure destructively, and so the module can be un-installed without having to meticulously and manually edit the core database tables.

By suggesting similar documents to the reader alongside with a given page in question, the website owner has the opportunity to help the reader gain more in-depth information about the topic of the current document.

Links within a site make it easier to expose otherwise hidden and relatively obscure documents that do not already have links from external sites or search engines. This makes it easier to showcase documents covering topics that the user would have otherwise not sought in search engines. In addition to this human-centric reason to use this module, it is indispensable to have links from one page to other pages within the same website for Search Engine Optimisation. If the search engine is crawling a page, by having links to related documents, it achieves the dual objective of giving the search engine crawler a path to crawl more pages (exposure), and also increases the site-wide SEO by grouping and interlinking documents that cover similar topics.

The Power of Drupal is as a result of the foundation that it forms for the added functionality and features that are provided by modules. Most of the modules (if not all of them) are developed as opensource software applications that can further be engineered, and improved upon. Being that many of the modules already available on Drupal.org have gone through several editions and revisions, they are stable and feature-rich enough to merit a review, and discussion of features and benefits.

Drupal core is a lean and efficient framework that integrates so closely with the 'out-of-box' modules and other third-party modules using the hooks system to provide functionality that seamlessly works with the core application. The following is a series of reviews of the many modules that I have reviewed and used in many installations and configurations of Drupal in the past three (3) years as Drupal has developed and improved both in fame, stability and functionality to be one of the most versatile CMS framework in the opensource and general CMS market.