[horde] trean: 404 when deleting or saving after edit
Jan Niggemann
jn at hz6.de
Sat Dec 13 15:27:22 UTC 2014
Am 11.12.2014 10:50, schrieb Jan Niggemann:
> Follow-Up: Debugging the request by adding Horde::debug($request,
> $filename); to rampage.php I found that the request is faulty:
>
> 2014-12-11T09:35:19+01:00 DEBUG: Variable information:
> object(Horde_Controller_Request_Http)#133 (2) {
> ["_path":protected]=>
> string(18) "/horde/rampage.php"
> ["_headers":protected]=>
> NULL
> }
>
> Backtrace:
> 1. Horde::debug() /var/www/virtual/htjn/html/horde/rampage.php:58
>
> Of course the request can't be correctly mapped to the appropriate
> controller...
> On a working installation the request is like this:
>
> 2014-12-11T00:32:42-08:00 DEBUG: Variable information:
> object(Horde_Controller_Request_Http)#159 (2) {
> ["_path":protected]=>
> string(13) "/trean/b/save"
> ["_headers":protected]=>
> NULL
> }
>
> Backtrace:
> 1. Horde::debug() /opt/horde/rampage.php:59
>
> Any ideas as to what may cause this?
Do I need any additional config setting to get this straight? I'd like
to debug this further but I'm unsure where to start. As far as I
understand, the request for trean/b/save is redirected to rampage.php
because of the htaccess mod_rewrite rule.
$injector->getInstance('Horde_Controller_Request'); instantiates the
subclass Horde_Controller_Request_Http and
Horde/Controller/Request/Http.php does the further processing...
I can also provide ssh access if one of the devs is interested...
Regards
jan
More information about the horde
mailing list