In The Series Part 1 Part 2 Part 3 Part 4 So, when we left off in part two, I was leaning towards WordPress as a candidate for a CMS. It's popular, has tons of themes, plugins, etc. It's almost perfect, but for only certain situations.
Enter Drupal Now, I've been hearing a lot about Drupal. For years now. I tried it once and I didn't like it. However, since then, I've revisited it.
How The Problem Started Christmas Eve have just started at about 12:03 AM, when I logged on and saw that dreaded message:
Your Account Has Exceeded Its CPU Quota
So I did what all normal people do at first: I ignored it. Actually, I had a very good reason to at the time. Since it was 12:03 AM, I assumed that my nightly backup job (backup and compress files and databases) was causing the issue.
This is the second installment of my Auth Component Tutorial. I included a link to download a file for during the first installment:
CakePHP Auth 1 (4.3 KiB, 18,444 hits)
I just think that some of the stuff in there warrants some explanation.
isAuthorized() This function is needed when $this-Auth->authorize = ‘controller’. Theory has it, you can do something similar in app_model if $this-Auth->authorize = ‘model’, but I haven't looked into this.
First off, I would like to say much thanks to Gwoo for finally helping me to understand this thing.
So I know what you're thinking; I'm probably the last person to finally figure out the CakePHP's Auth Component. For the past few months, I've been using obAuth because that's the only authentication I could get to work with CakePHP. I think that I was just making it more difficult than it should have been.
So I guess the CakePHP development staff doesn't take any holidays. Bright and early New Years Day 2008, we're greeted with a fresh new release of CakePHP 1.2.6331 beta. No, not pre-beta a full blown beta. Needless to say I'm excited about this.
There have been some nice changes which have gone through all through the Christmas season. Guys, I thank you for your dedication. The one major thing I'm excited about is the way that the Form Helper now processes dates and times; there's no longer a cleanUpFields() function, everything is automatic (or should I say automagic).
I can't remember where exactly I heard about this web host, but InsaneGB.com sounded like a great deal. You can read their website for more details, but in a nutshell they got PHP 5, MySQL 4, and everything (Databases, Add-on domains, etc) is unlimited except disk space and bandwidth. They give you 5GB for disk space and 20GB on bandwidth per month. Which is great for a free host, if you ask me; heck, they even offer cron jobs.
One of the nice things about CakePHP is that it includes ready to use CSS compression. Granted, compressed CSS can be buggy at times, but for the most part it works just fine.
Poll results for What Do You Look for in a PHP Framework are in:
Most of you prefer a framework that is Quick and Easy. Hey, I'm totally with you guys on that. When deciding on a web development framework, it has to be easy. It's no fun if it takes hours to learn and saves you minutes. For me, CakePHP definitely fits this bill. The bake routines save me so much time during initial development.
Now i doubt it has crossed anyone's mind to use CakePHP to create a custom content management system (CMS). Even though you're not designing a full blown CMS, sometimes it's nice to give novice users a way to create HTML content for a website or web application. The simplest way to do this is to integrate a WYSIWYG (What You See Is What You Get) editor.
When it comes to WYSIWYG editors, they are a dime a dozen.
First of let me state that this post is very bias towards CakePHP. Truth be told, I haven't even installed or used Ruby on Rails. The closest I've come is looking at various code snippets I've found around. With that said, you may want to stop reading now.
These arguments are not based on hard facts, since I haven't done much research on the matter. A lot of them come from a post at Clickable Bliss discussing the PHP vs. Ruby On Rails Issue.
Steep Learning Curve - Laziness
One thing I really hate is learning stuff. It is especially bothersome when you're trying to crank out a project or web application in a limited amount of time.
With CakePHP I'm required to learn about the **MVC style of development** as well as CakePHP **conventions**.
With Ruby on Rails, I would have to learn MVC, Ruby on Rails conventions and I would have to s**tart from scratch with the Ruby programming language** as well.