Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Can you check the version of your Chrome?
I have no problems with my Google Chrome version 7.0.517.44 and editor to reply to your post but I think Joseph R. posted a similar question some time ago to tracker.
Check also that under the forum post content (drop down box) you have HTML format selected. Or you could try to use mouse right click - Inspect element to check if some custom script (or some Chrome plugin) might break code on your Chrome.

Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Hi, Mauno
My version is exactly the same (after all, Chrome is used to silently update itself). And HTML is the only format option available for the forum post for me, so I simply can't choose anything else.
What's make it more interesting is the fact, that the problem isn't reproducible on qa.moodle.net (checked right now again, TinyMCE works all right there on the same Chrome, just another tab), but consistently exists on moodle.org. This make me think it is may be somehow related to the special moodle.org theme or something similar. So I reported it as MDLSITE bug instead of MDL one.
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Well, if this is browser configuration/plugin issue than why
1. TinyMCE is absent consistently on any computer I use to access moodle.org
2. TinyMCE is present consistently on qa.moodle.net on the same browser, even in the same session
But this isn't account-related issue either, since there are TinyMCE for me on moodle.org when using IE to access it.
This thing is really weird!
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Doesn't Chrome have a developer tool like Firbug for firefox? It would be worth using that to check that the page is trying to load TinyMCE. It would also be worth checking to make sure there are no JavaScript errors.
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Ooops. Thanks, Tim. You are correct. There is error loading language strings: Failed to load resource /lib/editor/tinymce/extra/strings.php?elanguage=ruðeme=advanced
All still works OK in qa.moodle.net ( are language packs there and on moodle.org synchronised?), even when I set the language to Russian. And there is no such errors there (strange).
I'll convert the issue to MDL-one, but we have to decide what we want to do: just tell russian language pack mainainers to update it (I already written them on their forum), or additionally create an issue for Moodle to behave better when language strings are absent, not confusing users with such strange disappearance.
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
This is to confirm Oleg's finding. In Moodle 2.0, TinyMCE does not work in the Chrome browser if language is set to any other than English.
Error: Failed to load resource: /lib/editor/tinymce/extra/strings.php?elanguage=frðeme=advanced
When I first reported the bug, I was actually trying to post in a forum on the Francophone forums.
Joseph
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Helen - no, problem remains. Judging by Joseph's remark this may be not problem of individual language pack. But then why it works on qa.moodle.net?!
Joseph - if you reported this bug on the tracker, please write it's number (i.e. MDL-....) or link MDLSITE-1136 with it.
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
I reported the bug in MDLSITE-1136
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Joseph - did you find this bug on another site than moodle.org? If it moodle-wide, I'll convert it into MDL-xx issue. But for now I coudn;t reproduceit on qa.moodle.net.
Judging by Chrome reports there is no query to load something from /lib/editor/extra/strings.php at al on the qa.moodle.net. Which is strange.
Helen, could you check that code on qa.moodle.net is actually latest and language packs too, I see on qa.moodle.net "russian {$a} in forum RSS string" problem that you know of and it is solved on moodle.org . Something may be amiss with updating qa.moodle.net (migration to git may have a part there). Also please add people who done TinyMCE integration as a watchers to the CONTRIB-1136 and alert them - they certainly should know more about /lib/editor/extra/strings.php query
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
My Chrome renders editor here (moodle.org) with English, English-US and Latin and on my test site with other languages too so I suppose the problem comes from some non-latin characters or wrong encoding of those "non-latin-character" language files (here) - I added some comments to MDLSITE-1136
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
The most strange thing is that qa.moodle.net doesn't make query for /lib/extra/strings.php, which is done on the moodle.org and failed.
Why that difference? Is moodle.org updated long ago and doesn't go in time with new development, which may have fixed this bug?
Helen - how long moodle.org itself was updated?
Re: Am I the only one who get plain text box instead of TinyMCE on moodle.org?
Hi, I have had a similar issue and managed to hack a workaround. We are running a Windows Server 2008 (64 bit) R2 and IIS 7.5 and Moodle 2.0.1. Languages is en-au. We have the empty TinyMCE editor and this seems independent of browser/machine viewed from. The error can be traced back to lib/editor/tinymce/extra/strings.php?elanguage=enðeme=advanced. If I try to browse direct in IE7 I get a 'download or open' dialogue which will not actually download or save any content. In Chrome it displays the content but never finishes downloading.
In any browser, if I wait long wnough the tinyMCE eventually displays. There seems to be an issue in strings.php file line 58 which reads:
@header('Content-length: '.strlen($output));
Commenting this line out means the script completes succecssfully and the editor renders properly. The issue seems to be in the strlen($output) code as if I replace that with a fixed arbitrary number the page will render properly.
I hope this helps in your tracking down of the issue.