Plone 6.0.0a2 tinymce pattern, in '/en' the visualblocks plugin cannot load the css because of a wrong url

[yurj]

I've found a bug with multilingual (or '/en' folder) and tinymce. If you enable the visual blocks (view -> Show Blocks), in an english site the tinymce-visualblocks css url miss the ++plone++static part :http://<mysite>/++plone++static/components/tinymce-builded/js/tinymce/plugins/visualblocks/css/visualblocks.css vs http://<mysite>/en//plugins/visualblocks/css/visualblocks.css (the // misses ++plone++static plus all the path to the plugin).

The bug happen if the folder is called, for example, 'en' and language negotiation (folder and browser) is enabled in the control panel, and the language 'en' is added to available languages. If I call the folder with a different name, or with a non installed language, or if I disable the language negotiation, then the css is loaded correctly, the css url in the head is http://mysite/++plone++static/components/tinymce-builded/js/tinymce/plugins/visualblocks/css/visualblocks.css

[yurj]

plone/plone.base#18 maybe has anything to do with it? I would close this if it is fixed in current plone 6 but it seems still there: https://6-classic.demo.plone.org/en/demo/a-page/edit

[Rudd-O]

I would like to help you fix this but I need some guidance. What's the visualblocks plugin and how do I enable it on my TinyMCE?

[Rudd-O]

Actually, the tinymce-builded folder is gone from the buildout (as of Plone 6 beta). Not sure how. Perhaps this matter is not at all related to plone/plone.base#18 .

[thet]

@yurj @Rudd-O yes, the tinymce-builded folder as well as the components folder are gone.
the URL‌ cannot work with current Plone 6 this way.

the only occurrence for tinymce-builded I found in my Plone 6 coredev buildout omelette tree is this:

thet@then:/home/_thet/data/dev/sprints/plone6ui/REPOS/buildout.coredev/parts/packages$ rg tinymce-builded
Products/CMFPlone/patterns/settings.py
160:            "loadingBaseUrl": "{}/++plone++static/components/tinymce-builded/"

But then, this is also the only occurrence of loadingBaseUrl.

Any more information how to reproduce this problem or where the loadingBaseUrl or the tinymce-builded directory might be used?

[Rudd-O]

That needs fixin', I just don't know what to include there.