#33 — Re-installation of RichDocument fails

by Sean Fulmer — last modified Apr 23, 2010 02:51 PM
State Unconfirmed
Version: 3.0.1
Area Functionality
Issue type Bug
Severity Medium
Submitted by Sean Fulmer
Submitted on Dec 07, 2007
Responsible
—
Target release:
—
Return to tracker
Re-installing RichDocument, either directly TTW or when re-installing a policy product that includes RichDocument, fails with the following:

  KupuError: Resource type: linkable, invalid type: RichDocument

(full traceback attached)

Looks like maybe RichDocument is not completely un-installing itself before the re-installation - specifically, it isn't being removed from the Kupu resource configuration.

CMFPlone 3.0.3, kupu 1.4.4
Steps to reproduce:
1. Install RichDocument.
2. Re-install RichDocument via portal_quickinstaller
Attached:
Octet Stream icon traceback — Octet Stream, 2 kB (2276 bytes)
Added by Sean Fulmer on Dec 07, 2007 05:56 PM
re-attaching traceback with TXT extension, so it doesn't look like a scary binary file.
Added by (anonymous) on Jan 26, 2008 07:39 PM
I got the same error here...does anyone know a workaround?
Added by (anonymous) on Mar 31, 2008 12:36 PM
Happens for me too.. I came across this by using the tutoral code from Professional Plone Development (code from chapter 8), and trying to reinstall the tutorial product (optilux).
 
Added by Graham Perrin on Apr 16, 2008 07:26 AM
> KupuError: Resource type: linkable, invalid type: RichDocument

See also:

http://dev.plone.org/plone/ticket/7987 with a focus on
http://dev.plone.org/plone/ticket/7987#comment:6

No responses can be added.