Editors not working after move to new host

After moving Swift Books from Plzhosts to Total Choice Hosting I noticed the HTLMArea was not working.

Knowing that HTMLArea is apparently defunct I decided to install FCKEditor.

Despite having FCKEditor selected in Configuration \ My Store I get just the raw text editor in the product pages, but in the Define Pages I get

The requested URL /editors/fckeditor/editor/fckeditor.html was not found on this server.

The file definitely exists in /home/MY_USER/public_html/editors/fckeditor/editor/fckeditor.html with permission 644

It looks as though it's a setup problem (permissions or a missing file). Any suggestions?

Added: Zen Cart version 1.3.7

I was able to run your FCK... so u did fix it?

Nope. No success so far.

I've logged out, cleared cache, logged back in - no luck.

I've tried in the above in FireFox and IE7.

I've tried adding FCKEditor to the site still on the old host, where it works in the Define Pages Editor and the original collect_info scripts (but not the one for 'product book' which I'll worry about later as mine is heavily customised so I've probably broken something I wasn't using at the time).

What I really need is to get either HTMLArea or FCKeditor working on the new host. I don't really care which but my preference is FCKEditor if HTMLArea is no longer supported.

Update.

I've installed a clean copy of 137 (no mods, add-ons, whatever), and added HTMLArea and FCKEditor.

They both work.

So, this problem is, probably, a corrupt or missing file - or another mod sticking it's oar in.

Since HTMLArea works on the old host - and I've recopied admin and editors from the old to the new I'm at a bit of a loss.

I suppose my next step is to compare file permissions although FileZilla, without any changes to settings, has been used throughout so ownership and permissions should be the same in the live and clean systems. :blink:

Any thoughts, anyone?

Fixed.

The problem was down to the way I'd edited the configure.php files. It seems the editors are very particular about what works for them and what doesn't.

If I'd waited for the DNS change to propagate instead of ploughing ahead, using the http://hostURL/username to get access, to prepare the system in advance the problem with the editors would probably not have happened. :censored:

Still, doing it this way means less downtime after the DNS propagation.