The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.The scenario is the following:
A CCK content type called T
A field of T called FT of type View Field
A view called V with an argument AV, in FT. The argument AV is replaced by %viewer.
When a node of type T, NT, is invoqued, the view V in FT is not refreshed.
Instead of refreshing the view, the data shown are that of the previous %viewer.
The problem is solved DELETING the record related to NT in the table CACHE_CONTENT.
I suppose is a problem in refreshing the cache, but I do not know if depends on CCK or Viewfield.
Can be solved the problem?
The versions are:
CCK 6.x-2.0-rc7
Views 6.x-2.x-dev (2008-Sep-20) This version fixes a problem in types of arguments.
Viewfield 6.x-1.x-dev (2008-Ago-28)
thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | viewfield.module-312131-5_HEAD.patch | 2.61 KB | darren oh |
| #4 | viewfield-312131-4.patch | 4.66 KB | plach |
| #1 | viewfield-312131-1.patch | 41.13 KB | plach |
Comments
Comment #1
plachThis was a big issue, the patch should solve it but I had to rework the "core" so be sure to test it heavily.
Comment #2
jerdavisCan you please re-roll this patch against CVS HEAD and verify it does not replace the entire module line-by-line? :)
Jer
Comment #3
plach@jerdavis: excuse me, but this is a little bit confusing: what the does the status change mean? did you commit the patch or reject it?
Comment #4
plachHere is the rerolled patch, I had to ignore whitespace differences because the repository is using a CR CR LF end-of-line delimiter.
Comment #5
darren ohI cleaned up the patch so it could be reviewed more easily. As far as I can tell, it simplifies token replacement. I do not see how it prevents view fields from being cached.
Comment #6
plachWith the current patch the token replacement is performed on node view, so the result does not get cached.
Comment #7
darren ohMakes sense to me. Patch applied in CVS commit 180902.