Have not had much experience with tinyMCE however for JCE I have found it works best on linux hosting (if you are on basic, this is what you have), have to have all folders set to permissions of 755 and file set to 644.

You will also want to make sure if using JCE to have php5 enabled from within cpanel.   While it does work on php4, I have found works best on php5

I have noticed however that for some reason, joomla causes the files to change ownership or cause files to change to incorrect permissions, so you will want to check these via an FTP program such as filezilla.

TInyMCE is a WYSIWYG editor that comes with Joomla 1.5 by default (not sure about earlier versions) , and usually in most cases should work "out of the box"

If you are using Joomla 1.5, I recommend trying the step located here:  http://www.fandangle.com.au/joomla-tutorials/131-tinymce-doesnt-work-in-joomla-1-5-12.html

Dear Troy L and MrPhil.

Excuse me if I have not responded, but for a few days I have been sick with a fever. Then, when I recovered, I have followed the trend of tickets Lunarpages staff, and I have temporarily solved the problem by restoring the site. Then, the old problem was partially resolved. However, I have treasured your advice and went to read the link.

Now the problem is another! Following an operation to restore my site, have appeared strange characters, like ¨ Ã, Â Ã, Ã ¬ Ã ¨, Ã ¹, Which are in place of accented vowels.
The restore operation is this: in fact, the root public_html public_html_old has been renamed, and then it was done restoring the public_html folder, perhaps the cause is due to the fact that the servers have generally editor coarse but very fast ... but that's not what interests me! I would just like to know if there is a program or some technique that can convert those strange characters in the original character. Someone help me?

Cicerone80

When you see accented letters appear as pairs of odd letters, what's usually happening is that your database and/or application is creating text encoded in UTF-8, but the page is marked as Latin-1 (ISO-8859-1). In UTF-8, European language accented characters come out as pairs of bytes, which happen to be various Latin-1 accented characters if that's what your page is displaying as.

Check your database and Joomla settings that they are consistent (probably as UTF-8), and that Joomla is configured to display in the same encoding (UTF-8). You can View > Page source in your browser and look at the "Content-Type" <meta> tag up near the top. Once they're all singing from the same book, you should see the correct accented characters.

This is material (text) that you or members put into the database, rather than hard-coded Joomla language files? Does it happen with new material, or just with old (from before the restore)? If it happens to new material, I'm stumped -- you say the database, Joomla settings, and page display are all UTF-8? If new material works OK, but old material gets displayed as pairs of letters (for accented characters), all I can think of is that something got corrupted during the backup or restore.

Go into phpMyAdmin and "browse" your Joomla database. Do a View > Page source to confirm that the page is displaying in UTF-8, rather than Latin-1/ISO-8859-1. Do the entries look OK there, but are corrupted when displayed on the Joomla page? If they are bad, even in the database, then it sounds like whoever did the backup and restore did some kind of "conversion" in the process, to make the pairs of UTF-8 bytes (for accented characters) be treated as Latin-1, and then they were converted to equivalent pairs of UTF-8 characters. What was originally a two-byte UTF-8 accented character became two one-byte Latin-1 accented characters, became two two-byte UTF-8 accented characters?

I think whoever did the backup and restore on your site has some investigating to do, to see where the process went off the tracks, and to see what might be done to correct it. If you now have pairs of "wrong" UTF-8 characters in your database, worst case you'll have to manually edit all the text fields in the database to replace them with single UTF-8 characters. Let's hope it's not that bad, and can be fixed without manual editing of everything.