ansaurus

Question

cakephp routing for cushycms preview link

Answer 1

A:

First, by virtue of having Cake in a subdirectory (/cake125), I think you may need to connect the /cake125/:controller/:action, rather than how you have it. Not 100%, though; Cake might be robust enough to handle that use case. If you have weird errors, I'd check that.

On with my answer: I think you are somewhat misunderstanding how the Router class works. You connect URLs, not relative filesystem paths, using Router::connect. By default (which you may have erased, but it's pretty simple to fix), Cake will route requests to /pages/* to the PagesController::display() function, passing it one argument (the action listed in the http request).

So, to have the pages controller map /pages/one to the app/views/pages/one.ctp element, simply make sure that the following (default, i.e. Cake normally has this setup) line is in the routes config (and make sure that lines above it do not match that pattern):

Router::connect( '/pages/:action', array( 'controller' => 'pages', 'action' => 'display', :action);

This should ensure that PagesController::display( $action ) is invoked during the request, which is (I think) what you're after.

If your CMS generates preview links that you want to correctly re-route, I'd suggest adding a new route. E.g., if your CMS generates links like http://somesite.com/cms/preview/newly_edited_file, you can route it like this:

Router::connect( '/cms/preview/:action', array( 'controller' => 'pages', 'action' => 'display', :action );

For your second question: have a default rule in your routes (make it the last rule, and have it match *). It will then be configured to route all not found requests to your controller/action pair as requested. Try this:

Router::connect( '/:action', array( 'controller' => 'pages', 'action' => 'display', :action );

Major caveat this will break your existing routes. You will need to manually add an entry for each of your existing controllers (Router::connect( '/users/:action', ...etc...). If you google around you can find some clever solutions, such as having that list generated at runtime for you. But you will need to address "normal" routing, once you've added that catch-all (and make sure your catch-all is at the end of the routing file).

Also, if you want to parse URLs like /test.html, simply add a call to Router::parseExtensions(...) so that Cake will register .html as an extension for it to parse. Check the manual on that function for more info.

Travis Leleu 2010-01-19 17:14:33

You do not need to change your Routes if you have Cake in a subdirectory. All Routes are relative to the working directory, you only need to concern yourself with the parts "internal" to the app. Secondly, `..., 'action' => 'display', :action);` will throw a PHP syntax error. What you're after is `..., 'action' => 'display'), array('pass' => array('action')));`.

deceze 2010-01-20 03:02:02

Right, forgot to put the pass params into an array. WRT the other routing stuff, I didn't mean if Cake was in a subdir; OP asked how he could route the "preview" URLs generated by his CMS to map them in Cake. But yeah I was def a bit lazy w/ my code above, thanks for the correction!

Travis Leleu 2010-01-20 16:38:40

Answer 2

A:

How can I dynamically connect the url http://localhost:8888/cake125/app/views/pages/test.ctp to http://localhost:8888/cake125/pages/test?

Well, the thing is, you don't. :-)

What I mean by that is, you do not connect a URL to another URL. What you really do is, you make certain URLs trigger certain Controller functions (or Actions for short) which in turn may (or may not) render certain Views. By default it's all straight forward through naming conventions. The URL /foo/bar triggers the Controller Foo's Action bar and renders the View /views/foo/bar.ctp.

The PagesController is already a special case. The URL /pages/foo triggers the Controller Pages's Action display, passes it the parameter foo, which renders the View /views/pages/foo.ctp. Notice the difference in which Action is triggered.

Since there are a lot of steps inbetween, it's not a given that a certain URL corresponds to a particular file on the hard disk. The URL /foo/bar might trigger Controller Baz' Action doh which renders the View /views/narf/glob.ctp.

This makes translating http://localhost:8888/cake125/app/views/pages/test.ctp to render the file /views/pages/test.ctp somewhere between an uncertainty and a pain in the rear.

Edit:

Having said that, the particular problem in your case is that the base URL is http://localhost:8888/cake125/app/. You can invoke a Cake app from http://localhost:8888/cake125/, http://localhost:8888/cake125/app/ or http://localhost:8888/cake125/app/webroot. All three URLs will be handled by the same file cake125/app/webroot/index.php, if you use one of the shorter URLs the request will be "forwarded" (rewritten) via .htaccess rules.

So the Route you're trying to connect, the Route that Cake sees, is actually /views/pages/test.ctp.

Actually, my mistake, this might not be the problem, but it depends on your .htaccess files and server configuration.

It doesn't seem to make much sense in a CMS though, since every newly created page would need its own rule. So I'd recommend against trying to do so and rather hack Cushy to properly construct URLs using the Cake HtmlHelper or Router::url(). Failing that, connect all URLs with a catch-all rule to some Action, parse the URL there and render the correct View "manually".

Alternatively, use .htaccess files and rewrite rules to actually rewrite the URL into a normal Cake URL, so Cake doesn't have to worry about it. As said above though, this can be very fragile.

deceze 2010-01-20 03:34:16

Answer 3

A:

As others have pointed out how CakePHP Router works, I'll leave it at that.

For the second part of your question (handling old links), I'd suggest adding this to the end of your Routes list:

Router::connect( '/:page', 
    array (
        'controller' => 'pages', 
        'action' => 'display',
    ), 
    array (
        'pass' => array ('page'),    // to pass the page as first arg to action
        'page' => '.+\.html$',       // to verify that it ends with .html
    )
);

You'd unfortunately have to parse out the .html yourself though

K Prime 2010-01-20 04:52:52

ansaurus

tags:

views:

answers:

cakephp routing for cushycms preview link

related questions