collective.pluggablelogin 1.2.1

Configuration

Go to the Addons control panel and activate “Pluggable Login Page.”

Now if you go to /login while logged in as a Manager, you’ll see a “Manage portlets” link which you can use to manage the available login portlets. By default, the standard login portlet and a registration form portlet are enabled (the latter is only shown if self registration is enabled for the site).

As well as manual assignment via the web interface, the pluggable login page can also be assigned portlets via GenericSetup, in the same way as Plone’s other portlet managers can. For example, to register a custom porlet on the pluggable login page, use this an example within portlets.xml inside a GenericSetup profile:

<portlets
    xmlns:i18n="http://xml.zope.org/namespaces/i18n"
    i18n:domain="plone">
 <assignment
    name="navigation"
    category="context"
    key="/"
    manager="collective.pluggablelogin"
    type="my.product.portlets.CustomLoginPortlet"
    insert-before="*"
    visible="True">
    <property name="title">string:Login portlet title</property>
    <property name="description">string:Example property</property>
 </assignment>
</portlets>

1.2.1 (2015-05-20)

• Avoid double form tags and invalid markup on the registration portlet with new-style z3cforms. [davidjb]

1.2 (2015-03-23)

• Allow the registration portlet to work with both new (z3cform) and old-style (zope.formlib) register forms. [davidjb]

1.1 (2014-01-30)

• Add id to the login-portlets div, ensuring the element can be selected on the page. [davidjb]

• Improve styles for login page, normalising with logged out page. [davidjb]

• Add logged out page templates to display pluggable login. [davidjb]

• Improve styles and formatting for login page. [davidjb]

• Fix issue with empty <div> generated on login page after trailing </html> end tag. [davidjb]

1.0 (2012-05-10)

• Initial implementation [davisagli]