Re: [O] org-mode based groupware wiki

[Torsten Wagner]

Hi Eric,

On 16 October 2013 15:55, Eric Schulte <address@hidden> wrote:
> Lets at least try to isolate the problem.  Could you try the following?
>
> 1. (require 'elnode), then point your browser to http://localhost:8000 where
> you should see a directory listing and a test.html file, clicking on the
> test.html file should show elnodes test web page.  If this doesn't work you
> don't have elnode installed correctly.
>
> 2. (require 'ox-ehtml), then open an Org-mode file and export with C-c C-e,
> you should now see a normal html export of the file.
>
> 3. (setq org-ehtml-everything-editable t), then re-export the file to
> editable html, you should now see [edit] buttons on most elements

Until here it worked somehow now. I had editable files already in step
2 but that might be because I somehow set the editable flag during
testing and playing with it.

> 4. (require 'org-ehtml) then (setq org-ehtml-docroot
> test-org-ehtml-example-dir), then (elnode-start 'org-ehtml-handler :port
> 8888) and browse to http://localhost:8888 where you should see a directory
> listing.  Clicking on the Org-mode files in that directory should yield
> editable versions which actually change on disk when edited.
>

That still fails with the same error message on the browser.
However, I found some info in the  *Message* buffer.

Entering debugger...
"/home/torsten/test-wiki/"
Mark set
((8888 . #<process *elnode-webserver-proc*<1>>) (8000 . #<process
*elnode-webserver-proc*>))
elnode-error: elnode--sentinel 'open from 127.0.0.1.' for process
*elnode-webserver-proc*<1> <127.0.0.1:60889> with buffer nil
elnode-error: Elnode status: *elnode-webserver-proc*<1>
<127.0.0.1:60889> open from 127.0.0.1
elnode-error: filter: calling handler on *elnode-webserver-proc*<1>
<127.0.0.1:60889>
elnode-error: filter: caught an error in the handling
elnode-error: elnode--sentinel 'deleted.' for process
*elnode-webserver-proc*<1> <127.0.0.1:60889> with buffer
*elnode-request-60889*
elnode-error: Elnode status: *elnode-webserver-proc*<1>
<127.0.0.1:60889> deleted
elnode-log-access: Symbol's function definition is void: aget


This missing aget function might be the problem?! I would need to test further.

Thanks for your help and suggestion

Torsten


> Could you try the above and let me know where it fails?
>
> Thanks,
>
>
> On Wed, Oct 16, 2013 at 6:08 AM, Torsten Wagner <address@hidden>
> wrote:
>>
>> Hi Eric,
>>
>> thanks for the reply. Unfortuantely, I still stuck with the same problem
>> after updating from ELPA.
>> If it works ok for you with the recent version of elnode and ehtml, I
>> might have to digg where my config is broken. I tried following the readmes
>> but the elnode server responeses with
>>
>> <h1>Server error</h1>
>>
>> at the website and I can't find any addtional error message in the logs.
>>
>> Thanks for help and support
>>
>> Torsten
>>
>>
>>
>> On 14 October 2013 15:07, Eric Schulte <address@hidden> wrote:
>>>
>>> Hi Torsten,
>>>
>>> Sorry I missed your earlier email, I'm happy to hear that this package
>>> is being used for collaboration between Org-mode users and normal
>>> people.
>>>
>>> The org-ehtml package hadn't been updated in over a year, in the mean
>>> time the many changes have taken place in Org-mode (especially what was
>>> the "new" export framework becoming the "main" Org-mode export
>>> framework).
>>>
>>> I've just finished updating org-ehtml to work with current versions of
>>> Org-mode and elnode (and I've updated the ELPA package).  Please try
>>> with the latest version of org-ehtml and let me know if you run into
>>> problems.
>>>
>>> Cheers,
>>>
>>> Torsten Wagner <address@hidden> writes:
>>>
>>> > Hi Eric,
>>> >
>>> > still trying to figure out whats wrong with my set-up. Did you had time
>>> > to
>>> > look intio it.
>>> > It seems somehow elnode does not play well anymore with the current
>>> > version
>>> > of ehtml.
>>> > Or something like this.
>>> > I can access elnodes standard services and I can create new services
>>> > like
>>> > described in the elnode wiki.
>>> > However, following the README of ehtml. I receive the early posted
>>> > error
>>> > message. This is not an emacs-based error or any sort of crash. It
>>> > seems to
>>> > be something which is "well" handled by elnodes error catching.
>>> >
>>> > Would be glad if you could give us some advice how to deal with that or
>>> > how
>>> > to test further. We are in the middle of setting up a groupware wiki.
>>> > Two
>>> > of us are org-mode users and the others do not really care what
>>> > markup-language that might have to use. Thus, it gives us the comfort
>>> > to
>>> > stick with org-mode and we only have to decide to go the ehtml/emacs
>>> > way or
>>> > the gollum/org-ruby way. Even more luckily this is not a decision
>>> > forever,
>>> > since the files remain to be native org-files on both systems, I
>>> > believe we
>>> > could switch at anytime.
>>> > This is again a nice example of the pure text based org-mode paradigm.
>>> >
>>> > Thanks
>>> >
>>> > Torsten
>>> >
>>> >
>>> > On 7 October 2013 17:02, Torsten Wagner <address@hidden>
>>> > wrote:
>>> >
>>> >> Hi Eric,
>>> >>
>>> >> thanks for the email. I will give org-ehtml a try. Do you still
>>> >> actively
>>> >> maintain it. We would rely rather heavily on it ( a group of about 10
>>> >> people) and I would be happy to know that I do not ride a dead horse.
>>> >> On
>>> >> the other hand you get a bunch of beta-testers ;)
>>> >>
>>> >> Could you agree with the following comparison:
>>> >>
>>> >> * gollum
>>> >> - standalone application, based on git and org-ruby.
>>> >> - can use different makeup-languages
>>> >> - can be integrated in a larger environment (read something about
>>> >> using
>>> >> Apache Webserver)
>>> >> - enables the creation and editing of pages via webbrowser (a minimal
>>> >> org-mode editor is available)
>>> >> - basic settings of the theme (top, footer, sidebar).
>>> >>
>>> >> * org-ehtml
>>> >> - part of org-mode requires emacs and elnode
>>> >> - makes use of the new exporter
>>> >> - ...
>>> >>
>>> >> ... because I tried to give it a test but it did not work out.
>>> >> I tried a test instance via the following commands (and its outputs)
>>> >>
>>> >> (ert "org-ehtml")
>>> >> ->
>>> >> Selector: "org-ehtml"
>>> >> Passed: 0
>>> >> Failed: 0
>>> >> Total:  0/0
>>> >>
>>> >> Started at:   2013-10-07 16:44:00+0200
>>> >> Finished.
>>> >> Finished at:  2013-10-07 16:44:00+0200
>>> >>
>>> >> (setq org-ehtml-docroot "/home/torsten/test-wiki/")
>>> >> ->
>>> >> "/home/torsten/test-wiki/"
>>> >>
>>> >> (elnode-start 'org-ehtml-handler :port 8888)
>>> >> ->
>>> >> ((8888 . #<process *elnode-webserver-proc*>))
>>> >>
>>> >> When I start it according to the README, all I get when calling
>>> >> http://localhost:8888/simple.org is:
>>> >>
>>> >> <h1>Server error</h1>
>>> >>
>>> >> No errors are given in any log-buffer I could find.
>>> >>
>>> >> Not sure where the problem appears. A test of elnode according to the
>>> >> elnode README worked out ok
>>> >>
>>> >> (defun my-test-handler (httpcon)
>>> >>   "Demonstration function"
>>> >>   (elnode-http-start httpcon 200 '("Content-type" . "text/html"))
>>> >>   (elnode-http-return httpcon "<html><b>HELLO!</b></html>"))
>>> >>
>>> >> (elnode-start 'my-test-handler :port 8010 :host "localhost")
>>> >>
>>> >>
>>> >> Might it be, that the elnode API changed and that the handler function
>>> >> need some rewrite?
>>> >>
>>> >> All the best
>>> >>
>>> >> Torsten
>>> >>
>>> >>
>>> >>
>>> >> On 4 October 2013 16:03, Eric Schulte <address@hidden> wrote:
>>> >>
>>> >>> Check out org-ehtml.  See the original announcement [1] and the repo
>>> >>> on
>>> >>> github [2].  It might need some attention as the Org-mode export API
>>> >>> is
>>> >>> constantly in flux, but it does work to allow editing of Org-mode
>>> >>> pages
>>> >>> through a web page.
>>> >>>
>>> >>> Cheers,
>>> >>>
>>> >>> Footnotes:
>>> >>> [1]  http://thread.gmane.org/gmane.emacs.orgmode/58773/focus=58884
>>> >>>
>>> >>> [2]  https://github.com/eschulte/org-ehtml
>>> >>>
>>> >>> --
>>> >>> Eric Schulte
>>> >>> https://cs.unm.edu/~eschulte
>>> >>> PGP: 0x614CA05D
>>> >>>
>>> >>
>>> >>
>>>
>>> --
>>> Eric Schulte
>>> https://cs.unm.edu/~eschulte
>>> PGP: 0x614CA05D
>>
>>
>