Eric Abrahamsen writes: > On Thu, Aug 16 2012, Eric Schulte wrote: > >>>> Every time I edited a block and clicked "save", it just deleted the >>>> whole block. I got these errors in ~/.elnodelogs/elnode-error: >>>> >>> >>> I'm not sure what could be causing this problem. Did the test suite run >>> successfully for you? >> >> I've now added a POST test to the test suite. So if your problem >> persists you should now see a failing test, and conversely if you are >> now passing the test suite this problem should be eliminated. > > So yes, I did run the tests the first time, and you're right that, > without the "post" test, they went just fine. The documents were also > altered on-disk (ie, the chunks really were deleted). Interesting. > I updated org-ehtml to get the new tests, and the "post" test failed > thusly: > > --8<---------------cut here---------------start------------->8--- > F org-ehtml-post-request > (ert-test-failed > ((should > (string-match "foo" html)) > :form > (string-match "foo" > #("\n

foo\n

" 0 17 > (fontified t front-sticky > (field inhibit-line-move-field-capture) > rear-nonsticky t field output inhibit-line-move-field-capture t) > 17 21 > (fontified t front-sticky > (field inhibit-line-move-field-capture) > rear-nonsticky t field output inhibit-line-move-field-capture t))) > :value nil)) > --8<---------------cut here---------------end--------------->8--- > > This is still with my regular emacs environment. > Even thought this test is failing, it does show that your elnode server is returning the HTML in response to your POST requests. It looks like it only fails because your Emacs exports *foo* as foo instead of as foo. > > Then I restarted emacs -Q and used your batch.el file. I'm still getting > the same problem, unfortunately: the editable blocks disappear when I > hit "save". I realized I don't actually know whether this is supposed to > edit the simple.org or simple.html files: Edits are applied to the simple.org file itself. The simple.html file will not be updated until you refresh the page through your web browser. > anyway, the text disappears from the org file, but not from the html > file. Here's the output of *Messages*: > [...] Nothing here looks odd. > > And the elnode error file: > [...] The elnode error output don't generally contain anything interesting. Instead of listing errors it just lists routine access. I've just pushed up some changes to the git repository which add new require statements. Hopefully the errors above were caused by some required functions not being loaded at run time. If the newest from git doesn't work fix these problems, please try running emacs -Q -l batch.el with this updated version of batch.el, and let me know what is printed in the *Messages* buffer in the line which starts as "params:".