> 2) trying to locate a resource depends on what your data model is
> like. You essentially need a central repository that acts as your site
> map which consists of parent_ids and stubs/slugs for that resource.
> Assuming resource stubs/slugs are unique, it'd be a simple matter of
> retrieving fro
> On Wed, Jun 4, 2008 at 6:11 PM, <[EMAIL PROTECTED]> wrote:
>> Here is my problem though: I don't want to impact my users' sites,
>> meaning I want to keep their URLs intact and continue to use the same
>> underlying database containing sites and pages (where a record in the
>> "page" table has
On Wed, Jun 4, 2008 at 6:11 PM, <[EMAIL PROTECTED]> wrote:
> Here is my problem though: I don't want to impact my users' sites,
> meaning I want to keep their URLs intact and continue to use the same
> underlying database containing sites and pages (where a record in the
> "page" table has a URI,
My first instinct is to go with a custom pages controller. I'm doing
something similar right now with custom SEO paths in a site, and just
jumping over Cake's pages routing entirely was the easiest way
forward.
- James
On Jun 4, 6:11 pm, [EMAIL PROTECTED] wrote:
> Hi All,
>
> Over the course of
Hi All,
Over the course of last year I rebuilt my employer's website from
scratch using CakePHP. It is a site for a futures trading firm with
lots of interesting tools for sorting and combining data that were
remarkably fun and easy to build with CakePHP. I'm now a total convert
to the cult of Ca
