1. Disable node entity translation on admin/config/regional/translation (uncheck 'node')
  2. Clear cache
  3. Visit admin/config/regional/translation and check an entity ('node') which was not previously checked
  4. Visit any page which requires entity information (like /node/1 in this case)
  5. Result: Fatal error: Cannot access empty property in ...sites/all/modules/translation/includes/translation.handler.inc on line 207
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

das-peter’s picture

Status: Active » Needs review
Issue tags: +dcsprint5
FileSize
487 bytes

Thanks rfay for helping me to verify this issue :)

Attached patch adds a entity_info_cache_clear() in the form submit handler of the Content Translation settings form. That way we can make sure the entity_info array is up to date on the next usage.

rfay’s picture

Status: Needs review » Reviewed & tested by the community

This seems logical and does resolve the issue.

sun’s picture

Status: Reviewed & tested by the community » Fixed

Closely related core issue: #996236: drupal_flush_all_caches() does not clear entity info cache

Made the comment a bit more concise:

  // Clear the entity info cache for the new entity translation settings.

Thanks for reporting, reviewing, and testing! Committed to HEAD.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

Status: Fixed » Closed (fixed)
Issue tags: -dcsprint5

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