The clickable link and text in the message block is very small on the front page. Is there a way I can enlarge it?
Many thanks in advance
No - at the bottom of styles_fonts.css etc - if you open your theme folder, for example theme/Clouds/config.php you should find a row like
$THEME->sheets = array('styles_layout', 'styles_fonts', 'styles_color');
and you could paste the css to styles_fonts.css or styles_colors.css found from the same folder. If standard sheets is true and no custom sheets are defined paste the code to standard theme css files...Mike,
one more thing - if you need to change size of text "No messages waiting" the css is
.block_messages .info, .block_messages .footer a, .block_messages .message a, .block_messages .user a {
font-size:1.5em;
line-height:2em;
}
Instead of those values you could use for example font-size:12px; and line-height:16px; (I did not know which theme you have - standard theme has em values but several themes use pixels)
Check also that you have pasted css to correct theme (your current theme) css file. By the way...what version of moodle you have? (tested this with moodle 1.8 myself)
Mike,
add for example the following css to the end of the last css file in your theme config.php $THEME->sheets = array(...):
.sideblock .message a {
font-size:1.5em;
line-height:2em;
}
if you want to change font size of the name too use
.sideblock .message a, .sideblock .user a {
font-size:1.5em;
line-height:2em;
}
May I check your site somewhere in www ? All I need is to see the source code (css files)
Edit: I'm sure that this code works in moodle 1.8 with standard theme css but you have not told either your version of moodle or theme so I can't test it - sometimes pages may stay in cache for some time.
Well there really should not be any secrets in css files...if you look at source code of moodle.org you find after <head> ...
<link rel="stylesheet" type="text/css" href="http://moodle.org/theme/standard/styles.php?lang=en_utf8" />
<link rel="stylesheet" type="text/css" href="http://moodle.org/theme/moodleorange/styles.php?lang=en_utf8" />
and so on. Moodle reads first css from standard theme, then from custom theme, then from css for ie7 or ie6 and if you have not made any changes to core code the latter tags always override the former tags. It's the same in css files. Css at the bottom overrides css at the top.
On the other hand if you read source code of your site you should see some "classes" before "Messages" etc - those classes are used in css to give certain properties for the following html tags. With Firefox Web Developer plugin you may view css for different tags yourself too 
Hello - reading this post eminded me about my problems when I first installed a new theme.
Use the Firefox browser and download a plugin called greasemonkey. I can't remeer all the details but this allows you to see which element of css i controlling a particular element of the page.
When set up you shift+click on a field and it displays element information then you can have the option to edit the css temporarily
Have a look around for more information - but this saved my bacon
Use the Firefox browser and download a plugin called greasemonkey. I can't remeer all the details but this allows you to see which element of css i controlling a particular element of the page.
When set up you shift+click on a field and it displays element information then you can have the option to edit the css temporarily
Have a look around for more information - but this saved my bacon
To that folder where your theme (on server) is...
yourmoodlesite/theme/yourtheme/fw_fonts.css
One note about greasemonkey - I have not used it and vulnerabilities from the past may be fixed but read this before you start running scripts through greasemonkey
http://tipsosaurus.com/security-tips/security-threats-of-using-greasemonkey
JFTR
Greasemonkey's security holes have been long since closed:
"Avoid Common Pitfalls in Greasemonkey - How the History of Greasemonkey Security Affects You Now"
by Mark Pilgrim, author of Greasemonkey Hacks
http://www.oreillynet.com/pub/a/network/2005/11/01/avoid-common-greasemonkey-pitfalls.html
(for more information on Greasemonkey see http://diveintogreasemonkey.org/)
And I suppose the above mentioned Firefox plugin is meant to be Firebug.
And CSS FAQ and Themes FAQ are always good starting points for learning more about CSS and theming.
Cheers,
Frank
Greasemonkey's security holes have been long since closed:
"Avoid Common Pitfalls in Greasemonkey - How the History of Greasemonkey Security Affects You Now"
by Mark Pilgrim, author of Greasemonkey Hacks
http://www.oreillynet.com/pub/a/network/2005/11/01/avoid-common-greasemonkey-pitfalls.html
(for more information on Greasemonkey see http://diveintogreasemonkey.org/)
And I suppose the above mentioned Firefox plugin is meant to be Firebug.
And CSS FAQ and Themes FAQ are always good starting points for learning more about CSS and theming.
Cheers,
Frank
回复ian lake