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

Internal url widget (from TinyMCE link) has current path at a page, instead of its container #2664

Closed
ewohnlich opened this issue Dec 12, 2018 · 1 comment

Comments

@ewohnlich
Copy link
Contributor

What I did:

On the front page of a new Plone site, create a link in the wysiwyg and use the Internal option

What I expect to happen:

I expect the "Current path" to start from the page's container.

What actually happened:

The base path starts from the front page. This effectively means that none of my searches will work until I change the "current path"

I believe the problem is actually in plone.app.widget.utils. The get_relateditems_options function there does attempt to check if the current base path context is folderish, but I believe it does so insufficiently.

(Pdb) base_path_context
<Document at /ootb/front-page used for /ootb/front-page>
(Pdb) aq_parent(base_path_context)
<Document at /ootb/front-page>

So obviously in this case aq_parent doesn't actually yield the container.

What version of Plone/ Addons I am using:

Plone 5.1.4

@jensens
Copy link
Sponsor Member

jensens commented Mar 12, 2023

I close the issue, because it addresses a Plone version that is no longer supported.
If you think this is wrong please reopen the issue and assign a matching milestone.

@jensens jensens closed this as completed Mar 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants