Symfony

Symfony is a neat little application framework for PHP. More information: http://www.symfony-project.com/

Notice: Array to string conversion sfToolkit.class.php on line 329

I got this problem when trying to implement a custom validator in the update.yml file. My solution was to split it up into a seperate named validator:

names:
  name_field:
    required:       yes
    required_msg:   A name must be entered
    validators:     [valid_name, valid_name_hyphen]

valid_name:
  class:       sfRegexValidator
  param:
    match:       Yes
    match_error: The name has invalid characters or is too short/long.
    pattern:     /^[a-z0-9\-]{2,63}$/im

valid_name_hyphen:
  class:       sfRegexValidator
  param:
    match:       No
    match_error: The name cannot start or end with a hyphen.
    pattern:     /^(-.+|.+-)$/im

Get the count of a column in Propel

The simplest solution is to just use the methods provided in the Propel model:

public function getArticles($criteria, $conn);
public function countArticles($criteria, $distinct, $conn);

Or, you can do it manually:

public function countArticles(...} {
  $criteria = new Criteria();
  $criteria->add(ArticlePeer::USER_ID, $this->getId());
  return ArticlePeer::doCount($criteria);
}

Global application variables

I wanted to share certain variables across multiple Symfony applications. My solution:

apps/myapp/config/config.php
Add to the end of this file, and to every other config.php file in your applications:

// load additional config
sfConfig::add(sfYaml::load(sfConfig::get('sf_config_dir').'/global.yml'));

config/global.yml
Create a new file here:

# global application variables
app_password_salt:    1234
app_email_sender:     bot@jevon.org

You can now access these variables like normal, e.g.

return sfConfig::get('app_password_salt');     // will return '1234'

However these variables will override other existing config variables. Things still left to do: Make it accept "normal" yaml structure; make it so that the config variables do not overwrite local settings.

OR: You can use settings.yml to create global settings with the sf_ prefix (read the end of this article).

Enabling Validation .yml for both GET and POST

Normally a myAction.yml file in the validate/ directory will only work on POST requests. You can change this to work on both GET and POST by adding this to your myAction.yml file:

methods:
  - get
  - post

fields:
  ... and so on

"[propel-sql-exec] SQLSTATE[HY000]: General error: 1005 Can't create table"

For more information on the error, you can log into MySQL as root and execute the command SHOW ENGINE INNODB STATUS:

------------------------
LATEST FOREIGN KEY ERROR
------------------------
110816 15:53:44 Error in foreign key constraint of table ticketsfmini/ticket:

 FOREIGN KEY (<code class="inline_code">event_id</code>)
 REFERENCES <code class="inline_code">event</code> (<code class="inline_code">id</code>)
 ON DELETE SET NULL,
 INDEX <code class="inline_code">ticket_FI_2</code> (<code class="inline_code">user_id</code>),
 CONSTRAINT <code class="inline_code">ticket_FK_2</code>
 FOREIGN KEY (<code class="inline_code">user_id</code>)
 REFERENCES <code class="inline_code">user</code> (<code class="inline_code">id</code>)
 ON DELETE SET NULL
 )Type=InnoDB:
You have defined a SET NULL condition though some of the
columns are defined as NOT NULL.

Here, this error was occuring because I was trying to create a table with two foreign key references with onDelete set to setnull... but nulls are not allowed, as defined by required:

event_id: { type: integer, foreignTable: event, foreignReference: id, required: true, onDelete: setnull }

Remove the "required: true" declaration and this error message will not appear.