plone

I am having different theme HTML files for different site sections. There are some major layout differences depending if the page is the front page, or a certain subsection. As far as I see the default behavior is just to have one HTML file: http://pypi.python.org/pypi/collective.xdv#usage What would be the best strategy to use multiple theme files, slight rule variations and collective.xdv? Plone 4.1b. We usually just utilize plain xdv and use the rules.xml (or whatever you want to call it) file to setup the theme templates leaving the corresponding properties in the collective.xdv

I'm working on setting up a Zope Replicated Storage (ZRS) based deployment. I currently have two servers (east and west) west will be the primary east will be the secondary I haven't touched the west box yet . On the east box I've edited my buildout as follows (I had to pin plone.recipe.zeoserver to 1.2.6 because the zrs features didn't exist before version 1.2.6): [zeoserver] recipe = plone.recipe.zeoserver[zrs] replicate-from = ${hosts:zeoserver-west}:${ports:zeoserver-zrs} [versions] plone.recipe.zeoserver = 1.2.6 After running bin/buildout I try to start my cluster and the instances seem

We had a whole collection of Plone 3 sites with a custom Image type subclassed from ATImage. This allowed us to add an extra image scaling to the standard list ("'logo':(454, 58)", used by our theme package). While this still works in Plone 4, it isn't really the correct approach now that plone.app.imaging is part of the standard toolkit. That can define custom scales on the fly. It looks like I can enable plone.app.imaging on any type subclassed from ATImage by simply setting "sizes = None" for the collection of custom scales on the type. I am however then left with a redundant subclass of

The users do it because they can. However, image auto-resize etc. breaks down. This make me a sad boy. How to limit image uploads to GIF, PNG and JPEG sitewide? For Archetypes For Dexterity i ran into similar problems these days and worked around them like that: add a custom widget that adds an accept attribute to the file input set field.swallowResizeExceptions = True so users at least don't get a site-error when uploading an unsopported image type state mimetypes that work in description The field definition looks like this: atapi.ImageField('image1', swallowResizeExceptions = True, widget =

I am using Plone and Sugar CRM. I want to allow users to only have a single username and password across both systems. When they change their password in Plone they should not have to change it in Sugar CRM. Is there a simple way to do this? Configure both to authenticate against an LDAP server. If you want single sign on, you can also look at Plone 4's mod_auth_tkt support. Basically, Plone will set a cookie that is compatible with the auth_tkt standard. Other systems (such as Apache or nginx as fronting web servers) can use the same cookie format to authenticate a user. 来源： https:/

Is there a comprehensive reference list of the generic setup import step names? The names of generic setup import steps don't always match the names of their corresponding xml files for example 'types.xml' has an import step called 'typeinfo'. In the absence of a list, I would be satisfied with a simple approach to finding out the name of the import step. For example the import step name for plone.app.registry which is managed by the 'registry.xml' file is not obvious, I tried to refer to it as 'registry' but this fails, see code below: from Products.CMFCore.utils import getToolByName PROFILE

How to: Make an Asp.Net application to recognize a plone authenticated user (his/her id, roles and any other available data) and vice-versa? Show plone contents inside my asp.net application or show some application-specific data inside plone? Insert plone contents from inside an asp.net application? optilude There are a couple of high level approaches: Security: Put a web server in front of both Plone and the ASP.net application and use the auth_tkt cookie format. Apache and nginx support this, for example, and Plone 4 has built-in auth_tkt cookie format support. Use a shared ActiveDirectory

How one could override files in nested portal_skins folder? The default behavior seems to be that you need to copy whole folder structures if you want to override a single file. This is a maintenance nightmare. E.g. how to override file: Producs.TinyMCE/skins/tinymce/plugins/table/js/table.js ... without needing to create a duplicate for the whole Products.TinyMCE skins codebase? Use z3c.jbot , and put a file in your jbot template directory called Products.TinyMCE.skins.tinymce.plugins.table.js.table.js You cannot override parts of a nested skins folder structure. If you want to customize

I'm trying to upgrade Plone 4.3.7 to Plone 5.0 via the portal_migration tool, and encounter the following error. Any thoughts? This is simple site (no add-ons), but it dates back to Plone 2.x, so there may be some old crud left that I've forgotten about. Output of UPGRADE tool: Dry run selected. Starting the migration from version: 4311 Ran upgrade step: Miscellaneous Role / permission map imported. Archetype tool imported. Step languagetool has an invalid import handler Step kupu-setup has an invalid import handler Ran upgrade step: Run to50alpha3 upgrade profile Ran upgrade step: Upgrade