Reset the Content viewing counter statistics via Drush

Thanks for a fast reply @cilefen, but modules are free to define their own Drush commands. See for example Search API's Drush commands.

Or do you mean that Drupal core modules specifically won't be allowed to include Drush commands?

Here is a patch which can be used as a starting point, even if it isn't going to get implemented here, but has to be worked through as a feature requests on the Drush project.

The fields in the Statistics node_counter table are nid, totalcount, daycount and timestamp:

$ drush sql-query "SELECT * FROM node_counter"
1 3 3 1585666771
2 1 1 1585666767

$ drush statistics:reset:day
 [success] Statistics day count reset.

$ drush sql-query "SELECT * FROM node_counter"
1 3 0 1585666771
2 1 0 1585666767

$ drush statistics:reset:total
 [success] Statistics total count reset.

$ drush sql-query "SELECT * FROM node_counter"
1 0 0 1585666771
2 0 0 1585666767

Aliases

$ drush srd
 [success] Statistics day count reset.

$ drush srt
 [success] Statistics total count reset.

I want at least to make it pass the test-bot :-)

Another great improvement for the Drupal core Statistics counter would be adding more granular statistics, like visits per current week, month and year. That should probably be done in another issue, though.

Yes @cilefen, I noticed that there are none yet. Also, the requirement for a custom Drush command of adding a composer.json in the root of a module is something to consider.

Perhaps adding the reset option as a button firstly ("Reset statistics" ?) and adding a Drush command which can trigger the action which clicking that "Reset statistics" button does is a viable plan?

Hi @cilefen: I have thought more about it, and you are probably right that it is a Drush issue.

I have updated the patch for Drupal 9 in #54798: "Clear all recorded statistics" button, since the correct way would probably be to have that ready, and then hook in to it with Drush.