Family Tree Stories in Memories
Wny isn't the save or submit feature working in memories for stories. I started a story some months ago and returned to it recently to finish typing the content. I have typed the same sections at least four times now on different days and they are never saved when I click submit. Help, please. Thanks.
Answers
-
That can be so frustrating when your work is lost. Have you looked at this help article? It might answer some of your questions. One thing that jumped out at me as I read the article is that the system times out after an hour, so you want to save your work often. I hope this helps!
0 -
I am able to upload an article into "memories," however I am unable to access a particular memory. When I click on the memory, I am getting a 404 error code. This has been happening all day today, 7 May 2024. Is this a glitch, or is there something that is preventing just me from looking at memories. Thanks for any help.
0 -
at one point this was a known bug - I thought they had fixed it though.
Apparently not.1 -
@Sue Anne Beckstrand Thompson I have forwarded this to the appropriate group. In the meantime, I have been told the edits take a little while to save. I tried to recreate your problem and found after about 24 hours my edits showed up to a saved story.
0 -
In that case there should at least be a warning message shown to the submitting user. As it stands this is simply bad user interface design. (And why does it take 24 hours anyway?)
0 -
Its a bug/flaw (not intendd design) that no one realzied was there - until the programming code was updated in the live system. - thus they couldnt progran a warning message - for something they didnt even know existed until it hit the live system.
Hopefully this will be fixed soon.0 -
I do get that, but if an application doesn't handle all its updates in real time (and especially on a high volume site like FS) there's always a finite danger of users being left confused as in this case. You can always switch a warning message off if you find everything's getting processed in a timely manner, but it's a lot harder (as you say) to add it post go live.
0 -
After editing the text of an older story the "submit" button highlights but after pressing it, the text reverts to the original and all of the changes are lost.
I have used FamilySearch for many years and submitted 100's of memories. I have often edited the stories to add information or correct the content. This is a recent "glitch" as the editing feature was working fine a few weeks ago.
0 -
This memories viewer bug was marked as resolved
"Some Stories are being cached by the browser and are not updating after a change is submitted"But I still have it occuring for me.
What about the rest of you? Is it still broke for you as well?0 -
mod note: several discussions were collected into this thread and some comments deleted for clarity and to keep the conversation flowing.
0 -
I have had the same problem over the last few weeks and as of today, it still has not been fixed. I will check back in 24 hours to see if the edit I just made was saved or not.
They have apparently recently updated and modernized "memories" but the text editor still has very limited features. There is no way to create columns since the editor does not support tabs and extra spaces are removed when the text is saved. This is unfortunate as it doesn't allow for a quick visual comparison of data from, for example, several censuses.
0 -
Thanks
yeh - Id just like confirmation from the moderators that the engineers confirm this is still a known issue they are still working on and it has not yet been fixed . . .
You would have thought this would have been one of the highest priority items - and maybe it was - and maybe they thought they fixed it - but its still broke - and just want to ensure engineers know that is the case.0 -
The story I edited at 3:30 was updated 2 hrs. later. I guess this is not a big deal for the three of us in this thread but will be confusing and frustrating for the 99.99% of people who have no idea what is going on.
0 -
the two hour (or more) delay is just a temporary work around until the real time update gets fixed. It will be real time when it gets fixed.
but yeh - in the mean time - 99% of the people dont even know whats going on and just get frustrated and confused.0
