Submitted By: Klas Berlič
Adddate: 2010-07-13 06:12:59
Ok, as advised here is new patch that adds this option to global configuration
and to make things more consistent also to com_content component parameters.

Cascading logic is the same as with module caching - there are only Off and
Global on component level so that global off disables all counters.

To test: 
- Set Joomla cache to off, open single article view. If you reload page hits
counter will increase. 
- Apply patch. Open com_content Options and resave. 
- Reload single article view - hits keep on increasing as before.
- Open com_content Options, set Enable hit counter to Off. Resave. Reload page
and counter stops increasing. Set it back to Global. Resave. Hits are
increasing again.
- go to Global configuration > System settings > System > Enable
counters, set it to off, save. Hits are not increasing. Turn it on, save, hits
are increasing again.

After patch global off should also disable/enable weblinks click counter -
testing is the same procedure as with the last test step with articles. 

Note: hit number you are seeing is actually the one from the previous load. So
after you turn hits counter on you must reload page twice to see the effect.

Submitted By: Amy Stephen
Adddate: 2010-07-13 16:04:29
I had a bit of trouble getting this to work until I went into the Article
Options and re-saved the parameters.

Klas - the Yes and No on the Global Config for Counters should be changed to
match the Web services. (Switch yes and no on new option.)

Other than that, the parameter worked, as indicated.

@test

Submitted By: Louis Landry
Adddate: 2010-07-15 05:50:26
This is a good thought and something that does need holistic review for a future
release (maybe 1.7).  My concern about approving it for 1.6 at this point is
that it not only affects other core features such as the most read module and
hits column in article lists/blogs, but it also will have an impact on
explaining those changes in functionality via the user interface.  So what we
have is a cascading set of changes that will impact everything from the model
you are adjusting all the way down to language strings and user interface in
explaining what the impact of the switch is both at the point of the switch and
at all of the points where the switch would have impact (the modules and
view/layout options).

That's why I would say lets move in this direction at a point in the release
cycle when we can really address this problem holistically.

Submitted By: Rouven Weßling
Adddate: 2011-06-06 17:14:17
Reopening as confirmed as the tracker is now non version specific.