| # |
Dec 13th 2019, 17:07 |
slackebot |
but instead was simply a `model->find` method with `recursive=2` no longer returning the expected results. Imagine finding that particular needle in a much larger haystack of many, many other changes. |
| # |
Dec 13th 2019, 17:07 |
 sean.kelly |
The other reason (for anyone who cares) is that some of the changes between even minor release numbers are subtle but have vast effects. For example, 2.0 to 2.1 claims to be "API compatible" but that should come with an asterisk. Support for finding classes in `.php` files that didn't match their declared names got dropped in that release. The behavior in the application, though, wasn't a warning or a stack trace or any useful diagnostic, |
| # |
Dec 13th 2019, 16:53 |
storkovo |
to keep your future github templates under your version control |
| # |
Dec 13th 2019, 16:52 |
damiano |
last stupid question , i promise :) why does .github folder is not in .gitignore? |
| # |
Dec 13th 2019, 16:47 |
damiano |
ok |
| # |
Dec 13th 2019, 16:47 |
ndm |
`cakephp/app` (the application template) is not `cakephp/cakephp` (the framework), the former is available as 3.8.0, and will require the latest 3.8.x of the latter. |
| # |
Dec 13th 2019, 16:43 |
damiano |
:| |
| # |
Dec 13th 2019, 16:43 |
damiano |
i read 3.8.7 in the composer.json |
| # |
Dec 13th 2019, 16:43 |
damiano |
Installing cakephp/app (3.8.0) - Installing cakephp/app (3.8.0): Downloading (100%) |
| # |
Dec 13th 2019, 16:43 |
damiano |
ok a stupid question...but i am installing cake via cakephp/app why do i see: |
| # |
Dec 13th 2019, 16:32 |
damiano |
i will use that tool thanks |
| # |
Dec 13th 2019, 16:31 |
damiano |
ok |
| # |
Dec 13th 2019, 16:31 |
damiano |
yeah i mean the master... "Upgrade tools for CakePHP meant to facilitate migrating from CakePHP 2.x to 3.0.0." |
| # |
Dec 13th 2019, 16:31 |
challgren |
https://github.com/cakephp/upgrade/tree/4.x |
| # |
Dec 13th 2019, 16:31 |
damiano |
does it iwll be released when cakek 4 will come out ? |
| # |
Dec 13th 2019, 16:31 |
challgren |
not 3.x to 4.x |
| # |
Dec 13th 2019, 16:30 |
damiano |
@challgren tool for 2.x to 3.x is still under development :) |
| # |
Dec 13th 2019, 16:29 |
challgren |
https://github.com/cakephp/upgrade |
| # |
Dec 13th 2019, 16:29 |
sean.kelly |
To minimize surprises: it's a huge app, it requires extensive testing with pair of people with QA scripts, because I have zero experience with CakePHP, and barely even more with PHP itself—and the last time I made a big version jump it was an enormous headache. If Paul Hollywood were critiquing it, he'd say it was both overbaked and had a soggy bottom. |
| # |
Dec 13th 2019, 16:29 |
damiano |
awesome! |
| # |
Dec 13th 2019, 16:28 |
challgren |
4 will provide tools to upgrade from 3.8 |
| # |
Dec 13th 2019, 16:28 |
ricksaccous |
that being said I encourage you to use the knew authentication/authorization, it isn't so bad |
| # |
Dec 13th 2019, 16:27 |
ricksaccous |
because i know there will be a LOT of changes to start with 4 after it comes out |
| # |
Dec 13th 2019, 16:27 |
ricksaccous |
@damiano you'll be good with the latest 3.x i personally don't want to jump to 4 until there are at least a couple versions out |
| # |
Dec 13th 2019, 16:27 |
damiano |
*too |
| # |
Dec 13th 2019, 16:27 |
damiano |
:) |
| # |
Dec 13th 2019, 16:27 |
damiano |
oh i am talking about 4.x and there is still discussions on 2.4 :) i think i was going to fast |
| # |
Dec 13th 2019, 16:27 |
ricksaccous |
or whatever latest 2.x is |
| # |
Dec 13th 2019, 16:26 |
ricksaccous |
because you read the migration notes for each version/etc |
| # |
Dec 13th 2019, 16:26 |
ricksaccous |
or are you migrating in small version jumps |
| # |
Dec 13th 2019, 16:26 |
ricksaccous |
why not just make the jump to 2.8 |
| # |
Dec 13th 2019, 16:24 |
sean.kelly |
Curiously, the problem seems to be in 2.4.10 itself. If I deploy a raw (sorry, wrong terminology for this group—an "unmodified") Cake app, I gt the same problem. Going to 2.4.9 is fine, though. |
| # |
Dec 13th 2019, 16:24 |
sean.kelly |
@ricksaccous … tried that earlier—big mistake! Going piecemeal resulted in a lot more sanity. Thanks though! ;) |
| # |
Dec 13th 2019, 16:20 |
damiano |
thank you! |
| # |
Dec 13th 2019, 16:20 |
damiano |
yeah ok |
| # |
Dec 13th 2019, 16:20 |
storkovo |
you will not have to “start it again”, don’t worry :) Right now, you want something you know, is pretty well documented, does have support, and is released as stable version - to get your app out of the door first. |
| # |
Dec 13th 2019, 16:18 |
damiano |
@storkovo yes you are right i think, i just asked because it is a new project and i hope it will be online for a long time, so starting again in 3 months it is a waste of time ...but, ok, i will go with 3.8 |
| # |
Dec 13th 2019, 16:16 |
storkovo |
yes - and I insist that you do not want to mess with these new approaches (unknown to you ATM) while they are unstable |
| # |
Dec 13th 2019, 16:15 |
damiano |
now there are plugins, policies etc.. |
| # |
Dec 13th 2019, 16:15 |
damiano |
@storkovo ok but for example i read that for authentication / authorization everything is changed |
| # |
Dec 13th 2019, 16:13 |
storkovo |
honestly, in measures of 2months projects, I think migration 3=>4 will be piece of cake - build your app with 3.x without usage of deprecated things, and you will be good with smooth transition to 4.x later |