the one that I think the author is more interested in. It's the
"Where do I go from here after I bake a site?"
The short answer to that is you customize. Baking only gives you a
lot to work with, but is your site ready for the big times? No. It
doesn't have security built in, it doesn't have e-mailing, any
specific application specific minded code in there. After you bake
your site you are left with a great start but it's not the finished
polished product.
The main parts that took me a while to grasp is the MVC model itself.
Know that what you need in a view can only be sent by the controller,
and what you need in a controller in terms of data can only be sent by
the model's. Sure there are exceptions but let's try to keep it
easy. Next will be looking at the code that was generated in the
bake, you'll see admin_index, index_edit ect (assuming you said yes
that you want admin routing). Those are admin only functions, and
they are how something like {domain}/admin/{function} translates to
function admin_{function}. So: {domain}/admin/edit/1 will go to
function admin_edit($id) (where $id is the 1 in this case).
Truth be told, I don't typically bake a site now unless it's a rather
complex site that I haven't done before or has way more tables than I
want to make models for manually. Most the time I copy and paste
files (since Cakephp is extremely module) and then build the specific
details of the application into it. Could you release a baked site
out into the wild? Sure. But will it be secure and be ready to
service your customers the way you want? Probably not.
I've developed a lot of sites in cake, and one that's really getting a
lot of attention lately is http://theeasyapi.com because it's an API
that connects to other API's easily and standardizes the output into
XML regardless how the other API's send data.
Enjoy, and happy baking!
On Feb 23, 3:11 am, WebbedIT <p...@webbedit.co.uk> wrote:
> Is your website's subject matter a particularly sensitive/illegal one?
> If not then I'm unsure what you're worried about?
>
> There's possible compliance with Disability Discrimination Act,
> Distance Selling Regulations and a few terms and conditions to state
> that user contributed content contains the views of the user and not
> the site owner. But if you ignored these the worst you would truly
> get was a warning to comply, unless your developing something like the
> Australian Olympics website of course ... ergo the ONLY legal case
> against a web site for accessibility.
>
> http://contenu.nu/socog.html
>
> I've designed a lot of websites and never once have I or my clients
> felt threatened that we would be 'sued into oblivion'. Maybe it is an
> American thing?!?
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.
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
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
No comments:
Post a Comment