> 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'm a bit sick of wingy .. people complaining about something they
obtained for free as if they're owed something. Is it really too much
to ask for users to think a bit, do functional tests on their code and
read the ample documentation? (que attempted witty retort regarding
well that's open source philosophy etc.)
>
> 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.
you only need to:
set the cookie name
if you use the email component - set the xMailer
anything else whereby you could potentially come across the cakephp
showing up in the source is a file you should be editing anyway - like
email layouts, error messages and the default home page.
> 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 .
the cleaning it out bit sounds like 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.
You mean you use your clients for testing? do they get a discount for
that?
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