GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/150
Fix bulk-delete on all-doc-page
On Couch 1.6 `/_bulk_docs` returned `ok: true` when the request was an
success. On 2.0 the ok property is missing:
Example success message on 2.0:
```
[{"id":"Brocket","rev":"6-b6fa9e703c3eb92aa9c3a49cedf1e8c2"}]
```
Example error message on 2.0:
```
[{"id":"Blaggie-System","error":"conflict",
"reason":"Document update conflict."}]
```
Steps to reproduce the error in Fauxton:
- select 1 document in the all_docs screen
- click the trash icon to delete it
- click ok to delete it
- you are able to click the trash icon again and if you do, you
get an error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-fauxton
COUCHDB-2462-bulk-delete-broken
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fauxton/pull/150.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #150
----
commit 450bbb50475320d6dc50e7580d65a0f5ea271e79
Author: Robert Kowalski <[email protected]>
Date: 2014-11-14T15:04:31Z
Fix bulk-delete on all-doc-page
On Couch 1.6 `/_bulk_docs` returned `ok: true` when the request was an
success. On 2.0 the ok property is missing:
Example success message on 2.0:
```
[{"id":"Brocket","rev":"6-b6fa9e703c3eb92aa9c3a49cedf1e8c2"}]
```
Example error message on 2.0:
```
[{"id":"Blaggie-System","error":"conflict",
"reason":"Document update conflict."}]
```
Steps to reproduce the error in Fauxton:
- select 1 document in the all_docs screen
- click the trash icon to delete it
- click ok to delete it
- you are able to click the trash icon again and if you do, you
get an error
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
