SARG ChangeLog
-Feb-02-2009 Version 2.3
+Feb-09-2009 Version 2.3
- LDAP usertab added.
Now you can have your users in a LDAP Server.
Use these tags in sarg.conf: LDAPHost, LDAPPort, LDAPBindDN, LDAPBindPW,
LDAPBaseSearch, LDAPFilterSearch
- Parse the string flags from sarg.conf once during the reading of sarg.conf instead of manipulating and duplicating the tests of the strings where they are used.
- Useragent report limited to requested date range.
+ - Link to external css file instead of including it verbatim in each HTML file (thanks to Maxim Britov).
Feb-04-2010 Version 2.2.7
- Extra compile and run time protection (FORTIFY_SOURCE) fixed in configure.
void css(FILE *fp_css)
{
- FILE *fp_in;
- char buf[MAXLEN];
- size_t nbytes;
-
if(ExternalCSSFile[0] != '\0') {
- if((fp_in=fopen(ExternalCSSFile,"r"))==NULL) {
- fprintf(stderr, "SARG: (css) %s: %s\n",text[45],ExternalCSSFile);
- exit(1);
- }
- fputs("<style type=\"text/css\">\n",fp_css);
- while((nbytes=fread(buf,1,sizeof(buf),fp_in))>0)
- fwrite(buf,1,nbytes,fp_css);
- fclose(fp_in);
- fputs("</style>\n",fp_css);
+ fprintf(fp_css,"<link rel=\"stylesheet\" href=\"%s\" type=\"text/css\">\n",ExternalCSSFile);
return;
}
#block_it none
# TAG: external_css_file path
-# This tag allow internal sarg css override.
+# This tag allow internal sarg css override by providing the name of
+# the css file to link into each HTML page.
+#
+# In versions prior to 2.3, this used to be an absolute file name to
+# a file to include verbatim in each HTML but as it takes a lot of
+# spaces, version 2.3 switched to a link to an external css file.
+# Therefore, it must be the HTTP server path on which a client browser
+# may find the css file.
+#
# Sarg use theses style classes:
-# .body body class
+# .body body class
# .info sarg information class, align=center
# .title title class, align=center
# .header header class, align:left