Hide "slug" field from users on participant detail form

[KimSJ]

User testing shows that this field causes panic. And it also gives them the power to destroy permalinks. Reckon it should be responsibility of whoever approves the particiapnt info to fix it then, once, if needed.

[mattions]

I see,
well I thought people will be familiar with something like this.
I mean it's the link that they want to use for their participant.

On Sun, Feb 17, 2013 at 3:47 PM, Kim SJ [email protected] wrote:

User testing shows that this field causes panic. And it also gives them
the power to destroy permalinks. Reckon it should be responsibility of
whoever approves the particiapnt info to fix it then, once, if needed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/188.

Michele Mattioni, PhD
http://michelemattioni.me

[KimSJ]

Problem is, they don't know what the implications and side-effects are, which makes them scared. And also, there is nothing to stop them messing with this field at any time, with sad consequneces for people who have bookmarked pages.

[mattions]

Ok,
shall we compute it from the participant name and just give it to them?

On Sun, Feb 17, 2013 at 6:38 PM, Kim SJ [email protected] wrote:

Problem is, they don't know what the implications and side-effects are,
which makes them scared. And also, there is nothing to stop them messing
with this field at any time, with sad consequneces for people who have
bookmarked pages.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/188#issuecomment-13690759.

Michele Mattioni, PhD
http://michelemattioni.me

[KimSJ]

Since it won't have meaning until it's approved, I think that's fine. I guess the perfect solution would be not to display it at all until approved, then make it a read-only piece of information they can copy for use elsewhere.