Htmlarea trouble aka. iwantmywysiwig

[snorki]

Just installed the 6.3 release, everything looks fine and dandy but I can't seem to get the Htmlarea working as my editor for content etc....

I:
- switched "use Wysiwig" to true/false and back again
- made sure *.cgi would execute and file/dir-permissions are set as specified by Htmlarea docs

Could it be that I have to add something to a php file (¿config.php or header.php?) to make HTMLArea work as the editor?

if anybody could point me in the right direction I'd appreciate it

snorki

[edit: added ps about the Chinese]

ps. in "/admin" it looks as if language is set to "simplified chinese", but everything is in english as it should be (¿missing SELECTED?)

[Bewbs]

What web browser are you using, and what version is it?

[snorki]

on windows:
Windows IE 5.5
Windows IE 6.0

a separate install of the latest HTMLArea-3.0-rc1 works fine for the windows browsesr, which leads me to believe that I just have to hook it up to cmsmadesimple somehow ...

snorki

ps.

on mac
Safari (tested separately installed HTMLArea, not working at all)

[snorki]

IGNORE THIS NONSENSE

if I grep for htmlarea (excluding the /htmlarea/ dir) I get :

admin/editcontent.php: $htmlarea_flag = true;
admin/moduleinterface.php: $htmlarea_flag = "true";
admin/moduleinterface.php: $htmlarea_replaceall = true;
admin/addcontent.php: $htmlarea_flag = true;

, which all looks very "true" to me

, and also more lines in header.php :

admin/header.php: _editor_url = "/htmlarea/";

Is this leading underscore normal here, or is it perhaps used to disable htmlarea

admin/header.php: /htmlarea/htmlarea.js">

to me this looks like the line that adds the htmlarea-editor to a page

the other lines matched contain if()'s with the $htmlarea* variables

[jammo]

a separate install of the latest HTMLArea-3.0-rc1 works fine for the windows browsesr, which leads me to believe that I just have to hook it up to cmsmadesimple somehow ...

i dont think you really need to install anything to get this to function.

i had a problem of two immediately after installation and so i re-installed the DB schema of the CMS and it worked fine.

ya try that?

[snorki]

Thanks,

Excellent tip, reinstalled the initial DB and everything worked perfect.

Still don't know what I did wrong, but I'm very happy about it all now.

lovely cms+helpfull forum

[Ted]

I'd sure like to know why it's doing that. That's awefully weird. I'll look into it this weekend.

[jammo]

Thanks,

Excellent tip, reinstalled the initial DB and everything worked perfect.

Still don't know what I did wrong, but I'm very happy about it all now.

lovely cms+helpfull forum

glad we could help ya out.

that's what's so good bout a community like this.