#44 — Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom

by (anonymous) — last modified Jul 29, 2009 06:00 PM
State Resolved
Version: 3.1
Area Functionality
Issue type Bug
Severity Important
Submitted by (anonymous)
Submitted on Dec 13, 2007
Responsible Jon Baldivieso
Target release:
Attempted an upgrade from version 1.0.3 to 3.1 on Plone 2.5.2. It did not upgrade. Getting Kupu errors. Tried uninstalling and then re-installing. Again same issue. I am running the following versions:

Plone 2.5.2,
CMF-1.6.2,
Zope (Zope 2.9.6-final, python 2.4.4, win32),
Five 1.3.8,
Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)],
PIL 1.1.5

The error is:

KupuError: Resource type: linkable, invalid type: PressRoom

The full string is below:

2007-12-13 11:48:37
failed:
Traceback (most recent call last):

  File "E:\Enfold Server\Products\CMFQuickInstallerTool\QuickInstallerTool.py", line 322, in installProduct
    res=install(portal)

  File "E:\Enfold Server\Zope\lib\python\Products\ExternalMethod\ExternalMethod.py", line 225, in __call__
    try: return f(*args, **kw)

  File "E:\Enfold Server\Products\PressRoom\Extensions\Install.py", line 25, in install
    setup_tool.runAllImportSteps()

  File "E:\Enfold Server\Products\GenericSetup\tool.py", line 251, in runAllImportSteps
    message = self._doRunImportStep(step, context)

  File "E:\Enfold Server\Products\GenericSetup\tool.py", line 725, in _doRunImportStep
    return handler(context)

  File "E:\Enfold Server\Products\PressRoom\setuphandlers.py", line 86, in importFinalSteps
    configurator.configureKupu(site)

  File "E:\Enfold Server\Products\PressRoom\setuphandlers.py", line 29, in configureKupu
    kupuTool.updateResourceTypes(({'resource_type' : 'linkable',

  File "E:\Enfold Server\Products\kupu\plone\librarytool.py", line 159, in updateResourceTypes
    portal_types = self._validate_portal_types(resource_type, type['portal_types'])

  File "E:\Enfold Server\Products\kupu\plone\librarytool.py", line 146, in _validate_portal_types
    raise KupuError, "Resource type: %s, invalid type: %s" % (resource_type, p)

KupuError: Resource type: linkable, invalid type: PressRoom

=============
2007-12-13 11:48:26
uninstalled
Uninstalling Press Room
Removed reference to PressRoom types from kupu's linkable and collection types
Removed PressContact from types_not_searched
Removed PressRoom types from default page types
Removed PressRoom from use_folder_tabs
Removed PressRoom from typesLinkToFolderContentsInFC
Removed 'folder_listing_pressroom' view from topic's list of view methods
Steps to reproduce:
Trying to install on my instance.
Added by Toni Mueller on Dec 23, 2007 08:09 PM
Severity: ImportantMedium
Responsible manager: jbaldivieso(UNASSIGNED)
I'm seeing a similar problem with a 3.0.4 buildout-based installation and PressRoom 3.1. I've created a policy product along the lines of Martin's book, and when I add "PressRoom" to the list of products to be installed, everything breaks. I've tried with a blank Plone instance. The install works the first time, but when I uninstall all products that were installed as a dependency and try to install the policy product again, it fails with this traceback:

2007-12-23 21:04:20 ERROR Zope.SiteErrorLog http://localhost:8082/[…]/installProducts
Traceback (innermost last):
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 364, in installProduct
   - __traceback_info__: ('ffii.policy',)
  Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
   - __traceback_info__: ((<PloneSite at /f1>,), {'reinstall': False}, (False,))
  Module /home/zope/ffii-buildout/src/ffii.policy/ffii/policy/Extensions/Install.py, line 19, in install
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 405, in installProduct
   - __traceback_info__: ('ffii.theme',)
  Module Products.GenericSetup.tool, line 319, in runAllImportStepsFromProfile
   - __traceback_info__: profile-ffii.theme:default
  Module Products.GenericSetup.tool, line 1023, in _runImportStepsFromContext
  Module Products.GenericSetup.tool, line 982, in _doRunImportStep
   - __traceback_info__: onenwtemplate-final
  Module Products.PressRoom.setuphandlers, line 86, in importFinalSteps
  Module Products.PressRoom.setuphandlers, line 29, in configureKupu
  Module Products.kupu.plone.librarytool, line 239, in updateResourceTypes
  Module Products.kupu.plone.librarytool, line 210, in _validate_portal_types
KupuError: Resource type: linkable, invalid type: PressRoom
/home/zope/ffii-buildout/parts/plone/CMFQuickInstallerTool/QuickInstallerTool.py:392: DeprecationWarning: This will be removed in ZODB 3.7:
subtransactions are deprecated; use sp.rollback() instead of transaction.abort(1), where `sp` is the corresponding savepoint captured earlier
  transaction.abort(sub=True)

What makes it even weirder is that none of my other products (currently a custom theme and SQLPASPlugin) should so much as take a look at kupu, and everything except the theme can be installed alone, no problem. But on the theme, I also get this error. When I leave out the PressRoom from the dependencies, I can install and uninstall without a problem, and as often as I want.
Added by Jon Stahl on Mar 21, 2008 02:01 AM
Issue state: unconfirmedopen
Responsible manager: (UNASSIGNED)jbaldivieso
Added by Jon Stahl on Mar 21, 2008 02:21 AM
Severity: MediumImportant
From #48, it is reported:

Further information:

I have successfully done a migration from 1.0.3 to 1.1.1 and then from 1.1.1 to 3.1 on the same site and platform as above.

NOTE that I had to do a "clear and rebuild" on the portal catalog to get existing clips to display. Before I did that, they were not being found by the press clips smartfolder.
Added by Kevin Strasser on Mar 21, 2008 01:48 PM
I tried clear and rebuild as suggested and it has no impact. Also note that I am having this issue on two different machines. I can replicate this issue easily on my end. There definitely is a problem here somewhere.
Added by Jon Stahl on Mar 21, 2008 01:54 PM
Kevin-

We agree, there is definitely an issue. That is why I opened the ticket. :-)

The above comment suggests that one user was able to work around by upgrading from 1.0.3 -> 1.1.1, then to 3.1, with a clear and rebuild along the way. A clear-and-rebuild alone wouldn't work, because it wouldn't address the underlying issue with migrating the linkable types.

Added by Jon Baldivieso on Mar 21, 2008 03:13 PM
Kevin, et al:
Before you try reinstalling Press Room, try going into the Kupu control panel, click on the "Resource Types" tab, and save the settings there without changing them. That might make the install work -- let us know if it works.

Jon Baldivieso
Added by Kevin Strasser on Mar 21, 2008 08:25 PM
I tried saving the Kupu settings as suggested. I still get the Kupu error -- Resource type: linkable, invalid type: PressRoom. Also tried removing PressRoom as a linked type and saving that. Same error. Then tried uninstalling PressRoom and installing 3.1 instead of as an update. Same problems.
Added by Jon Baldivieso on Apr 04, 2008 06:20 PM
Kevin/Toni/anyone else reporting these symptoms -- in r62070 in trunk, I just committed what I think might be a workaround for this issue, and I'd love feedback from you about whether it works. If you are familiar with subversion, I'd love your help! Simply delete your current version of Press Room and in your products directory and check out trunk using this command:

svn checkout http://svn.plone.org/svn/collective/PressRoom/trunk PressRoom

Thanks!

Jon
Added by (anonymous) on Apr 11, 2008 08:42 PM
No SVN access here. Working on US government machines, which are strict about adding custom software, etc. Anywhere I could download a zip, etc of the new beta version?
Added by Kevin Strasser on Apr 15, 2008 03:08 PM
Finally got around to trying the SVN version. Deleted the old version, deleted the reference in products control panel and restarted Zope. Then loaded up the new version and restarted Zope.

Still getting the same errors.

Broken Product:

2008-03-21 16:21:41
failed:
Traceback (most recent call last):

  File "E:\Enfold Server\Products\CMFQuickInstallerTool\QuickInstallerTool.py", line 322, in installProduct
    res=install(portal)

  File "E:\Enfold Server\Zope\lib\python\Products\ExternalMethod\ExternalMethod.py", line 225, in __call__
    try: return f(*args, **kw)

  File "E:\Enfold Server\Products\PressRoom\Extensions\Install.py", line 25, in install
    setup_tool.runAllImportSteps()

  File "E:\Enfold Server\Products\GenericSetup\tool.py", line 251, in runAllImportSteps
    message = self._doRunImportStep(step, context)

  File "E:\Enfold Server\Products\GenericSetup\tool.py", line 725, in _doRunImportStep
    return handler(context)

  File "E:\Enfold Server\Products\PressRoom\setuphandlers.py", line 86, in importFinalSteps
    configurator.configureKupu(site)

  File "E:\Enfold Server\Products\PressRoom\setuphandlers.py", line 29, in configureKupu
    kupuTool.updateResourceTypes(({'resource_type' : 'linkable',

  File "E:\Enfold Server\Products\kupu\plone\librarytool.py", line 239, in updateResourceTypes
    portal_types = self._validate_portal_types(resource_type, type.get('portal_types', ()))

  File "E:\Enfold Server\Products\kupu\plone\librarytool.py", line 210, in _validate_portal_types
    raise KupuError, "Resource type: %s, invalid type: %s" % (resource_type, p)

KupuError: Resource type: linkable, invalid type: PressRoom
Added by (anonymous) on Jun 17, 2009 12:53 PM
hello, I did get a similar problem, but not related to PressRoom... and the above solutions, did help me...

Thanks a lot for all the suggestions...
Added by Jon Baldivieso on Jul 29, 2009 06:00 PM
Issue state: ConfirmedResolved
Ok, I've finally replicated this issue on Plone 2.5 (I suspect that 3.x is unaffected by this). My untested theory is that it's a Generic Setup bug of some sort, but I have what I believe is a workaround. Here's what worked for me:

- Uninstall PressRoom
- Go to portal_setup -> properties, and set "Plone Site" to be the profile used
- Install PressRoom.

I think this should do the trick, which is why I'm marking this issue resolved finally.

No responses can be added.