I’ll try and sequence the problems I’ve been having. NOTE: I have used both LG TinyMCE editor and the first party one. I have the same problem with both.

First of all, when I actually configure the Extension through the manager, simply using a relative path—it will not work. For example, in the field “URL of Tiny MCE Script” usually, a relative path: “/scripts/tinymce/jscripts/tiny_mce/tiny_mce.js” will suffice. But for me, on my entry pages, the custom WYSIWYG fields simply don’t load TinyMCE.

When I changed the path in the Extension Manager to use the absolute path:“http://www.ecologyaction.ca/asrts/scripts/tinymce/jscripts/tiny_mce/tiny_mce.js” the editor shows up on my entry pages, however the image paths all link to the system folder automatically, and there’s nothing I can do to change it. Also, the use of “{filedir_1}myImage.jpg” won’t work—the image is broken on the site.

Therefore, I’ve set TinyMCE to relative_path = true, and have been linking images relatively, but this will be a nightmare for the client to update. The images will all break every time they edit a post, and then they will have to insert paths depending on which page they’re on eg: “../../images/uploads/myImage”

Is this a hosting issues? I have used the TinyMCE extension many times and I’ve never had this problem. Thanks.

Also, a side note: PLEASE EE DEVELOPERS, MAKE THE NEXT VERSION HAVE WYSIWYG BUILT IN FROM THE INSTALL!!