Closed (won't fix)
Project:
Node registration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Feb 2018 at 16:57 UTC
Updated:
8 Feb 2018 at 19:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gerson.analista commentedComment #3
gerson.analista commentedComment #5
rudiedirkx commentedNR adds
registrationinhook_node_load, which should not be cached. Is that whatentitycachedoes? Cache the result ofhook_node_load? That would be very unDrupal...Comment #6
rudiedirkx commentedLooking at the source code, I don't see where/when entities are cached, but I do understand it caches after
hook_node_load.I see 2 options:
hook_node_loadworks withoutentitycache.I don't think NR should do anything. If
entitycachebreaks howhook_node_loadis supposed to work, it should fix it, but it won't, because that's the entire point ofentitycache. The only party that used both modules, and knows their interaction, is you, the website's developer, so only you should fix this.Implement
hook_entitycache_load(should always come afterhook_node_load, also for uncached entities) to override$node->registration. Docs here.NR could do that, but that would be strange, because it doesn't use
entitycache.Comment #7
gerson.analista commentedthanks for the explanation.