Ticket #144 (closed defect: fixed)

Opened 10 years ago

Last modified 10 years ago

PressRoom fails to install

Reported by: datakid Owned by: andycat
Priority: major Milestone: 0.2
Component: ATEngageVideo Severity:
Keywords: PressRoom Cc:
Who will test this:


When installing on a fresh Plone installation on

Ubuntu Gutsy (7.10),
Plone 2.5.5,
Zope (Zope 2.9.8-final, python 2.4.4, linux2),
Five 1.4.2,
Python 2.4.4 (#1, Jan 14 2008, 14:42:50) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)],
PIL 1.1.6

(ie, the Plone 2.5.5 unified installer)

and the trunk of the plumi svn.

Here is the output:

2008-01-14 15:42:41
Traceback (most recent call last):

  File "/opt/Plone-2.5.5/zeocluster/client1/Products/CMFQuickInstallerTool/", line 333, in installProduct

  File "/opt/Plone-2.5.5/lib/python/Products/ExternalMethod/", line 225, in __call__
    try: return f(*args, **kw)

  File "/opt/plumi_trunk/PressRoom/Extensions/", line 90, in install
    kupuTool.updateResourceTypes(({'resource_type' : 'linkable',

  File "/opt/Plone-2.5.5/zeocluster/client1/Products/kupu/plone/", line 159, in updateResourceTypes
    portal_types = self._validate_portal_types(resource_type, type['portal_types'])

  File "/opt/Plone-2.5.5/zeocluster/client1/Products/kupu/plone/", line 146, in _validate_portal_types
    raise KupuError, "Resource type: %s, invalid type: %s" % (resource_type, p)

KupuError: Resource type: linkable, invalid type: CallOut


Change History

comment:1 Changed 10 years ago by datakid

After doing some searching online, I discovered that you could get it to install if you comment out part of the function (?) "def install(self)" in /opt/plumi_trunk/PressRoom/Extensions/ The diff is below

I read about that [here't-install-SignupSheet-on-Zope-2.9---Plone-2.5.2-p11020529s21655.html]

---	(revision 56843)
+++	(working copy)
@@ -87,15 +87,15 @@
     # kupu_library_tool has an odd interface, basically written purely to
     # work with its configuration page. :-(
-    kupuTool.updateResourceTypes(({'resource_type' : 'linkable',
-                                   'old_type'      : 'linkable',
-                                   'portal_types'  :  linkable},
-                                  {'resource_type' : 'mediaobject',
-                                   'old_type'      : 'mediaobject',
-                                   'portal_types'  :  mediaobject},
-                                  {'resource_type' : 'collection',
-                                   'old_type'      : 'collection',
-                                   'portal_types'  :  collection},))
+#    kupuTool.updateResourceTypes(({'resource_type' : 'linkable',
+#                                   'old_type'      : 'linkable',
+#                                   'portal_types'  :  linkable},
+#                                  {'resource_type' : 'mediaobject',
+#                                   'old_type'      : 'mediaobject',
+#                                   'portal_types'  :  mediaobject},
+#                                  {'resource_type' : 'collection',
+#                                   'old_type'      : 'collection',
+#                                   'portal_types'  :  collection},))
     print >> out, "Added PressRoom types to kupu's linkable types, PressRoom type to collection"
     # enable two indices to be used by smart folders

When I look at the local site  http://localhost:8080/plumi-test/kupu_library_tool/zmi_resource_types (on my machine) I see 4 Resource types, yet in the code I commented out, I only see 3 - the type "media" is missing?

comment:2 follow-up: ↓ 3 Changed 10 years ago by datakid

Note that doing this means you can successfully "publish a callout" in that it installs, doesn't fail when you add one, appears in the member's call out's folder...but does not appear in the callouts portlet on the home page ("Recent callouts")

comment:3 in reply to: ↑ 2 Changed 10 years ago by datakid

  • Status changed from new to closed
  • Resolution set to fixed

This has been fixed, closing.

I went to find the changeset, but it was difficult - I don't quite understand that part yet. I would seem that we are different from the changeset I found here:

comment:4 Changed 10 years ago by datakid


Add a comment

Modify Ticket

as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.