plone

I'm used to achieve this under Plone 3 by override base_edit.cpt file under portal_skin and make columns empty: <metal:head fill-slot="column_one_slot"></metal:head> <metal:head fill-slot="column_two_slot"></metal:head> I have tried to achieve this with Plone4 and the result is quite weird: I have two empty columns and the edit mode doesn't stretch (stay in the middle of the page). In Plone 4 you can disable the columns by setting a couple variables on the request: <metal:override fill-slot="top_slot" tal:define="disable_column_one python:request.set('disable_plone.leftcolumn',1); disable

I made a webportal on my mac using plone4.1 and Diazo. Now, I'm trying to deploy it on my server (CentOs) where there is yet another site with plone4.0.5 + collectivexdv. When I run the site (in a brand new buildout) with my diazotheme I obtain this lines via shell (instance fg): 2011-09-27 09:32:10 ERROR plone.transformchain Unexpected error whilst trying to apply transform chain Traceback (most recent call last): File "/home/plone/.buildout/eggs/plone.transformchain-1.0-py2.6.egg/plone/transformchain/transformer.py", line 42, in __call__ newResult = handler.transformIterable(result, encoding

We are implementing Plone as a document management system in a hospital setting. In doing so, the review process asks for two review steps: where nursing staff review a document where physicians review a document The problem arises when we found out that the nurses are grouped based on the types of machinery they handle (specifically types of scanners, ultrasound,...). On these machines they perform all kinds of exams, on all kinds of bodyparts. The physicians on the other hand are grouped based on bodyparts expertise. This means that a document that pertains to an ultrasound of the pelvis

I am using 'one state workflow' for image types in Plone, and it appears an anonymous user can still see an image even if it's 'publishing date' is set in the future... Is 'publishing date' ignored in 'one state workflow' for images? It also appears 'expiry date' is also ignored ie it appears when you dial up its url. Note: I am accessing the image direct via it's URL eg my.site.com/assets/images/myexpiredimage Perhaps these publish/expiry dates only useful for listings and collections etc, they dont control access and visibility? Tried to find good Plone doco on this but couldn't... happy for

In Plone 2, there were icons for print, fullscreen and email in object views. How do I enable these in Plone 4? They don't seem to be present in a default installation of Plone 4.1, but I must be missing something, and I'd like to know what? Thanks IIRC, document actions can be re-enabled in Plone 4 in the ZMI interface for the actions tool: http://plone.293351.n2.nabble.com/document-actions-in-plone-4-td5788892.html Go to ./manage_main for your Plone site. Click on portal_actions Click on document_actions Click on each action you want to make a visible link (print, rss, etc). Click "visible"

I have a custom edit (browser page) for my dexterity content type. In template I have defined a form using Bootstrap and added some Angular JS code for form behavior. It is working. :) I need to replace a simple textarea with rich text widget. So how can I render in my template the rich text widget (one that is normally used in dexterity)? keul If you are using Mockup (not sure if anybody use it on Plone 4) you can find tips there: Obtaining the "default" mockup TinyMCE configuration on Plone 5 Otherwise (the Plone 4.3 version of TinyMCE) it's only a matter of CSS classes and configurations.

I want to get email notifications to the portal email address whenever a new user joins the portal. My guess is that I should code a new product to do that. Does such product already exist (for Plone 4)? I checked content rules, but AFAICT it could work only if I made the users contentish themselves with something like membrane/remember, but for my requirements that would be overkill. I don't think such a product already exists. It should be trivial to create a package that adds a content rule condition, that would let you write a content rule for the Products.PluggableAuthService.interfaces