It has been suggested that Radioactivity module would be a good replacement for the statistics module in core. (http://drupal.org/node/1209532#comment-4979538)

I would like this thread to track thoughts, ideas and todos to get the module ready for core.

Comments

mikgreen’s picture

Radioactivity tracks popularity (one values for particular period of time), which is not the same as statistics (how many times a node is viewed, every day etc.).

tcmug’s picture

Obligatory copy-paste from (http://drupal.org/node/1209532#comment-4986442)

Radioactivity is heading towards a slimmer and lighter set of basic features that will be easy to extend: it will in its most basic form track "views" and have cache piercing and be as fast as drupal can (memcache storage, non-drupal-boostrap storage would all be extensions).

The current Radioactivity 2.x in core sounds way silly. I'd go for having the extendable basic functionality in core instead that is in the (unwritten) plans for 3.x.

Wim Leers’s picture

Subscribing. I'm very interested :)

Ravi.J’s picture

Sub

slowflyer’s picture

Issue summary: View changes

Drupal 8 is there, Radioactivity not part of core.
Will this module be updated to Drupal 8?

Thanks,
slowflyer

tcmug’s picture

I'm glad to say that yes and it will be released soon, it will be a lot more minimalistic than the D7 version though :)

Sutharsan’s picture

@tcmug, could you write a (short) roadmap for the D8 version? It would give us insights of you plans.

Paulset’s picture

Is a date of release planned?

mike.davis’s picture

Any further news on release date for the D8 version as I would really like to use this for a new client project?

Do you have a roadmap of issues that need looking at before you can get a release as I would be interesting in helping out if I can?

rich.yumul’s picture

subscribe :)

tcmug’s picture

Making a note here on progress:

  • Radioactivity fields can be added
  • Counter, linear and decay modes
  • Emits are working with the internal route
  • Cron decays works

Whats missing is all the tiny details and big features from D7 version, e.g. history, separate decay profiles (do we even need those, since the use case for this has been one per field most of the times?), rules integration, etc... so there is lots to cover.

I've started producing a way to define the rest endpoint to emit to. This will be dead simple, that is, setting the URL as a configuration and if the endpoint is not defined, the default one will be used (=the internal route). This probably does not need a UI yet apart from seeing the effective setting in the status report page.

Once that is done the module SHOULD BE USABLE but without all the *bling*. That said, I have already installed the current version of the module on a production site and it seemed to do its job very well :)

mike.davis’s picture

Thanks @tcmug, I have had a play with what is currently available and as a MVP it does seem to work well.

Do you think it is worth a bit of tidy up and release the first alpha release?

Could you create a 'meta issue' which links off to an issue for each task that you feel needs to be done to bring it up to a full D8 version?

From this we can have discussions on each issue and relevant patches, which also enables the highlighting of whether certain tasks would be needed for D8 or not (like the decay profiles that you mentioned).

tcmug’s picture

That is certainly the way to go.

I'll set up the alpha release during this week (theres one more thing that I need to test '& check & do), feel free to create those meta issues in the mean time if you want.

tcmug’s picture

Status: Active » Closed (fixed)

Closing this.