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

Contentchooser calls jsonbytype on wrong url for portal root #733

Closed
mauritsvanrees opened this issue Jun 21, 2017 · 1 comment
Closed
Labels

Comments

@mauritsvanrees
Copy link
Member

Tested on current master branch (and it seems to have been there at least since 2012).
Steps:

  • Create a cover
  • Go to the compose page
  • Click on 'Add content' (the contentchooser)
  • Click on 'Content tree'
  • Navigate to a folder, for example news. This uses javascript to call http://127.0.0.1:8080/Plone/news/@@jsonbytype
  • In the breadcrumbs of the content tree, click on the portal root. This uses javascript to call /Plone/@@jsonbytype

The last step works fine locally, but fails with a 404 on a live site. This is because the resulting full url is something like http://my.domain/Plone/@@jsonbytype, and http://my.domain usually directly points to the Plone site, and this does not have a folder Plone inside it.

This only happens for the root, all other folders in the breadcrumbs use the full url, but the root uses the physical path.
Seems easy to fix by using the full url for the root as well. I will make a pull request.

@idgserpro
Copy link
Member

Solved in #734.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants