[TYPO3-english] AWStats in 6.2

[Jigal van Hemert]

Hi,

On 06/06/2015 09:18, Scotty C! wrote:
> I share Clemens' sentiments exactly.  I had no idea this feature (and
> therefore extension) was on the chopping block,  otherwise I surely
> would have expressed disapproval. I too have been using this extension
> for almost a decade

Generating data for general statistics is not a task for a CMS. For 
normal access statistics the log files of your web server software 
contain better information. Piwik and Google Analytics have features 
which any extension an only dream of. Storing this data in a 
specialistic application will also not pollute the CMS database.

With so many people using specialistic applications for statistics it is 
not smart to slow down all requests in all installations for generating 
statistics data in a very small number of installations.
An extension could easily implement the code for these statistics if 
they want to store it inside the CMS.

> and I know there's a better way to handle its
> demise. I'm going to have some angry clients when o tell them we have to
> abandon their old logs and move to another system, which could also
> disappear in a few years.

Any system can disappear at any moment. Extensions are often developed 
for one or more projects. If the requirements change or the developer 
moves to another company or other development systems these extensions 
may very well be abandoned.

> In fact,  I could say the same for the dozens
> of extensions I've had to simply abandon because they're not compatible
> with 6.2. I have easily spent 100 hours of staffing costs trying to
> shoehorn longtime faithful extensions from 4.5 LTS into 6.2 LTS and/or
> find new ones altogether.

In most cases it's not a lot of work to make extensions work in 6.2. 
After a lot of migrations I can say that it's generally a matter of 
removing require/include calls and replacing a few calls to removed 
functions. In some cases it requires more work to make extensions 
compatible.

> This does not bode well for newcomers and it
> frustrates people like me who would much rather put the cost of that
> labour toward a membership/donation to TYPO3/association.

Newcomers don't see the old extensions in TER (unless they activate a 
filter) and TER always shows the compatible TYPO3 versions.
The costs of upgrading an installation are something that needs to be 
taken into account as part of the cost of maintaining a website.

-- 
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org