Skip to content


Subversion checkout URL

You can clone with
Download ZIP


KeyError: u'profile-collective.prettydate:default' #3

teroajk opened this Issue · 8 comments

3 participants


When trying to activate this in Plone 4.1.4, I got the traceback below. I tried installing collective.prettydate, but the error remains.

Traceback (innermost last):
  Module ZPublisher.Publish, line 126, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 46, in call_object
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 575, in installProducts
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 498, in installProduct
   - __traceback_info__: ('collective.twitter.portlets',)
  Module Products.ExternalMethod.ExternalMethod, line 234, in __call__
   - __traceback_info__: ((,), {'reinstall': False}, (False,))
  Module /home/tero/Plone/buildout-cache/eggs/collective.twitter.portlets-1.0b1-py2.6.egg/collective/twitter/portlets/Extensions/, line 12, in install
  Module Products.GenericSetup.tool, line 325, in runAllImportStepsFromProfile
   - __traceback_info__: profile-collective.twitter.portlets:default
  Module Products.GenericSetup.tool, line 1059, in _runImportStepsFromContext
  Module Products.GenericSetup.tool, line 1042, in getProfileDependencyChain
  Module Products.GenericSetup.tool, line 1040, in getProfileDependencyChain
  Module Products.GenericSetup.tool, line 825, in getDependenciesForProfile
KeyError: u'profile-collective.prettydate:default'

System information:

Plone 4.1.4 (4113)
CMF 2.2.5
Zope 2.13.12
Python 2.6.7 (r267:88850, May 31 2012, 22:30:53) [GCC 4.6.3]
PIL unknown


how are you trying to activate it, from control panel or running the GS profile?


From control panel at prefs_install_products_form.


I did some searching and from here

and some further research, I'd venture a guess that this is caused by the following commit in collective.prettydate:


The commit removes the "default" GS-profile, which collective.twitter.portlets seems to look for.

I'll try downgrading collective.prettydate to 1.0 and see if that fixes the problem for me.


Well, the downgrading was surprisingly hairy, but it's done now. I can confirm that everything works fine with collective.prettydate version 1.0, but the error appears with 1.1.


you are completely right about this; thanks for pointing out :-)

@frapell frapell was assigned

@frapell this issue should be affecting other packages as well; please take care of it

@hvelarde hvelarde closed this in a6529d5

Thanks, working smoothly now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.