Needs review
Project:
Decisions
Version:
6.x-1.6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Apr 2010 at 23:50 UTC
Updated:
15 Jun 2010 at 06:58 UTC
I was trying to cancel my vote and revote again as a test and was finding that I only kept getting the cancel vote button to show up. I looked through and found that there was no implementation of hook_flush_caches() which is what allows for drupal to know which cache tables can be flushed.
Attaching the patch made from diff.
| Comment | File | Size | Author |
|---|---|---|---|
| flush-cache.patch | 392 bytes | btmash |
Comments
Comment #1
ezra-g commentedThanks for the patch here. However, the lack of cache clearing in general is by-design. This cache is not supposed to be cleared unless the vote is deleted. This *should* be accomplished by decisions_votingapi_delete() -- Can you confirm that this function isn't working properly?
Comment #2
btmash commentedThe name for the table is quite misleading then. I would imagine tables following the cache_* format of naming cache tables should be allowed to flush the cache when a call to flush all caches is made (decisions_cache would not be quite as misleading in a similar vein as the votingapi_cache).
Back on point, however - while the decisions_votingapi_delete does remove the vote, the decisions_reset_form_submit does not (it explicitly only removes from votingapi).
Comment #3
btmash commentedWas never looked at - felt this is still necessary.