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
@@sharing is broken on Page objects in Plone 4.3.12 and 4.3.14 #2053
Comments
@dpc22 the problem with changelog happen that the code review take too much time to merge the pull request, and one release was done in the middle time. Of course I didn't realize it when I rebase the branch.. my mistake. This change was merged at version |
Did some changes thinking better on how URL is formed. New jenkins job http://jenkins.plone.org/job/pull-request-4.3/14/console |
@hvelarde green \o/ |
This one can be closed after the merge |
For anyone trying to solve this problem, the solution is to upgrade to Plone 4.3.15. I found the problem persisted with the same exception shown at plone/plone.app.workflow#14 after the upgrade, but what had happened was the Throwing an exception like that on an invalid authenticator token is probably something else that needs fixing, mind you. |
BUG/PROBLEM REPORT (OR OTHER COMMON ISSUE)
What I did:
What I expect to happen:
List of potential users as search results
What actually happened:
Large python back trace because the search form AJAX accessed:
http://localhost:8080/Plone2/test/@@sharing/@@updateSharingInfo
rather than the following used by Plone 4.3.11:
http://localhost:8080/Plone2/test/@@updateSharingInfo
The root cause appears to be:
https://pypi.python.org/pypi/plone.app.layout/2.3.17
2.3.15 (2016-06-28)
Fixes:
Fix base tag differs from actual URL (fixes 86). [rodfersou]
which was actually made after plone.app.layout 2.3.15 was released, (December 2016): that comment is placed incorrectly in the README file. I'm happy to make a bug report there as well.
What version of Plone/ Addons I am using:
Vanilla Plone 4.3.14, which uses plone.app.layout 2.3.17. So does Plone 4.3.12, and I see exactly the same problem there.
(NB: Pinning plone.app.layout 2.3.15 in Plone 4.3.14 resolves the problem).
Update: appears to be the same issue discussed in: #2051
The text was updated successfully, but these errors were encountered: