Personal tools
You are here: Home → Products → Poi → Issue tracker → adding issue fails on Plone 3
Navigation
Log in


Forgot your password?
New user?
 
Document Actions

#140 — adding issue fails on Plone 3

State Resolved
Version: 1.0
Area Functionality
Issue type Bug
Severity Medium
Submitted by Hans-Peter Locher
Submitted on Aug 20, 2007
Responsible Maurits van Rees
Target release:
—
Return to tracker
Last modified on Nov 14, 2007 by Maurits van Rees
Using the Poi Plone 3 bundle,
adding an issue to the tracker fails (see Traceback for Error)


used versions:

Poi https://svn.plone.org/[…]/plone3-support revision 47490
Plone 3.0-rc2
Zope 2.10.4-final

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module Products.PDBDebugMode.pdbzope.runcall, line 60, in pdb_runcall
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFPlone.FactoryTool, line 368, in __call__
  Module Products.CMFPlone.FactoryTool, line 152, in __getitem__
  Module Products.CMFPlone.PloneFolder, line 348, in invokeFactory
  Module Products.CMFCore.TypesTool, line 716, in constructContent
  Module Products.CMFCore.TypesTool, line 276, in constructInstance
  Module Products.CMFCore.TypesTool, line 450, in _constructInstance
  Module Products.Poi.content.PoiIssue, line 9, in addPoiIssue
  Module Products.PDBDebugMode.archetypes, line 12, in initializeArchetype
  Module Products.Archetypes.BaseObject, line 443, in setDefaults
  Module Products.Archetypes.Schema, line 497, in setDefaults
  Module Products.Archetypes.utils, line 160, in mapply
  Module Products.Archetypes.ExtensibleMetadata, line 277, in allowDiscussion
  Module Products.CMFDefault.DiscussionTool, line 82, in overrideDiscussionFor
AttributeError: allow_discussion
> /home/hplocher/develop/octopus/im3/zope-instances/octopus/Products/CMFDefault/DiscussionTool.py(82)overrideDiscussionFor()
-> del content.allow_discussion
Steps to reproduce:
Install Poi and dependencies (included in the bundle) to a Plone 3 (RC2) instance.
Create an issue tracker and submit a new issue.
Added by (anonymous) on September 21, 2007 - 11:37
Same problem, but I have it with Plone 3.0.1 and latest (today) SVN checkout.

Traceback (innermost last):

    * Module ZPublisher.Publish, line 119, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFPlone.FactoryTool, line 376, in __call__
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFFormController.FSControllerPageTemplate, line 90, in __call__
    * Module Products.CMFFormController.BaseControllerPageTemplate, line 28, in _call
    * Module Products.CMFFormController.ControllerBase, line 232, in getNext
      __traceback_info__: ['id = base_edit', 'status = success', 'button=None', 'errors={}', 'context=<PoiIssue at poiissue.2007-09-21.5687588566>', 'kwargs={}', 'next_action=None', '']
    * Module Products.CMFFormController.Actions.TraverseTo, line 38, in __call__
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFFormController.FSControllerPythonScript, line 104, in __call__
    * Module Products.CMFFormController.Script, line 145, in __call__
    * Module Products.CMFCore.FSPythonScript, line 140, in __call__
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPythonScript, line 196, in _exec
    * Module None, line 1, in content_edit
      <FSControllerPythonScript at /Plone/content_edit used for /Plone/aaaa/portal_factory/PoiIssue/poiissue.2007-09-21.5687588566>
      Line 1
    * Module Products.CMFCore.FSPythonScript, line 140, in __call__
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPythonScript, line 196, in _exec
    * Module None, line 13, in content_edit_impl
      <FSPythonScript at /Plone/content_edit_impl used for /Plone/aaaa/portal_factory/PoiIssue/poiissue.2007-09-21.5687588566>
      Line 13
    * Module Products.Archetypes.BaseObject, line 655, in processForm
    * Module Products.Archetypes.BaseObject, line 644, in _processForm
      __traceback_info__: (<PoiIssue at /Plone/aaaa/poiissue.2007-09-21.5687588566>, <Field details(text:rw)>, <bound method PoiIssue.setDetails of <PoiIssue at /Plone/aaaa/poiissue.2007-09-21.5687588566>>)
    * Module Products.Archetypes.utils, line 160, in mapply
    * Module Products.Archetypes.ClassGen, line 76, in generatedMutator
    * Module wicked.fieldevent, line 34, in store
    * Module zope.event, line 23, in notify
    * Module zope.component.event, line 26, in dispatch
    * Module zope.component._api, line 130, in subscribers
    * Module zope.component.registry, line 290, in subscribers
    * Module zope.interface.adapter, line 535, in subscribers
    * Module wicked.fieldevent, line 24, in notifyFieldEvent
    * Module zope.component._api, line 130, in subscribers
    * Module zope.component.registry, line 290, in subscribers
    * Module zope.interface.adapter, line 539, in subscribers
    * Module wicked.fieldevent.meta, line 83, in field_value_set
    * Module Products.Archetypes.Field, line 1036, in set
    * Module Products.Archetypes.Field, line 1334, in _process_input
    * Module Products.Archetypes.BaseUnit, line 52, in update
    * Module Products.MimetypesRegistry.MimeTypesRegistry, line 365, in __call__
    * Module OFS.Uninstalled, line 48, in __getattr__


Added by (anonymous) on November 6, 2007 - 20:04
Same problem. On Plone 3.02, Poi Plone3-Support bundle.

Traceback (innermost last):

    * Module ZPublisher.Publish, line 119, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFPlone.FactoryTool, line 376, in __call__
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFFormController.FSControllerPageTemplate, line 90, in __call__
    * Module Products.CMFFormController.BaseControllerPageTemplate, line 28, in _call
    * Module Products.CMFFormController.ControllerBase, line 231, in getNext
    * Module Products.CMFFormController.Actions.TraverseTo, line 38, in __call__
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Products.CMFFormController.FSControllerPythonScript, line 104, in __call__
    * Module Products.CMFFormController.Script, line 145, in __call__
    * Module Products.CMFCore.FSPythonScript, line 140, in __call__
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPythonScript, line 196, in _exec
    * Module None, line 1, in content_edit
      <FSControllerPythonScript at /Plone/content_edit used for /Plone/it/helpdesk/portal_factory/PoiIssue/poiissue.2007-11-06.3594747819>
      Line 1
    * Module Products.CMFCore.FSPythonScript, line 140, in __call__
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPythonScript, line 196, in _exec
    * Module None, line 13, in content_edit_impl
      <FSPythonScript at /Plone/content_edit_impl used for /Plone/it/helpdesk/portal_factory/PoiIssue/poiissue.2007-11-06.3594747819>
      Line 13
    * Module Products.Archetypes.BaseObject, line 655, in processForm
    * Module Products.Archetypes.BaseObject, line 644, in _processForm
      __traceback_info__: (<PoiIssue at /Plone/it/helpdesk/poiissue.2007-11-06.3594747819>, <Field details(text:rw)>, <bound method PoiIssue.setDetails of <PoiIssue at /Plone/it/helpdesk/poiissue.2007-11-06.3594747819>>)
    * Module Products.Archetypes.utils, line 160, in mapply
    * Module Products.Archetypes.ClassGen, line 76, in generatedMutator
    * Module wicked.fieldevent, line 34, in store
    * Module zope.event, line 23, in notify
    * Module zope.component.event, line 26, in dispatch
    * Module zope.component._api, line 130, in subscribers
    * Module zope.component.registry, line 290, in subscribers
    * Module zope.interface.adapter, line 535, in subscribers
    * Module wicked.fieldevent, line 24, in notifyFieldEvent
    * Module zope.component._api, line 130, in subscribers
    * Module zope.component.registry, line 290, in subscribers
    * Module zope.interface.adapter, line 539, in subscribers
    * Module wicked.fieldevent.meta, line 83, in field_value_set
    * Module Products.Archetypes.Field, line 1036, in set
    * Module Products.Archetypes.Field, line 1334, in _process_input
    * Module Products.Archetypes.BaseUnit, line 52, in update
    * Module Products.MimetypesRegistry.MimeTypesRegistry, line 365, in __call__
    * Module OFS.Uninstalled, line 48, in __getattr__

AttributeError: binary
Added by Maurits van Rees on November 14, 2007 - 19:28
Issue state: unconfirmed → open
Responsible manager: (UNASSIGNED) → maurits
I fixed the original "AttributeError: allow_discussion" at the end of August on the branch in r48443.

I have not yet looked at the second error "binary" as reported in the responses here.
Added by Maurits van Rees on November 14, 2007 - 19:40
Issue state: open → resolved
Ah, I now remember that "AttributeError: binary". Well, Google remembered it for me. ;-)

And I already fixed a while ago. :) So I will close this report.

Advice:

When going from Plone 2.5 to 3.0:
- Uninstall intelligenttext from the quick installer while still running 2.5.
- Stop zope, put the Plone 3.0 files in their places.
- Remove Products/intelligenttext.
- Start zope and run the plone migration. This will give you the mimetypes and transforms from plone.intelligenttext, which is the way forward.



Details for those interested:

See this thread:
http://groups.google.com/[…]/c452da675b2d6925

And this plone ticket:
http://dev.plone.org/plone/ticket/6684

which again points to this thread:
http://comments.gmane.org/[…]/15759

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by