[Tickets #657] HTML editing broken if scripts/editor not a subdirectory of Horde webroot

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=657
-----------------------------------------------------------------------
 Ticket     | 657
 Updated By | kyrian at ore.org
 Summary    | HTML editing broken if  scripts/editor not a subdirectory of Horde webroot
 Queue      | IMP
 Version    | 4.0-ALPHA
 State      | Feedback
 Priority   | 1. Low
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


kyrian at ore.org (2004-10-02 04:04) wrote:

It ties in with the other bug ID I mentioned, with regards to making Horde
tools integrate with Giapeto and other CMS-es.

In the implementation I'm working on, there are only two more "bugs" which
are stopping it from going live inside this CMS, both of which relate to
services/editor/htmlarea.js in the Horde system.

In this setup, they are outside the normal webroot, and hence are generating
a 404 error, which has the knock on effect of causing Javascript errors,
thusly (using Mozilla JavaScript console, edited for client
confidentiality):

Error: syntax error.
Source File: {snip}/services/editor/htmlarea/htmlarea.js

Error: HTMLArea is not defined
Source File: {snip}/services/javascript.php?file=htmlarea_lang.js&app=horde

Error: HTMLArea is not defined
Source File: {snip}/{snip}/mail/compose.php?uniq={token snipped}

This comes about (I think entirely, but maybe just in the first instance)
because htmlarea.js can't be loaded because the Horde tree is outside the
CMS, aside from the contents of the application graphics (which I do have
the option to put there), but because there's no config option to put the
scripts there, and I can't really put the javascript inside the horde tree
visible to the web either, it's a bit broken.

So I guess it's more a feature request to put a registry.php option in there
so we can put the scripts somewhere outside of the horde source tree.

I'd hack it myself, but I'm not sure where to start (although I think
hacking addScriptFile[?] in the Horde libs would be the place), and if I
did, it would probably disagree with the "horde way", and since Chuck has
asked if I can write a Horde-inside-a-CMS HOWTO I'd rather check with you
guys about how this would be implemented too.

K.