[quills-dev] Fixed portlets with Quills 1.7.0b1?
Tim Hicks tim at sitefusion.co.ukTue Jun 24 22:02:12 UTC 2008
- Previous message: [quills-dev] Fixed portlets with Quills 1.7.0b1?
- Next message: [quills-dev] Fixed portlets with Quills 1.7.0b1?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Duane, Duane Raymond (FairSay) wrote: > Hi, > > I'm trying out Quills 1.7.0b1 (both Quills and QuillsEnabled but only > one at a time) on Plone 3.1.2 and have found that for both, a number > of portlets are automatically added however they aren't manageable via > the 'manage portlets' options nor do they seem to be editable via > old-style 'slots' properties. > > Does anyone have suggestions on how to remove the default portlets so > I can manage them using the standard Plone 3 method (manage portlets)? I'm travelling at the moment so can't really look too deeply at this. I remember the portlet handling code being rather complicated when I wrote it, so it wouldn't surprise me if there turned out to be this deficiency that you point out. Do you have any experience with plone[.app].portlets code? It would be great if you could take a look at this. The best place to start would be <http://dev.plone.org/collective/browser/quills.app/trunk/quills/app/portlets>, and in particular the configure.zcml and context.py files in there... Tim
- Previous message: [quills-dev] Fixed portlets with Quills 1.7.0b1?
- Next message: [quills-dev] Fixed portlets with Quills 1.7.0b1?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the quills-dev mailing list