Summary | horde directory name (applicationurl) |
Queue | Horde Base |
Queue Version | 3.0.5 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | nick-horde (at) glued2 (dot) net |
Created | 08/25/2005 (7277 days ago) |
Due | |
Updated | 08/25/2005 (7277 days ago) |
Assigned | |
Resolved | 08/25/2005 (7277 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
surprise that horde couldn't correctly figure this out on it's own and
that it had actually got it wrong - and what was clear was that it was
looking for the word horde (and the first occurance). I did find the
offending code the strstr statement in the registry strstr being the
first occurance of the word horde (or first occurance of the first
value in the array). I guess checking it the otherway around (for the
last occurance) doesn't make sense as that would trip up with any
folders called horde under the document root. I did wonder about
checking the number of occurances, and just using the /horde fall back
if there was more than one, or doing a comparison with the document
root, or checking that a directory exists once the result is checked -
but I guess it all adds overhead.
Many Thanks
Nick.
State ⇒ Not A Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ horde directory name (applicationurl)
Queue ⇒ Horde Base
horde.domain.com
with the document root being:
/home/vhosts/sites/horde/docs
horde was then in /home/vhosts/sites/horde/docs/horde
I fired up horde, but the opening frame tried to open
http://horde.domain.com/horde/docs/horde/login.php
(the correct URL would have been
http://horde.domain.com/horde/login.php - manually entering the URL's
worked just fine...
The Horde::applicationurl is wrong...