Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I would like to clear out all emissions history and set all nodes to zero. I am currently using the Live storage and Basic profile mode.
I see these tables in the db.
radioactivity_decay_profile
radioactivity_deferred_incidents
radioactivity_flood_map
radioactivity_history
I thought I could also delete the radioactivity field from the content types but was wondering if there was another way.
Thank you.
Comments
Comment #1
lenoz CreditAttribution: lenoz commentedI have the same issue Isabug. I set up radioactivity wrong and need to reset.
You're actually missing the most important table from your list - the one that stores radioactivity values is (off the top of my head) node_field_radioactivity - it's pretty easy to read, with node IDs and radioactivity values pretty obvious.
I'm stuck without SQL access to edit the table though - and the DBA module is not (and will not ever be, I would imagine) updated to allow database editing in its Drupal 7 version.
I also considered changing the Energy cut off value to a ridiculously high level, and then set it back again, but it does state this would only be a level under which energy is ignored and not reset, which of course makes sense considering this setting is for just the particular decay profile.
Comment #2
jfrederick CreditAttribution: jfrederick commentedThe Views Bulk Operations module has a bulk operation called 'Change Value'. It also has an initially disabled default View for the admin/content page that adds a VBO select list of operations to perform. With VBO installed and the View enabled, you can bulk-select your content on that page (using any filters you may add to the View), and then manually set the new value of the radioactivity field.
Comment #3
Sutharsan CreditAttribution: Sutharsan at LimoenGroen commentedIssue triage: Closing issue due to lack of activity.
If you believe this issue is closed in error, feel free to re-open.