Symfony Blog

What framework are you using for your PHP work? If you aren't using a framework (because your work doesn't need one), then switching languages probably isn't going to change much, but if you are, there are several good, fun PHP frameworks out there. The best PHP framework I've used is Symfony (http://www.symfony-project.org/), which is actively developed, fun to work with, and really powerful.

Here's what i would like to say on your pros and cons list. P: 1. open source code is exposed to the whole bunch of users doesn't necessarily mean the code will end up unsecured, let's take it as we get lots of contributor around to find and patch those security holes. 2. once you get working with PHP frameworks understanding the code will be easy. 3. why not bother looking at the framework code if you get benefits on every work onwards? C: 1. Most of the frameworks follow MVC separation, understanding that takes time, once you get the idea, writing code and using your existing code as plugins/libraries to the framework will be super easy. 2. The whole community is contributing, it will just take few posts in community forums or few minutes of googling to find the feature you are looking for. if you ended up coding the feature yourself, give it back to community. that is how you become part of the community and how the frameworks grow. In situation when you need to hire someone to work on your codebase, use of available opensource frameworks will save a lot. i will suggest any one of these frameworks to work with: https://github.com/tylerhall/simple-php-framework (structured code) http://codeigniter.com (easy to start with, very good documentation) http://www.symfony-project.org/ (nice documentation yet steep learning curve, once you get it as easy as CodeIgniter) i personally appreciate your approach too, that is a lot of effort you put there, but if you don't feel…

When I started learning PHP, after basic tutorials of PHP, I jumped on MVC framework called Symfony (http://symfony-project.org/). It's a great framework and the documentation is really extensive with some basic examples as well. You might wonder isn't starting with MVC was more extensive, but here are the adavantages I found - 1. MVC helped me to automate many things, so it was faster productivity 2. It showed me how to organize and structure the code 3. Though initially it kept details unknown from me, it was good because it didn't baffle me a lot initially. Once I started get going with my actual application, I started reading more details of PHP as on when required. But MVC helped to accelerate my process of building the real thing instead of investing of time in reading tutorials. Also, I found these tutorials are good for plain PHP - http://www.phpro.org/tutorials/ . It also explains the MVC and all. So you might want to read these tutorials, and then start with Symfony. I hope this helps.

Disclaimer: I am working for a shop with much PHP knowledge. There are some really nice frameworks for PHP - for example we are using Yii (http://www.yiiframework.com/), Symfony (http://www.symfony-project.org/) and Flow3 (http://flow3.typo3.org/). I was using Yii in one of my projects and it worked really nice (altough I can't compare it to Rails or Django, because I have no experience with those).

it's been awhile since I've done much with PHP,so I thought this was symfony...are these two CMS/frameworks related? http://www.symfony-project.org/

Have a play around with a framework such as Symfony [1]. That's the most natural way of learning a better style of PHP web development. [1] http://www.symfony-project.org/

Ever used Delicious.com, Yahoo! Answers or Yahoo! Bookmarks? Then you've used a site built on the Symfony MVC framework. Make sure you check that out as well. http://www.symfony-project.org/

Hey, the mention of "Symphony" for PHP - is that symfony (http://www.symfony-project.org/) or really Symphony (http://symphony-cms.com/)? They both look kinda cool. I was able to disambiguate Django really easily, though, fwiw.

check out the symfony framework for php - http://www.symfony-project.org/ It has MVC architecture, is decently fast, and has an active community behind it.

The original commenter might have their own thoughts, but after using both Symfony and Django here are mine: - A well organized, much more cohesive plugin structure: http://www.symfony-project.org/plugins/ Plugins are versioned with compatibility matrices for each major Symfony release, and indexed in a centralized location. - Much better extensibility of both framework and plugin classes. You can easily subclass any existing model class to customize to your needs. Django is severely lacking here (e.g. customizing auth.User to accept an email based login without breaking existing apps that rely on auth.User). - Much better customizability of the admin interface. - Very powerful model level validation. This isn't Symfony so much as Doctrine, which is the best PHP ORM I've ever worked with. - symfony project:deploy production is pretty sweet. Of course, in general, I still prefer Django to Symfony. - PHP as a language is so unexpressive that Symfony has resorted to using YAML files and code generation to represent configuration data and model objects. - The code generation gets a bit unwieldy at times (tons of classes and empty subclasses). - Frankly, if your language is so verbose that you end up needing to store your data in a different format (e.g. YAML and PHP, XML and Java), you're using the wrong language. - Jinja2 is also a much nicer templating language than straight PHP.

I agree with this sentiment completely. 12 months ago, I can safely say that my experience with PHP had been a simple modification of an ExtJS application and me screwing around with my Delicious bookmarks and the Yahoo BOSS API (both of these took more than a day to complete and I was very upset with life). I decided that I should learn how to actually create working websites and over the Winter Intercession, I looked at the various frameworks. Being on a Mac, I looked long and hard at Ruby on Rails, but something about it's syntax irked me. In hindsight, it shouldn't have as my only experience had been with Java and other related OOP languages, but oh well. I next looked at Zend, as many of the apps I developed for (Joomla, WordPress etc) were PHP apps, and therefore it made sense to go with what the Zend Engine people created. It took all of 2 minutes to realize that it would take me HOURS to figure out how to setup a basic MVC package. Not to mention a friend had used Zend in a previous project of ours - I developed the frontend in ExtJS, he the backend API - and was thoroughly upset with it. I moved on to CodeIgniter and Kohana and thought it was great... except that it required that I specify a lot. I hate specifying things. Love automagic. From there, it was Symfony, but it's application tutorial was too big and confusing for a PHP-noob like me (http://www.symfony-project.org/jobeet/1_4/Doctrine/en/). I think I just didn't give it enough of a chance. Then I read…

Edit: Rather than fighting with escaping code in HN, here are scripts to setup symfony and tornado examples: http://gist.github.com/275785 The symfony one requires some more loving to the apache setup which is well documented (http://www.symfony-project.org/getting-started/1_4/en/05-Web-Server-Co… The script suggests the frontend_dev.php to make sure things are set up right but for actual performance benchmarking you'll have to tweak your apache.

install xampp or lampp and start coding, you might want to do jobeet from http://www.symfony-project.org/jobeet/1_2/Doctrine/en/

Impressive resume on Symfony. I think Symfony powers all of Delicious http://www.symfony-project.org/blog/2007/10/02/delicious-preview-built…