Awstats and subdomains in DA 1.37

N

nieuwhier

Verified User
Joined
Sep 8, 2005
Messages
279
Location
Netherlands
The awstats adjustment in 1.37 works fine and solves the previous month issue. Also disabling .html output it great.

However, what about subdomains and awstats. I think nothing is changed there ?

Does someone knows that ?
 
To me it looks like DirectAdmin forgot to add CGI version of AWStats to subdomains, because it is only static html versions available.

The big question then, is what will happen with subdomains stats if we disable static html pages for AWStats? Will it break the stats for subdomains?
 
I have sent them a email with a link to this thread, so I think they will respond here soon ...
 
I disabled generation of static html for AWStats, and the daily stats have now been generated. However it did not generate stats for subdomains! All my users is now without stats for subdomains!

We need a quick fix for this! My customers is going to complain. They want stats also for subdomains. :(

(However, one thing that make me happy, is that before AWStats used about 40 minutes to generate stats for all domains. With static html pages disabled, it took only 2 minutes to generate all stats! That I like!)
 
Last edited:
Hello,

I've just implemented the full compliment of stats options for subdomains as well. It will have the awstats dropdown with static months and cgi option, as well as a link to webalizer if both are enabled at the same time. (same as for domains).

I'm just compiling all binaries now and they should be uploaded to the pre-release section in about an hour for testing, for whoever wants to try it out.

John
 
Thank you, John. I hope you will release a new version with this fix soon.

Could you also please make it so that the AWStats dropdown link open the stats page in a new window? Because customers can't right click and do it themself, because it is in a drop down box.

It is very hard for us when you hard code this html, so that we can't access it. It would be so very much better if you placed the html directly in the skin template files.

Also, please remove the link in drop down for "This month" when we have disabled static html pages. I have now been forced to do this to remove it (it is not possible to hide with style="display:none;", because that does not work on the "option" html element:

Code: 
|$/usr/local/bin/php
<?php
$data = <<<END
|DOMAINS|
END;
$data = str_replace(">This month", " disabled='disabled'>", $data);
echo $data;
?>
DONE|

I have a lot more replacement in that code also, but have removed it in this example. I do a lot replacements to make the html code valid. It must be said, the hardcoded html code is often bad.
 
Last edited:
You must log in or register to reply here.
Back
Top