The site slogan doesn't come out anywhere useful in Garland. Is there any chance we could get this fixed? My preferred option would be for it to be a) smaller, and b) on the line after the title, rather than the same line.

Comments

dwrunyon’s picture

Agreed. At the very least I think it should be tagged and in the sylesheet so that we can easily adjust it without having to make any changes to the main Garland code... see this thread:

http://drupal.org/node/198500

catch’s picture

Title: Proper support for site slogan » Garland: better support for site slogan
Version: 6.2 » 7.x-dev

Feature requests go against the development version.

WorldFallz’s picture

Status: Active » Needs review
StatusFileSize
new1.08 KB

This has been a thorn in my side for a while-- so here's a patch against the current head. I don't like to mess with other designer's designs, so this patch preserves the original look and feel (there's no change to the css) while adding id's to the site name and slogan so those wishing to style differently can do so very easily.

My only question is to the validity of having span tags inside an h1 tag. Anyone know if that will validate? (i'm working on a local test box, so I'm not sure how to check the validation).

EDIT: Here's an example of some css that this patch makes possible:

#sitename {
  display: block;
  top: 14px;
  line-height: 1.5em;
  position: relative;
  font-variant: small-caps;
}
#siteslogan {
  display: block;
  font-size: 50%;
  line-height: 3em;
  font-style: italic;
}
dmitrig01’s picture

Status: Needs review » Needs work

Your code style needs a bit of work

+  $site_title ='';

Space after =.

+    $site_fields[] = '<span id="siteslogan">'. check_plain($vars['site_slogan']).'</span>';

We have spaces on both sides of the .

Also, we do not use two words run together for IDs or classes - please hyphenate.
And, can you add the CSS to your patch?

WorldFallz’s picture

StatusFileSize
new1.09 KB

Your code style needs a bit of work

Sorry... i'm lost without coder, lol. You'd think i'd remember the style rules after a while, but they don't seem to want to stick.

We have spaces on both sides of the .

Is this new? The one rule I do remember from coder (asking me to change dozens of lines) was that "." did not have a space when one of the items was quoted.

Also, we do not use two words run together for IDs or classes - please hyphenate.

done.

And, can you add the CSS to your patch?

Of course I can, but I purposely didn't as I didn't want to change the original appearance of the Garland theme which, as far as I know, hasn't changed since it was released. My patch was just intended to make individual styling of the site name and slogan easier-- not change the style of the distributed theme itself. I just included that bit of styling as an example for any beginners following the thread.

If you really want it in the patch itself let me know and i'll reroll.

Attached is updated patch for the other issues.

wayland76’s picture

I'm looking at the 6.x version, but it seems to me that the mission statement could do with some CSS too -- while we're doing things, is there any chance that that could happen? Not sure if it makes any difference, but the styling I'm complaining about is in the "Belgian Chocolate" colour scheme.

Anonymous’s picture

Version: 7.x-dev » 6.9

Hi,

I applied the v2 patch and received an error/failure.

I'm using MAMP on MAC OS X and have the root of this site in /Applications/MAMP/htdocs/bhwcc.

I ran the patch from that directory with the following output:

Chili:/Applications/MAMP/htdocs/bhwcc Rick$ patch -p0 < garland_slogan-v2.patch
patching file themes/garland/template.php
patch unexpectedly ends in middle of line
Hunk #1 FAILED at 37.
1 out of 1 hunk FAILED -- saving rejects to file themes/garland/template.php.rej

Any suggestions or comments are appreciated.

Thanks,
Rick

iantresman’s picture

This is surely a bug. The theme allows a slogan, and concatenates it with the site title making it unusable as it stands. Since Garland is the theme that comes out of the box, it doesn't help newbies.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.