Yeaah... but.. Suppose I simply want a restricted access (no authentification needed for the CMS, just restrict the access to a group) to tens if not hundred(s) of portal (in my department, we tried at least that number over the years). I would have to write a controller every time for each portal ? Ouch, a more ouch is that it would probably just be a reference to a controller.. But what about something really easy that is intended to be installed once for a particular course and the guy who knows how to write in Cake is on vacation :P . The competent, yet not-knowing Cake teacher could simply copy the files into the vendors directory then work through it simply by creating a session and doing whatever he wants on it after, no pipes for identification (or later if the product looks good enough)..
I don't know, it looks like the most versatile way to do so.. I'm looking for the holy graal here, dealing with human vs computers ^^ Maybe I need to learn more about how to "hack" the routes.php so that it could call a controller if a vendor is present.. Thanks ps. not to forget that every dep/lab may need it's own sub-system + it's own platform(s) (that is, a different database). All these would need to refer to a really simple to maintain core system and only one copy of each portal on the server... ouch my head.... :P On 24 oct, 23:52, Gwoo <[EMAIL PROTECTED]> wrote: > You do not need to make any changes to the Cake the core in order to > handle this. It should be as simple as creating controllers for the > various pass thru applications and using include to get the output > from those applications. Good luck. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
