| # |
Apr 23rd 2019, 09:42 |
 edgaras.jan |
add $this->loadModel('Users'), then you'll be able to use $this->Users |
| # |
Apr 23rd 2019, 09:40 |
COOurb |
I forgot how to use other tables in controller |
| # |
Apr 23rd 2019, 09:39 |
edgaras.jan |
$usersquery = $users->find(); $query = $articles->find()->where(['field IN' =>$usersquery]); |
| # |
Apr 23rd 2019, 09:38 |
edgaras.jan |
use another query in place of array |
| # |
Apr 23rd 2019, 09:36 |
COOurb |
I can do it in sql then parse, but I wanna use Paginator features |
| # |
Apr 23rd 2019, 09:36 |
COOurb |
like "select * from tab1 where tab1.field1 in (select field2 from tab2)"? |
| # |
Apr 23rd 2019, 09:35 |
COOurb |
what if my array is slection from other table? |
| # |
Apr 23rd 2019, 09:35 |
edgaras.jan |
without IN, array won't be accepted |
| # |
Apr 23rd 2019, 09:34 |
edgaras.jan |
where(['field IN' => [1, 2, 3]]) |
| # |
Apr 23rd 2019, 09:33 |
kgb.acct.personal |
'field' => [1, 2, 3] |
| # |
Apr 23rd 2019, 09:33 |
kgb.acct.personal |
You just pass an array as value |
| # |
Apr 23rd 2019, 09:32 |
COOurb|2 |
hi, how to create query with "IN" statement? |
| # |
Apr 23rd 2019, 09:22 |
dereuromark |
We just dont have a life :P |
| # |
Apr 23rd 2019, 09:22 |
kgb.acct.personal |
Daamn. How do you guys balance your work while making developments for Cake? |
| # |
Apr 23rd 2019, 09:20 |
dereuromark |
Soft deprecations and smaller upgrade steps then. |
| # |
Apr 23rd 2019, 09:20 |
dereuromark |
We often backport useful things from the new major into the previous one to ease migration. |
| # |
Apr 23rd 2019, 09:20 |
dereuromark |
yeah |
| # |
Apr 23rd 2019, 09:12 |
Letze |
I see 3.8 and 4.0 being worked in parallel? |
| # |
Apr 23rd 2019, 09:12 |
Letze |
I meant 3.8 >_< |
| # |
Apr 23rd 2019, 09:12 |
Letze |
haha! nice joke and catch. |
| # |
Apr 23rd 2019, 09:09 |
josbeir |
;) |
| # |
Apr 23rd 2019, 09:08 |
edgaras.jan |
3.8 however very soon :D |
| # |
Apr 23rd 2019, 09:08 |
edgaras.jan |
I think in 4+ years |
| # |
Apr 23rd 2019, 09:07 |
josbeir |
maybe in 2 years? |
| # |
Apr 23rd 2019, 09:06 |
Letze |
Anyone know when Cake 4.8 will be released? |
| # |
Apr 23rd 2019, 08:36 |
challgren |
Man RFID is some crazy stuff, was about to figure out what products my neighbors have. |
| # |
Apr 23rd 2019, 07:53 |
challgren |
Morning |
| # |
Apr 23rd 2019, 07:50 |
conehead |
Good mornin |
| # |
Apr 23rd 2019, 07:43 |
neon1024 |
Morning all |
| # |
Apr 22nd 2019, 22:53 |
phantomwatson |
I'm trying to port a CakePHP 3 site to 4 and running into a weird problem where the `HTTPS` env variable isn't being set, even when the request is using the HTTPS protocol, resulting in `request->is('ssl')` incorrectly returning `false`. In the CakePHP 3 version of this site, `$_SERVER['HTTPS']` is being set to `'on'`, but it's not being set at all in CakePHP 4. I'm having trouble figuring out what's causing this. |
| # |
Apr 22nd 2019, 22:12 |
lorenzo |
@phantomwatson was objecting to what @sdevore suggested |
| # |
Apr 22nd 2019, 20:28 |
phantomwatson |
I'm not sure which point you're objecting to. I'm not planning to load environment variables from a file in production. |
| # |
Apr 22nd 2019, 20:26 |
lorenzo |
That’s not how the env variables feature is supposed to be used. You should be providing env variables, not loading them from a file in production |
| # |
Apr 22nd 2019, 19:45 |
sdevore |
I use a linked file config/local.php that are the over-rides for producation/staging/development it is not checked in to source control and the deployment scripts handle linking it |
| # |
Apr 22nd 2019, 18:24 |
phantomwatson |
I'm not sure how to distinguish between `/staging.sitename.com` and `/sitename.com` using environm- oh hell, it can just check which directory it's in. Staring me right in the face the whole time. |
| # |
Apr 22nd 2019, 18:22 |
admad |
Having an uncommited file per environment is fine too |
| # |
Apr 22nd 2019, 18:20 |
admad |
Environment variables is the way to go |
| # |
Apr 22nd 2019, 17:30 |
slackebot |
read in `bootstrap.php`, but that doesn't feel right. Does anyone have input about whether this is a realistic concern and what their personal approach is? |
| # |
Apr 22nd 2019, 17:30 |
slackebot |
`bootstrap.php` that get committed and pulled by production, but now I'm uncertain about being able to do that in a way that intuits what the environment is and doesn't expose a vulnerability. I would just rely on environment variables (e.g. `ENV_MODE = development`) but that wouldn't work for distinguishing between staging and production on the same server. I could have an uncommitted "what environment is this" file in the root of each site that gets |
| # |
Apr 22nd 2019, 17:30 |
phantomwatson |
The way I've been handling different configurations for different environments (dev, staging, production) is by checking the current hostname. I'm concerned that someone could do some DNS fiddling and request a production site using a URL just meant for internal development, like `sitename.localhost`, and then have the production site load in development mode. It would be convenient to continue having a single version of `app.php` and |
| # |
Apr 22nd 2019, 16:53 |
ricksaccous |
yeah |