Tracker log
An overview of recent activity in the tracker.
- New issue »update Pressroom from 3.2 to 3.3 does not work« added by Pavel Bogdanovic
Removed PressRoom types from default page types
Removed 'folder_listing_pressroom' view from topic's list of view methods
2010-03-12 11:23:29 ERROR Zope.SiteErrorLog 1268389409.990.222454532454 http://l
ocalhost:8080/plone/portal_quickinstaller/reinstallProducts
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module Products.PDBDebugMode.runcall, line 70, in pdb_runcall
Module ZPublisher.Publish, line 42, in call_object
Module <string>, line 6, in _facade
Module AccessControl.requestmethod, line 64, in _curried
Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 644, in reinsta
llProducts
Module <string>, line 4, in _facade
Module AccessControl.requestmethod, line 64, in _curried
Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 626, in uninsta
llProducts
Module Products.CMFQuickInstallerTool.InstalledProduct, line 288, in uninstall
Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
- __traceback_info__: ((<PloneSite at /plone>,), {'reinstall': True}, (False,
))
Module c:\workspace\plone3\eggs\products.pressroom-3.3-py2.4.egg\Products\Pres
sRoom\Extensions\Install.py, line 42, in uninstall
AttributeError: 'NoneType' object has no attribute 'getvalue'
> c:\workspace\plone3\eggs\products.pressroom-3.3-py2.4.egg\products\pressroom\e
xtensions\install.py(42)uninstall()
-> return out.getvalue()
(Pdb) l
37 # 2: Remove PressRoom's contributions to various portal_properties.s
ite_properties props
38 out = restorePropertiesSettings(portal, out)
39 # 3: Remove 'folder_listing_pressroom' view from topic's list of vie
w methods
40 out = restoreViewMethods(portal, out)
41
42 -> return out.getvalue() [EOF]
(Pdb) p out
None
(Pdb)Added 8 day(s) ago.
- Jon Baldivieso added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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.Issue state: Confirmed → Resolved.
Added 234 day(s) ago.- (anonymous) added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 276 day(s) ago.
- New issue »Providing for internal/external workflow« added by Ian Ruffell
Is it worth catering for the default intranet workflow that ships with Plone, which has internally_published and external states, rather than published states?
At the moment, if you want to combine intranet with public website, you either have to redefine the workflow or override browser/pressroom.py to search the catalog for 'external' material.
A solution out-of-the-box which catered for the standard plone set-ups would be great.Added 340 day(s) ago.
- New issue »HTML validation errors« added by Ian Ruffell
There are validation errors in the main Press Room view template for the 3.2 release (skins/pressroom_content/pressroom_view.pt). Easy enough to fix; haven't checked earlier releases though.
Added 340 day(s) ago.
- Jon Stahl added a new response to »Batch listing of press releases, clips and contacts«:
http://dev.plone.org/plone/changeset/21670 may be relevant.
Added 386 day(s) ago.
- Jon Stahl added a new response to »Batch listing of press releases, clips and contacts«:
Bumping this priority.
Severity: Low → Medium.
Added 386 day(s) ago.- New issue »Provide translation .pot file in SVN« added by Lachlan Musicman
Could the two pot files be included in the i18n directory please?
plone.pot and portletification.pot
I have created them locally, but will be submitting some South East Asian translations soon and would like to work from svn...
Alternatively, how should I submit the translations?Added 411 day(s) ago.
- Jon Baldivieso added a new response to »Batch listing of press releases, clips and contacts«:
Agreed.
Issue state: unconfirmed → open.
Added 481 day(s) ago.- New issue »Batch listing of press releases, clips and contacts« added by Jon Stahl
We should probably make the press release and press clips folder view use batching.
Added 483 day(s) ago.
- New issue »PR Date should set Effective Date« added by Chris Shenton
When creating a Press Release, it asks for a Date. But when I create a collection (e.g., for a portlet) it lists the date the PR was created (e.g., now), not the date given to the PR. This means I can't use standard collection portlet to display these properly.
It also means -- I think -- that if I create a PR with a date in the future, it won't be embargoed until that date, since it's not setting the actual dublic core Effective Date.
So instead of storing the PR date in its own attribute, shouldn't it store into the DC Effective Date?Added 504 day(s) ago.
- Kevin Strasser added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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: PressRoomAdded 704 day(s) ago.
- (anonymous) added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 708 day(s) ago.
- Jon Baldivieso added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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!
JonAdded 715 day(s) ago.
- Jon Baldivieso added a new response to »Make StoryDate field available to Smart Folders«:
Closed in trunk; will be part of 3.2 release.
Issue state: open → resolved.
Target release: None → 3.2.
Responsible manager: burbank → jbaldivieso.
Added 715 day(s) ago.- Kevin Strasser added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 729 day(s) ago.
- Jon Baldivieso added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 BaldiviesoAdded 729 day(s) ago.
- Jon Stahl added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 729 day(s) ago.
- Kevin Strasser added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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 729 day(s) ago.
- Jon Stahl added a new response to »Broken Product Errors - KupuError: Resource type: linkable, invalid type: PressRoom«:
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.Severity: Medium → Important.
Added 730 day(s) ago.