|
 February 27th - Online tool
You can now build your configuration file online. Using an editor to manually fill all configuration entries was really painful and
subject to errors. Now, you can do the job on the w3perl website, it will allow people without a web server running to use the administration
interface and will provide a user's configuration template database.
Configuration files are available to anyone with no restriction, it means if you don't want your paths to be public, use fake values.
As everything is public, you can change other user's configuration files ... or delete them. So be nice, I don't want to act as a policeman.
I hope to improve the forms thanks to your feedback, contact me if you are puzzled.
February 22th - 3.021
First bug report from users using 3.02....
Fix done :
- If you install w3perl on a virtual secure server and want the stats to
be output on another virtual server, there is a path problem to
extract the URI as document root are different for the two virtual
servers.
=> I have no choice than adding a new parameter in the
configuration file.
- Weekly stats are not well updated, as only the last week is shown on
the web page.
=>Adding a -b flag to reset weekly stats and fixing the problem
- Missing country codes (serbia,somalia and montenegro)
=> Adding new flags
- Login field with space is not well understood (IIS logfile)
=> if login field with space is not quoted, will bypass the line
Fix in progress :
- W3Perl is not able to use logfiles from load-balancing
server.
=> AWStats have a nice answer to this problem and I will
implement this also as Awstat's author gave me his agreement.
- Mail stats show an empty day when switching to incremental mode.
- Hourly stats about days only read one logfile even if daily stats are spread over
several logfiles.
- Real time stats on Windows doesn't load images
- Ajax search too slow with big website
=>split datafile
- if server installation and document server are different, pages links to server installation rather than document server.
Requests :
- Support for SiteMinder logfiles
- Support for more than one referer page with cron-refer.pl -p <page>
- Building configuration file on w3perl website
- Windows installer : choosing the web server root path
- Support for load-balancing websites
- CSS
February 13th - v3.02
New release ! 3.02 is out !
Another step have been done to the perfect tool ;)
W3Perl can run as a web analytic tool, no need to get log files from
your server. Using a javascript tag to be inserted in your pages, your
own logfiles can be generated. Then W3Perl is able to retrieve them
remotely to be able to compute your stats locally (avoiding the use of
your server CPU).
Use javascript tag only if you have no access to your logfiles server
as stats are being rather poor this way. You can't monitor traffic as
only web pages can be tagged.
But if you have logfiles access, you can add another javacsript tag to
monitor screen size, color depth and plugin. (see /w3perl/resources/js/miscstats.js)
Few minor bugs have been fixed, the most important being :
- Proftp logfile rotation begin with number 0 (apache starts at 1), so
I've changed the scripts to begin with 0 instead of 1.
A Windows installer for Abyss Web Server have been added with a
dedicated configuration file : config-abyss.pl
I've planned to add heatmap in 3.03, looks a nice tool to add.
February 04th - v3.016
Document stats show inactive files (unix only), so it will be easier
for you to remove all those files with very old 'last access'. Largest
files are listed in order to save your bandwidth usage.
Some bugs have been fixed about IIS/W3C in the administration
interface. Status code display files even if requete size is null.
|