Cakephp installation bug.

Stinger51

I've been tasked with reviewing Cakephp as a framework. I installed version 1.3 to my local server (Apache 2.2) but I keep getting this error:

Error: Index.phpController could not be found.
Error: Create the class Index.phpController below in file: app\Controller\Index.phpController.php

<?php
class Index.phpController extends AppController {
}

So, I created the file "Index.phpController.php" in the Controller directory and then created the class as instructed. But then I got this error:

Parse error: syntax error, unexpected '.', expecting '{' in C:\wamp\www\cakephp\app\Controller\Index.phpController.php on line 2

It apparently did not like the period after "Index" (which also looks funny to me for a class name). So, I took out the period and was then back to square one:

Error: Index.phpController could not be found.

I'm beginning to wonder, if it's this difficult to install this framework then is it going to be even more difficult to learn it? :rolleyes:

cretaceous

I also had a lot of trouble installing Cake - I ended up installing as apache virtual host
there's some stuff on this on the web..
I didn't end up liking CakePHP that's for sure!

Stinger51

cretaceous;10994595 wrote:
I also had a lot of trouble installing Cake - I ended up installing as apache virtual host
there's some stuff on this on the web..
I didn't end up liking CakePHP that's for sure!

We took a look at CodeIgniter today. Lots of folks claim this is the best PHP framework out there. What we found was mostly good old C.I.P.U. (clear if previously understood). But at least it installed correctly and we got it up and running. For now anyway. The CodeIgniter tutorial, despite the claims, is just more CIPU, with almost no explanation of how it fits the MVC model. Proves my point that you should never let the development team anywhere near a word processor. :queasy:

The CIPU part was, why in hell are we going to all this trouble, just to have a nice code library (on top of the extensive one we already have) and to force us into a coding style that is, repeat, CIPU. The MVC model looks great, until you drill down a bit and discover that, it's just another way of doing things as opposed to the way we've always done things. No better, no less.

Our final thots are, if we wanted all this complexity with an MVC framework, we might as well just abandon PHP and move onto that big, grotesquely bloated and obese "framework" call Java.

cretaceous

I'm kind of in agreement with you..
Documentation on CakePHP is scrappy - there are a couple of lightly used forums so support is thin
They made revisions from code base 1 to code base2 such that an upgrade from 1 to 2 requires major restructuring
I was handed a site built on Cake v1 and asked to make some updates and fix some bugs but since v1 was by then 2 yrs out of date, I also had to change code base to v2 - not fun.

But I think plenty of people here have praise for Code Igniter

The question is, is the hassle of learning the abstraction layer, more trouble than it's worth..

Derokorian

I happen to love using MVC and I never really got it until I made my first site in Code Igniter. I think its a great framework and learning to use it has really advanced my coding style, IMO. I don't use Code Igniter for projects unless I'm on a swift deadline because I like to minimize the code used in my projects that I didn't develop. That said I also feel CI was so easy to catch on to because of the video tutorials (you did watch them right?) and I feel all of the methods are very well documented, you just have to think like a programmer (which if you are using CI you should be a programmer!)