John, This sounds possibly like a Futon bug...and Futon is no longer being maintained. Did you reload the page before trying to edit the code? If not the page will have the old _rev data in it and your change will fail.
Would you try the same thing from the command line using curl? First, get a copy of your design document: curl http://your-server:5984/dbname/_design/viewdocname > viewdoc Then, edit the design document (being sure to remove any newlines, or convert them to \n) using your favourite editor. Then, PUT it back to the database: curl --upload-file viewdocname \ http://your-server:5984/dbname/_design/viewdocname You should get back an {"ok":true,..."} that includes the document's new revision number. If this succeeds, you've likely hit a Futon bug, one that probably won't be fixed. Sorry about that. -Joan ----- Original Message ----- > From: "John Le Brasseur" <[email protected]> > To: [email protected] > Sent: Thursday, March 30, 2017 11:55:03 AM > Subject: Re: Confused Design Docs > > Thanks Jan. > (v 1.6.1): I am editing the code inside futon using the steps: view, > design > documents, selecting the specific design document in 'source' and > then > editing it right there. > When I try to save the changes, I get the error I indicated. > It's almost as if there is a conflict but no conflicts are shown when > searched for. > The design document shown should be the 'latest'. Hence my question. > It > should save no matter what changes are made. > It seems as if there is 'something' corrupted but everything looks > correct. > > > > > > On 30 March 2017 at 17:09, Jan Lehnardt <[email protected]> wrote: > > > > > > On 30 Mar 2017, at 15:20, John Le Brasseur > > > <[email protected]> > > wrote: > > > > > > Is it possible that when editing design docs in v 1.6.1 and v > > > 2.0.0 and > > > then replicating both ways, that 'something' can go wrong? > > > > Not really, no. > > > > > I have found my design docs sent both ways become uneditable and > > > I had to > > > create entirely new design docs with very different names to > > > solve it. > > If I > > > tried editing them, the doc refuses to save and says: Error > > > conflict > > > Document update conflict. > > > > Sound like you’re not sending the correct _rev in your update. It > > works > > like > > with all other documents. > > > > Best > > Jan > > -- > > > > > > > John > > > > > John >
