Canceled: No client for fragment menu-local-tabs [#2190607]

I have installed the module and File Cache module too. Caching is working on the frontpage. When I went to view one of the nodes, the debugger said I had to activate the Menu module. Done that, the message I get now is:

Canceled: No client for fragment menu-local-tabs

There is also another log message that says:

Canceled: Only cache allowed HTTP content types (HTML, JS, etc)

What am I doing wrong?. What is the Authcache fields module for? Is it not caching the whole node. Sorry, I'm a bit confused with the Authcache module.

Any help please? Thanks.

Comments

Comment #1

znerol CreditAttribution: znerol commented 6 February 2014 at 22:10

You need to either enable the Authcache Ajax or Authcache ESI client modules. Those are responsible for delivering personalized fragments to the client.

Comment #2

taote CreditAttribution: taote commented 10 February 2014 at 10:47

Ok, two questions.

1. I don't understand why I have to activate Authcache Ajax, in theory I'm not using ajax to show the node page, am I?.
2. When I do it the message I get know is:

Cache Status: "Caching CANCELED"
Message 1: "Canceled: No client for partial field"

Sorry, but I don't understand this means. Are there any guidelines telling you what steps to follow?

Thanks!

Comment #3

znerol CreditAttribution: znerol commented 10 February 2014 at 13:52

There is no way to tell whether the menu tabs on a node page will be the same for every user having the same role combination. For example when the "edit own article" permission is set for a role, the owner of a node will see the edit-tab, but others will not. Therefore it is necessary remove the tabs before saving a page to the cache and load them using Ajax or ESI when a cached page is displayed to the user.

That said, you most probably need to enable Authcache Ajax anyway.

Some documentation is available. However currently there is no overview of the page fragments which potentially need to be loaded via Ajax/ESI.