|
Bosnian=ba, Chinese (Taiwan)=tw, Chinese (Traditional)=cn, Czech=cz, Danish=dk,
@@ -159,10 +160,10 @@ But this can change. You should ask to have a such Add-On to PHPNuke authors, an
FAQ-SET050 : ERROR "MISSING $ ON LOOP VARIABLE ..." -PROBLEM: +PROBLEM: When I run awstats.pl from command line, I get: "Missing $ on loop variable at awstats.pl line xxx" -SOLUTION: +SOLUTION: Problem is in your Perl interpreter. Try to install or reinstall a more recent/stable Perl interpreter. You can get new Perl version at ActivePerl (Win32) or Perl.com (Unix/Linux/Other). @@ -170,10 +171,10 @@ or Perl.com (< FAQ-SET100 : I SEE PERL SCRIPT'S SOURCE INSTEAD OF ITS EXECUTION -PROBLEM: +PROBLEM: When I try to execute the Perl script through the web server, I see the Perl script's source instead of the HTML result page of its execution ! -SOLUTION: +SOLUTION: This is not a problem of AWStats but a problem in your web server setup. awstats.pl file must be in a directory defined in your web server to be a "cgi" directory, this means, a directory configured in your web server to contain "executable" files and @@ -186,12 +187,12 @@ properties, with Apache you have to use the "ExecCGI" option in the directory "D FAQ-SET150 & FAQ-SET200 : INTERNAL ERROR OR ERROR 500 IN MY BROWSER ERROR "... COULDN'T SPAWN CHILD PROCESS..." IN APACHE ERROR LOG -PROBLEM: +PROBLEM: AWStats seems to run fine at the command prompt but when ran as a CGI from a browser, I get an "Internal Error". Sometimes I get the following message in my error log file: [error] [client xx.xx.xx.xx] No such file or directory: couldn't spawn child process: c:/mywebroot/cgi-bin/awstats.pl -SOLUTION: +SOLUTION: This problem occurs with Apache web server with no internal Perl interpreter (mod_perl not active). To solve this, you must tell Apache where is your Perl interpreter. For this, you have 2 solutions: 1) Change the first line of awstats.pl file with the full path of your Perl interpreter. @@ -206,9 +207,9 @@ to find the Perl interpreter. FAQ-SET250 : LOG FORMAT SETUP OR ERRORS -PROBLEM: Which value do I have to put in the LogFormat +PROBLEM: Which value do I have to put in the LogFormat parameter to make AWStats working with my log file format ? -SOLUTION: +SOLUTION: The AWStats config file give you all possible values for LogFormat parameter. To help you, this is some common cases of log file format, and the corresponding value for LogFormat you must use in your AWStats config file: @@ -263,8 +264,8 @@ support other various log formats. FAQ-SET260 : SETUP FOR FTP SERVER LOG FILES -PROBLEM: What do I have to do to use AWStats to analyze some FTP server log files. -SOLUTION: +PROBLEM: What do I have to do to use AWStats to analyze some FTP server log files. +SOLUTION: AWStats was built to analyze web,wap or proxy server's log files. However it can be used with some FTP server log files. This is example for ProFTP: Modify the proftpd.conf file. At the very top add two new defines. @@ -276,18 +277,19 @@ Copy config awstats.conf file to "awstats.proftp.conf". Modify this new config file: LogFile="/var/log/xferlog" LogFormat="%time1 %host %logname %method %url %code %bytesd" -DNSLookup=0 +DNSLookup=0 ShowLinksOnUrl=0 ShowAuthenticatedUsers=1 + Warning: This tip doesn't work for FTPed files that contains spaces in them (they are not reported). You can still convert your log file to replace 'space' char into '_'... FAQ-SET280 : ERROR "NOT SAME NUMBER OF RECORDS OF..." -PROBLEM: When I run AWStats from command line (or as a cgi from a browser), I get +PROBLEM: When I run AWStats from command line (or as a cgi from a browser), I get a message "Not same number of records of ...". -SOLUTION: +SOLUTION: This means your AWStats reference database files (operating systems, browsers, robots...) are not correct. Check in your disk that you have only ONE of those files (They should be in 'db' directory where awstats.pl is installed): browsers.pl @@ -299,9 +301,9 @@ Check in your disk that you have only ONE of those files (They should be in 'db' FAQ-SET300 : ERROR "COULDN'T OPEN FILE ..." -PROBLEM: I have the following error: +PROBLEM: I have the following error: "Couldn't open file /workingpath/awstatsmmyyyy.tmp.9999: Permission denied." -SOLUTION: This error means that the web server +SOLUTION: This error means that the web server didn't succeed in writing the working temporary file (file ended by .tmp.9999 where 9999 is a number) because of permissions problems. First check that the directory /workingpath has "Write" permission for @@ -320,12 +322,12 @@ user, used by web server process, can write into). FAQ-SET350 : EMPTY OR NULL STATISTICS REPORTED -PROBLEM: AWStats seems to work but I'm not +PROBLEM: AWStats seems to work but I'm not getting any results. i get a statistics page that looks like i have no hits. -SOLUTION: That's the most common problem you +SOLUTION: That's the most common problem you can have and reason is simple: Your log file format setup is wrong. If you use Apache web server -The best way of working is to use the "combined" log format (See into the README.TXT file +The best way of working is to use the "combined" log format (See the Setup and Use page to know the way to change your Apache server log from "common" log format into "combined"). Don't forget to stop Apache, reset your log file and restart Apache to make change into combined effective. Then you must setup your AWStats config file with value LogFormat=1. @@ -342,9 +344,9 @@ You can also read the next FAQ to have examples of LogFormat value according to FAQ-SET450 : NO PICTURES/GRAPHICS SHOWN -PROBLEM: AWStats seems to work (all data and counters seem to be good) +PROBLEM: AWStats seems to work (all data and counters seem to be good) but I have no image shown. -SOLUTION: With Apache web server, you might have +SOLUTION: With Apache web server, you might have troubles (no picture shown on stats page) if you use a directory called "icons" (because of Apache pre-defined "icons" alias directory), so use instead, for example, a directory called "icon" with no s at the end (Rename your directory physically and change the DirIcons parameter in config file @@ -353,10 +355,10 @@ to reflect this change). FAQ-SET500 : HOW TO ROTATE MY LOGS WITHOUT LOOSING DATA -PROBLEM: I want to archive/rotate my logs using my web server +PROBLEM: I want to archive/rotate my logs using my web server system options or a third software (rotatelog, cronolog) but don't want to loose any visits information during the rotate process. -SOLUTION: +SOLUTION: If you use a rotate system (internal web server feature or third software), this means you probably not use AWStats PurgeLogFile nor ArchiveLogRecords parameter. * If your config file is setup to process current log file (because you want to use the AllowToUpdateStatsFromBrowser @@ -376,9 +378,9 @@ To use cronolog or rotatelog you must setup your web server log file name using FAQ-SET550 : HOW TO RUN AWSTATS FREQUENTLY -PROBLEM: AWStats must be ran frequently to update statistics. +PROBLEM: AWStats must be ran frequently to update statistics. How can I do this ? -SOLUTION: +SOLUTION: With Windows, you can use the internal task scheduler. The use of this tool is not an AWStats related problem, so please take a look at your Windows manual. @@ -399,9 +401,9 @@ To run update every hour, use : FAQ-SET600 : HOW CAN I EXCLUDE MY IP ADDRESS (OR WHOLE SUBNET MASK) FROM STATS ? -PROBLEM: I don't want to see my own IP address in the stats or I want to exclude counting +PROBLEM: I don't want to see my own IP address in the stats or I want to exclude counting visits from a whole subnet. -SOLUTION: +SOLUTION: You must edit the config file to change the SkipHosts parameter. For example, to exclude: - your own IP address 123.123.123.123, use SkipHosts="123.123.123.123" @@ -416,24 +418,24 @@ log file). FAQ-COM100 : AWSTATS SPEED/TIMEOUT PROBLEMS ? -PROBLEM: When I analyze large log files, +PROBLEM: When I analyze large log files, processing times are very important (Update process from a browser returns a timeout/internal error after a long wait). Is there a setup or things to do to avoid this and increase speed ? -SOLUTION: Yes. You really need to understand +SOLUTION: You really need to understand how a log analyzer works to have good speed. There is also major setup changes you can do to decrease your processing time. - Launch AWStats more often (from crontab or a scheduler). More often you launch AWStats, more faster is AWStats (because the less is the number of NEW lines in log, since last run, to process). See the Benchmark page to get examples of launching frequency according to your web traffic -- You can disable DNSLookup in configure file (set DNSLookup=0) -but this requires absolutely that hosts addresses in your log file are already -resolved (need to setup your web server to do so). +- You can disable DNSLookup in configure file (set DNSLookup=0) +but this requires that hosts addresses in your log file are already resolved (need to setup your web server to do so) or that +you don't need the domain/country report. Log analyze speed can be increased by 2 to 50 times but your web server will be slowed. If you don't understand what is an "already resolved reverse DNS lookup", keep this parameter to 1. -- If you use Apache, set PurgeLogFile to 1 (By default, to avoid bad surprise, +- If you use Apache, set PurgeLogFile to 1 (By default, to avoid bad surprise, PurgeLogFile is 0 in configure file, but you can set it to 1 to ask AWStats to purge the log file after processing it. This increase speed for next run). - Use last AWStats version. @@ -441,18 +443,18 @@ to purge the log file after processing it. This increase speed for next run). FAQ-COM150 : BENCHMARK / FREQUENCY TO LAUNCH AWSTATS TO UPDATE STATISTICS -PROBLEM: What is AWStats speed ? -PROBLEM: What is the frequency to launch AWStats process to update my statistics ? -SOLUTION: +PROBLEM: What is AWStats speed ? +PROBLEM: What is the frequency to launch AWStats process to update my statistics ? +SOLUTION: All benchmarks information and advice on frequency for update process are related into the Benchmark page. FAQ-COM200 : HOW REVERSE DNS LOOKUP WORKS, UNRESOLVED IP ADDRESSES -PROBLEM: The reported page AWStats shows me +PROBLEM: The reported page AWStats shows me has no hostnames, only IP addresses, countries reported are all "unknown". -SOLUTION: When AWStats find an IP address +SOLUTION: When AWStats find an IP address in your log file, it tries a reverse DNS lookup to find the hostname and domain if the DNSLookup parameter, in your AWStats config file, is DNSLookup=1 (Default value). So, first, check if you have the good value. The DNSLookup=0 @@ -472,9 +474,9 @@ provided with AWStats distribution (This tools is an improved version of logr FAQ-COM250 : DIFFERENT RESULTS THAN OTHER ANALYZER -PROBLEM: I also use webalizer (or another +PROBLEM: I also use webalizer (or another log analyzer) and it doesn't report the same results than AWStats. Why ? -SOLUTION: +SOLUTION: If you compare AWStats results with an other log file analyzer, you will found some differences, sometimes very important. In fact, all analyzer (even AWStats) make "over reporting" because of the problem of proxy-servers and robots. However AWStats is one the most accurate and its "over reporting" @@ -502,10 +504,10 @@ an algorithm to detect keywords of unknown search engines with unknown url synta FAQ-COM300 : DIFFERENCE BETWEEN LOCAL HOURS AND AWSTATS REPORTED HOURS -PROBLEM: I use IIS and there's a difference +PROBLEM: I use IIS and there's a difference between local hour and AWStats reported hour. For example I made a hit on a page at 4:00 and AWStats report I hit it at 2:00. -SOLUTION: This is not a problem of time +SOLUTION: This is not a problem of time in your local client host. AWStats use only time reported in logs by your server and all time are related to server hour. The problem is that IIS in some foreign versions puts GMT time in its log file (and not local time). So, you have also @@ -524,8 +526,8 @@ So this means this way of working might never be changed. FAQ-COM350 : HOW CAN I PROCESS OLD LOG FILE ? -PROBLEM: I want to process an old log file to include its data in my AWStats reports. -SOLUTION: +PROBLEM: I want to process an old log file to include its data in my AWStats reports. +SOLUTION: You must change your LogFile parameter to point to the old log file and run the update. However the update process can only accept files in chronological order, so if you have already processed a recent file, you must before reset all your statistics (see next FAQ) and restart all the update process for all past log files and in chronological order. @@ -533,18 +535,18 @@ reset all your statistics (see next FAQ) and restart all the update process for FAQ-COM400 : HOW CAN I UPDATE MY STATISTICS WHEN I USE A LOAD BALANCING SYSTEM THAT SPLITS MY LOGS ? -PROBLEM: How can I update my statistics when i use a load balancing system that split my logs ? -SOLUTION: +PROBLEM: How can I update my statistics when i use a load balancing system that split my logs ? +SOLUTION: The best solution is to merge all split log files resulted from all your load balanced servers into one. For this, you can use -the logresolvemerge tool provided with AWStats since version 3.2 : +the logresolvemerge tool provided with AWStats : logresolvemerge.pl file1.log file2.log ... filen.log > newfiletoprocess.log And setup the LogFile parameter in your config file to process the newfiletoprocess.log file. FAQ-COM500 : HOW CAN I RESET ALL MY STATISTICS ? -PROBLEM: I want to reset all my statistics and restart my stats from now. -SOLUTION: +PROBLEM: I want to reset all my statistics and restart my stats from now. +SOLUTION: All analyzed data are stored by AWStats in files called awstatsMMYYYY.[site.]txt (one file each month). You will find those files in directory defined by "DirData" parameter (same directory than awstats.pl by default). To reset your stats for a month, you just have to delete the file for the required month/year. @@ -555,9 +557,9 @@ You will have to process all past log files (in chronological order) to get old FAQ-COM550 : CAN I SAFELY REMOVE A LINE IN HISTORY FILES (awstatsMMYYYY*.txt) ? -PROBLEM: After processing a log file I want to change my statistics +PROBLEM: After processing a log file I want to change my statistics without running AWStats update process but changing directly data in AWStats historical database files. -SOLUTION: +SOLUTION: If you remove a lines starting with "BEGIN_" or "END_", AWStats will find your file "corrupted" so you must not change those kind of lines. All lines that are not in any "section" (between a BEGIN_xxx and END_xxx line) should also not be removed. However you can change any line that is a "section record", but you do this at your own risk. Your reported stats @@ -568,27 +570,27 @@ might have wrong values after that. FAQ-SEC00 : CAN AWSTATS BE USED TO MAKE CROSS SITE SCRIPTING ATTACKS ? -PROBLEM: If a bad user use a browser to make a hit on an URL that include a < SCRIPT > ... < /SCRIPT > +PROBLEM: If a bad user use a browser to make a hit on an URL that include a < SCRIPT > ... < /SCRIPT > section in its parameter, when AWStats will show the links on the report page, does the script will be executed ? -SOLUTION: +SOLUTION: No. AWStats use a filter to remove all scripts codes that was included in an URL to make a Cross Site Scripting Attack using a log analyzer report page. FAQ-SEC150 : HOW CAN I PREVENT SOME USERS TO SEE STATISTICS OF OTHER USERS ? -PROBLEM: I don't want a user xxx (having a site www.xxx.com) to see statistics of user yyy (having +PROBLEM: I don't want a user xxx (having a site www.xxx.com) to see statistics of user yyy (having a site www.yyy.com). How can i setup AWStats for this ? -SOLUTION: +SOLUTION: Take a look at the security page. FAQ-SEC200 : HOW TO MANAGE LOG FILES (AND STATISTICS) CORRUPTED BY 'CODE RED VIRUS LIKE' ATTACKS ? -PROBLEM: My site is attacked by some Code Red Viruses. This make my log file corrupted +PROBLEM: My site is attacked by some Code Red Viruses. This make my log file corrupted and full of 404 errors. So my statistics are also full of 404 errors. This make AWStats slower and my history files very large. Can I do something to avoid this ? -SOLUTION: +SOLUTION: Yes. 'Code Red virus like' attacks are infected browsers or robots that make hits on your site using a very long unknown URL like this one (hoping your server is IIS): diff --git a/docs/awstats_security.html b/docs/awstats_security.html index 03cf3ab3..50ac3aac 100644 --- a/docs/awstats_security.html +++ b/docs/awstats_security.html @@ -57,7 +57,7 @@ be securely viewed by correct allowed users only (or sent by mails). If users have a command line access (telnet) on statistics server, you must set correct permissions on AWStats database files. Set all AWStats database files (built by the update process) for config/domain1 to have read/write for user1 (or an admin user) and NO read and NO write permissions for any other users. -Then, check that the "SaveDatabaseFilesWithPermissionsForEveryone" parameter is set 0 in your config/domain files. +Then, check that the SaveDatabaseFilesWithPermissionsForEveryone parameter is set 0 in your config/domain files. If AWStats database files for config/domain1 are read protected, only allowed users can see statistics for config/domain1. If AWStats database files for config/domain1 are write protected, only allowed users can update statistics for config/domain1. @@ -117,8 +117,8 @@ AuthType Basic require valid-user </Files> -Then edit each config/domain file you want to be protected to set "AllowAccessFromWebToAuthenticatedUsersOnly" to 1. -You can also edit list of authorized users in the "AllowAccessFromWebToFollowingAuthenticatedUsers" parameter. +Then edit each config/domain file you want to be protected to set AllowAccessFromWebToAuthenticatedUsersOnly to 1. +You can also edit list of authorized users in the AllowAccessFromWebToFollowingAuthenticatedUsers parameter. Other tip: If you define AWSTATS_CONFIG environment variable in your web server environment (Adding SetEnv AWSTATS_CONFIG myconfigvalueformydomain with other directives in your Apache VirtualHost config), AWStats diff --git a/docs/awstats_setup.html b/docs/awstats_setup.html index a8e17493..a36748c1 100644 --- a/docs/awstats_setup.html +++ b/docs/awstats_setup.html @@ -78,11 +78,11 @@ Whatever the name you choose, this new file must be stored in - /etc/opt/awstats or /etc/awstats or /etc or same directory than awstats.pl (so cgi-bin) for Unix/Linux users. - same directory than awstats.pl (so cgi-bin) for Windows and other OS. Edit this new config file with your own setup : -- Change "LogFile" value with full path of your web server log file (You +- Change LogFile value with full path of your web server log file (You can also use a relative path from your awstats.pl directory). -- Check if "LogFormat" has the value "1" (it means "NCSA apache combined/ELF/XLF log format"). -- Change "DirIcons" parameter to reflect relative URL of icon directory. -- Edit "SiteDomain" parameter with the main domain name or the intranet +- Check if LogFormat has the value "1" (it means "NCSA apache combined/ELF/XLF log format"). +- Change DirIcons parameter to reflect relative URL of icon directory. +- Edit SiteDomain parameter with the main domain name or the intranet web server name used to reach the web site to analyze. - You can change other parameters if you want. @@ -128,11 +128,11 @@ awstats.virtualhostname.conf, and, if not found, will look for awstats.conf. Whatever the name you choose, this new file must be stored in - same directory than awstats.pl (so cgi-bin) Edit this new config file with your own setup : -- Change "LogFile" value with full path of your web server log file (You +- Change LogFile value with full path of your web server log file (You can also use a relative path from your awstats.pl directory). -- Change "LogFormat" to value "2" (it means "IIS Extended W3C log format"). -- Change "DirIcons" parameter to reflect relative URL of icon directory. -- Edit "SiteDomain" parameter with the main domain name or the intranet +- Change LogFormat to value "2" (it means "IIS Extended W3C log format"). +- Change DirIcons parameter to reflect relative URL of icon directory. +- Edit SiteDomain parameter with the main domain name or the intranet web server name used to reach the web site to analyze. - You can change other parameters if you want. @@ -143,7 +143,7 @@ Install and Setup is finished. You can jump to the Build 3) With other web servers Setup process is similar to setup for Apache or IIS. -Use "LogFormat" to value "3" if you have WebStar native log format. +Use LogFormat to value "3" if you have WebStar native log format. @@ -167,8 +167,8 @@ Found 0 old records, Found 225601 new records. Dropped records are records discarded because they were not user HTTP request or requests were not qualified -by AWStats filters (See "SkipHosts", "SkipFiles", -and "OnlyFiles" parameters). +by AWStats filters (See SkipHosts, SkipFiles, +and OnlyFiles parameters). If you want to see which lines were dropped, you can add the -showdropped option on command line. Corrupted records are records that does not match log format defined by "LogFormat" parameter in AWStats config/domain file. With all webservers you can experience a little bit corrupted records (<5%) even when everythings work correctly. @@ -183,7 +183,7 @@ purge your log file after each update process even if it's HIGHLY recommended to Note : A log analysis process is slow (one second for each 4100 lines of your logfile with Athlon 1Ghz, plus DNS resolution time for each different IP -address in your logfile if "DNSLookup" is set to 1 and not already done in your log file). +address in your logfile if DNSLookup is set to 1 and not already done in your log file). See Benchmark page for more accurate information. @@ -199,7 +199,7 @@ For sites with: This is ABSOLUTELY necessary to keep good performances. See AWStats Benchmark page for more accurate information. -!!! Warning, if you don't use (or can't use with IIS) the "PurgeLogFile" parameter, +!!! Warning, if you don't use (or can't use with IIS) the PurgeLogFile parameter, it's very important that you don't forget to purge/rotate your log file yourself (or setup your web server to do it) frequently. Even if AWStats never analyzes twice the same log record, the more often you clean your log file, the faster AWStats will be. @@ -238,7 +238,7 @@ will use awstats.virtualhostname.conf file). If you named your config file awstats.conf, just use URL: http://www.myserver.mydomain/cgi-bin/awstats.pl -Note: If "AllowToUpdateStatsFromBrowser" parameter is set to 1 in AWStats config/domain file, +Note: If AllowToUpdateStatsFromBrowser parameter is set to 1 in AWStats config/domain file, you will also be able to run the update process from your browser. Just click on link "Update now". diff --git a/docs/awstats_what.html b/docs/awstats_what.html index aee5cc9d..fa2af6f2 100644 --- a/docs/awstats_what.html +++ b/docs/awstats_what.html @@ -38,26 +38,27 @@ Features A full log analysis enables AWStats to show you the following information: - * Number of VISITS, and UNIQUE VISITORS, list of last visits, - * Visits duration, + * Number of VISITS, and number of UNIQUE VISITORS, + * Visits duration and list of last visits, * Authenticated users, * Days of week and Rush hours (pages, hits, KB for each hour and day of week), + * Hosts list and unresolved IP addresses list, * Domains/countries of hosts visitors (pages, hits, KB, 259 domains/countries detected), - * Most often pages viewed, entry pages and exit pages, - * File types, + * Most viewed, entry and exit pages, + * Files type, * Web compression statistics (for mod_gzip), * Browsers used (pages, hits, KB for each browser, each version, 72 browsers: Web, Wap, Media browsers...), * OS used (pages, hits, KB for each OS, 28 OS detected), - * VISITS OF ROBOTS (287 robots detected), - * SEARCH ENGINES, Keyphrases or Keywords used to find your site (The 61 most famous search engines are detected like yahoo, google, altavista, etc...), - * HTTP errors (Page Not Found, ...), + * VISITS OF ROBOTS (286 robots detected), + * SEARCH ENGINES, Keyphrases or Keywords used to find your site (The 63 most famous search engines are detected like yahoo, google, altavista, etc...), + * HTTP errors (Page Not Found with last referrer, ...), AWStats also supports the following features: * Can analyze a lot of log formats: Apache NCSA combined log files (XLF/ELF) or common (CLF), IIS log files (W3C), WebStar native log files and other web, proxy or wap servers log files). See AWStats F.A.Q. for examples. * Works from command line and from a browser as a CGI, * Update of statistics can be made from a web browser and not only from a scheduler, * Unlimited log file size, support split log files (load balancing system), - * Reverse DNS lookup during analysis, + * Reverse DNS lookup before or during analysis, * A lot of options/filters can be defined, * Multi-named web sites supported (virtual servers, great for web-hosting providers), diff --git a/docs/styles.css b/docs/styles.css index 9b1cd92f..667420c6 100644 --- a/docs/styles.css +++ b/docs/styles.css @@ -1,15 +1,17 @@ -body { - background-color: #FFFFFF; - font: 14px verdana,arial; - font-family: sans-serif; - margin-top: 4; - margin-bottom: 4; - margin-right: 4; - margin-left: 4; -} -a:link { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } -a:visited { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } -a:active { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } -a:hover { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: underline; } - -td.CFAQ { font: 14px verdana,arial; color: #000000; font-family: sans-serif; text-decoration: none; } +body { + background-color: #FFFFFF; + font: 14px verdana,arial; + font-family: sans-serif; + margin-top: 4; + margin-bottom: 4; + margin-right: 4; + margin-left: 4; +} +a:link { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } +a:visited { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } +a:active { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: none; } +a:hover { font: 14px verdana,arial; color: #2200C0; font-family: sans-serif; text-decoration: underline; } + +td.CFAQ { font: 14px verdana,arial; color: #000000; font-family: sans-serif; text-decoration: none; } +.CProblem { font: 14px verdana,arial; color: #660000; font-family: sans-serif; text-decoration: none; } +.CSolution { font: 14px verdana,arial; color: #448866; font-family: sans-serif; text-decoration: none; } -- 2.47.3 |