Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zope.app.dublincore.view permission renamed to zope.dublincore.view #8

Closed
prsephton opened this issue Aug 22, 2017 · 2 comments · Fixed by #20
Closed

zope.app.dublincore.view permission renamed to zope.dublincore.view #8

prsephton opened this issue Aug 22, 2017 · 2 comments · Fixed by #20
Labels

Comments

@prsephton
Copy link

The zope.dublincore-4.1.1-py2.7.egg package underwent changes on 2010-08-19 where zope.app.dublincore.* shims were removed and replaced with zope.dublincore.**

Some dependency has clearly changed to subsequently use the new zope.dublincore release.

The default etc/site.zcml.in still contains a reference to zope.app.dublincore.view

Simply changing that to zope.dublincore.view did not work. (how come?). The server would only run after commenting that permission grant line out completely.

@icemac icemac changed the title zope.app.dublincore.view renamed to zope.dublincore.view zope.app.dublincore.view permission renamed to zope.dublincore.view Sep 5, 2017
@icemac icemac added the bug label Sep 5, 2017
@icemac
Copy link
Member

icemac commented Sep 5, 2017

@prsephton Do you feel comfortable to write a PR for this issue?

@prsephton
Copy link
Author

I think simply removing (commenting out) the permission will have other repurcussions. The right way to fix it would be to add the correct permission (zope.dublincore.view) to the zcml, but I am not smart enough to know why that (just replacing zope.app.dublincore.view with zope.dublincore.view) breaks.

That's why I provided the information, but made no attempt at a PR - for fear of doing the wrong thing.

I don't mind going digging myself if no one else has an instant insight.

@icemac icemac mentioned this issue Dec 21, 2023
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants