How do you recommend to upgrade from Symfony from 2.1 to 4.0
I have a project that is on Symfony 2.1 and need to upgrade to 4.0
Do you know how is the best way?
Can I just upgrade from 2.1 to 4.0 directly? or is better to migrate first from 2.1 to 3.0 and then 4.0...
Do you know what's teh best way?
Thanks so much!
symfony
add a comment |
I have a project that is on Symfony 2.1 and need to upgrade to 4.0
Do you know how is the best way?
Can I just upgrade from 2.1 to 4.0 directly? or is better to migrate first from 2.1 to 3.0 and then 4.0...
Do you know what's teh best way?
Thanks so much!
symfony
add a comment |
I have a project that is on Symfony 2.1 and need to upgrade to 4.0
Do you know how is the best way?
Can I just upgrade from 2.1 to 4.0 directly? or is better to migrate first from 2.1 to 3.0 and then 4.0...
Do you know what's teh best way?
Thanks so much!
symfony
I have a project that is on Symfony 2.1 and need to upgrade to 4.0
Do you know how is the best way?
Can I just upgrade from 2.1 to 4.0 directly? or is better to migrate first from 2.1 to 3.0 and then 4.0...
Do you know what's teh best way?
Thanks so much!
symfony
symfony
asked Nov 12 '18 at 20:14
user10642659user10642659
112
112
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
You should not upgrade directly. Instead upgrade to 2.8 first, fix all deprecations using a tool like deprecation-detector. You might want to do this in smaller steps. There were quite a few deprecations and even some BC-breaks back then, especially around the form component, and reading the changelogs between versions is important to keep track of these changes. This doesn't sound like much, but it can already be a very tedious task, but it's worth it.
Once you have moved to 2.8 you can make the switch to Symfony 3.4, again fix all deprecations. There was one security related BC-break, that's easy to fix. Other than that upgrading from 2.8 to 3.4 should be easier than upgrading to 2.8.
From 3.3 on there is a persisted deprecation log you can use to fix all deprecations introduced during the minor releases. When you make it to 3.4 you are fine for a while. This is a long term support-version, so you will not require major updates until next year.
4.0 does not receive bug fixes and security fixes are only available until January 2019, so if you want to switch to the next major version I suggest going to 4.2 and then keep updating regularly (every 6 months when a new minor release comes out). If this sounds like too much of a hassle, I recommend staying on 3.4 for a while and then upgrade to the next LTS release using the same steps as above.
Especially when upgrading Symfony 3.4 to 4.x you could also look at a tool called rector which can do automatic upgrades for you. As far as I can tell it does not support all changes that happened, but it will at least make some of the deprecation-changes easier by automating them for you.
edit: Also keep in mind that when you upgrade you will also have to upgrade the bundles you use and some of them might not even support 3.x or 4.x. Addressing those by either doing the manual config changes or replacing them is probably the most annoying bit of the work. Using composer why
and composer why-not
to figure out why composer won't upgrade certain packages or even Symfony itself will be very useful.
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
add a comment |
Thanks for replying back. I'll try yo start upgrading to 2.8.0 first, but there are a lot of conflicts of versions in my composer.json, currently I have this:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.",
"twig/extensions": "1.0.@dev",
"symfony/assetic-bundle": "2.1.",
"symfony/swiftmailer-bundle": "2.1.",
"symfony/monolog-bundle": "2.1.",
"sensio/distribution-bundle": "2.1.",
"sensio/framework-extra-bundle": "2.1.",
"sensio/generator-bundle": "2.1.",
"jms/security-extra-bundle": "1.2.",
"jms/di-extra-bundle": "1.1.",
"kriswallsmith/assetic": "1.1.@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
Do you know if there is a way to know which versions shoukd I have to put after require section? Thanks!
add a comment |
Sorry, sending the composer.json code again:
{
"name": "symfony/framework-standard-edition",
"description": "The "Symfony Standard Edition" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*@dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269433%2fhow-do-you-recommend-to-upgrade-from-symfony-from-2-1-to-4-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should not upgrade directly. Instead upgrade to 2.8 first, fix all deprecations using a tool like deprecation-detector. You might want to do this in smaller steps. There were quite a few deprecations and even some BC-breaks back then, especially around the form component, and reading the changelogs between versions is important to keep track of these changes. This doesn't sound like much, but it can already be a very tedious task, but it's worth it.
Once you have moved to 2.8 you can make the switch to Symfony 3.4, again fix all deprecations. There was one security related BC-break, that's easy to fix. Other than that upgrading from 2.8 to 3.4 should be easier than upgrading to 2.8.
From 3.3 on there is a persisted deprecation log you can use to fix all deprecations introduced during the minor releases. When you make it to 3.4 you are fine for a while. This is a long term support-version, so you will not require major updates until next year.
4.0 does not receive bug fixes and security fixes are only available until January 2019, so if you want to switch to the next major version I suggest going to 4.2 and then keep updating regularly (every 6 months when a new minor release comes out). If this sounds like too much of a hassle, I recommend staying on 3.4 for a while and then upgrade to the next LTS release using the same steps as above.
Especially when upgrading Symfony 3.4 to 4.x you could also look at a tool called rector which can do automatic upgrades for you. As far as I can tell it does not support all changes that happened, but it will at least make some of the deprecation-changes easier by automating them for you.
edit: Also keep in mind that when you upgrade you will also have to upgrade the bundles you use and some of them might not even support 3.x or 4.x. Addressing those by either doing the manual config changes or replacing them is probably the most annoying bit of the work. Using composer why
and composer why-not
to figure out why composer won't upgrade certain packages or even Symfony itself will be very useful.
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
add a comment |
You should not upgrade directly. Instead upgrade to 2.8 first, fix all deprecations using a tool like deprecation-detector. You might want to do this in smaller steps. There were quite a few deprecations and even some BC-breaks back then, especially around the form component, and reading the changelogs between versions is important to keep track of these changes. This doesn't sound like much, but it can already be a very tedious task, but it's worth it.
Once you have moved to 2.8 you can make the switch to Symfony 3.4, again fix all deprecations. There was one security related BC-break, that's easy to fix. Other than that upgrading from 2.8 to 3.4 should be easier than upgrading to 2.8.
From 3.3 on there is a persisted deprecation log you can use to fix all deprecations introduced during the minor releases. When you make it to 3.4 you are fine for a while. This is a long term support-version, so you will not require major updates until next year.
4.0 does not receive bug fixes and security fixes are only available until January 2019, so if you want to switch to the next major version I suggest going to 4.2 and then keep updating regularly (every 6 months when a new minor release comes out). If this sounds like too much of a hassle, I recommend staying on 3.4 for a while and then upgrade to the next LTS release using the same steps as above.
Especially when upgrading Symfony 3.4 to 4.x you could also look at a tool called rector which can do automatic upgrades for you. As far as I can tell it does not support all changes that happened, but it will at least make some of the deprecation-changes easier by automating them for you.
edit: Also keep in mind that when you upgrade you will also have to upgrade the bundles you use and some of them might not even support 3.x or 4.x. Addressing those by either doing the manual config changes or replacing them is probably the most annoying bit of the work. Using composer why
and composer why-not
to figure out why composer won't upgrade certain packages or even Symfony itself will be very useful.
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
add a comment |
You should not upgrade directly. Instead upgrade to 2.8 first, fix all deprecations using a tool like deprecation-detector. You might want to do this in smaller steps. There were quite a few deprecations and even some BC-breaks back then, especially around the form component, and reading the changelogs between versions is important to keep track of these changes. This doesn't sound like much, but it can already be a very tedious task, but it's worth it.
Once you have moved to 2.8 you can make the switch to Symfony 3.4, again fix all deprecations. There was one security related BC-break, that's easy to fix. Other than that upgrading from 2.8 to 3.4 should be easier than upgrading to 2.8.
From 3.3 on there is a persisted deprecation log you can use to fix all deprecations introduced during the minor releases. When you make it to 3.4 you are fine for a while. This is a long term support-version, so you will not require major updates until next year.
4.0 does not receive bug fixes and security fixes are only available until January 2019, so if you want to switch to the next major version I suggest going to 4.2 and then keep updating regularly (every 6 months when a new minor release comes out). If this sounds like too much of a hassle, I recommend staying on 3.4 for a while and then upgrade to the next LTS release using the same steps as above.
Especially when upgrading Symfony 3.4 to 4.x you could also look at a tool called rector which can do automatic upgrades for you. As far as I can tell it does not support all changes that happened, but it will at least make some of the deprecation-changes easier by automating them for you.
edit: Also keep in mind that when you upgrade you will also have to upgrade the bundles you use and some of them might not even support 3.x or 4.x. Addressing those by either doing the manual config changes or replacing them is probably the most annoying bit of the work. Using composer why
and composer why-not
to figure out why composer won't upgrade certain packages or even Symfony itself will be very useful.
You should not upgrade directly. Instead upgrade to 2.8 first, fix all deprecations using a tool like deprecation-detector. You might want to do this in smaller steps. There were quite a few deprecations and even some BC-breaks back then, especially around the form component, and reading the changelogs between versions is important to keep track of these changes. This doesn't sound like much, but it can already be a very tedious task, but it's worth it.
Once you have moved to 2.8 you can make the switch to Symfony 3.4, again fix all deprecations. There was one security related BC-break, that's easy to fix. Other than that upgrading from 2.8 to 3.4 should be easier than upgrading to 2.8.
From 3.3 on there is a persisted deprecation log you can use to fix all deprecations introduced during the minor releases. When you make it to 3.4 you are fine for a while. This is a long term support-version, so you will not require major updates until next year.
4.0 does not receive bug fixes and security fixes are only available until January 2019, so if you want to switch to the next major version I suggest going to 4.2 and then keep updating regularly (every 6 months when a new minor release comes out). If this sounds like too much of a hassle, I recommend staying on 3.4 for a while and then upgrade to the next LTS release using the same steps as above.
Especially when upgrading Symfony 3.4 to 4.x you could also look at a tool called rector which can do automatic upgrades for you. As far as I can tell it does not support all changes that happened, but it will at least make some of the deprecation-changes easier by automating them for you.
edit: Also keep in mind that when you upgrade you will also have to upgrade the bundles you use and some of them might not even support 3.x or 4.x. Addressing those by either doing the manual config changes or replacing them is probably the most annoying bit of the work. Using composer why
and composer why-not
to figure out why composer won't upgrade certain packages or even Symfony itself will be very useful.
edited Nov 12 '18 at 20:43
answered Nov 12 '18 at 20:38
dbrumanndbrumann
9,31611940
9,31611940
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
add a comment |
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
2
2
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
Wow, thanks for mentioning Rector. I'm glad it starts helping people
– Tomáš Votruba
Nov 12 '18 at 21:01
add a comment |
Thanks for replying back. I'll try yo start upgrading to 2.8.0 first, but there are a lot of conflicts of versions in my composer.json, currently I have this:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.",
"twig/extensions": "1.0.@dev",
"symfony/assetic-bundle": "2.1.",
"symfony/swiftmailer-bundle": "2.1.",
"symfony/monolog-bundle": "2.1.",
"sensio/distribution-bundle": "2.1.",
"sensio/framework-extra-bundle": "2.1.",
"sensio/generator-bundle": "2.1.",
"jms/security-extra-bundle": "1.2.",
"jms/di-extra-bundle": "1.1.",
"kriswallsmith/assetic": "1.1.@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
Do you know if there is a way to know which versions shoukd I have to put after require section? Thanks!
add a comment |
Thanks for replying back. I'll try yo start upgrading to 2.8.0 first, but there are a lot of conflicts of versions in my composer.json, currently I have this:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.",
"twig/extensions": "1.0.@dev",
"symfony/assetic-bundle": "2.1.",
"symfony/swiftmailer-bundle": "2.1.",
"symfony/monolog-bundle": "2.1.",
"sensio/distribution-bundle": "2.1.",
"sensio/framework-extra-bundle": "2.1.",
"sensio/generator-bundle": "2.1.",
"jms/security-extra-bundle": "1.2.",
"jms/di-extra-bundle": "1.1.",
"kriswallsmith/assetic": "1.1.@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
Do you know if there is a way to know which versions shoukd I have to put after require section? Thanks!
add a comment |
Thanks for replying back. I'll try yo start upgrading to 2.8.0 first, but there are a lot of conflicts of versions in my composer.json, currently I have this:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.",
"twig/extensions": "1.0.@dev",
"symfony/assetic-bundle": "2.1.",
"symfony/swiftmailer-bundle": "2.1.",
"symfony/monolog-bundle": "2.1.",
"sensio/distribution-bundle": "2.1.",
"sensio/framework-extra-bundle": "2.1.",
"sensio/generator-bundle": "2.1.",
"jms/security-extra-bundle": "1.2.",
"jms/di-extra-bundle": "1.1.",
"kriswallsmith/assetic": "1.1.@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
Do you know if there is a way to know which versions shoukd I have to put after require section? Thanks!
Thanks for replying back. I'll try yo start upgrading to 2.8.0 first, but there are a lot of conflicts of versions in my composer.json, currently I have this:
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.",
"twig/extensions": "1.0.@dev",
"symfony/assetic-bundle": "2.1.",
"symfony/swiftmailer-bundle": "2.1.",
"symfony/monolog-bundle": "2.1.",
"sensio/distribution-bundle": "2.1.",
"sensio/framework-extra-bundle": "2.1.",
"sensio/generator-bundle": "2.1.",
"jms/security-extra-bundle": "1.2.",
"jms/di-extra-bundle": "1.1.",
"kriswallsmith/assetic": "1.1.@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"SensioBundleDistributionBundleComposerScriptHandler::buildBootstrap",
"SensioBundleDistributionBundleComposerScriptHandler::clearCache",
"SensioBundleDistributionBundleComposerScriptHandler::installAssets",
"SensioBundleDistributionBundleComposerScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
Do you know if there is a way to know which versions shoukd I have to put after require section? Thanks!
answered Nov 14 '18 at 20:46
user10642659user10642659
112
112
add a comment |
add a comment |
Sorry, sending the composer.json code again:
{
"name": "symfony/framework-standard-edition",
"description": "The "Symfony Standard Edition" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*@dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
add a comment |
Sorry, sending the composer.json code again:
{
"name": "symfony/framework-standard-edition",
"description": "The "Symfony Standard Edition" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*@dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
add a comment |
Sorry, sending the composer.json code again:
{
"name": "symfony/framework-standard-edition",
"description": "The "Symfony Standard Edition" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*@dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
Sorry, sending the composer.json code again:
{
"name": "symfony/framework-standard-edition",
"description": "The "Symfony Standard Edition" distribution",
"autoload": {
"psr-0": { "": "src/" }
},
"require": {
"php": ">=5.3.3",
"symfony/symfony": "2.1.*",
"doctrine/orm": ">=2.2.3,<2.4-dev",
"doctrine/doctrine-bundle": "1.0.*",
"twig/extensions": "1.0.*@dev",
"symfony/assetic-bundle": "2.1.*",
"symfony/swiftmailer-bundle": "2.1.*",
"symfony/monolog-bundle": "2.1.*",
"sensio/distribution-bundle": "2.1.*",
"sensio/framework-extra-bundle": "2.1.*",
"sensio/generator-bundle": "2.1.*",
"jms/security-extra-bundle": "1.2.*",
"jms/di-extra-bundle": "1.1.*",
"kriswallsmith/assetic": "1.1.*@dev",
"hearsay/require-js-bundle":"*",
"symfony/options-resolver": "2.6",
"wsdl2phpgenerator/wsdl2phpgenerator": "3.3"
},
"scripts": {
"post-install-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
],
"post-update-cmd": [
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installAssets",
"Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::installRequirementsFile"
]
},
"extra": {
"symfony-app-dir": "app",
"symfony-web-dir": "web"
}
}
answered Nov 14 '18 at 20:53
user10642659user10642659
112
112
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53269433%2fhow-do-you-recommend-to-upgrade-from-symfony-from-2-1-to-4-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown