ST: some sub-locales cannot add suggestion when there is approved data

Description

This happens with all sub-locales.
for example, with French Canada (fr-CA), try to add a new suggestion to this entry, nothing happens.
http://st.unicode.org/cldr-apps/v#/fr_CA/Languages_K_N/65717fb17b4b01b3
Dari: http://st.unicode.org/cldr-apps/v#/fa_AF/T_Europe/5c86541307b0961a

Step:
1. Log in with Kristi's test account
2. go to http://st.unicode.org/cldr-apps/v#/fr_CA/Languages_K_N/65717fb17b4b01b3
3. + to add suggestion
4. type "mapuche" (same term as English without the capital)
5. Submit

Actual: suggestion does not appear anywhere

Also repro'd data points:
1. Dari: http://st.unicode.org/cldr-apps/v#/fa_AF/T_Europe/5c86541307b0961a. (Used 20 votes to add correct value. Notice that the 4 vote attempts now show against the approved)
2. Spanish sub-locales: http://st.unicode.org/cldr-apps/v#/es_SV/Fields/1d45310cbcf1b2e5 want to add "anteayer"

xpath

None

locale

None

Activity

Show:
TracBot
May 9, 2019, 10:13 PM
Trac Comment 27 by —2018-09-28T03:15:56.891Z

Ok, let's close it.

TracBot
May 9, 2019, 10:13 PM
Trac Comment 26 by —2018-09-27T13:07:35.216Z

I still can't reproduce this. The inability to reproduce it motivated my question above about db backups, and the creation of ticket [].

For "mapuche" in fr_CA, and "anteayer" in es_SV mentioned above, those rows now have "mapuche" and "anteayer" as the inherited values, in the Others column. Some inheritance-related bugs have been fixed, such as [], where the inherited value didn't reach the client, and [], where votes for inheritance were confused with votes for the specific value matching the inherited value. Possibly this is a duplicate of one or more of those bugs. Maybe without realizing it, users were trying to input "new" values that matched the inherited value, which was killed on its way from the server to the client.

There's also a separate issue discussed above, about "locked" accounts, and there's a reference to ticket [] which is still open, not assigned to me.

I suggest that we close this ticket since we can't reproduce it and it may have been fixed and/or be a duplicate.

TracBot
May 9, 2019, 10:13 PM
Trac Comment 25 by —2018-07-21T16:04:35.044Z

I'm trying to reproduce, without success. If we saved daily backups of the db, it would be easier to reproduce bugs like this. What's the current backup schedule/procedure?

TracBot
May 9, 2019, 10:13 PM
Trac Comment 24 by —2018-07-06T15:37:28.366Z

Comment #22 is a good test case to look at while we have a repro in the latest environment.

TracBot
May 9, 2019, 10:13 PM
Trac Comment 9.23 by —2018-07-06T15:35:13.718Z

Replying to (Comment 9 kristi):

I switched one of my test account to fr and fr_CA.

 

After switching the account, I’m able to repro the issue.

What I am noticing is that ST indicates that I’m in a Locker user account. (see attached email)

I'm not a locked user though, and I’m able to vote on existing selection (e.g. I can vote for “Foobar” that you entered.)

Is it a guest user? "account is locked" is

Priority

blocks-release

Assignee

Thomas Bishop

Reporter

Kristi Lee

Fix versions

Components

Labels