fixed

from plone.app.contenttypes.

nevertheless, the view should not be called on anything else than a dexterity document as well as the old archetypes-event_view will throw errors on anything except than the old archetypes event-types. That is one of many reasons why we want to move away from skin-templates...

from plone.app.contenttypes.

On 10/08/2012 11:03 PM, Philip Bauer wrote:

nevertheless, the view should not be called on anything else than a dexterity
document as well as the old archetypes-event_view will throw errors on
anything except than the old archetypes event-types. That is one of many
reasons why we want to move away from skin-templates...

—
Reply to this email directly or view it on GitHub
#5 (comment).

hoppla schorsch,

I just checked out a new version. The problem is not fixed yet:

*URL:

file:/home/zope/energieclusterR5/src/plone.app.contenttypes/plone/app/contenttypes/skins/templates/document_view.pt*
Line 17, Column 8
Expression: <PathExpr standard:u'context/text'>
Names:

{'container': <ATDocument at /ecweb/ecweb5/front-page>,
'context': <ATDocument at /ecweb/ecweb5/front-page>,
'default': <object object at 0x7f827c3164e0>,
'here': <ATDocument at /ecweb/ecweb5/front-page>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x7f826c33e628>,
'request': <HTTPRequest, URL=http://localhost:8192/ecweb/ecweb5/front-page/document_view>,
'root': ,
'template': <FSPageTemplate at /ecweb/ecweb5/front-page/document_view>,
'traverse_subpath': [],
'user': <PropertiedUser 'robert'>}

Module zope.tales.expressions, line 217, in call

Module Products.PageTemplates.Expressions, line 147, in _eval

Module zope.tales.expressions, line 124, in _eval

Module Products.PageTemplates.Expressions, line 74, in boboAwareZopeTraverse

Module OFS.Traversable, line 317, in restrictedTraverse

Module OFS.Traversable, line 285, in unrestrictedTraverse

traceback_info: ([], 'text')

and this is the fix:

<metal:content-core fill-slot="content-core">
<metal:content-core define-macro="content-core">
<tal:comment replace="nothing">
This is fixed in dexterity trunk
http://code.google.com/p/dexterity/issues/detail?id=200 and
tal:condition="context/text" should be removed after the next release
of dexterity.
/tal:comment
<div id="parent-fieldname-text"

          tal:condition="context/text|nothing"
          tal:content="structure context/text/output" />
 </metal:content-core>

/metal:content-core

from plone.app.contenttypes.

We're planning to write Browser-Views for these content-types in the near future. Again: The views that plone.app.contenttypes has are overriding the ones in CMFPlone/skins/plone_content and are not meant to be used on ATContentTypes instances. So: At the present state either don't use this package in a site where there are instances of those present or register different views to them in the portal_types tool.

Documentation will be out with the first apha-release.

from plone.app.contenttypes.

As I said before:
the error happens when I use a site with nothing but a bunch of
dexterity based folders.

So I suggest you add the hyper trivial fix I did add to the ticket.

thanks
robert

On 12.10.2012 16:05, Philip Bauer wrote:

We're planning to write Browser-Views for these content-types in the
near future. Again: The views that plone.app.contenttypes has are
overriding the ones in CMFPlone/skins/plone_content and are not meant
to be used on ATContentTypes instances. So: At the present state
either don't use this package in a site where there are instances of
those present or register different views to them in the portal_types
tool.

Documentation will be out with the first apha-release.

—
Reply to this email directly or view it on GitHub
#5 (comment).

from plone.app.contenttypes.