I’ve always hardcoded the domain name in my htaccess’es, requiring me to make changes each time I deploy a new website.

The solution:

Behold, an alternate, generic method of redirecting non-www to www and www to non-www, requiring no changes between deployments!

Non-www to www

RewriteCond %{HTTP_HOST} !^www\.
RewriteRule (.*) http://www.%{HTTP_HOST}/$1 [R=301,L]

www to non-www

RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^/(.*)$ http://%1/$1 [R=301,L]

Bonus tip: Remove trailing slash from address line

RewriteRule ^(.+)/$ http://%{HTTP_HOST}/$1 [R=301,L]

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

$data = array( 
    1 => array('Post' => array( 
            'id' => 1, 'post_comment_count' => 2, 
            'name' => 'My first title', 'body' => 'My first body' 
        ), 
        'PostComment' => array( 
            array( 
                'id' => 1, 'post_id' => 1, 'is_active' => 1, 
                'name' => 'My first comment', 'body' => 'My first comment'), 
            array( 
                'id' => 2, 'post_id' => 2, 'is_active' => 1, 
                'name' => 'My second comment', 'body' => 'My second comment'), 
            array( 
                'id' => 3, 'post_id' => 2, 'is_active' => 1, 
                'name' => 'My third comment', 'body' => 'My third comment') 
        ) 
    ), 
    2 => array('Post' => array( 
            'id' => 2, 'post_comment_count' => 1, 
            'name' => 'My second title', 'body' => 'My second title' 
        ), 
        'PostComment' => array( 
            array( 
                'id' => 4, 'post_id' => 2, 'is_active' => 
                1, 'name' => 'My fourth comment', 'body' => 'My fourth comment' 
            ) 
        ) 
    ), 
    3 => array('Post' => array( 
            'id' => 3, 'post_comment_count' => 0, 
            'name' => 'My third title', 'body' => 'My third title' 
        ), 
        'PostComment' => array(                   
 
        ) 
    ) 
);                   
 
$dataExtra = array( 
    4 => array('Post' => array( 
            'id' => 4, 'post_comment_count' => 1, 
            'name' => 'My fourth title', 'body' => 'My fourth title' 
        ), 
        'PostComment' => array( 
            array( 
                'id' => 5, 'post_id' => 4, 'is_active' => 1, 
                'name' => 'My fifth comment', 'bdoy' => 'My fifth comment' 
            ) 
        ) 
    ) 
);

Set::merge

PHP doc blcok

This function can be thought of as a hybrid between PHP's array_merge and
array_merge_recursive. The difference to the two is that if an array key
contains another array then the function behaves recursive (unlike array_merge)
but does not do if for keys containing strings (unlike array_merge_recursive).
See the unit test for more information.         

Note: This function will work with an unlimited amount of arguments and
typecasts non-array parameters into arrays.

A bit like array_merge_recursive. Merge joins two arrays on their keys.
If we want to add the $extraData array into the $dat most people would probably think, hey, lets merge them using Set::merge… but.. no, dont, unless you know what your doing.

1

pr(Set::merge($data, $dataExtra));

The above cod will only produce the ‘expected’(?) result because I have added the numeric key 4 in the $extraData array (Line 40). If I had, as I did the first time around, just let php auto-increment the keys for me, both $datad and $extraData would contain the numeric index key 0, and since Set::merge works on keys, $extraData’s Fourth post would overwrite $data’s First post where they had anything in common (id, name, post_comment_count, body and everything in the first PostComment (My first comment)).

In case I had let php handle the index keys, I would have to use Set::insert to append the fourth comment to the list.

A better use of Set::merge is in CAKE/libs/model/model.php where is automagic merges ‘actsAs’ from your current model (PostComment) and your AppModel, so you automagic inherit the global behaviors from AppModel:

384
385
386
387
388
389
390
391
392
393
394
395
396
397
398

