collective/collective.geo.geographer — pull request #3 by jone (2013-03-27 12:49:02+00:00)
Title: Loading zope.security ZCML causes wrong permissions to appear

**No fix included, only a failing test.**

---

**Symptom**
It seems that collective.geo.geographer somehow causes the zope.security permissions to be registered wrong: somehow the permission in manage_access is registered with the translation id (e.g. view-permission) instead of the translation default (View).

![manage_access](https://f.cloud.github.com/assets/7469/308055/50ecbc46-96db-11e2-9b18-b449638c15b4.png)

The permissions marked in the screenshot do not appear when installing only Plone, but they appear when installing collective.geo.geographer (Plone-4.3rc1).

**Cause**
The permissions are defined in [zope.security permissions.zcml](https://github.com/zopefoundation/zope.security/blob/3.8.3/src/zope/security/permissions.zcml#L19) as translatable (msgid is "view-permission", default is "View").

I think the zope.security permissions.zcml is not loaded by Plone by default, because the `View` permission is also defined in [AccessControl's permissions.zcml](https://github.com/zopefoundation/AccessControl/blob/3.0.6/src/AccessControl/permissions.zcml#L76), which is used by Plone.

**Problem**
So the `zope.security` permissions are something new, I think, which is not used by Plone at all and should therefore not be loaded.
collective.geo.grapher loads zope.security in [the configure.zcml](https://github.com/collective/collective.geo.geographer/blob/master/collective/geo/geographer/configure.zcml#L10), because it uses `zope.View` (not `zope2.View`) and `zope.ManageContent`).

**Fix?**

I think collective.geo.geographer should use load the `AccessControl` permissions and use `zope2.View` (AccessControl) instead of `zope.View` (zope.security).
But I'm not sure what to do with `zope.ManageContent`, with which `zope2.*` or Plone permission should it be replaced?

I'll happily change it as soon as I know which permission to use and update the pull request.
The pull request currently only contains a failing test illustrating the problem.