# |
Apr 25th 2019, 14:49 |
this.impetus |
well.. `composer require --dev cakephp/bake:~1.0`, which I just copied and pasted from the CookBook admittedly, gives `Nothing to install or update` |
# |
Apr 25th 2019, 14:46 |
this.impetus |
Ah. Sorry, if that was in the migration guide I am missing it. Counsel where i can read about achieving that? |
# |
Apr 25th 2019, 14:45 |
admad |
You probably need to upgrade bake plugin too |
# |
Apr 25th 2019, 14:45 |
this.impetus |
One more—migrated to Cake3.7, added a new table for a HABTM relationship between two models that had already existed. When I run `cake bake all` the console is throwing `Exception: Call to a member function addMany() on null in [<project>/vendor/cakephp/cakephp/src/Core/BasePlugin.php, line 248]` |
# |
Apr 25th 2019, 13:46 |
this.impetus |
flawless thanks guys |
# |
Apr 25th 2019, 13:43 |
cnizzardini |
I don't like the idea that I had to use a plugin to auto create configs, would've love for it to happen automatically |
# |
Apr 25th 2019, 13:43 |
admad |
then run `composer update` |
# |
Apr 25th 2019, 13:43 |
this.impetus |
great, tyvm |
# |
Apr 25th 2019, 13:43 |
admad |
manually or using `composer require` |
# |
Apr 25th 2019, 13:42 |
ricksaccous |
yep |
# |
Apr 25th 2019, 13:42 |
admad |
the proper way to update the version constraint for that plugin in composer.json |
# |
Apr 25th 2019, 13:42 |
ricksaccous |
remove upgrade restrictions in composer.json |
# |
Apr 25th 2019, 13:41 |
slackebot |
it |
# |
Apr 25th 2019, 13:41 |
this.impetus |
Hopefully quick an easy question; I'm migrating from cake3.6 to 3.7; the current version of one of my composer-managed plugins isn't compatible with 3.7—I'm actually upgrading because the newer version of this plug-in *is* compatible with 3.7 and has features I want access to. That said, the old version currently installed is blocking the update. Obvs I can just delete it and reinstall, was curious if there was a 'proper' means of doin |
# |
Apr 25th 2019, 13:33 |
cnizzardini |
Its not a PHP unit thing, its that our custom config file is not copied over for customer.default.php when composer install is run. I got around this by using the Config File Provider Plugin. |
# |
Apr 25th 2019, 13:23 |
neon1024 |
Ahh, they’re all in columns! :face_palm: |
# |
Apr 25th 2019, 13:22 |
neon1024 |
Why isn’t firstMatch in this list? I tried editing the doc page, but the one in the repo seems different to what’s on live to me |
# |
Apr 25th 2019, 13:22 |
neon1024 |
https://book.cakephp.org/3.0/en/core-libraries/collections.html#list-of-methods |
# |
Apr 25th 2019, 12:22 |
admad |
App::uses() is just glorified `include()` |
# |
Apr 25th 2019, 12:21 |
val |
Hi, has anybody tried to use namespaces in cake 2.x instead of `App::uses()`? |
# |
Apr 25th 2019, 12:14 |
admad |
kiwi_14: this might help you https://stackoverflow.com/questions/30241975/how-to-limit-contained-associations-per-record-group |
# |
Apr 25th 2019, 12:05 |
kiwi_14 |
So, i have 3 Tables : "Category", "Host" and "Experience". I would like to get 12 max experiences by Category. |
# |
Apr 25th 2019, 12:04 |
Martin` |
bad request? |
# |
Apr 25th 2019, 12:03 |
mrgrimpy |
And what type of error would you suggest I throw if the request header !== application/json? |
# |
Apr 25th 2019, 12:02 |
np |
what is problem? |
# |
Apr 25th 2019, 12:02 |
Martin` |
Just drop the question :) |
# |
Apr 25th 2019, 12:01 |
kiwi_14 |
Hi, i have a problem with Cake's ORM, is someone available to help ? |
# |
Apr 25th 2019, 12:00 |
admad |
@mrgrimpy though i would suggests allowing access to URL without .json extension too but if request had Accept: application/json header. For that you just need to use `$this->request->is('json')` instead of checking for `_ext` param. |
# |
Apr 25th 2019, 11:59 |
admad |
welcome |
# |
Apr 25th 2019, 11:58 |
mrgrimpy |
Thank you for your help, and for your I18n plugin |
# |
Apr 25th 2019, 11:58 |
admad |
:slightly_smiling_face: |
# |
Apr 25th 2019, 11:58 |
mrgrimpy |
Already done lol |
# |
Apr 25th 2019, 11:58 |
mrgrimpy |
Indeed :slightly_smiling_face: |
# |
Apr 25th 2019, 11:58 |
admad |
what i suggested above is easier |
# |
Apr 25th 2019, 11:57 |
admad |
while ensuring that no other mapped routes map to your particular action |
# |
Apr 25th 2019, 11:57 |
admad |
to do it at routes level you will have to connect connect required routes with `.json` paths without enabling extension parsing |
# |
Apr 25th 2019, 11:55 |
mrgrimpy |
I just tought there was a way to handle it at routes level |
# |
Apr 25th 2019, 11:55 |
mrgrimpy |
Will do |
# |
Apr 25th 2019, 11:55 |
mrgrimpy |
Yes I am |
# |
Apr 25th 2019, 11:55 |
admad |
that's assuming you are using extension parsing in router |
# |
Apr 25th 2019, 11:53 |
admad |
then just check `$this->request->getParam('_ext')` and throw `NotFoundException` if the value is not `'json'`. |