Caching problems?
| Project: | relatedviews |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I have set up a view block properly. I have nodes to which are assigned a term (course 1, course 2, course 3, etc) from a vocabulary (Courses). My Related block should be able to get all nodes tagged with course 1 if the node currently displayed is tagged with only course 1, or all nodes tagged with course 2 if the node currently displayed is tagged with course 2, etc. Right?
Here's my problem. If after saving the filter I go and view a node tagged with course 1, then the Related block shows all other nodes tagged with course 1 perfectly. If I then go and view a node tagged with course 2, the Related block is not updated! And no matter what I do, it'll continue to display the content related to course 1. The only thing that seems to reset the condition is if I save the view again, or if I clear the cache (with the Devel module). And then if I go and view a node tagged with course 2, well the related content now shows up properly, but it's be stuck displaying content realted to course 2 no matter what.
I have the latest official release of the views module, and I don't have caching enabled on my site.
Am I doing something wrong, or is this a bug?
#1
Hello,
I am going to *BUMP* this as I have the exact same issue as above, the only way I can cure it is to clear the views cache the from the views tool option. This bug renders the module as unworkable for any site with more than one category to reference, which by all accounts is most sites that would find this module useful!
Assistance and remedies more than welcome, I spend the next few hours trying to figure this myself.....
#2
I love the potential of this module but also have the same caching problems. Please help fix this issue!
#3
Another **bump** to see if we can get this resolved? I have had another fresh look at the module being used and attempting to pick though where this seems to cache, but I am not incredibly technical with module development so to me its a fruitless experiment
#4
same problem here. hope the *bumps* will help solve it
#5
I was just having the same problem with this module, but I think I stumbled onto a decent (although inelegant) workaround: set your Taxonomy:Term from Current Node filter to exposed. This forces it to reload it, rather than using the cached version. The only problem is that you've now got an ugly little exposed filter box on your page, but you should be able to tweak your CSS so to hide it.