// model.php 
if (is_subclass_of($this, 'AppModel')) { 
    $appVars = get_class_vars('AppModel'); 
    $merge = array();             
 
    if ($this->actsAs !== null || $this->actsAs !== false) { 
        $merge[] = 'actsAs'; 
    }             
 
    foreach ($merge as $var) { 
        if (isset($appVars[$var]) && !empty($appVars[$var]) && is_array($this->{$var})) { 
            $this->{$var} = Set::merge($appVars[$var], $this->{$var}); 
        } 
    } 
}

A funny thing is that Set::merge is still rarely used in the core code yet. Probably because array_merge (or am()) is faster for simple operations like just merging two simple 1 level arrays like a config array.

Set::filter

PHP doc blcok

Filters empty elements out of a route array, excluding '0'.

This method is not recursive. So doing

1
2

< ?php 
pr(Set::filter($data, true));

wont change anything in the array sinc no elements in first level is empty.

1
2
3
4
5
6
7
8
9

pr(Set::filter($data[3], true));      
 
array('Post' => array( 
    'id' => 3, 
    'post_comment_count' => 0, 
    'name' => 'My third title', 
    'body' => 'My third title' 
    ) 
);

We will notice that the PostComment array is gone, since its empty

Set::pushDiff

PHP doc blcok

Pushes the differences in $array2 onto the end of $array

That sounds simple enough, and it really is.

1

pr(Set::pushDiff($data, $dataExtra));

just pushes the $dataExtra on the end of $data, since they have nothing in common. Again, this method operates on the array keys when comparing arrays.

Set::map

PHP doc block

Maps the contents of the Set object to an object hierarchy.
Maintains numeric keys as arrays of objects

That sounds very fancy, and it is! A lot of people migrating to CakePHP from Symfony (PHPDoctrine, Propel) will probably be confused at first that all model data in CakePHP is arrays, and not objects like other frameworks. This method attemps to ‘fix’ this issue by converting a model data array to a set of objects (StdClass). StdClass is a build-in dummy class in PHP, and it doesnt really do anything but contain data, no methods or fancy magic there.

1
2
3
4
5
6
7
8
9

< ?php 
// Convert to objects 
$map = Set::map($data); 
// id of first post (Object style) 
echo $map[0]->id; 
// name of first comment to first post (Object style) 
echo $map[0]->PostComment[0]->name; 
// name of first comment to first post (array style) 
echo $map[0]['PostComment'][0]['name']; // WONT WORK, Cannot access StdClass as an array

As you can see above, its important to decide what method you want to use, Object or Array style, since they cannot be mixed.
Also, the return from Set::map is a mix of arrays and StdClass, thats why I can access $map[0] as array, but not access $map[0]['name'].

Set::numeric

PHP doc blcok

Checks to see if all the values in the array are numeric

Not much to say on this one, because it doesnt do more or less than the name implies.

1
2
3
4
5
6
7
8

// false 
var_dump(Set::numeric($data)); 
// false 
var_dump(Set::numeric($data[1])); 
// false 
var_dump(Set::numeric($data[1]['PostComment'])); 
// true 
var_dump(Set::numeric(array(1,2,3)));

——-

Thats it for now, next time I will look at:

Set::enum, Set::format, Set::extract, Set::insert, Set::remove, Set::check, Set::diff, Set::isEqual, Set::contains, Set::countDim, Set::normalize, Set::combine and Set::reverse.

Look forward to it

I have made a small change to the feeds now. Everybody who has subscribed by Feedburner should not notice anything strange.

The reason for the change is that I want to be able to blog in Danish too once in a while, and to avoid the ‘danish pølsesnak’ for you guys who does not understand Danish, I have moved the feed location to include only posts with the ‘english’ tag in the future

English posts only (Hopefully your using this one right now ), Danish posts only and Danish+English posts

/Jippi

Its actually a quite good presentation, too bad he ran out of time in the end

Welcome to the second edition of the CakePHP weekly summaries.
Its quite embarrassing that it had to take so long time to get the second editon out. Too long time has passed and the amount of things that has happend during that period is waaay too big to be covered here.
Therefor I present this half-done 2nd edition of the weekly summaries, with a promise that every week from now on I will give you the latest and greatest from the CakePHP world.
So with no further ado, please enjoy this old and probably rather outdated edition of the weeklymonthly summaries. See you at the 3rd edition soon

