AEM content fragments sometimes blank out upon navigation

[sonaliku]

We have some data stored on the AEM content fragments which gets cleared out upon clicking back button on the page or moving out of the page. The modified user shows the logged in User irrespective of whether or not user clicked Save button option.

Why is the data not persisted in this case ? Is it a known issue or do we have a resolution? This is on AEM 6.5

[Ekhlaque]

@sonaliku  AEM uses auto-save features that might be capturing changes as soon as they are made, which could explain why the "modified by" field is updated. However, if navigating away from the page without explicitly saving reverts the changes, it indicates that the auto-save might not be fully committing the changes to the repository.Please check  the auto-save settings in your AEM instance to ensure that they are configured to commit changes appropriately. You might need to adjust the frequency and conditions under which auto-saves occur

Sharing a document which details the auto-save functionality and session management in AEM, which explains how changes might be captured but not fully committed if sessions are not handled correctly.

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/ext...

[anupampat]

Hi @sonaliku ,

What service pack of AEM 6.5 are you using ?

Regards,

Anupam Patra

[sonaliku]

Thanks @Ekhlaque 

@anupampat We are on SP21.

[kautuk_sahni]

@sonaliku Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

[sonalik30429345 · Accepted solution]

Apologies for late response but wanted to respond once we had a proper solution for this issue.

The issue was fixed partially by setting autosave parameters at the level of the model as suggested above. It would still blank out upon clicking back button but the data was loaded upon reopening the content fragment.

Additionally, we wrote a custom java script that would first save the content fragment upon load which helped with the persistence issue we were running into frequently.