You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Ken Coar (Jira)" <ji...@apache.org> on 2023/03/21 23:22:00 UTC
[jira] [Comment Edited] (WHIMSY-398) Editing my Whimsy members.txt messed up my data
[ https://issues.apache.org/jira/browse/WHIMSY-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703406#comment-17703406 ]
Ken Coar edited comment on WHIMSY-398 at 3/21/23 11:21 PM:
-----------------------------------------------------------
I'm not sure I was clear. The members.txt field was the *only* one I edited.
If there are portions of that field that should not be edited, that should probably be made clear — or the authoritative source moved out of something the user can edit.
Yeah, if that field/file is going to contain authoritative origin data, Whimsey shouldn't allow a save if those are modified. A better solution long-term would be to break them out into separate read-only (for the user) fields, but that's a rather bigger job.
So should I open an improvement issue to move 'mustn't touch' fields elsewhere? Aren't they already in an LDAP field somewhere? (Probably populated from members.txt...)
This can probably be downgraded to 'minor' but I think it's still a bug. The current behaviour certainly violates the PLA (Principle of Least Astonishment). :D
was (Author: coar):
I'm not sure I was clear. The members.txt field was the *only* one I edited.
If there are portions of that field that should not be edited, that should probably be made clear — or the authoritative source moved out of something the user can edit.
> Editing my Whimsy members.txt messed up my data
> -----------------------------------------------
>
> Key: WHIMSY-398
> URL: https://issues.apache.org/jira/browse/WHIMSY-398
> Project: Whimsy
> Issue Type: Bug
> Components: Roster
> Environment: Firefox 107.0 on Fedora
> Reporter: Ken Coar
> Priority: Major
>
> I just used [https://whimsy.apache.org/roster/committer/coar] to edit my '{{{}Members.txt{}}}' entry, and now it appears to be gone. As does my 'forms on file' and 'member status' fields, possibly among others.
> I _did_ remove some of the textual information that appeared to be duplicated in the other fields on the page (like PMC membership, '{{{}Avail ID{}}}', {_}&c.{_}), but AFAIK i didn't delete the entire {{Members.txt}} form field *content* before clicking on submit.
> So, hopefully, there's a way to roll this back. The {{/committers/{_}user{_}}} form appears to be an update-in-place, so I can't use my browser's Back button to move to a version prior to the edit.
> If some of the information that populates the other fields on the form has its authoritative version in the {{members.txt}} entry, it came as a surprise to me..!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)