Trac changes

• Changeset #6321 (phpnut) Fixes Ticket #3817, Some non-executable files in source tree have executable permissions
• Changeset #6322 (phpnut) Updating controller tests created with the console. Added associated fixtures to model tests
• Changeset #6323 (gwoo) Updating Cache to apply prefix for every key, closes Ticket #3821
• Changeset #6324 (phpnut) Correcting links generated to additional app tests
• Changeset #6325 (phpnut) Adding support for test fixture generation when creating models, this will eventually be moved to a task. Currently the $records are hard coded to create field type specific data, this will eventually be changed to create random data based on the field type. Refactored tests that are created for models, 3 working tests are not created when generating tests for the model. Added notice output to terminal when creating a project, the CAKE_CORE_INCLUDE_PATH is automatically altered and may need to be changed when moving to a production environment. ”
• Changeset #6326 (phpnut) Fixes svn file property line
• Changeset #6327 (phpnut) Removing unneeded ‘ : ‘
• Changeset #6328 (phpnut) Removing unneeded ‘ : ‘
• Changeset #6329 (nate) Fixing reading and writing in Configure class for references 3 levels deep, fixes Ticket #3845
• Changeset #6330 (nate) Removing un-needed method from TimeHelper? test
• Changeset #6331 (phpnut) Removing var $useTable; from generated model when tables follow conventions Fixed issue with model tests and fixtures not being created properly when Model name does not match table name
• Changeset #6332 (phpnut) Updating controller tests created with the console. Added associated fixtures to model tests
• Changeset #6333 (phpnut) Fixes Ticket #3849, Deprecated loadView() call in email component when using theme
• Changeset #6334 (gwoo) updating HttpSocket? with auth, closes Ticket #3838 removing type casting, fixes Ticket #3827 adding socket.group to tests
• Changeset #6335 (gwoo) updating component, removing use of Router not needed anymore, fixes Ticket #3858
• Changeset #6336 (nate) Adding non-null association key fix in Model, and updating Model::isUnique() to account for current record, fixes [ticket fixed 38599, closes [ticket fixed #2032]
• Changeset #6337 (nate) Fixing return value in Model::saveAll(), fixes Ticket #3852
• Changeset #6338 (phpnut) Fixes Ticket #3829, Scaffolding and bake script has problems with tables that has underscore in it’s name
• Changeset #6339 (phpnut) Fixes Ticket #3798, custom scaffolding file lookup paths inconsistent
• Changeset #6340 (phpnut) Fixes Ticket #3862, set_time_limit(0) has no effect because of ini_set(‘max_execution_time’, 60 * 5); changed max_execution_time , 0. Since php 4.3 this is the default anyway
• Changeset #6341 (phpnut) Fixes Ticket #3811, $_SESSION not found Fixes [ticked fixed 3823], Session not restarted after instantiating new SessionComponent? Fixes #3850, Configuration Session.start and SessionComponent::__active aren’t handle correctly
• Changeset #6342 (phpnut) Fixes Ticket #3851, Acl component fails to check() if a permission is denied in action (*)
• Changeset #6343 (phpnut) Adding test cases from [ticked closed 3810]
• Changeset #6344 (phpnut) Reverting [] and [] this commit broke the working implementation. Closes Ticket #3810
• Changeset #6345 (phpnut) Fixes Ticket #3854, Scaffolding is generating an id field with an empty value for auto_increment primary key
• Changeset #6346 (phpnut) Fixing bug with scaffold and valid Session id check
• Changeset #6347 (phpnut) Fixing bug with scaffold and valid Session id check in 1.1.x.x
• Changeset #6348 (gwoo) updating View error handling for extensions, fixes Ticket #3795
• Changeset #6349 (nate) Correcting parameter declaration in API shell
• Changeset #6350 (nate) Fixing database drivers for UPDATE/DELETE changes, updating drivers to comply with model tests, most passing. Fixes Ticket #3794
• Changeset #6351 (nate) Whitespace fixes
• Changeset #6352 (gwoo) adding connection param to schema shell
• Changeset #6353 (nate) Enabling alternate titles for PaginatorHelper::sort() links based on sort direction, closes Ticket #3865
• Changeset #6354 (nate) Removing MySQL-specific schema code from core, improving support for PostgreSQL sequences, most tests passing

