Jump to:
| Project: | Chaos tool suite (ctools) |
| Version: | 7.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I asked this over at the Panels issues but never got any responses. I'm hoping it's not because there is no answer.
I have several pages using Taxonomy term template, and the system works great, as long as views caching is turned off. If I turn on views caching, visitors, and authenticated users see the page as having no content. However the admin, and moderator roles can see the page content. I have checked and rechecked all the permissions, and I can't find any reason why cached content is being seen only by the admin and moderator, and it happens only on any Taxonomy term template pages.
I also noticed that the pages that are showing the views 'No results behavior' text to the non admin viewers, are also showing the pager, and the correct number of pages. It's acting like the content is actually there, but only the admin can see the content. Everyone else only sees the pager.
Comments
#1
I've asked this at Panels, now here, but I guess there's no answer. Does anyone have any ideas where else I might look?
#2
If Views caching is the trigger, I'd start in the Views' queue and provide reproduction steps so someone can try to set up the same thing and investigate it.
#3
I'd also do a search on the views queue and see if there are any other people reporting caching bugs.
#4
I will check into the views cache. The reason I didn't before is because it only happens on the Taxonomy term template pages.
I have another page that does a similar type of display, and uses views cache. It has no problems with any of the roles seeing the content.
#5
I just did an experiment. I made a test panel page using a basic page, and the same view. With the caching turned on, and all the caches flushed, no role has any problem seeing the content. Even the pager worked. It has something to do with the Taxonomy term template showing the view.
#6
Make sure you're not running into something like http://drupal.org/node/1792380
#7
I'm not sure how I could check that out.
I don't know if it's any help, but I turned on the devel module, and let everyone see the results. I can see that when viewing the page as admin, the page array shows page =>content >system_main >content >#markup containing the page content. If viewed as a visitor it sees page =>content >system_main but stops there.
NOTE: I was able to get the page to work. I disabled the cache in views, and turned on the cache in the panel itself. The visitor could see the content as well as the admin. The only other change was I had to turn on ajax in the view to make the pager work.
#8
Odd. Views caching shouldn't happen at any level that can even affect that piece of markup.
#9
I guess I'm just going to have to see if that odd setup will work for now.