-- Ralf Eggert r.egg...@travello.de wrote
(on Saturday, 15 September 2012, 11:17 AM +0200):
to clarify my last message. The ACL check does work for unknown actions.
It just doesn't work correctly for any unknown controllers.
Currently I am thinking about using the controller loader to try to
Hi Matthew,
thanks for this new idea.
I just had another idea. Use an initializer.
I tried to build this but noticed that the initializer is only processed
for existing controllers. But the acl check problems I have have to do
with not existing controllers.
Currently I used this listener
Hi again,
to clarify my last message. The ACL check does work for unknown actions.
It just doesn't work correctly for any unknown controllers.
Currently I am thinking about using the controller loader to try to load
the controller and only do the ACL check when the controller can be
loaded. But
Hi Ralph,
thanks for your reply. I am also working on the better solution you
suggested but with that solution I got stuck. This is my listener (a
little shortened):
class RouteListener implements ListenerAggregateInterface
{
You effectively have 2 options:
First, and I am sure least favorite option from a framework
perspective: Put your acl check in an onDispatch() method inside of the
routed controller (that means at least a controller was dispatched).
Inside of this method, you could do whatever check you
Hi Marc,
Marc Tempelmeier schrieb am 11.09.2012 08:56:
in ZF1 I solved this with checking if the route is dispatchable and if not
screw the whole ACL check. I didn´t check if there is something like that in
ZF2 though.
I did not find any isDispatchable method yet though I think it is not
Hi,
I wrote a listener that checks the ACL for the current user to forward
to a forbidden page when the rights are insufficient. This works
perfectly but now I have a problem.
If the routing matches a route but controller or action does not exist
these 404 errors are not shown. This is due to
