Archived

forked from https://github.com/symfony/symfony

This repository has been archived on 2023-08-20. You can view files and clone it, but cannot push or open issues or pull requests.

Go to file

Fabien Potencier 4790a5e43f merged branch Gregwar/proxy_file_issue (PR #1968 ) Commits ------- `0e00e3f` [DoctrineBundle] CS `0c4b793` [DoctrineBundle] Fixed performances issues on "On-demand" proxy file generation `e866a67` [DoctrineBundle] Tries to auto-generate the missing proxy files on the autoloader Discussion ---------- [DoctrineBundle] Tries to auto-generate the missing proxy files on the autoloaded See: https://github.com/symfony/symfony/issues/1965 https://github.com/symfony/symfony/issues/1535 This fix is not really clean and there's maybe a factorizing work to do on it, but this work and avoid me spending my day deleting session cookies each time I clear cache. --------------------------------------------------------------------------- by stloyd at 2011/08/23 10:37:28 -0700 You should follow Symfony2 CS (http://symfony.com/doc/current/contributing/code/standards.html). --------------------------------------------------------------------------- by ruudk at 2011/09/26 02:50:13 -0700 +1 --------------------------------------------------------------------------- by fabpot at 2011/09/27 07:01:51 -0700 It looks like a bug fix, so this PR should be closed and a new one based on the 2.0 branch should be open. @beberlei: are you fine with this patch? --------------------------------------------------------------------------- by beberlei at 2011/09/29 04:24:22 -0700 What is this for? I dont understand the bug and the solution here screams cache slam. --------------------------------------------------------------------------- by beberlei at 2011/09/29 04:34:02 -0700 Ok i get the problem but the solution is still a monsterous hack. Can we find a real solution to the problem? There has to be one. --------------------------------------------------------------------------- by Gregwar at 2011/09/29 04:34:25 -0700 @beberlei, when an user is authenticated for instance, there can be proxies serialized in session. Si if you clear the cache in dev environment you'll get an error because the matching proxy classes won't exist and you'll be forced to clear your cookies and reauth, which can be annoying --------------------------------------------------------------------------- by Gregwar at 2011/09/29 04:38:45 -0700 @beberlei, yes, I agree that we should do something more elegant, but the problem is that when PHP "meet" the proxy class we can't really know what was the "original" class it is supposed to extend And as @schmittjoh said, this will only be executed very rarely --------------------------------------------------------------------------- by beberlei at 2011/09/29 05:18:35 -0700 You agree you want something more suitable and still want this to be merged? To ease the immediate pain wr could allow this however only in debug mode. A real solution here is maybe to move the proxy files out of the env folders. Rhey dont depend ont the env after all. --------------------------------------------------------------------------- by stloyd at 2011/09/29 05:21:33 -0700 Proxy is not depending on env, but generation of proxy is... So this solution will be hard IMO, or even unacceptable... --------------------------------------------------------------------------- by Gregwar at 2011/09/29 05:25:39 -0700 @beberlei what I meant is that I agree that's dirty but I don't think of anything better to solve this... --------------------------------------------------------------------------- by fabpot at 2011/09/29 06:23:03 -0700 Even if the current patch is not the best solution, we should probably apply it to fix the problem and think about a better solution afterwards. Does it sound good for everybody?		2011-09-30 18:07:40 +02:00
src/Symfony	merged branch Gregwar/proxy_file_issue (PR #1968 )	2011-09-30 18:07:40 +02:00
tests	[Routing] fixed route overriden mechanism when using embedded collections (closes #2139 )	2011-09-30 12:01:46 +02:00
.gitignore	Added vendor directory to .gitignore	2010-06-24 10:44:28 +02:00
autoload.php.dist	fixed autoloader when tests are run on a machine without intl installed	2011-07-20 14:27:10 +02:00
CHANGELOG-2.0.md	updated CHANGELOG for 2.0.3	2011-09-25 11:50:40 +02:00
check_cs	fixed root search path to include only './src' and './tests'	2011-06-08 18:11:05 +02:00
composer.json	[composer] add composer.json	2011-09-27 00:55:43 +02:00
CONTRIBUTORS.md	update CONTRIBUTORS for 2.0.2	2011-09-25 10:26:33 +02:00
LICENSE	added the LICENSE file for the YAML component	2011-02-18 11:52:11 +01:00
phpunit.xml.dist	[Security] cleaned up opt-in to benchmark test	2011-03-06 20:06:13 +01:00
README.md	[README] Adding a small section with information about contributing.	2011-09-23 11:21:11 -05:00
UPDATE.ja.md	updated translation of UPDATE file (Japanese RC5 added)	2011-07-30 02:08:25 +09:00
UPDATE.md	updated UPDATE file	2011-07-22 17:45:02 +02:00
vendors.php	removed time limit for the vendors script (closes #2282 )	2011-09-28 08:30:05 +02:00

README.md

README

What is Symfony2?

Symfony2 is a PHP 5.3 full-stack web framework. It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP.

Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.

Requirements

Symfony2 is only supported on PHP 5.3.2 and up.

Installation

The best way to install Symfony2 is to download the Symfony Standard Edition available at http://symfony.com/download.

Documentation

The "Quick Tour" tutorial gives you a first feeling of the framework. If, like us, you think that Symfony2 can help speed up your development and take the quality of your work to the next level, read the official Symfony2 documentation.

Contributing

Symfony2 is an open source, community-driven project. If you'd like to contribute, please read the Contributing Code part of the documentation. If you're submitting a pull request, please follow the guidelines in the Submitting a Patch section.