Ensure user preference panel links adhere to navigation root; fixes https://dev.plone.org/ticket/11909
Merge remote-tracking branch 'origin/navrootfixes'
Allow password changes on INavigationRoot too
Allow password changes on INavigationRoot too
fix for non-ASCII passwords
fix for non-ASCII passwords
update the documentation of plone.app.users using collective.example.userdata doc
update documentation from collective.examples.user
Preparing release 1.1.4
Back to development: 1.1.5
Unified the site setup html structure

Change to unify the site setup html structure
=============================================
- Check for structure:

  #portal-column-content
    #content
      .setup-link
      .documentFirstHeading
      .documentDescription
      #content-core

- Check for body template- class

Related changes
---------------
Templates have also changed in:
  plone.app.contentrules
  plone.app.controlpanel
  plone.app.discussion
  plone.app.registry
  plone.app.users
  Products.CMFPlone

Styles have been updated in plonetheme.sunburst
tune ignores
add local buildout to run tests
specifiy missing test dependency
Merge branch '1.1.x'

add buildout to run tests
Fix email as login validation in personalize form (UserDataPanel).

This is for the case when email is used as login.  It checked that a
changed email address was valid as user id.  But the user id is never
changed here, only the login name.  We only need to
check if this address is not used by another user.

Also, we would get an error when changing an email address to for
example pete_o'hara+hello@example.org.  That one may look silly but is
a fine email adddress and should be allowed, also for login.  (Whether
this works everywhere is a different issue.)
Add generate_user_id method for registration.

No behavior is changed, but this gives possibilities for changing the
user id that is taken, especially when using email as login.

A few more checks added for email as login.

This refs issue http://dev.plone.org/ticket/11616
Use the generate_user_id also when not using email as login.

No change in behavior.

Note that the call to getInputValue is not needed as far as I see,
because the data dictionary is already filled after the call to
super(BaseRegistrationForm, self).validate(action, data)
Added two inline TODO notes.
Merge branch '1.1.x'