I'm still using Quills for my blog as well: http://claytron.com
I just upgraded to 3.1 last night (which went pretty smoothly, and i need to blog about it :) To remove those portlets in 1.7 beta 2 you need to do this: <code> from transaction import commit from zope.component import getUtility from Products.CMFCore.utils import getToolByName #from plone.portlets.constants import CONTENT_TYPE_CATEGORY from plone.portlets.interfaces import IPortletManager from plone.app.portlets.storage import PortletAssignmentMapping from quills.core.interfaces import IWeblog from quills.core.interfaces import IWeblogEnhanced from quills.app.portlets.context import INTERFACE_CATEGORY left_column = getUtility(IPortletManager, name="plone.leftcolumn") right_column = getUtility(IPortletManager, name="plone.rightcolumn") left_category = left_column[INTERFACE_CATEGORY] right_category = right_column[INTERFACE_CATEGORY] ifid = IWeblog.__identifier__ left_portlets = left_category.get(ifid, None) right_portlets = right_category.get(ifid, None) # see what keys are assigned left_portlets.keys() ['recententries', ...] # to remove a portlet from the 'mapping' del left_portlets['recententries'] # then commit (if from debug prompt) import transaction transaction.commit() </code> That's what I did :) for the left and right. I believe they changed this on the trunk, but i'm not sure. Clayton -- S i x F e e t U p , I n c . | "Nowhere to go but open source" Direct Line: +1 (317) 861-5948 x603 Toll-Free: 1-866-SIX-FEET [email protected] http://www.sixfeetup.com | Zope/Plone Custom Development On Dec 28, 2008, at 12:05 PM, Matt Fisher wrote: > > On Dec 28, 2008, at 7:00 AM, [email protected] wrote: > >> >>> Anyone know how to turn off the "recent entries", "recent comments", >>> and "recent authors" portlets on Quills? >> >> this, in fact, has been puzzling me, too. see http://tomster.org/ : >> they're still there and they're annoying me to no end. i assume that >> they are assigned to the IWeblog marker interface but am clueless on >> how to make that configurable. any ideas? who switched these portlets >> to this? > > > The only successful way I've found to turn off the Quill portlets is > with a css hack. It's the dumb way to do it, but it works. Each of > the Quills portlets has a unique ID, so you can isolate it and change > its style declaration to display:none in your style sheet, like: > > .portletQuillsLinks, > .portletWeblogAuthors, > .portletWeblogAdmin, > .portletRecentEntries { > display: none !important; > } > > This works no matter what version of Plone you're running. Of course, > this hides the portlets everywhere, all the time, and you won't be > able to add them back at all. As an alternate, you can add a column > declaration to your css, so that the portlets are hidden only when > assigned to the left or right columns, as in: > > #portal-column-two .portletWeblogAdmin, > #portal-column-two .portletRecentEntries { > display: none !important; > > As you've already found out, Quills completely ignores @@manage- > portlets on Plone 3.x, which is infuriating, IMO. As far as I can > tell, the developers are working on this, but who knows what the > timeline is. > > Your Quills portlets are initialized, as far as I can tell, in quills/ > app/setuphandlers.py a python script hidden deeeeeep in your > filesystem. I've played with the script but it doesn't seem to affect > anything-- maybe it only makes a difference on initial install... (& > I'm certainly not a dev expert--any experts care to chime in...?). > For as long as Quills doesn't respect @@manage-portlets, it would be > great to have some kind of alternate TTW config, like a control panel > or something. > >> >>> Am I still the only person in the world actually trying to use >>> Quills >>> as a blog? > >> certainly not, but it's far from as widespread as wordpress etc. >> > > It is a little confusing to notice how many Plone developers use some > other blogging platform. Take a browse through planet.plone.org and > you'll find a great variety of blogging solutions. For me, I like > Quills, or at least I like it enough to stick with it. I use > QuillsEnabledRemoteBlogging, which lets me edit & upload everything > via a desktop/iPhone client (MarsEdit & iBlogger respectively). > There's a longstanding discussion > [http://plone.org/events/sprints/past-sprints/snow-sprint3/blogging > ] about what the prospects are for blogging in Plone, and it's an > open issue. I think one sentiment you've seen is that Plone shouldn't > try to keep up with big organizations that specialize in development > for blogging-- I mean, wordpress is just amazing. Blogs on plone > probably will never be able to do all the things that wordpress, > blogger, et al can do. But that doesn't mean that blogging couldn't > be much, much easier on Plone, and IMO QuillsEnabled is definitely the > way forward. Certainly, Plone ought to be at least as visible as a > blogging platform as Drupal, anyway. > > I don't really know what it would take to build more momentum around > improving Quills & blogging generally on Plone. A big part of the > issue would seem to be that developer time & energy are scarce > commodities, and rightly so. And also, projects tend to get worked on > in priority of what kinds of demands your clients present, and it's > possible the individual nature of most blogs means that blog functions > usually aren't tied into large development projects, just a guess. But > as you've noticed, the whole problem isn't just about dev hours, it's > also about the way the crowd thinks and talks about the prospects, > which currently is pretty unfocused, IMO. i.e. if more people talked > more about blogging being central to Plone (and content management > generally), and about Quills being the best way forward, maybe more > dev hours would filter out of the woodwork. </soapbox> > > > > > _______________________________________________ > quills-dev mailing list > [email protected] > http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev _______________________________________________ quills-dev mailing list [email protected] http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev
