Buckets: silent failure when new bucket name already exists
Bug #1825238 reported by
Beth Willis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
3.2.4
If you attempt to create a new bucket (item, record or user) and assign the same name as an existing bucket, the bucket is not created and there is no user-visible error generated. In the xul client, an alert was generated in this instance.
An alert is needed here to prevent users from accidentally changing the contents of existing buckets.
| tags: | added: patronbuckets |
Revision history for this message
| Andrea Neiman (aneiman) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| tags: | removed: webstaffclient |
| tags: |
added: buckets-user removed: buckets patronbuckets |
To post a comment you must log in.
Confirmed in 3.6 for record, item, and user buckets. An error appears in console but no user-visible error is generated.