You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the Reports log tab on an AMI set is an Entity Form (means, it depends on the Entity) there is an edge case where someone visits it before any processing has happened (means the Log is still not created) and Drupal caches (because it uses the entity and the user context) the empty one. Another user, visiting it afterwards will see the Reports, but the original user will keep seeing an empty Form until global caches are cleared (or user caches, tags) or the entity itself changes (someone changes the status, updates a CSV or the JSON config)
The solution so far (but needs more testing) is very simple, make cache last 0.
The text was updated successfully, but these errors were encountered:
What?
Because the
Reports
log tab on an AMI set is an Entity Form (means, it depends on the Entity) there is an edge case where someone visits it before any processing has happened (means the Log is still not created) and Drupal caches (because it uses the entity and the user context) the empty one. Another user, visiting it afterwards will see the Reports, but the original user will keep seeing an empty Form until global caches are cleared (or user caches, tags) or the entity itself changes (someone changes the status, updates a CSV or the JSON config)The solution so far (but needs more testing) is very simple, make cache last 0.
The text was updated successfully, but these errors were encountered: