URL translation to extension URL w/user parameters?

Tuesday 27 February 2007 10:39:19 am

Running eZ 3.6 and trying to do the following. I have an extension at /foo and can
call it with user parameters, e.g., /foo/(bar)/foobar.

extension/foo/module/foo/module.php:

<?php
$Module = array('name' => 'foo');

$ViewList = array();

$ViewList[""] = array
    (
    "script" => "foo.php",
    "params" => array()
    );
?>

I would like to setup a URL translation to redirect /foobar to /foo/(bar)/foobar. I have tried setting up a "New system URL forwarding" and a "New virtual URL forwarding with wildcard" (with & without "Redirecting URL" checked). If I setup /foobar to redirect to /foo, that works perfectly fine. However, if I try to setup /foobar to redirect to /foo/(bar)/foobar, I get this error:

Undefined view: foo::(bar)

Tracing through the eZ kernel code, it appears that the whole process is treating (bar) as a view inside the contact module rather than realizing that I am calling the "empty" view with user parameters.

Am I not specifying the destination URL correctly? Or is this something that requires hacking the eZ kernel to handle?

Wednesday 28 February 2007 4:27:01 am

Yes, both /foo and /foo/(bar)/foobar work if I enter them directly in my browser. The page renders as I would expect. I have found a partial solution at the moment; I first have to create the URL translation as /foo/(bar)/foobar. Then, I have to edit it to read /foo//(bar)/foobar. For some reason, creating it as /foo//(bar)/foobar does not work; it will only work after you hit the "apply changes" button after it has already been created. However, it does not seem to be passing the parameters along to the extension.

As for mod_rewrite, sure, I could do it that way, but it would be counterproductive for my purposes. I want people skilled enough to use eZ but not nearly skilled enough to mess around with Apache configuration to be able to see and manage URL translations in one place.