Link tool in TinyMCE in Plone 4.2/4.3 no longer working/depending on Proxy vs. non-proxy

Plone Support Add-on Development
1

Situation: a long-running Plone 4.2 site does no longer display the link tool of TinyMCE . The console show some 404 errors which are possibly unrelated. In general the popup link tool looks pretty weird. This happens when we access the site over Nginx -> Varnish -> HAProxy

out.png1709×992 183 KB

Opening the same site by accessing one app-server through a SSH tunel works (the link tool displays without errors) but: there is an error in plone.project.js and the overall functionality of the link tool is broken (likely related to the JS error in plone.project).

out2.png1709×992 167 KB

Anyone seen this?

2

we experienced that issue in many sites running Plone 4.2 in the past and I think it had to do something with missing upgrade steps, with the <base> tag in the pages, or with both issues.

check if the tiny_mce_javascript_variables.js script is being loaded in the resource registries; if not, add it like this

<?xml version="1.0"?>
<object name="portal_javascripts">
  <javascript id="tiny_mce_javascript_variables.js"
    insert-after="plone_javascript_variables.js"
    authenticated="True"
    bundle="default"
    cacheable="True"
    compression="none"
    conditionalcomment=""
    cookable="True"
    enabled="True"
    expression=""
    inline="False"
    />
</object>
3

Nope. This would not explain the different behavior of the same app server accessed through proxy or without proxy. And there is tiny_mce_javascript_variables.js file.?

-aj

4

if you're experiencing a different behavior using a proxy then you're being bitten by the <base> tag issue I mentioned above.

@rodfersou do you remember how we fixed that?

5

We were bitten again about it here: https://github.com/plone/archetypes.querywidget/pull/13/files

I'm not sure now why the problem come.. but we need to remove the /edit in the end of the base url here

6

that is related with this issue, remember?

probably the oldest bug in Plone still open (already fixed in Plone 5).