Hy all,

I crawled throught this group searching for endless need to configure
every app used for editing cackephp templates for syntax higlighting.

Big annoyance of cakephp (or any app with same aproach). Why let all
the world change their settings if one could sipmly let the templates
be with php extension and also automatically protect them from public
acces if something happens with webserver etc? Afterall it's just a
file that's included in templating process and the extension has no
meaning what so ever as it can contain any kind of text informatin.

It's the same thing again that was with *.inc files and all the users
who write their pw -s into some files with absurd extensions :) and
got f**ked if anything in security line went wrong.

So put yourself in a project manager position:  60 designers, coders
aso to change their user habits :) not a good thing and easy task for
project manager to explain (+ new workers). The integration of
cackephp would be a lot easier if this extension was php or html or
whatever default value for tons of editors recognise without a change
in settings.

I understand it's so cool but for my point of view it's just another
unneccecary task for managers, developers, designers and server admins
who have to secure those files.

So someone has a clue how to manually change this .ctp -> .php in
local cakephp install?

1 task with change&replace in all files vs 60+ tasks is a huge leap to
better usability.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to