Symfony upgrade from 2.0 to current version - json

I got a site using Symfony 2.0 and want to upgrade it to last version of Symfony (2.4 from what I see on github).
I have already done one step: upgrade to 2.1. I fixed all issues and now I am ready to upgrade to 2.2 (I am not sure I could go to the current version directly). From my understanding, to do so, I need to retrieve the composer.json on github and add my own dependencies (only one). Is that right?
I tried to do it and it failed. Furthermore Symfony folder under vendor is empty after this attempt. I checked the composer.json for 2.2 and I do not see any symfony specified in it. Did I miss something?
Any help would be more than welcome :o)

ok the problem was only due to the fact that I was getting the composer.json from the wrong github repository. Be sure to use the one from the symfony-standard repository.

You can update from Symfony 2.0 to Symfony 2.4 directly. And yes, for it you need original composer.json file of Symfony 2.4 in symfony/symfony-standard repository and add to it your own dependencies if you have

Related

Yii2 Upgrade version step by step

Im trying upgrade from version Yii 2.0.13 to the last version (2.0.23), but step by step, now need upgrade to 2.0.14 and next to 2.0.15 etc..
I follow the instructions in documentation and use this command, but the app upgrade automatically to the last version 2.0.23
composer require "yiisoft/yii2:~2.0.14" --update-with-dependencies
you have "~" before "2.0.14" which tells composer to use a newer version up to but not including 3.0
do
composer require "yiisoft/yii2:2.0.14" --update-with-dependencies
instead
source: https://getcomposer.org/doc/articles/versions.md
You don't need to upgrade step by step, you can upgrade Yii directly from 2.0.13 to 2.0.23. You need to follow all upgrade instructions for all versions between 2.0.13 and 2.0.23, but no need to install all versions between - you can install 2.0.23 directly and make all necessary upgrade changes in one step. This usually gives you less work and possible problems.

Error: Class MigrationShell could not be loaded (Cakephp -3.0 )

I am using cakephp 3.0 and i am facing problem while installing migration plugin..i am following the steps mentioned below
Installation - First get the plugin!
$:~/public_html/cakephp3/myCakeApp/plugins$ git clone git://github.com/CakeDC/migrations.git
Add the following to app/Config/bootstrap.php
CakePlugin::load('Migrations');
now next installation part is given in documentation as(may be this part may work for cakephp 2.x)
$ app/Console/cake
Available Shells:
migration [Migrations]
i am not getting this part and also don't know how to load MigrationShell in cakephp 3.. Can anybody help me out please??
CakePHP 3 comes with its own migrations plugin. Create a fresh CakePHP 3 project and you will be able to execute bin/cake migrations
You can read the documentation of the official migrations plugin in this page:
https://github.com/cakephp/migrations

Install Laravel 5 on Openshift - gives blank page

I installed Laravel 5 on Openshift via Git. Hitting my app (the clean install) in a browser returns a blank page. Any idea what could be the cause?
Here is the URL: http://dev-rogercreasy.rhcloud.com/
Looks like you have old composer. I had the same error. To fix it go to your php dir and update composer.
In my case I gone to folder where placed my php.exe and ran command composer self-update:
cd d:\work\OpenServer\modules\php\PHP-5.5>D:\work\OpenServer\modules\php\PHP-5.5\
composer self-update
After it I gone back to folder with project and composer install command completed without any errors.
Check out the Laravel 5 QuickStart. The QuickStart uses a custom version of the standard OpenShift PHP 5.4 cartridge. The only difference is the included version of Composer has been updated.

ZBXNEXT-245 2.2 issue

I am trying to do this patch to the 2.2 version of zabbix, but i dont know to apply the patch to the frontends version 2.2 because there are differents .php elements that what are indicated for modify in the patch.
The url of the patch: https://support.zabbix.com/browse/ZBXNEXT-245
I really need this improvement to my front-ends, can anyone say me if is possible to apply this patch in zabbix 2.2, and how to proceed?
Thank you a lot.
You need some dev work, because you want to apply patch for Zabbix 1.8 to Zabbix 2.2 -> difference is two major releases.

Spring 3 MVC on JBoss 5.1: ConflictingBeanDefinitionException

When I try to deploy my application on JBoss 5.1 Spring 3 MVC throw me this stack trace: http://pastebin.com/Aah386PJ
Telling me that I have two definition of the same bean in two different packages. The thing is I don't have this IntershipConfigurationController in the controller package, but I have it in controller.internshipConfiguration. I previously add it under the root of controller but I deleted it from SVN and it doesn't appear anymore in the tree.
I cleaned JBoss, Eclipse's project, tried to redeploy it, to restart JBoss, Eclipse, etc. but I can't get this project working while my mates with the same repository can run it with no issue.
I don't know what to do this is really annoying.
I know this can be frustrating sometimes but you might want to know why this could happen. Spring annotation based ant path matcher checks for the class-path with a URI pattern to search for controllers or components. In your case the class-path either has a jar having the previous version of your class or some referencing .class file in your build path.
Make sure you have your project cleaned up and if possible disconnect
from SVN and download the project again.
You could also try CTRL+SHIFT+T to see if your controller is
referenced from any other library.
I finally deleted my JBoss folder, removed the projects from JBoss in Eclipse, extract a proper JBoss, made a clean on JBoss in Eclipse and then redeployed my projects and it's now working.
Nonetheless it's a really strange issue...
Edit :
It was in fact because the build folder at the root of my project was versioned and the old classes were still present.
Now the folder is ignored and removed from the SVN and I've deleted the old classes from my FS.