Problem Awstats

[sci2tech]

(01-08-2009 04:23 AM)pgentoo Wrote:  Doesn't it make sense to tie this password to the account password though?

There are not tie together and should not be. This user (I speak about protected areas) can be removed, or password can be changed. I guess that is better not to add a default user, and better just tell in account creation email that they can add users to this area using Webtools -> Group / User management. The idea was that everybody can add as many users as they need for this area (and users to be named freely not using a pattern like user@domain.tld).

(01-08-2009 04:23 AM)pgentoo Wrote:  Would it make more sense to manage the passwords for stats entirely through their "Protected Areas" interface, instead of in the actual VirtualHost? That way they would see right away that they have a protected area called "Statistics", and they could even remove the user/password if they wanted to.

I did not wanted to use "Protected Areas" interface mainly because no .htaccess file is generated. Things were more complicated to tunnel authenticate date trough proxy and keep synchronization between user folder htaccess and awstats directory. But I guess we can add a form that permit to edit user belonging to statistics group in "Protected Areas" just to make things simpler for users. It a first implementation, and always can be improved. Any suggestion is welcomed.
Daniel Andreca aka sci2tech