The module assumes all radioactivity fields are stored in the database. However, I'm developing a site that uses MongoDB as the default field storage. For example, _radioactivity_update_energy() fails when run on such environment (since there's not table named field_data_my_radioactivity_field). Is it possible to make the module independent of whatever field storage is being used?

Comments

tcmug’s picture

tcmug commented

There is (was?) a bug which prevented the use of the core functions and I haven't had the time to see if it has been fixed in D7 yet - there seems to be a patch for it though (http://drupal.org/node/1126000). Have to give that a go at some point.

tr’s picture

tr commented
Issue summary: View changes
Status: Active » Closed (outdated)

Alternative storage is supported for Radioactivity entities by default in Drupal core 8+.

Drupal 7 is no longer supported.