We are about to start a project and we believe Symfony framework will make our work easier considering our requirements. Our problem is we don't know whether to start our project in Symfony 2.0x or in Symfony 1.4. My choice would be to start with upgraded version only, but we could not find detailed documentation for symfony 2.0x.
Which is better to use?
If I use Symfony 1.4, can I upgrade to 2.0x easily?
What are the major differences between Symfony 1.4 and Symfony 2.0?
I suggest using 2.0x for the following reasons:
2.0x is stable and the newest version.
the doc is getting bigger every day and there is much going on on the mailinglist.
upgrading from 1.4 to 2.0x not possible.
Related
I have a cakephp website on 2.6 and want to run it on php 7. Will it work if I upgrade cakephp to 2.8?
I have shared server therefore I cannot have php 5.*.
Requirements
Here are the Requirements for running CakePHP 2.x
As longs as you have those you should be fine.
Migration Guide 2.6 -> 2.8
More about PHP7 Compatibility
And make sure you read this migration guide here
2.7
2.8
There are no breaking changes, but still worth a read.
I would like know if there is a method for detecting compatibility of symfony packages for symfony version?
I would like to upgrade symfony from 2.8 to 3.4.
Example: if sonata/userbundle is compatible with symfony 3.4.
For upgrading major versions follow this guide,
for specific incompatibilities and replacements look at this page.
Most of the work is handled by composer, but you will still need to replace deprecated functions and approaches.
I have started with symfony 3.2 project, then changed version in composer to 2.8 (which is long term support).
Problem is that folders structure still remains 3.2 project. Is there any way to change (not manually) folders structure to 2.8?
Of course you can downgrade. You might choose the old Symfony2 directory structure (deprecated) or keeping the current Symfony3 structure.
In either ways, please take a look at How to Override Symfony's Directory Structure.
Using the Symfony3 directory structure
If you choose to use the Symfony3 structure, it's easy as following up this article about upgrading from Symfony2 to Symfony3's directory structure.
Using the Symfony2 directory structure
First you'll have to rename and move some files (like var/cache/, var/logs/, etc.). Afterwards you'll have to change the autoloading file in app/autoload.php (formerly var/autoload.php which you must move too).
Basically it's the same in reverse order like upgrading from Symfony2 to Symfony3 (mentioned above).
Please be aware that Symfony 3.4 (next LTS) will be released in November 2017, so in my opinion it's not worth to downgrade, and then re-upgrade. Upgrading from 3.2 to 3.4 will be small and fast, Upgrading from 2.8 to 3.4 could be much more to do ...
At work we use Symfony 1.3 and I want to upgrade to the latest version of symfony.
I saw this article:
symfony upgrade 1.4
That's a upgrade from 1.3 to 1.4 not verry helfull.
Can I download the latest symfony and create a new project and copy the folders from 1.3 like app, web, lib, config etc etc to my new version?
Ralph
There are quite a few differences between symfony1 and symfony2
You can read about the differences between the 2 on the How Symfony2 Differs from Symfony1 docs page
I am trying to update my project written in Symfony 2.0 into Symfony 2.2.
Moving source codes into 2.2 project ended with config.yml and security.yml incompatibiliy.
Is there way how to properly migrate Symfony 2.0 project into Symfony 2.2?
It better to wait until Symfony 2.3 before migrating. It will be released somewhere in May. It's the first LTS (Long Time Support) release, meaning that it's maintained for three years. So: You don't have to worry about BC breaks for 3 years!
For the migrating of Symfony 2.0 to 2.3: There is nothing you can do. Read the UPGRADE-*.md files (which are stored in the root of the symfony/symfony package) and fix anything that is in their in your code. Every BC break that's important for normal users will be put in those UPGRADE files.
If you can't solve it after the fixing everything in the UPGRADE files, you should take a look at the CHANGELOG.md files in the root of the package (e.g. the symfony/security package). Try to find something that is changed and cause your code to break.
Finally, if you don't get your script working, there are a lot of active Symfony2 users who are waiting to help you. Take a look at the community page and find your place to ask questions.