Making changes to pre-existing STORIES items - not showing changes immediately
@Dennis J Yancey has posted:
It has been quite a few number of months that the new Memories viewer/processing has been in place and yet one of the bugs that was first noticed is still not fixed.
When making an update to an existing Memories story (Text based item) - the updates do not immediately show after you save - - but eventually do show after a day or so goes by. (Some sort of caching issue)
This is under a PC with Windows and a Chrome Browser
it also seems that it needs to be a story with more than just a few lines of text.
Can someone please fix this once and for all. This bug has been under the "RESOLVED" bug list for months and yet it is still broke.
We have closed this discussion in the Memories Categories of the Community and moved this discussion here, to the Memory Viewer Feedback group. If you have further comments or discussions regarding the Memory Viewer, please post in this group. Thank you!
Comments
-
Yes, this continues to be a very strange issue. For myself, I can get almost every Story edit to immediately populate any changes I make. Yet I still have one Story where it does not reflect edits after I click "Submit."
Yes, I do have to clear my cookies/cache if I want to immediately see these edits. Otherwise, I wait a bit, then they do populate.
I will put this back on the "Known Issues." However, it might take a while for this to fully resolve. Thank you for the continued patience.
0 -
for me - it does actually work - if the story is just a couple liners
but anything bigger than that doesnt work
I think this is related to the fact that the first few lines are actually stored in one field - but the larger text is actually stored in a second field.
0 -
Ahhh. Good thought. I will pass that along.
0 -
I also think the browser being used makes a difference.
0 -
Just an update about Story edits not changing immediately. . .
It appears that more users are experiencing this issue. The team has moved this problem up in priority. They are currently working on a fix. Thanks for everyone's patience!
0
