When editing a field the new value (new value #1) is correctly loaded and inserted into the DOM on the first edit.

Editing this field and saving a new value (new value #2) again without refreshing the page incorrectly loads the entity from cache, causing the displayed value to be new value #1 instead of new value #2.

This patch has been applied: #1206656-65: Error on Node view page: Argument 1 passed to drupal_array_get_nested_value()

Comments

scheepers created an issue. See original summary.

Scheepers de Bruin’s picture

StatusFileSize
new553 bytes
Scheepers de Bruin’s picture

Title: New value only correctly refreshed on first edit » Cached value displayed on second edit