nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

correcting paths in tiny mce using form api

yanSi

Whenever a user selects an image located under /htdocs/images/..., I want to have the /htdocs part of the path stripped out. I know some developers here have advised others to not have a folder like htdocs in their workarea to avoid this, but my workarea is set up this way and I can't change it.

I tried to register an onItemChange event handler on the field with tinymce but it will not trigger the event handler when its content is changed. I then reregisterd the handler on a field that does not have tinymce and the handler function is invoked just fine.

Does anyone have any ideas on how to strip out /htdocs using formapi in another way?

I can correct the path in the tpl, but I want to avoid that since the image won't display properly in the tinymce editor.

Find more posts tagged with

Comments

gzevin

I am not sure that rich text editor fields are open to FormAPI - the reason is the Javascript code that is handling all the editing functions.

what is stopping you to massage the code at the .tpl level?

yanSi

I initially thought it would be too late at the tpl level since the images won't display properly in the tinymce editor, but I added one more remap in iw.cfg like this: /htdocs/=/htdocs/ and it will preivew fine in tinymce and after I stripe the htdocs in the tpl, this remap: /images/=/htodcs/images/ will allow the prieview to work properly.

gzevin

I initially thought it would be too late at the tpl level since the images won't display properly in the tinymce editor, but I added one more remap in iw.cfg like this: /htdocs/=/htdocs/ and it will preivew fine in tinymce and after I stripe the htdocs in the tpl, this remap: /images/=/htodcs/images/ will allow the prieview to work properly.

Ah, Ok, I didn't simply realise that you wanted to preview in the context of the editor as well.