I have old app. It based on CakePHP 2.0.5.
I want to upgrade it to current latest version, 2.2.5.
Is it enough to replace new lib folder with the old one? or application folder needs to be changed, too.
(checking changelogs for about 17 versions takes time a lot!!!)
I think I should read Cookbook:
first:
http://book.cakephp.org/2.0/en/appendices/2-1-migration-guide.html
then:
http://book.cakephp.org/2.0/en/appendices/2-2-migration-guide.html
Related
i have cakephp3.3 windows and i need to upgrade to cakephp3.6. Checking the docs i see there is no tool available. Checking the migration guides i am not seeing any issues with my code in cake3.3 with newer versions.
Do i simply create a new instance of cake3.6 and create models,controllers again using bake and then copy over code to see if this works? what is an efficient way
The docs in cakephp are not clear on this process. do i upgrade to 3.4 then 3.5,3.6?
https://book.cakephp.org/3.0/en/appendices/3-x-migration-guide.html
Use composer.
For Windows, you can download it from here. After installation, locate composer.json file in your CakePHP application directory, and look for "require" part, and update line regarding CakePHP as follows:
"require": {
"php": ">=5.6",
"cakephp/cakephp": "3.6.*",
....
}
Then, in command line, navigate to your CakePHP installation directory and fire composer update. After a while you should have your CakePHP upgraded.
More info about updating to new version can be found in docs:
Keeping up to date with latest CakePHP changes
Another solution was given which was to install a new instance of cakephp and just copy over scr folder and other relevant code in the new instance. This is more work but the conversion from 3.3 to 3.6 isnt very clean with a composer update
I want to start a project with Symfony3 and SonataAdmin
I was trying a lot of versions of symfony and sonataAdminBundle
But I always get errors when updating composer
What's the correct composer.json to start my project
thanks
According to packagist the current v3.3.1 of SonataAdminBundle should be compatible with Symfony ^3.0.
You can just run composer require sonata-project/admin-bundle and it will automatically look for the newest compatible version. If that fails you could try allowing development-versions as well.
composer require sonata-project/admin-bundle:dev-master
That should be your last resort though as it pulls in an unstable dependency. Feel free to add composer's error to your question and maybe I or someone else can give a more precise answer.
I need a way to figure out which files are left over after upgrading Moodle to a newer version.
I have:
Old version + many plugins
New version
Merged version
In the new version some files have been removed but they still exist in the merged version.
I could start with the new version and copy all the plugins but many are in different sub folders which will take too long.
Is there a quick way to list or delete these left over files?
I would create a clone of Moodle in a separate folder.
git clone git://git.moodle.org/moodle.git moodleclone
Then check the version of Moodle in /version.php in your code - look for $release = '2.x.x. Then checkout the exact version of the Moodle clone
cd moodleclone
git checkout v2.x.x
Then use Meld to compare the 2 folders. http://meldmerge.org/
meld ../moodleclone ../yourmoodleversion
This will then show any code differences between the 2. You can see if its an official Moodle plugin or one that has been added.
It would be better if you use the uninstall plugin option via site admin -> plugins because it should remove any data in your database too. You might also want to do a clean install in a new database using the Moodle clone, then dump and compare the database structure from the clone and your code to see if there are any database changes.
While adding support for the Windows 8 environment, I've hit a Cordova bug. The folders are being reported as files when I get the directory listing: https://issues.apache.org/jira/browse/CB-5774
I want to apply the patch in my project as I understand you cannot upgrade the Cordova version in a Worklight project.
I am using Worklight 6.1.0.
I figured out a way to patch (JavaScript patch).. I am sure this is not a permnant solution - but a adhoc one till the patched Cordova is available with a new version of Worklight.
In my case the bug was in FileProxy.js. I created a directory structure to mirror the location of the problem file and added the patched file there.(www\worklight\plugins\org.apache.cordova.file\src\windows8\FileProxy.js).
At build time the cordova files are copied first and then www contents are copied after... so my patched file overwrote the one with the bug.
I'm sure this is not a supported way by Worklight - but I am no longer blocked.
It is currently not possible to replace or patch the Cordova version that is being used in Worklight. In Worklight v6.1.0, Cordova v3.1 is used.
If you are an IBM customer or business partner you can open a PMR to see if an iFix can be produced that will contain a patched version of Cordova 3.1.
I have developed a project with cakephp-1.3.10 .
Now I want to upgrade it to cakephp-1.3.11.
What's the easiest process to upgrade from cakephp-1.3.10 to cakephp-1.3.11 ?
download the cake zip, unpack, delete the app folder, put your app folder in.
I'm sure you can't use composer! And there's a high cost in upgrading by a large jump between versions, meaning that you will end up with a lot of deprecated code.
I would go like:
complete backup
upload your app to a Github repository
tag your code
create a new branch
upload your new code
debug
merge branch
since you were just upgrading from 1.3.10 to 1.3.11 the simplest way would have been to download latest cakephp and then simply copy lib/ folder from the downloaded folder and replacing it with your existing cakephp/lib/ folder. I would prefer to download latest version from cakephp's official website https://cakephp.org/
Note- If you have to upgrade from 1.x to 3.x then you have to move from 1.x to 2.x and then 2.x to 3.x, direct migration from 1.x to 3.x is not possible