Google group topics

Why doesn't Find* return a group of model objects?

This topic has been discussed many times before, but Deane felt that it was required to ask yet again: “Why doesn't Find* return a group of model objects?“. He wanted to be able to work with his models in the view (!BAD DESIGN!), and was confused why he only got an array back from the find* methods. Gwoo replied, and I quote: “Speed, simplicity, clarity” and pointed out that Cake provide view helpers to work with the arrays in almost any way you can imagine, and that the models provide callback functions (afterFind, afterSave, beforeFind, beforeFind) to format your data.
Deane thanked gwoo for the reply, but “We couldn’t disagree more strenuously, and we think you’re wrong beyond belief in your reasoning, but we appreciate the response”…. didnt like gwoo’s reply at all.
Gwoo replied in a calmly matter that “Everyone is entitled to their opinion and their choice of frameworks.”
rtconner joined the discussion, offering a solution based on some old code by gwoo that would enable the models to return objects (StdClass, not models classes)instead of arrays.
Nick also joined the thread, backing up Deaen’s point of view (Cake is wrong, symfony lover is right) that its proper OO to use objects instead of arrays for the view data, but also reasoned that cake does indeed have the needed hooks and concepts to achieve Deane’s initial idea with a minimal effort. He explained that in a project he had created with CakePHP was that relationships (belongsTo, hasMany ect.) get more complicated with the OO styled approach, since the queries often fetched much more data than was really needed in the view. The combination of the controller didnt know wich fields the view required and the complex relation ships was in his opinion, not ideal at all. Their work a round was to create a “LazyData” class to handle it.
Robby Anderson dropped in his 2 cents, and agreed that the cake was isnt 100% pure OO, but that the concept of “having the view incapable of performing any meaningful business logic” is bad, and will sooner or later lead to an unmanagelbe code base.
Deane, the creater of the thread, posted a public apoligy to gwoo, explaining that he was fustrated at the time when he posted his previous post.

So, the summary must be that while some people dont like the design decission that CakePHP models return arrays instead of objects, others agree that its the right way to encapsulate the buisness logic in a correct Model View Control manner, and if you want to break theese convensions, its rather easy to do with minimal effort.

Passing Data To A Form

Travis asked how you are Passing Data To A Form. A bit unexpted (or perhaps expected given the flood of duplicate / newbie questions hitting the groups daily) nobody answered his question. The answer is pretty simple, and covered in any tutorial aviable on cakephp website AND in the documenation / manual.

1
2
3

function update($employeeID)  { 
     $this->data =  $this->Employee->findAllById($employeeID); 
}

The Show Is Back!

Jeff Loiselle aka phishy announced that the show is back. No replies, no thing, its sad… the show rocks !

I18n in 1.2 model validation message

Athies asked how does i18n in 1.2 model validation message work. His iniital attemp was to use the i18n method ‘__()’ in the model $validate array, but he was getting syntax errors when doing that.
Since PHP does not support useage of functions in instance delclarations its not possible to use i18n directly in the validate array.
Francky06l pointed at his solution in another google post i18n: static language references with __("My lang key", true) in models and controllers, and while the solution will work, its far from ideal when working with i18n.
A CakePHP google group regular, Dr. Tarique Sani, pointed out that the correct way to handle i18n validation messages was in the view, not at the model level. Amit Badkas backed up Tarique up and provided a simple example on how to do it:

1
2
3
4
5

< ?php echo 
$form->input('username', array('error' => array( 
    'alphanumeric' => __('Username must contain alpha-numeric characters', true), 
    'between' => __('Username must be between 8 to 20 characters', true)))); 
?>

