class AppModel extends Model {
        function unbindModelAll() {
                foreach(array(
                        'hasOne' => array_keys($this->hasOne),
                        'hasMany' => array_keys($this->hasMany),
                        'belongsTo' => array_keys($this->belongsTo),
                        'hasAndBelongsToMany' => array_keys($this->hasAndBelongsToMany)
                ) as $relation => $model) {
                        $this->unbindModel(array($relation => $model));
                }
        }
}

If you set the security level in a cake application to high, an algorithmus regenerates the SessionID.

Usually, this is not a bad idea. But as sometimes several requests are started simoultaniously, I discovered that random requests didn't get a proper user-id in the session and further found out that during AJAX-Requests requests the sessioncookie got deleted and in the same request a new one was set. As a result, a few AJAX-Requests failed due to an invalid session id.

After reducing the security to medium, the errors were gone.

It seems that this is a known issue to the developers (https://trac.cakephp.org/changeset/5982) and should have been fixed for over two years. As far as I can tell from the current source, SessionIDs are regenerated each tenth request - even if a XML-HTTP-Request was made. Due to race conditions this will make many developers headaches and is a bug that should be fixed.

Deprecated: Assigning the return value of new by reference is deprecated in /data/workspace/us/htdocs/tixi/cake/libs/debugger.php on line 99

cake/libs/configure.php

$ diff configure.php configure.php.new
295c295
<                               error_reporting(E_ALL);
---
>                               error_reporting(E_ALL & ~E_DEPRICATED);

while(@$i++ < 2) {
        switch('test') {
                case 'test':
                        echo "was here $i\n";
                        continue;
        }
        echo "fail\n";
}

was here 1
fail
was here 2
fail

continue 2;

Usually PHP-Code looks like this (source):

$dir = "/etc/php5/";

// Open a known directory, and proceed to read its contents
if (is_dir($dir)) {
    if ($dh = opendir($dir)) {
        while (($file = readdir($dh)) !== false) {
            echo "filename: $file : filetype: " . filetype($dir . $file) . "\n";
        }
        closedir($dh);
    }
}

But IMHO this is bad coding style. A long indent does not make your code better. Far from it! On the one hand, an ident should be used to separate nested code blocks. On the other hand you should avoid unnecessary deep nesting. Try to alter your code and seperate error-cases in own blocks:

$dir = "/etc/php5/";

if(!is_dir($dir)) {
    throw new Exception("...");
}

$dh = opendir($dir);

if(!$dh) {
    throw new Exception("...");
}

while (($file = readdir($dh)) !== false) {
    echo "filename: $file : filetype: " . filetype($dir . $file) . "\n";
}

closedir($dh);

This is kind of annoying if you have a class (+1 indent) and a method (+1 indent) and switch-block (+1 indent) in your code. If you now start to create further nested code, you have about 5-7 indents and it is hard to track your code. Not only because half of your screen is blank and you have to scroll vertically to see the rest of the line, sometimes the error-handling is several dozen lines behind the original statement that caused the error.

Ever needed some help when calculating a subnetmask or a broadcast address? Then this one is your friend!

Neither phpmyadmin nor MySQL Query Browser is able to load a CSV file directly into a DB. As this is a frequent issue, i wrote an import script.