| # |
Dec 30th 2019, 16:31 |
 kevin.pfeifer |
yeah, the most work for me was refactoring the old CakePHP Shell scripts to the new "Commands" and some special work in some of my Components |
| # |
Dec 30th 2019, 16:30 |
ricksaccous |
i suppose you don't really know if it's user error or cake4 though yet |
| # |
Dec 30th 2019, 16:30 |
ricksaccous |
but i know what you mean it's good to upgrade |
| # |
Dec 30th 2019, 16:30 |
ricksaccous |
lol |
| # |
Dec 30th 2019, 16:30 |
ricksaccous |
except +1 year dates ;) |
| # |
Dec 30th 2019, 16:29 |
kevin.pfeifer |
my app is running on cakephp 4 since 2 or 3 months without a problem |
| # |
Dec 30th 2019, 16:28 |
kevin.pfeifer |
i can definitely recommend it :) refactored my old cakephp3 app to 4 and basically had no problems |
| # |
Dec 30th 2019, 16:27 |
ricksaccous |
i haven't touched cake4 yet XD |
| # |
Dec 30th 2019, 16:27 |
kevin.pfeifer |
just wanted to check if someone else also had this problem till now^^ |
| # |
Dec 30th 2019, 16:27 |
ricksaccous |
ok |
| # |
Dec 30th 2019, 16:27 |
kevin.pfeifer |
i have a barebones cakephp4 install on antoher server, i will try to recreate the issue there |
| # |
Dec 30th 2019, 16:27 |
ricksaccous |
if you can recreate on a new project then create a github issue |
| # |
Dec 30th 2019, 16:24 |
kevin.pfeifer |
and i tried updating an entity and therefore "reupdating" the modified date. But it still keeps +1 year |
| # |
Dec 30th 2019, 16:24 |
kevin.pfeifer |
even the composer update didn't change anything |
| # |
Dec 30th 2019, 16:23 |
kevin.pfeifer |
i know this always sounds good but "i didn't change anything" |
| # |
Dec 30th 2019, 16:23 |
kevin.pfeifer |
and noticed that the year is wrong |
| # |
Dec 30th 2019, 16:23 |
kevin.pfeifer |
just opened the page today |
| # |
Dec 30th 2019, 16:22 |
kevin.pfeifer |
it worked fine on cakephp4 wor months |
| # |
Dec 30th 2019, 16:21 |
dsar |
That's weird, did it work on cakephp 3? |
| # |
Dec 30th 2019, 16:19 |
kevin.pfeifer |
ill try a quick composer update, probably there has been some update |
| # |
Dec 30th 2019, 16:17 |
kevin.pfeifer |
i have set that globally in my config/bootstrap.php ```Time::setToStringFormat('dd.MM.YYYY HH:mm'); // For any mutable DateTime FrozenTime::setToStringFormat('dd.MM.YYYY HH:mm'); // For any immutable DateTime Date::setToStringFormat('dd.MM.YYYY HH:mm'); // For any mutable Date FrozenDate::setToStringFormat('dd.MM.YYYY HH:mm'); // For any immutable Date``` |
| # |
Dec 30th 2019, 16:17 |
dsar |
Where do you use the time formatter? Could you show that part? |
| # |
Dec 30th 2019, 16:13 |
kevin.pfeifer |
im on cakephp4 |
| # |
Dec 30th 2019, 16:13 |
slackebot |
<kevin.pfeifer> |
| # |
Dec 30th 2019, 16:10 |
dsar |
How do you output the value in the view? |
| # |
Dec 30th 2019, 16:08 |
kevin.pfeifer |
has anyone experienced problems with +1 year on the "modified" column? The values in the DB are correct but when i output the date with $entity->modified the output is +1 year. The $entity->created is fine. |
| # |
Dec 30th 2019, 15:56 |
tibor.hajos |
I'm finalizing my code regarding the HTTP part of this ticket https://github.com/cakephp/cakephp/issues/13493 I have a question on something I'm stuck with though. `Http/Middleware/CspMiddleware` implements the MiddlewareInterface, per PSR-15 requirements. However, in PHP <7 the interface is not yet available. I could leave it out, but that would be against PSR. Could anyone help me as to how I should proceed? |
| # |
Dec 30th 2019, 15:34 |
luizcmarin |
ok |
| # |
Dec 30th 2019, 15:33 |
ndm |
`2.0.3` was just released a few hours ago, their cache probably takes some time to update. |
| # |
Dec 30th 2019, 15:31 |
luizcmarin |
@ndm Just one comment: cakephp / bake is flagged as cakephp / bake ":" ^ 2.0.3 ", (https://raw.githubusercontent.com/cakephp/app/master/composer.json) but at https://semver.mwl.be/#!?package=cakephp%2Fbakeandversion=%5E2.0andminimum-stability=dev only up to 2.0.2. I don't know if this causes problems |
| # |
Dec 30th 2019, 15:24 |
luizcmarin |
@ndm understand. |
| # |
Dec 30th 2019, 15:24 |
dereuromark |
it is also annoying to have to switch dev- prefix to -dev suffix for these numeric branch names |
| # |
Dec 30th 2019, 15:23 |
dereuromark |
Thus my recommendation to use cake4 as branch names etc, dont use sth that can get confused with plugin major versions :) |
| # |
Dec 30th 2019, 15:21 |
ndm |
@luizcmarin The `4.x` branch of `cakephp/migrations` won't be released as version `4.0`, but as version `3.0`, it doesn't follow the same versioning as CakePHP, the `4.x` branch just means "_for CakePHP 4.x_". Bake is the same thing, `2.0` is the CakePHP 4.x compatible version, and it was previously maintained in a branch named `4.x` |
| # |
Dec 30th 2019, 15:15 |
luizcmarin |
? |
| # |
Dec 30th 2019, 15:15 |
luizcmarin |
and "cakephp/bake": "^2.0", |
| # |
Dec 30th 2019, 15:12 |
luizcmarin |
@admad, pardon, but... you suggested in composer.json from https://raw.githubusercontent.com/cakephp/app/master/composer.json: "cakephp / migrations": "^ 3.0", but now that you've taught me how to use composer, could you suggest "^ 4.0"? https://semver.mwl.be/#!?package=cakephp%2Fmigrationsandversion=%5E4.0andminimum-stability=dev |
| # |
Dec 30th 2019, 14:31 |
luizcmarin |
I'll do it. :cakephp::thumbsup_all: |
| # |
Dec 30th 2019, 14:27 |
admad |
later read https://getcomposer.org/doc/articles/versions.md to understand how composer versioning works |
| # |
Dec 30th 2019, 14:26 |
admad |
then just run `composer update` whenever a new cake release is done |
| # |
Dec 30th 2019, 14:25 |
admad |
replace you composer.json with this one and forget about it https://raw.githubusercontent.com/cakephp/app/master/composer.json |