- September 13, 2006 at 2:45 pm #10589
Is it because of my extensions?
- March 17, 2007 at 2:02 am #11135
Hi, I have the problem that IE could show the editor but now the cms login does not work anymore (in IE) in all other browser I tried (Opera, Firefox) the login and everything works, but in Opera I simply get a text area for the FCKEditor and in Firefox I simply get nothing. After just doing what you wrote above I started thinking that this is absolute crap. Renaming a folder which is accessed by try-catch-create if renamed or deleted simply lets you miss all your settings and cache information not more. So what should that change in the problem that is not correctly interpreted by the browsers?
- March 17, 2007 at 10:54 am #11144
The problem is not that js is being incorrectly interpreted in Firefox, it’s that various extensions and add-ons interfere with FCK. Basically what you need is a fresh install of Firefox. However, simply re-installing the executable will not get you a fresh profile. The above method does this, while backing up your old profile, and lets you start from scratch.
- September 15, 2006 at 7:26 pm #10591
Firefox is a wonderful browser, streamlined, fast, efficient, and secure. But it can turn into a slow, inefficient resource hog when too many poorly designed extensions and addons are installed. In this case, the problem is that the TinyMCE or FCKEditors (WYSIWYG = What You See Is What You Get) editors would load fine in IE, Mozilla, and other browsers, but not in Firefox. At first it appeared that this issue was specific to the FCK and TinyMCE drupal modules, but then it turned out that not even the demo’s on the FCKEditor and TinyMCE pages would work. In other words – FCKEditor and TinyMCE work fine in recent versions of all the major browsers. The problem below is a result of a conflict with other extensions:
Error: navigator.appVersion.match(/MSIE (.\..)/) has no properties Source File: //www..com/modules/fckeditor/fckeditor/fckeditor.js Line: 144
The Solution – Fresh Firefox Profile
The solution involves a Fresh install of Firefox, and in some cases a new profile. If a re-install of the Firefox executable (into a new folder) does not solve your problem, you may need to reinstall your profile. First back it up by renaming the “Firefox” folder (instead of deleting it) to “Firefox-bak” in the following folder:
C:\Documents and Settings\USERNAME\Application Data\Mozilla
This is for Windows systems – replace USERNAME with your username. Now when you reinstall Firefox a new profile will be generated and you should no longer experience the above error. Please post any comments or questions below.
You must be logged in to reply to this topic.