I need a confirmation and your feedback about phpunit version.
In cakephp documention, the 8.5 release is suggested.
I have launched my tests with PHPUnit 9.5.21 and all seems to be OK, but perhaps there are some drawback I've did not seen ?
I use PHP 8.1.5.
Thanks for your feedback about that
The docs aren't always up do date with the latest and greatest stuff in every single aspect, as it kinda needs to cover the major version. As far as PHPUnit goes, version ^9.3 is officially supported as of CakePHP 4.2.
https://github.com/cakephp/cakephp/blob/4.2.0/composer.json#L58-L63
https://github.com/cakephp/app/blob/4.2.0/composer.json#L14-L20
Related
The CakePHP community has frequent minor release cycles. Can anyone suggest a strategy for selecting an LTS version - specifically a minor version.
Or would the best strategy be to upgrade as frequently as the minor versions are released?
We can assume that the 2.x and 3.x branches get updates for the next few years (i'm not sure, but i think even 1.3 still get security updates if leaks are found)...
So your choice is between 2.x and 3.x where 3.x is cleaner/faster and easier extendible in form of 3th party libraries and 2.x is more wide spread(plugins, tutorials,... ). I would definitely recommend you to go with 3.x due to a higher php version(it's sooo much faster).
Cakephp releases in minor versions (3.0.x) are bug and security fixes. So if you select:
"require": {
"cakephp/cakephp": "3.0.*"
}
you should be just fine for the next few years.
If you than feel like a feature is missing which is present in a newer 3.x release you can always find a migration guide for the newest version in the cookbook: http://book.cakephp.org/3.0/en/appendices/3-0-migration-guide.html as you can see from 2.x to 3.x there are a lot of breaking changes and an update is most likely really time consuming.
In comparison a update from 2.x to 2.6 is less complex as there are primary smaller feature improvements, renaming of functions and stuff like that: http://book.cakephp.org/2.0/en/appendices/2-6-migration-guide.html
CakePHP 3.0.x is the most current branch of CakePHP and if you're starting out with Cake is the best place to start (CakePHP 2.6.x is still being supported for the foreseeable future, but will eventually get dropped).
The recommended way of installing CakePHP is using Composer. If you want to install the current stable release then you want the following in your composer.json file:-
"require": {
"cakephp/cakephp": "3.0.*"
}
This will insure that every time you do a composer update you'll only get bug fixes and minor changes that shouldn't break your app. Ideally you want to ensure your app is bug free so it is a good idea to periodically update Cake with these minor version changes.
When CakePHP 3.1.x is released in the future it is likely to introduce new features that have the potentially to break an app's existing functionality. In this case upgrading needs to be done with caution. You will easily be able to update by modifying your Composer requirement, but the app will need thorough testing. This can potentially be time consuming, so unless you really need the new features is unnecessary.
I would highly recommend CakePHP 3.x if you are starting a new project. However, I was just at the CakePHP Conference in New York and the CakePHP Core Developers indicated they would be supporting 2.x for 2-3 years. That time period greatly hinges upon the community to some degree, they are not just going to stop supporting 2.x. any time soon. They are actually going to backport some of the 3.x features into 2.x. They tentatively plan to Release CakePHP 2.7 and CakePHP 3.1 sometime this summer.
I would also ask have you been using 2.x and what is your comfort level with CakePHP? Depends on the size of the project. I haven't made the jump to 3.x yet, haven't had a new project to try it on yet. I have a ton of code for 2.x like bake scripts and plugins that I have customized, so for profitability on a project I still might consider using 2.x.
There will be some learning with CakePHP 3.x especially if you are coming from 2.x, the ORM is awesome, but it much different than 2.x. So you have to weigh your options. They mentioned tools for upgrading from 2.x to 3.x that might help if you start with 2.x and jump to 3.x later. I don't think at this point I would do that, that is more for people upgrading from 2.x to 3.x. that have existing 2.x projects. I would pick a version and run with it.
The the other answers suggest use composer to install CakePHP. I started using composer about 8 months ago with CakePHP 2.x and love it. With CakePHP 3.x, I recommend using composer, like this if it is installed globally: composer create-project --prefer-dist cakephp/app [app_name]
We want to convert our web app to angularjs, the problem is we need to support IE8 so only option is to stick with angularjs version 1.2. The question is it safe to go with this version? As 1.3 is already out and soon version 2.0 will be there too, so in near future (like 8-12 months) if we dropped IE8 support and then want to migrate to 1.3 or even 2 how much effort it will be?
Migration from Angular 1.2 to 1.3 is far more easier as compared to moving to Angular 2.0
There is even a migration guide to migrate from 1.2 to 1.3. So migrating would be possible to 1.3 or 1.4 or 1.x.
There is a bit of paradigm shift when it comes to Angular 2.0. The migration path is still not clear and we even don't know whether one is possible.
Update: This video from ngconf 2015, gives some useful insight into how build today with 1.3, that makes transition easy.
I have been fighting with ACL for two days now and just recently i came across this plugin
alaxos
My question is: Does anyone know if it works with Cakephp 2.3 or higher?
The version that is currently online is not up to date. I won't give any excuse even if I have hundreds, but well, you know, bla bla bla...
That said, I have an updated version that I use with Cake 2.3 projects. I just made a quick download link on my server: you can find it here: http://www.alaxos.org/download/alaxos_acl_2.3.0.zip
And I promise, I'll update my website. Tomorrow...
I am trying to integrate Neil's search plugin http://www.neilcrookes.com/2009/11/21/cakephp-searchable-plugin to my application but I can't get it to work. Does it work with Cakephp 2.0 and how do I go about doing it?
Thanks,
Lyman
is CakeDCs search plugin not an option? its very sophisticated and works in 2.0.
Ah, I see. The functionality is completely different.
Well, I don't see any 2.0 implementations yet. But you can easily upgrade it using the UpgradeShell.
run "cake upgrade all -p Searchable"
I've made the necessary changes to Jose Gonzalez's fork of Searchable in order to get it compatible with CakePHP 2.0. You can get it here - https://github.com/sc0ttyd/searchable
Remember to check out the 2.0 branch for CakePHP 2.0 compatibility.
My web project (to be launched in a few months) is currently using CakePHP 1.2.5 / PHP 5.1.6 / MySQL 5.0.77.
From a performance point of view, is it a good idea to upgrade to 1.3?
Will it make it easier to later upgrade to the (PHP5-only) CakePHP 2?
I'd say it depends on when you expect to get your site out the door. 1.3 is currently in alpha status and probably won't be officially stable for a while. While the changes being made between 1.2 and 1.3 shouldn't have a huge impact on the overall stability, the new features being put in might still be buggy. The question is, is there anything in 1.3 that you absolutely need now?
If you want to release your site soon on an unstable version of 1.3, you need to make sure through a lot of testing that the parts you're using are performing as expected. If your project will evolve over time together with 1.3, let's say over the next 6 months or so, and you continuously keep updating, you'll probably be in better shape. For example, I developed a project on the 1.2 beta and there were a few bugs in Set, which tripped me up, but got ironed out 'till the final release.
For a long-term project, I'd prefer the 1.3 branch, while for a near-future release I'd stick with 1.2.5 for now. You can keep an eye on the Migration Guide to avoid API calls that will be deprecated in 1.3, to allow for an easier later upgrade.
I think an upgrade is always a better opition IF you have time to do it. Im not into CataPHP but, i would do any upgraded if i have enough time before the release.
i'd upgrade early situation allows. if you haven't you might want to start using the cakephp/simpletest test to make sure things work just fine.
i took my time upgrading from 1.1 to 1.2 and had a lot of 'fun' going through my codes. :)