There are a few different methods you can use if you’d like to hide created_at and updated_at columns from your generated forms.
The first way, and the easiest, is to simply unset the fields in your form class:
More…
There are a few different methods you can use if you’d like to hide created_at and updated_at columns from your generated forms.
The first way, and the easiest, is to simply unset the fields in your form class:
More…
Here are the required modifications for to a form class that contains a file upload field in symfony 1.2 using doctrine (and it probably works with propel, too).
More…
I recently discovered a quick way to edit the rsync parameters used when executing the symfony sync command with symfony 1.0. More…
I’m working on a plugin for symfony 1.0 and am really enjoying this workflow. Yes, symfony 1.0 is 4 versions old and should not be used for new projects.
With the help of the sfPropelMigrationsLightPlugin plugin, one of my favorites, I have been rapidly making changes to my plugin schema and adding new data to the database over and over again while I mock things up.
Here is the workflow:
More…
Symfony has a ton of documentation available online. The only problem is, with so many different versions (1.0 – 1.4) in the wild, it can be hard to locate exactly the right resource when you need it. Below is a simple and straightforward list of the most useful documentation:
Two good friends of mine just launched a new site dedicated to providing professional help to symfony developers.
The site is very well designed and will prove to be a valuable resource for developers of all skill levels — experts can make some extra money sharing their expertise, and beginners (or experts encountering a new problem) can get quick and succinct answers to their questions.
More…
I was trying to use the symfony command line tools to rebuild my test database and I couldn’t get past this error: More…
After setting up a simple file upload using the symfony 1.2 forms class and a doctrine model, I hit this error right away:
500 | Internal Server Error | Doctrine_Validator_Exception 1 field had validation error: * 1 validator failed on file (type)
The short solution: when using a doctrine form class and $form->save(), set the path option in your sfValidatorFile validator and do not attempt to save/set the file column yourself. If you are curious why this is, continue reading. More…
Speedup: Profile your symfony app using Xdebug – Web Mozarts.
Haven’t tried this but hope to, soon!
Here is the basic process we use to get a new developer started on a symfony project. This flow assumes you already have created your symfony project and it checked into an svn repository somewhere, and that the developer is on a mac. More…