[Tickets #657] HTML editing broken if services/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 | Chuck Hagenbuch <chuck at horde.org>
 Summary    | HTML editing broken if services/editor not a subdirectory of Horde webroot
 Queue      | IMP
 Version    | 4.0-ALPHA
-State      | Assigned
+State      | Feedback
 Priority   | 1. Low
 Type       | Bug
-Owners     | Chuck Hagenbuch
+Owners     | Horde Developers
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2004-10-09 21:25) wrote:

> *) lib/Horde/Editor/htmlarea.php, lines 28 & 29, what's that about?

I have absolutely no idea what that's for. Jan, Marko?

> However, it is my perception due to the prior bug comment, that the
> /services/editor/htmlarea/ stuff cannot currently be moved from the
current
> horde root into the apache webroot (therefore accessible without invoking
> the CMS), because the rest of horde is not there, and there is no
> configuration directive to do so.

Aha. Correct. I think I have a clear answer on this one, though not a
solution (yet?). We could solve this by adding a "services" parameter to the
registry that could be set for Horde to override the default horde/services
location - similar to how it can be done for templates/, graphics/, etc.
Here's the problem with this, though - there's a whole bunch of code in
services/ that relies on the rest of Horde being where it thinks it is. So
we'd have to add a whole bunch of Horde-finding logic for that to work
correctly.

It doesn't really seem worth it to me, from the options I see (essentially
making services into its own "application"), but hopefully that at least
points you in the right direction if you're up to continuing to pursue a
patch.

> as well as inconsistencies(?) in the code
> about how the directory they are in is referenced (which make it
difficult
> for me to come up with a patch of my own). That's the problem.

Okay, you lost me again here. What inconsistencies are you talking about?