Photos have been Added & recorded in ChangeLog. They DO NOT appear in Memories - x5 Days now! WHY?
Photos (x2) have been Added to and recorded in the ChangeLog, for a Person; but, they DO NOT appear in Memories section for that Person
- Where, it had been some x5 Days now
- ChangeLog records Photos with, Value as Blank; and, CURRENT
- Photos have NOT been recorded as being Deleted or Detached or Removed
Question: Why do the Photos NOT appear in Memories section for that Person?
Thoughts:
- Marked a "Private" by user who added them; hence, they cannot be seen by other users; but, NO indication of such
- Initially "Rejected" or "Restricted" by System; and, that rejection/restriction has been challenged; hence, delay in, appearance; or, Deletion or Detachment or Removal
[ Have not come across this before ]
[ Different Operating Systems ( Windows & Linux ) & Browsers ( Various ) - All Up-to-Date ]
Answers
-
@Jenny.B could we have the PID please?
0 -
@MandyShaw1
Sorry. Person is of some note. User does not want to publicise the PID.
Temple & Family History Consultants in our Ward are knowledgeable; but, have not come across this scenario.
There is nothing else to see against the PID that was not already advised.
Hoping someone experienced in with Memories may have some thoughts.0 -
@AmberML1 can you help with this please?
0 -
I just tagged a Private memory to my father, and could see the memory on his profile; also I could see the photo on the changelog Photo Attached entry.
However, when I signed out and signed in again with a different account, the memory appeared absent and the changelog entry looked like this:
This sounds as if it matches what you are seeing, so I'd suggest your '- Marked a "Private" by user who added them; hence, they cannot be seen by other users; but, NO indication of such' is what is happening here.
Hope that helps.
1 -
Sorry you are experiencing these challenges. Without being able to look at this specific situation (the specific PID), though, this might be difficult to provide general help.
In my own testing, looking over Change Logs, I am not able to reproduce this error. But your situation also suggests you are working with private images/restricted…..sounds like it is a complex situation to begin with.
If you could private message me with further details, I might be able to provide more specific help. Or advance your question to those who might be able to get you a good answer.
0 -
@AmberML1 I think I reproduced it, see above.
0 -
@MandyShaw1
Thanks. Your example above, appears to explain, the situation, for the scenario outlined in this post.
It certainly would have been more helpful to indicate in ALL of the, ChangLog (& Latest Changes); &, Memories; &, Following List (those we Follow), that the Photo added was Private
The System Does Not have to Show the Photo, just indicate that it was Private.
[ Or, alternatively, NOT indicate or record, that a "Private" Photo, was attached ]
Just another Bug, of the many Flaws, in the System - One that needs to be addressed.
@AmberML1
Thanks for your offer of help.
The PID is NOT required.
Will refer the post to a Moderator, to address the Bug and Flaw.0 -
@Jenny.B @AmberML1 even the existence of a private memory might well be considered a private fact, but there are other privacy related changes that are quietly hidden from the changelog (the fact that changes to relationships with living people are invisible to the public in deceased profile changelogs being the obvious one). I would say that suppressing the changelog entry unless the user can see the memory was the right answer/fix here.
0 -
@MandyShaw1
If you only mean, by "suppressing the changelog entry" for a Photo that has been Marked as Private by a User that other Users Cannot "See" the Photo in ALL of the, ChangLog (& Latest Changes); &, Memories; &, Following List (those we Follow) then that is fine.
But, as the System records the addition of a Photo then the System should indicate or record in the ChangLog (& Latest Changes); &, Following List (those we Follow) that the Photo was Marked as "Private" so that other Users would understand why they cannot see the Photo.
Whereas, what the System does at present is indicate that the Photo has been added but gives NO indication as to why the Photo cannot be seen by other Users.
Hence the reason for this post.
[ Not good for new or inexperienced Users ]
Like it or not that is the Bug and Flaw in the System.
[ Alternately, the System should NOT indicate or record in the ChangLog (& Latest Changes); &, Following List (those we Follow) the addition of a Photo that is Marked as "Private" ]
Personally, we prefer that the System does indicate or record in the ChangLog (& Latest Changes); &, Following List (those we Follow) the addition of a Photo that is Marked as "Private" just clearly indicate or record that it was "Private" - clears up any confusion as to why it cannot be seen.0 -
After having talked this issue through with some very knowledgeable people, let me share some thoughts.
Regarding the issue of having images added and recorded in the Change Log that do not appear….
As already discussed, if a notation appears in the Change Log that a Memory has been added, but you can’t see that image, it simply means someone added a private memory.
In talking with the Memories Team, however, this is not a BUG. The system is working as intended. Please understand that private memories can always be changed to public memories. If/when that happens, that public memory will then appear in the Change Log. The system keeps the exact “place-holder” for when that previously-private memory was attached.
Simply put: This is working as intended. The system keeps a “place holder” in the Change Log for if the image ever becomes public.
Regarding the issue that the Change Log does not indicate why an image cannot be seen by other users, you should assume it is because the image is private. There is currently no plan to offer a statement that the image is private.
Thank you for your patience. And for sharing your feedback.
1 -
@AmberML1
Thankyou for the information.
Not trying to be flippant or condescending.
One should never assume.
Even more so when it comes to programming.
How are and why should users be expected to know and understand the reason they cannot see a Memory that being added.
It was only through consultation with experiences users that this became evident, in this case.
To an inexperienced user it would make no sense - it would appear to be, a fault, a bug.
Even though the Team and Programmers consider the System is working as intended, to the majority of users it would not appear so.
Please have the Team and Programmers reconsider, the fact that, there needs to be an indication, on the ChageLog, that the Memory was "Private" and hence cannot be seen by other users, except of course, the user who added it.
The "place holder" has no bearing on this matter and is totally irrelevant.
Just something to consider.2 -
I completely agree with @Jenny.B on this.
Re 'There is currently no plan to offer a statement that the image is private.' - surely this simple change could at least be added to the list? Please ask the engineers to reconsider. Or could you perhaps talk to whoever has overall responsibility for the user experience about this? Anything that is likely to confuse a user should be of interest to them.
2 -
@AmberML1
Please advise.
Is the fact that, there needs to be an indication, on the ChageLog, that a "Private" Memory, is private; and, hence, cannot be seen by other users (except of course, the user who added it), being submitted to the Team and Programmers for reconsideration?
Thank You2
