| # |
Aug 28th 2019, 13:45 |
 ricksaccous |
i did enjoy that little goose chase of asking you to make it accessible though |
| # |
Aug 28th 2019, 13:45 |
ricksaccous |
@neon1024 i was going to suggest that next, glad you figured it out, lol |
| # |
Aug 28th 2019, 13:45 |
spriz |
I just realized that we run tests with debug => true, wouldn't you usually disable debug mode in tests/bootstrap.php? :P |
| # |
Aug 28th 2019, 13:18 |
dereuromark |
for tests you would usually overwrite in tests/bootstrap file then |
| # |
Aug 28th 2019, 13:18 |
dereuromark |
config app.php as documented for cache engine config |
| # |
Aug 28th 2019, 13:13 |
val |
@dereuromark do you know where is that done? |
| # |
Aug 28th 2019, 13:12 |
dereuromark |
basically making it always cache-invalidate |
| # |
Aug 28th 2019, 13:11 |
dereuromark |
this is what is done for debug mode pretty much anyway |
| # |
Aug 28th 2019, 13:11 |
dereuromark |
set the timeout to 1 or even 0 |
| # |
Aug 28th 2019, 13:11 |
val |
is there an easy way to disable one cache config? |
| # |
Aug 28th 2019, 13:10 |
admad |
except for the config name there is no differentiation between cache configs used by core and other user defined ones |
| # |
Aug 28th 2019, 13:07 |
val |
in 3.x |
| # |
Aug 28th 2019, 13:06 |
val |
Hi, is there an easy way to disable all caches except cake core in unit tests? |
| # |
Aug 28th 2019, 13:06 |
alexdd55976 |
it should be in the response after submitting the form |
| # |
Aug 28th 2019, 13:02 |
davorminchorov |
how would I display the validation errors? |
| # |
Aug 28th 2019, 13:01 |
javier.villanueva |
<?= dd($var) ?> |
| # |
Aug 28th 2019, 12:59 |
javier.villanueva |
without "echo" |
| # |
Aug 28th 2019, 12:58 |
javier.villanueva |
you can use dd in view too |
| # |
Aug 28th 2019, 12:35 |
alexdd55976 |
you do not wanna do it that way, i think |
| # |
Aug 28th 2019, 12:35 |
davorminchorov |
what I am trying to do is display validation errors under each field |
| # |
Aug 28th 2019, 12:35 |
alexdd55976 |
you can also use `debug()` and `pr()` which might be a more proper solution |
| # |
Aug 28th 2019, 12:29 |
davorminchorov |
`echo $var` worked, maybe it has something to do with `echo dump($var)` that is causing issues |
| # |
Aug 28th 2019, 12:28 |
davorminchorov |
I'll try with var_dump as well now |
| # |
Aug 28th 2019, 12:28 |
davorminchorov |
dump is the symfony's var_dump() on steroids |
| # |
Aug 28th 2019, 12:26 |
alexdd55976 |
i never used `dump`... did you mean `var_dump`? i use `pr()` most of the times |
| # |
Aug 28th 2019, 12:23 |
davorminchorov |
yeah the view is correct |
| # |
Aug 28th 2019, 12:16 |
alexdd55976 |
and the view you render is the right view? |
| # |
Aug 28th 2019, 12:16 |
alexdd55976 |
thats weird |
| # |
Aug 28th 2019, 12:15 |
davorminchorov |
yeah, $var shows an array of data when I use `dd($var)` in the controller but `null` in the view for some reason |
| # |
Aug 28th 2019, 12:13 |
alexdd55976 |
and $var is filled? |
| # |
Aug 28th 2019, 12:12 |
alexdd55976 |
@davorminchorov you sure its the right view? |
| # |
Aug 28th 2019, 12:11 |
davorminchorov |
Hi, when I try to add a variable to the view / element, I use `$this->set('var', $var)` but for some reason, I am seeing anything when I try to use `dump($var)` in the view / element. Any ideas? |
| # |
Aug 28th 2019, 12:11 |
waspinator |
I've also never been sure what the best way was to develop a plugin for outside consumption, so I just keep everything in my plugin directory. Maybe a paragraph in the docs describing a good way to do this would be helpful. especially from someone who has published so many awesome plugins. |
| # |
Aug 28th 2019, 11:06 |
admad |
@rudy1976s then submit an issue to the docs repo github.com/cakephp/docs |
| # |
Aug 28th 2019, 10:16 |
rudy1976s |
hello I find a broken link in cake elastic search docs |
| # |
Aug 28th 2019, 10:05 |
kaliel |
Sorry i want to spend huge time on a plugin and i want to make it right and easily maintanable |
| # |
Aug 28th 2019, 10:04 |
kaliel |
so you start a new "blank" project to developp your plugin inside the "plugins" folder ? |
| # |
Aug 28th 2019, 10:02 |
dereuromark |
That is how you bake your plugin skeleton. |
| # |
Aug 28th 2019, 10:00 |
kaliel |
@dereuromark thank you. So you're not using the CLI to generate plugin's skeleton ? |
| # |
Aug 28th 2019, 09:56 |
dereuromark |
In 3.x it is nice that you have testing isolated inside this vendor package (vendor/bin/phpunit etc), while you can already work with it as demo inside the actual app. they dont interfere here in terms of testing. |
| # |
Aug 28th 2019, 09:55 |
dereuromark |
I usually start baking the skeleton and making sure the composer+autoload works already. Then I require it already in a project as vendor package. I have two open IDEs, project + plugin. Then I start developing the plugin with TDD, having (unit)tests for rapid prototyping right away. In Parallel I can easily confirm this also in real life app. Once all is nice, I push plugin code for travis. |