Golden Rule #243: Never let the client touch your code. If they don't understand why it's 'complicated' they are going to break something. Then they get to keep both parts.
None of my clients have access to the code base <cackle> it's mine, all mine </cackle> but some can update their sites via forms. This is sooo trivial to implement in Cake. I fact only one client even knows why it's Cake running the show (they don't really care, but their old spagetti site broke every time a change was made and I wouldn't take on the maintenance without a re-write...) I'd be very nervous allowing a third party to introduce potentially exploitable code into a production site. ~GreyCells On Apr 18, 5:55 pm, beetlecube <[EMAIL PROTECTED]> wrote: > For those who have done PHP development for a client, and used cakePHP > to build their sites, a question: > > Have you received complaints from the client, when they have tried to > add a page on their own, ? like: > > "This cakephp stuff is complicated, and I just want to add another > page that accesses the database, and I didn't know you have to create > three different files for it. I can't get a php coder to help me, > because they don't know cakephp or MVC" > > Just curious and thought I'd ask > > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
