Edit: Initial posted in Entity cache.

Not sure if this issue belongs to this project or to Entity translation.

Problem: After a core entity (like "node") fields are translated using Entity translation they are still loading with old translated values (or untranslated).

Comments

claudiu.cristea’s picture

Title: Compatibility with Entity Translation » Clear the entity cache after translate
Project: Entity cache » Entity Translation

It seems that it's a Entity translation. Entity cache must be invalidate after a translate has been processed.

claudiu.cristea’s picture

Assigned: Unassigned » claudiu.cristea
Status: Active » Needs review
StatusFileSize
new1.28 KB

Here's a patch that works for me. This bug was discovered after translating a node that is also cached with Entity cache.

After translating, the node still loads old (or untranslated) fields. I think that using this module even without Entity cache or other persistent cache, the entity cache must be invalidated to refresh also the static cache.

mvc’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +montreal

plach says this is the right approach, since resetCache() is a method of the base class DrupalEntityControllerInterface.

plach’s picture

Status: Reviewed & tested by the community » Fixed

Committed, thanks!

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Updated issue summary.

  • Commit 95cedbf on master, et-permissions-1829630, factory, et-fc, revisions authored by claudiu.cristea, committed by plach:
    Issue #1262512 by claudiu.cristea: Fixed Clear the entity cache after...

  • Commit 95cedbf on master, et-permissions-1829630, factory, et-fc, revisions, workbench authored by claudiu.cristea, committed by plach:
    Issue #1262512 by claudiu.cristea: Fixed Clear the entity cache after...