Francky06l seemed to know that, his consern was the if he multiple views where the validation errors should show, it would be convenient to do it at model level.
Robby Anderson wasnt sure why you just couldnt do both, create the validation errors in the model, and wrap them in __() in the view.

And sure, that will work – but – you will loose some cake magic with that. The console application

cake i18n extract

will not add the i18n messages to the pot file automagic. Also, the i18n extract command will not even search your models for any i18n magic. It will only look in controllers and views. You can choose to call this a limit or a feature, but thats how cakephp has decided to do it, to enforce their paradime on how an application should be build and structured.

FormHelper Labels

Travis asked how it was possible to disable the automagic label in the FormHelper. Robby Anderson provided the correct solution for this issue, use ‘label’ => false:

< ?php echo $form->input('Employee.name',array('label' => false));?>

Using model objects in the controllers

Deane from earlier posted another question on Using model objects in the controllers. I dont really want to dwell much on this post, since its really attemp to take CakePHP in another direction than its supposed to. Deane clearly shows a lack of insight on how cakephp is supposed to work, and failed to provide any usefull examples that could show the group what he wanted to do.

Sorry that I havent created the weekly summaries for almost 1.5 week now. The reason is that I have begun on a new job, and its consuming quick alot of time and energy Lot of new systems to learn (They dont use Cake…. yet, booooh!)

I have the second edition 80% done, just need to clean it up and proof read it a few times Should be done before this weekend

Hello,

Just a little turtorial to demonstrate the new model counterCache feature.

CounterCache is a very fancy little addition to our beloved CakePHP framework.
Simply put, all it does is make sure that your belongsTo associations always have an updated field with the count of elements belonging to the parent.

Lets use this simple example, just two models and controllers:

• Posts (posts_controller) (hasMany PostComment)
• PostComments (post_comments_controller) (belongsTo Post)

SQL

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

