As for the "branding" override all of the templates from the core views, simple enough, and you can even create your own bake templates to use in all of your other projects so you are not "cleaning out" your installs every time.
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
On Mon, Jun 28, 2010 at 10:01 PM, Vangel <abhishek.dujari@gmail.com> wrote:
I am quite sick of cake doing tons of branding everywhere. (emails,
cookies, css etc etc)
Its starting to look like some other frameworks already.
I have set cookies etc, but Cake still sets its own CAKEPHP cookie. I
absolutely do not want to give any indication to snoopers and sniffers
about what framework I am using. Anyone here has done any research
into cleaning out cakes footprints please post some notes.
I will post a few clean ups I found. I think I will be putting
together a clean version of cake for all future projects. Cleaning it
out every time is a giant waste of time .
This can be used a topic to discuss on how to remove the default
messages and other related branding so you are not caught unaware of
your clients receiving emails from EmailComponent signed by Cakephp
and similar things.
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
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