Closed (fixed)
Project:
Viewfield
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 May 2013 at 04:28 UTC
Updated:
3 Sep 2019 at 18:39 UTC
Jump to comment: Most recent
Looking at my page it should appear like this:

But it keeps reverting to this:

The page seems to revert after some amount of time. The page looks blank whether you are logged in or not. It happens on other machines besides my own.
The page will fix itself after flushing the cache. I have tried using boost and other cache setting to fix it that way, but they all have the same result. I can flush the cache while I develop the pages, but this isn't very useful to other anonymous viewers.
As the other fields seem to be rendering fine, it would appear this is a viewfield issue. However, I don't know where to begin trying to debug it. Thanks for any and all feedback.
| Comment | File | Size | Author |
|---|---|---|---|
| ViewfieldWorking.jpg | 152.13 KB | bigfootnrg | |
| ViewfieldBroken.jpg | 105.93 KB | bigfootnrg |
Comments
Comment #1
SilviuChingaru commentedTry this patch: https://drupal.org/node/477244#comment-7510777
It is a diffrent approch of rendering view field. Let me know if it fixed your problem
Comment #2
aaronbaumanThis issue persists to 8.x
Comment #3
jerdavisPlease post more detail about your use and site configuration, including what entity type you're using the Viewfield on and what your site's cache settings are.
Comment #4
aaronbaumanViewfield is attached to a node.
The assigned view's cache is set to "None"
I have determined that rendered markup in dynamic page cache is incorrect, which is presumably somehow related.
What other cache settings do you want to know?
Comment #5
jerdavisCan you provide any more detail about how this is being used? What is the view showing? Is it driven by arguments? What arguments/filters? How are arguments being passed? Is there a reliable way to reproduce this with a simple test case?
Comment #6
jerdavisSo far I have been unable to reproduce this. If you can provide comprehensive steps to reproduce the problem, please re-open the issue.