Closed (fixed)
Project:
Radioactivity
Version:
7.x-2.8
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
25 May 2013 at 13:17 UTC
Updated:
1 Feb 2016 at 08:15 UTC
Jump to comment: Most recent
Comments
Comment #1
millionleaves commentedI had this issue on a new installation of Radioactivity. When I checked the radioactivity-bootstrap.cfg.inc file, the recommended changes were already there. Went in circles trying to figure out why the error was still occurring. Then I re-read the status report message and noticed the option to clear the Radioactivity cache and warnings; clicking that made the error go away.
Comment #2
brightboldAargh. Thanks for the RTFM pointer, @millionleaves. I had cleared the cache about 500 times, but hadn't clicked the link to clear the Radioactivity cache. *headdesk*
Comment #3
brightboldComment #5
pratik_kambleI had cleared Radioactivity cache, but same error again popped up in status report. What should I do?
Comment #6
bdupls commentedThanks for this, I thought you only clicked to clear cache once the messages have gone. Once fixed click here to clear Radioactivity warnings and caches.... little cryptic, makes you think you need to clear everything and once you have no messages then clock here. Anyways, thanks for info!
Comment #7
pratik_kamble@bettledupls pardon, but I didn't get what you are suggesting. I have already cleared both drupal and radioactivity cache but same message is popping in status report.
Comment #8
fox mulder commentedSame problem here...
Warning says: "One of the decay profiles is using a storage system that requires Drupal to boostrap. This may lead to serious slowdowns on high traffic sites. You should consider switching to one of the bootstrapless incident storages."
I have only one decay profile ( default ). What should I select in Incident storage dropdown on the /admin/structure/radioactivity/list/default/edit admin page, what are the "botstrapless incident storages"?
I have the next options:
Comment #9
kwlester commentedI'm having this same issue. I've noticed that the module does not record energy when this warning is showing. When you clear the cache, it temporarily works, but then the warning message appears again.
Any updates on this?