All of my private memories are corrupted
In checking through my Memories this morning, I realized that all of my memories that I've flagged as private are
now corrupted (see attached image). I was editing one of the stories this morning, so I know that problem is very new. I've tried refreshing the memories several times but I'm still having the problem.
Best Answer
-
@Charlie Black Your issue is actually different from the others. You might try deleting your browser cache (see here to learn how https://its.uiowa.edu/support/article/719). I wonder also if you are getting logged out somehow? This would result in you not seeing your private memories, even though they are there. Sometimes this can happen when I write a story or am doing something that takes longer than I expected it to. Then I will appear to be logged in, until I reload the page, and get an error message. If neither of these helps, please feel free to message me, so we can investigate this further.
@Heffner-Snyder York PA Tree Are you still seeing this?
0
Answers
-
After posting the above problem, I realized that I can recover the memory by changing the flag to public. But, the problem reoccurs once I change the flag back to private.
0 -
I cannot see any of the memories in my gallery. They appear to be there but they are not loading...just flashing. I believe it is a system error of sorts as I cannot view any memories in any profiles (mine or others).
0 -
I can see all the memories in my gallery with no problems. And I can see private memories just fine, as well -- public or private, my memories appear with no problems, just as they always have. I wonder why a couple of people are having such significant problems with their memories....
1 -
I restarted my PC and no change. When I try to open a memory I get "! Image Currently Unavailable (Unknown Error)". I currently have 997 files in my memories. I can see the circular profile pictures I've added however I cannot see the original file they come from.
0 -
Is this still occurring?
People still having issues?
0 -
Thank you for the suggestion to clear the browser cache - that seems to have corrected the issue.
0