Using TinyMCE leads to entries in Apache error log

[ken]

When I send a CiviMail, the following two errors appear in the Apache error log ...

[Sun Jun 21 16:27:47 2009] [error] [client 121.44.113.188] File does not exist: .../packages/tinymce/jscripts/tiny_mce/plugins/imagemanager, referer: ...
[Sun Jun 21 16:27:47 2009] [error] [client 121.44.113.188] File does not exist: .../packages/tinymce/jscripts/tiny_mce/plugins/filemanager, referer: ...

I fixed this by applying the following patch to remove the references to 'imagemanager' and 'filemanager' ...

Code: [Select]

--- /data/Download/CiviCRM/civicrm-2.2.0-joomla-alt/admin/civicrm/packages/HTML/QuickForm/tinymce.php 2009-06-19 12:53:52.000000000 +1000
+++ tinymce.php 2009-06-21 18:35:46.000000000 +1000
@@ -146,7 +146,7 @@
     mode : "textareas",
     theme : "advanced",
     editor_selector : "form-TinyMCE",
-    plugins : "safari,spellchecker,layer,table,advhr,advimage,advlink,emotions,iespell,inlinepopups,insertdatetime,preview,media,searchreplace,print,contextmenu,paste,directionality,fullscreen,noneditable,visualchars,nonbreaking,xhtmlxtras,template,pagebreak,imagemanager,filemanager",
+    plugins : "safari,spellchecker,layer,table,advhr,advimage,advlink,emotions,iespell,inlinepopups,insertdatetime,preview,media,searchreplace,print,contextmenu,paste,directionality,fullscreen,noneditable,visualchars,nonbreaking,xhtmlxtras,template,pagebreak",
     theme_advanced_buttons1 : "bold,italic,underline,strikethrough,|,justifyleft,justifycenter,justifyright,justifyfull,|,formatselect,fontselect,fontsizeselect",
     theme_advanced_buttons2_add : "separator,insertdate,inserttime,preview,separator,forecolor,backcolor",
     theme_advanced_buttons2_add_before: "cut,copy,paste,pastetext,pasteword,separator,search,replace,separator",


[Chris Burgess]

http://issues.civicrm.org/jira/browse/CRM-4693

[ken]

Thanks!

(Greetings from across the Tasman, bro!)

[Chris Burgess]

No worries Ken! Hey, that patch has been merged into CiviCRM now, so will probably be available on the next release.

We did a big site upgrade just recently, and I've been stalking the error logs looking for trouble. This one was ringing a bell that didn't need to be rung, but I'd been too lazy to identify the fix until I saw your post - so thank you!