jitka: to be quite honest, I have no idea. I didn't implement the
plugins feature, and it's pretty much the only part of the framework
that I haven't worked on much, but maybe PhpNut could weigh in here.
However, the admin stuff should still work with it by default, no other
changes necessary.
Schmidt.Troy: I've added some new Router features to 1.2, but the stuff
I posted above has been that way pretty much since the beginning.
DaiBach: In Cake 1.1, yes, you would need to add a route for each of
your controllers. Cake 1.2, however, allows you to specify regular
expression rules for each route element. So for example, you could set
that route up like this (using 1.2 syntax, which is slightly
different):
Router::connect(
"/:team/:group/:controller",
array("group" => null),
array("controller" => "news|gallery|blog|members"
);
The connect() method of the Cake 1.2 Router adds a third parameter that
allows you to specify a custom regular expression to match each route
element. That way, you can just add your controller names the list,
and they'll get matched.
The other important thing to note in the code above is that I gave the
"group" element a default value of null. That makes the element
optional, and the route will still match whether or not it is present,
which means that you can replace the two routes from above with this
one.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