-- our posts 
CREATE TABLE `posts` ( 
  `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, 
  `post_comment_count` int(11) UNSIGNED DEFAULT NULL, 
  `title` varchar(100) NOT NULL, 
  `body` text NOT NULL, 
  PRIMARY KEY  (`id`) 
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;             
 
-- comments to our post 
CREATE TABLE `post_comments` ( 
  `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, 
  `post_id` int(11) UNSIGNED NOT NULL, 
  `is_active` tinyint(1) UNSIGNED NOT NULL DEFAULT '0', 
  `name` varchar(100) NOT NULL, 
  `body` text NOT NULL, 
  PRIMARY KEY  (`id`), 
  KEY `post_id` (`post_id`) 
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;

To keep things simple, we are just going to use scaffolding in controllers.

Controllers

Posts controller

Put in APP/controllers/posts_controller.php

1
2
3
4
5

<?php 
// Posts controller 
class PostsController extends AppController { 
    var $scaffold; 
}

PostComments controller

Put in APP/controllers/post_comments_controller.php

1
2
3
4
5

<?php 
// Post comments controller 
class PostCommentsController extends AppController { 
    var $scaffold; 
}

Models

Post model

Put in APP/models/post.php

1
2
3
4

<?php 
class Post extends AppModel { 
    var $hasMany = array('PostComment'); 
}

PostComment model

Put in APP/models/post_comment.php

1
2
3
4

<?php 
class PostComment extends AppModel { 
    var $belongsTo = array('Post' => array('counterCache' => true)); 
}

The interesting thing is the above PostComment model. A you can see, a new options key is added, counterCache and is set to (bool) true. This informs cake that it should use counterCache on the class (Post) it belongs to.
This is three possible variables to assign counterCache

• (bool) true means enabled, and that cake should auto-generate the count field automagic
• (string) fieldname tells cake to use your custom field in Post (posts) model and table.
• any value that is considered ‘empty’disable the feature (this is default, NULL)

Its important to understand, that the field we specify here, is a field in the REMOTE model / table, not in the local table, so in this case, the field name is in posts table.!

As said earlier, cake will automagic generate the remote field name if you only provide a boolean true value, in this case the field will be named Inflector::underscore($this->alias) . ‘_count’ – meaning the alias of the LOCAL model (PostComment) and a suffix ‘_count’. All is that is converted to a lowercase, underscored value. When these rules are applied to our example above, the remote field in posts will be named post_comment_count (line 4 in SQL section)

With the code above, you have a very basic scaffolding setup running with couterCache enabled. Very simple stuff As always when its from the CakePHP team.

Using counterCache scope

As you might have noticed in the SQL table above, the post_comments table have a field called is_active (SQL line 14). This is a sample on how you could moderate your comments. Lets change a bit of code in our models to make this work.

Put in APP/models/post.php (Updated)

1
2
3
4
5
6
7

<?php 
// Updated Post model 
class Post extends AppModel { 
var $hasMany = array('PostComment' => array( 
        'conditions' => array('is_active' => 1) 
    )); 
}

Notice that I have added a conditions array to the hasMany relation to PostComment.
This will tell cake to only fetch comments from PostComment where is_active is 1 (aka. is active).

Put in APP/models/post_comment.php (Updated)

1
2
3
4
5
6

<?php 
class PostComment extends AppModel { 
    var $belongsTo = array('Post' => array( 
        'counterCache' => true, 
        'counterScope' => array('is_active' => 1) 
    ));}

Notice that I have added another field to the Post relation called counterScope, this is the conditions that cake uses in the find(‘count’)query it creates to find the amount of comments to the Post. By adding this simple array, our counterCache now only count active comments

Easy done

This week alot happened, but the biggest news is that CakePHP 1.2 have entered BETA phase, and with that – we are close to a feature (API) freeze of the 1.2 branch.

•••••••••••••••••••••••••••••••••••••••••••••••••••••••

CakePHP 1.2 beta

Yes, finally it happened. Please look at my post about the .

Trac changes

• Changeset #6288 (gwoo) Added support for stored procedues in DboMysqli, fixes Ticket #2340
• Changeset #6289 (gwoo) Updating controller task with i18n wrappers, closes Ticket #3490
• Changeset #6290 (nate) Updating help text for ACL shell interface, fixes Ticket #3790
• Changeset #6291 (phpnut) Moved merging of components, helpers, and uses vars to Controller::_mergeVars(); fixes bug with PluginAppController? vars not being merged before components are loaded. Fixed Ticket #3760
• Changeset #6292 (phpnut) Missing keys when Model merges actsAs. Fixed Ticket #3786
• Changeset #6293 (nate) Adding quoting and name-resolving fields in TreeBehavior. Fixed Ticket #3778
• Changeset #6295 A few new exciting features was pushed into the repository:
  • Model::generateList() was deprecated, and replaced by the new 1.2 cake find syntac. Model::find(‘list’)
  • Model::saveAll() was enhanced to save multiple records and associated records
  • Some transactional methods (begin, commit, rollback) was added to DataSource class as well
  • bindModel now support to change the bind settings on the fly if the model has already been bound
  • Fixed Ticket #3720, Ticket #2355, Ticket #3615
• Changeset #6296 Implemented Validation::extension(); and Vaidation::range(); Fixed Ticket #2897
• Changeset #6297 Some optimization in code. Fixed Ticket #3653
• Changeset #6298 Adding test for root path caching. Fixed Ticket #1349
• Changeset #6299 Adding full join model support. Fixed Ticket #828, Ticket #1045
• Changeset #6300 Adding Debugger::log and test cases. Fixed [ticket tixed 995]
• Changeset #6301 CSRF usability problems, Security Component and multiple instances of the webapp. Fixed Ticket #2608, Ticket #3436
• Changeset #6302 Adding new URL to validation test
• Changeset #6303 Renaming domains in test to generic names
• Changeset #6304 Fixing Model::find(‘list’) when using self-joins
• Changeset #6306 Refactoring, fixing SessionComponent test, adding String::tokenize()
• Changeset #6307 Adding regular expression support to Set::extract() [ Set::map($data, '{s}.{n}.{[0-9]} ]. Fixed Ticket #3263
• Changeset #6308 Fixing paths returned by Debugger::trimPath();
• Changeset #6309 Fixing paths in debugger tests
• Changeset #6310 Fixing paths in debugger tests
• Changeset #6312 Adding String class to shell boostrap. Fixed Ticket #3793
• Changeset #6313 Fixing JavascriptHelper::link() for script files outside of webroot/js (i.e. plugins). Fixed Ticket #3799
• Changeset #6314 Removing unused directories from app/pages. Merging changes from app/ to skel/
• Changeset #6315 Fixing after filters for Model::find(‘list’). Fixed Ticket #3805
• Changeset #6316 Updating TimeHelper. Fixed Ticket #3801
• Changeset #6317 Bug in hasAndBelongsToMany. Fixed Ticket #3814
• Changeset #6320 updating Set::map() handling of deeply nested arrays, thanks to speedmax for an updated test case. Fixed Ticket #3809

Google group topics

How to find referrer url?

A guy called ‘krr’ opened a question how to find referrer url?, and Daniel Hofstetter quickly replied that Controller::referer() would return the referer.

Will CakePHP be able to survive as the Zend Framework matures?

The framework war ignited yet again when “Action” created Will CakePHP be able to survive as the Zend Framework matures?.

Upgrade problems

Following the release of 1.2 beta “Mech7″ Upgrade problems after upgrading his application to the new beta verion. Chris Hartjes quite replied that Mech7 should check his apache and php error logs. Mech7 however, quickly replied that the error was solved (after only 9 minutes), and his solution was to clear the app/tmp/cache folder in this app.
I had however already written a list of steps I follow when my application suffers from the White Screen Of Death:

• Check that debug > 0
• Clear app/tmp/cache/persistent/*
• Check local vhost error log
• Check global httpd-error log
• Restart apache, (stop, start), restart cache services (memcached ect.)
• Enter the world of die(‘stop’); from app/webroot/index.php and downward in your application

Table inheritance, multiple schemas, and associations

Brian had a interesting question, well, for us postgresql users at least, table inheritance, multiple schemas, and associations. There we no response to this thread, but after a few hours, he returned with a working solution, very interesting stuff.

Depricated ListControllers

Ronald Chaplin asked what the ‘new’ way was in 1.2 to get a list of controllers in your application, since 1.2 had Depricated ListControllers ( listClasses( CONTROLLERS ); ). He had tried Configure::listObjects(‘controller’, ‘/app/controller’);, but without success.
Arno Esterhuizen quickly pointed Ronald in the right direction, the CakePHP 1.2 api

OthAuth looses session – upgrading to new 1.2.0.6311 (2008)

Klaus had a problem, othAuth looses session – upgrading to new 1.2.0.6311 (2008), but so far no replies, might be a local issue on his setup?

Themes management for an app ?

Max asked if anyone had a component/helper for Themes management for an app ?. Tarique shamelessly pointed to his own blog, where there is quick guide on how to make cakephp use ThemeView.

Cakephp with PHP 5 and Mysql 5

One of the too often asked questions on the group was asked yet again, Cakephp with PHP 5 and Mysql 5, and yes. CakePHP works fine with both MySQL5 and PHP5!!. Its rather funny, or sad depending on who you are, that the same questions is asked over and over on the googlegroups…. I’m sure the CakePHP guys chose google for a reason

Bug for find('All'

Another of repeating posts on the mailing list is the “I think I have found a bug” or just bug for find('All' in this case. And as always, people always point directly to Trac bugtracket, as its the one and only place to submit possible bugs..

CakeFest website Launched

Mariano Iglesias announced that the CakeFest website Launched! There was no replies or reactions on the list, I just hope that people did not overlook this little gem

Bakery hates me

Adam Royle claimed that “bakery hates me“, because he was not able to comment on a bakery article. Mariano Iglesias was quick to point to tracwebsite, but a Dr. Hannibal Lecter was snappy, and said “I don’t think posting links to Trac solves anything, it is a fact that bakery has many issues (some minor and some..not so minor). Some things should be seriously reconsidered and rewritten. But that’s just my 2c.”.

As much as Chris Hartjes agreed with Dr. Hannibal Lecter, he pointed out the important fact that trac is still the one and only place for bugs on cakephp related projects.
Dr. Hannibal Lecter hoped that someone from the core team was following the group, since it wouldn’t be very (And I quote) “userfriendly community” if they didnt.
Dr. Tarique Sani (Whats up with all those doctors?) replied that it was unfair against the php team to mark the community less userfriendly because users finding bugs wouldn’t bother to create tickets on trac, and just posting the errors on the mailing list.
And FWIW my personal experience is that posting in trac works

Adam Royle said that the reason why he hadn’t posted a bug report on trac yet was because he didn’t like opening tickets without a patch or solid way to reproduce the error.
Dr. Hannibal Lecter returned a apologized that it was not his intention to be unfair against the CakePHP team, and that he really appreciated their efforts. He was however puzzled that the creators of such a great framework as CakePHP would neglect The Bakeryand made a rather good point: If new users use the bakery, and its full of errors, what would they think of the underlying framework as well?
Adam Royle returned to the discussion and tried to get answers on his two original questions

• He was unhappy wit the quality of this article on the bakery
• What version of cake is the bakery running on? (1.2 pre-historic afaik)

Chris Hartjes, our favorite grumpy Canadian, closed the thread with a few harsh comments I’m not going to quote here Larry E. Masters aka PhpNut posted his announcement on the new 1.2 beta at: New Year, New Beta, that received a few “thanks”, but nothing else of interested.

Require SSL for entire site?

Bryan Encina asked if it was possible to Require SSL for entire site?. His own idea was to check $_SERVER['HTTPS'] in his AppController, and then redirect based on this. Chris Hartjes questioned the safety of $_SERVER['HTTPS'] (its perfectly safe), to his understanding, it was possible to spoof (its not) this variable. His suggestion was to limit access on webserver level instead of application level.

I (Christian Winther) pointed out that mod_rewrite would be a perfect solution for this problem, since the RewriteCond directive could check for both SERVER_PORT (port 80 = non ssl, port 443 = ssl) and SERVER_PROTOCOL (http = non ssl, https = ssl)
. Robby Anderson suggested using the SecurityComponent::requireSecure() method instead, also a possible solution if you wish to let ssl management be up to the application (htaccess will most likely perform alot better if its just for redirect).
Chris Hartjes returned to the thread because he had felt a bit wierd about his earlier reply to the group, and confirmed that $_SERVER['HTTPS'] indeed cannot be spoofed. He suggested using Robby’s solution.

Head over to the cakefest website and join the fun

Cakefest is the first global meetup for CakePHP (and probably also other PHP programmers) ever, so its going to be very excited

CakePHP 1.2 beta has been released.

Some of the new stuff includes:

• Reverse routing for array based urls
• RESTful automagic
• Forms are easier to create and maintain
• Security enhancements for better CSRF prevention and HTTP Authentication
• CookieComponent for securely storing persistent data on the client side
• Model behaviors
• The “with” key allows you to define a dynamic join table model
• Pagination of model records with an extensive helper
• Internationalization and Localization
• Authentication component
• Configure class to provide dynamic handling of configuration settings
• Cache Engine (memcache, xcache, apc, model, file)
• Console

View the rest of the changes at the bakery announcement made by PHPnut

I have been using the 1.2 branch for more than a year now, and it has been a real pleasure to see how development has moved in a very interested direction. Being in the -dev channel I have also been able to follow some of the discussions on what can stay and what can go. The result, a very clean codebase with a lot of cool features, that is very easy (and fast!) to use.

One of my personal favorites has to be the new ModelBehavior feature. Its incredible easy to work with, and makes its very easy to add new features to a already running project without having to hack your way into either Cake or App code

One of the few things I miss is the possibility to return a result set in Model::beforeFind – so it would be possible to create a simple cache mechanism for your query data (together with the new cache engines). Its possible, but requires a little bit of overloading of Model::find to get it to play nicely, oh well