Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.6.x-dev
-
[4.6] - Sprint 15
-
Ibexa Experience
Description
Steps to reproduce
- Create clean install of Experience 4.6.x-dev with Varnish reverse proxy.
- Log in to the back-office (admin).
- Go to dashboard page
- Create another admin user
- Log in to that user
- Go to dashboard page.
Actual result
Observe that dashboard page serves user widget in the top right corner using previously cached output. Can be compared with what you get when viewing some other admin page (Content structure, user settings, etc.)
Expected result
Cached is correctly served or invalidated. Technically cache will be disabled for the dashboard view as it makes the most sense ATM in general.