[#1438 Can't edit beneath leo.zwiki.org]

An attempt to follow http://leo.zwiki.org/LeoInAjax/editform delivered this error page:

Site Error

An error was encountered while publishing this resource.

NotFound
Sorry, a site error occurred.

Traceback (innermost last):

    * Module ZPublisher.Publish, line 202, in publish_module_standard
    * Module ZPublisher.Publish, line 150, in publish
    * Module Zope2.App.startup, line 252, in __call__
    * Module ZPublisher.Publish, line 119, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.ZWiki.Views, line 730, in editform
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.PageTemplates.ZopePageTemplate, line 330, in _exec
    * Module Products.PageTemplates.ZopePageTemplate, line 427, in pt_render
    * Module Products.PageTemplates.PageTemplate, line 98, in pt_render
    * Module zope.pagetemplate.pagetemplate, line 115, in pt_render
      Warning: Macro expansion failed
      Warning: exceptions.KeyError: 'macros'
    * Module zope.tal.talinterpreter, line 271, in __call__
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 854, in do_condition
    * Module Products.PageTemplates.Expressions, line 186, in evaluateBoolean
    * Module zope.tales.tales, line 696, in evaluate
      URL: /leo.zwiki.org/editform.pt
      Line 121, Column 16
      Expression: <NotExpr u'here/supportsEpoz'>
      Names:

      {'container': <Folder at /leo.zwiki.org>,
       'context': <ZWikiPage 'LeoInAjax' at 0x61b9a10>,
       'default': <object object at 0x2b1c2dd90200>,
       'here': <ZWikiPage 'LeoInAjax' at 0x61b9a10>,
       'loop': {},
       'nothing': None,
       'options': {'action': 'Edit',
                   'args': (<ZWikiPage 'LeoInAjax' at 0x61b9a10>,
                            <HTTPRequest, URL=http://leo.zwiki.org/LeoInAjax/editform>),
                   'id': u'Leo in Ajax',
                   'oldid': 'LeoInAjax',
                   'page': u'Leo in Ajax',
                   'text': "This page will discuss creating web pages that look like Leo outlines. It's a good place to post code.\n\n.. contents::\n\nIntroduction\n============\nIt is important in these discussions to recognize that Ajax does one thing only.\n\nIt allows a script in a web page to request the contents of another web page as if the script were a browser and receive the page as a browser would receive it, except in the form of a string.\n\nThe string received may be the contents of a static web page (html, xml) or a dynamically generated page from php, asp, cgi etc. or in a pickled data format such as JSON produced by a server script (or as plain text).\n\nPeople sometimes use 'AJAX' to mean 'dhtml', which is fine as long as we are aware of the distinction. 'dhtml' is perhap
 s more appropriate  for referring to the combination of html, javascript, css, AJAX, server scripting, etc which make up a modern dynamic web page.\n\nList of 'use cases'\n==================
 =\nThere are range of what can loosely call 'use cases'. Let's try to make a list of them from simplest to most esoteric.  Here is a start:\n\n  (It might be better if long comments were put in a separate section and only a short note with a link placed in this list.)\n\n  + Static XHTML/HTML (sample1_)\n\n    This is a straight forward conversion of an outline to an xhtml list that can be displayed as a web page. XHTML is perhaps better as it allows xml tools such as XSLT to post precess the page.\n\n.. _sample1: http://plumloco.co.uk/leo_to_dhtml/demo/xhtml/\n\n  + Dhtml page that allows the outline to be collapsed/expanded.\n\n    This still essentially only shows the page as it would be seen in the browser.\n\n  + Dhtml page that interprets bodyString (sample2_).\n    \n    This would
  allow leo to become a web authoring tool. The bodyString of a leo node could contain Wiki markup or raw html and then displayed as html.  @url nodes, when clicked could display the page ind
 icated.  Markup could be used to include forms in the page.\n\n.. _sample2: http://plumloco.co.uk/leo_to_dhtml/demo/dhtml/\n\n  + Web page as GUI (thin client).\n\n    It might be possible to use a webpage as a thin client, collecting keystrokes to feed to a leo running on localhost or a remote server and receiving instructions as to how to update the view.\n\n  + Web page as GUI (thick client).\n\n    Allow javascript  to do most of the editing and only report back to the server to store the results or run python code.\n\n  + Implement Leo in Javascript.\n\n    Not impossible, but a lot of work ...\n\n  + Create a Firefox plugin.\n\n    And have a complete javascript Leo operating out of firefox.  Actually this could apply to some of the above as well.\n\nPlumloco's experiments\n========
 ==============\n\nI ([Plumloco]) have an experimental plugin leo_to_dhtml_ where I will be exploring some of the easier aspects of this topic.\n\n.. _leo_to_dhtml: http://plumloco.co.uk/leo_
 to_dhtml/\n\n  \n"},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x512ef38>,
       'request': <HTTPRequest, URL=http://leo.zwiki.org/LeoInAjax/editform>,
       'root': <Application at >,
       'template': <ZopePageTemplate at /leo.zwiki.org/editform.pt used for /leo.zwiki.org/LeoInAjax>,
       'traverse_subpath': [],
       'user': <SpecialUser 'Anonymous User'>}

    * Module zope.tales.expressions, line 280, in __call__
    * Module Products.PageTemplates.Expressions, line 186, in evaluateBoolean
    * Module zope.tales.tales, line 696, in evaluate
      URL: /leo.zwiki.org/editform.pt
      Line 121, Column 16
      Expression: <PathExpr standard:u'here/supportsEpoz'>
      Names:

      {'container': <Folder at /leo.zwiki.org>,
       'context': <ZWikiPage 'LeoInAjax' at 0x61b9a10>,
       'default': <object object at 0x2b1c2dd90200>,
       'here': <ZWikiPage 'LeoInAjax' at 0x61b9a10>,
       'loop': {},
       'nothing': None,
       'options': {'action': 'Edit',
                   'args': (<ZWikiPage 'LeoInAjax' at 0x61b9a10>,
                            <HTTPRequest, URL=http://leo.zwiki.org/LeoInAjax/editform>),
                   'id': u'Leo in Ajax',
                   'oldid': 'LeoInAjax',
                   'page': u'Leo in Ajax',
                   'text': "This page will discuss creating web pages that look like Leo outlines. It's a good place to post code.\n\n.. contents::\n\nIntroduction\n============\nIt is important in these discussions to recognize that Ajax does one thing only.\n\nIt allows a script in a web page to request the contents of another web page as if the script were a browser and receive the page as a browser would receive it, except in the form of a string.\n\nThe string received may be the contents of a static web page (html, xml) or a dynamically generated page from php, asp, cgi etc. or in a pickled data format such as JSON produced by a server script (or as plain text).\n\nPeople sometimes use 'AJAX' to mean 'dhtml', which is fine as long as we are aware of the distinction. 'dhtml' is perhap
 s more appropriate  for referring to the combination of html, javascript, css, AJAX, server scripting, etc which make up a modern dynamic web page.\n\nList of 'use cases'\n==================
 =\nThere are range of what can loosely call 'use cases'. Let's try to make a list of them from simplest to most esoteric.  Here is a start:\n\n  (It might be better if long comments were put in a separate section and only a short note with a link placed in this list.)\n\n  + Static XHTML/HTML (sample1_)\n\n    This is a straight forward conversion of an outline to an xhtml list that can be displayed as a web page. XHTML is perhaps better as it allows xml tools such as XSLT to post precess the page.\n\n.. _sample1: http://plumloco.co.uk/leo_to_dhtml/demo/xhtml/\n\n  + Dhtml page that allows the outline to be collapsed/expanded.\n\n    This still essentially only shows the page as it would be seen in the browser.\n\n  + Dhtml page that interprets bodyString (sample2_).\n    \n    This would
  allow leo to become a web authoring tool. The bodyString of a leo node could contain Wiki markup or raw html and then displayed as html.  @url nodes, when clicked could display the page ind
 icated.  Markup could be used to include forms in the page.\n\n.. _sample2: http://plumloco.co.uk/leo_to_dhtml/demo/dhtml/\n\n  + Web page as GUI (thin client).\n\n    It might be possible to use a webpage as a thin client, collecting keystrokes to feed to a leo running on localhost or a remote server and receiving instructions as to how to update the view.\n\n  + Web page as GUI (thick client).\n\n    Allow javascript  to do most of the editing and only report back to the server to store the results or run python code.\n\n  + Implement Leo in Javascript.\n\n    Not impossible, but a lot of work ...\n\n  + Create a Firefox plugin.\n\n    And have a complete javascript Leo operating out of firefox.  Actually this could apply to some of the above as well.\n\nPlumloco's experiments\n========
 ==============\n\nI ([Plumloco]) have an experimental plugin leo_to_dhtml_ where I will be exploring some of the easier aspects of this topic.\n\n.. _leo_to_dhtml: http://plumloco.co.uk/leo_
 to_dhtml/\n\n  \n"},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x512ef38>,
       'request': <HTTPRequest, URL=http://leo.zwiki.org/LeoInAjax/editform>,
       'root': <Application at >,
       'template': <ZopePageTemplate at /leo.zwiki.org/editform.pt used for /leo.zwiki.org/LeoInAjax>,
       'traverse_subpath': [],
       'user': <SpecialUser 'Anonymous User'>}

    * Module zope.tales.expressions, line 217, in __call__
    * Module Products.PageTemplates.Expressions, line 131, in _eval
    * Module zope.tales.expressions, line 124, in _eval
    * Module Products.PageTemplates.Expressions, line 80, in boboAwareZopeTraverse
    * Module OFS.Traversable, line 301, in restrictedTraverse
    * Module OFS.Traversable, line 284, in unrestrictedTraverse
      __traceback_info__: ([], 'supportsEpoz')

NotFound: supportsEpoz (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: tuple index out of range)

Troubleshooting Suggestions

    * The URL may be incorrect.
    * The parameters passed to this resource may be incorrect.
    * A resource that this resource relies on may be encountering an error.

For more detailed information about the error, please refer to the error log.

If the error persists please contact the site maintainer. Thank you for your patience. 

--
forwarded from http://zwiki.org/1438CantEditBeneathLeoZwikiOrg#[email protected]