[MAGNOLIA-9144] Magnolia randomly serves an old version of an asset after performing changes on it Created: 16/Oct/23  Updated: 10/Jan/24

Status: Open
Project: Magnolia
Component/s: cache
Affects Version/s: 6.2.39
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: AuthorX Support
Team: AuthorX

 Description   

This issue is strange when it comes to reproducing it, since it doesn't affect all users the same way. It's reproducible on both Mac using Firefox and Windows, using both Firefox and Chrome. The steps to reproduce this issue are as it follows (on demo-author):

  1. Use Firefox/Chrome
  2. log in as superuser
  3. add new page (basic template)
  4. add image component
  5. now switch to the asset app
  6. edit asset you used in the image component and upload a diffrent picture
  7. switch back to the new page -> old image is still there (see: blob:https://jira.magnolia-cms.com/1eaae7d4-2242-4064-bc52-0e79cd378295)

It looks like a possible browser issue, but the fact that it can't be reproduced constantly even using the same browser version on different devices made it a pain to test.


Generated at Mon Feb 12 04:39:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.