I'm not quite sure how to approach this bug and I'm wondering if anyone is getting this same error. I just can't seem to be able to use the apostrophe (') when using tinymce. If I don't use tinymce, I can enter the apostrophe with no problem, but if I then switch to "enable rich-text", even though the apostrophe shows up in the tinymce editor, it will not show when published or previewed. All I get is "&undefined;" where the apostrophe should be.
I've looked in tinymce/tinymce/docs/tinymce_api/overview-summary-TinyMCE_Cleanup.class.js.html and have seen no reference to '#039;'. So I'm wondering if anyone else is having this problem, and if so, how are you dealing with it?
Running:
drupal 4.7 beta 6
tinymce.module,v 1.90 2006/04/25
and tried it with the following versions of tinymce with no change:
tinymce_2_0_5_1.tgz
tinymce_2_0_4.tgz
tinymce_2_0_3.tgz
tinymce_2_0_2.tgz
Comments
Comment #1
creatorsdream commentedSo friggin' weird! I just launched Safari, yes safari! Tried the apostrophe thing and it worked! So is it because I was using Flock or Firefox? I don't think so. I think somewhere along the way to getting tinymce working, I used a bad version and the actual browser has kept the buggy javascript in cache. What's strange is even when I quit the browser, in this case Flock, and restarted it. It kept the buggy code.
So, I'm leaving this comment for anyone having this problem...
When updating tinymce to newer versions, make sure you clear your browsers cache before testing the changes. I know this is the case with Flock. Probably the same with all browsers using javascript. Quiting the app is not enough. You must clear the cache!
... how the heck do you developers remember all the if's and's or but's?
Oh geez... now that I cleared my cache I can't preview this message. So I'm submitting in the blind! ;-)
Comment #2
shouchen commentedI'm having the same problem in IE and Firefox... all single quotes are converted to '&undefined;' Any ideas?
Comment #3
shouchen commentedProblem solved... upgraded to TinyMCE 2.0.6.1 and cleared browser cache and now it is working as expected.