Log message #4098860

# At Username Text
# Nov 27th 2017, 18:43 casmo Is the validationDefault (or validationCustom) the best place to check if fields are posted that are not be supposed to update?
# Nov 27th 2017, 18:30 dereuromark jep
# Nov 27th 2017, 18:23 casmo If it really doesn't do what you want it to do, you can always override the action
# Nov 27th 2017, 18:22 casmo For whatever reason
# Nov 27th 2017, 18:22 casmo I always find myself coming back to the Crud plugin
# Nov 27th 2017, 18:19 dereuromark if crud works it should be preferred as it upgrades for free usually :slightly_smiling_face: no code to maintain. but customization is harder (callbacks and other tricks, also some limitations here).
# Nov 27th 2017, 18:14 casmo It is a pretty decent description
# Nov 27th 2017, 18:05 dereuromark forever=real files to persist and use, fly=dynamic, no real files usually
# Nov 27th 2017, 18:04 dereuromark one generates it forever, the other on the fly
# Nov 27th 2017, 17:58 goldiman what's the difference between bake and crud ? :)
# Nov 27th 2017, 17:58 goldiman Hi
# Nov 27th 2017, 17:25 GuillaumeP Thank you dereuromark !
# Nov 27th 2017, 17:23 dereuromark "^x.y" to be precise
# Nov 27th 2017, 17:23 dereuromark or specicy the version with ...:"x.y" as documented in composer
# Nov 27th 2017, 17:23 dereuromark it will auto set the latest minor
# Nov 27th 2017, 17:22 dereuromark composer require cakephp/cakephp will do the trick :slightly_smiling_face:
# Nov 27th 2017, 17:22 GuillaumeP Hi guys, when I run composer update, cakephp is updated to 3.3.16 - how should I do to update to 3.4 via composer ?
# Nov 27th 2017, 14:48 tywe another newby looking for tips for LDAP auth with cake 2.X anyone with some experience in this that have a couple minutes for my case? :)
# Nov 27th 2017, 14:48 tywe Hi
# Nov 27th 2017, 13:54 obinoob neon1024: thank you :)
# Nov 27th 2017, 13:07 justcharlz @neon1024, been able to run composer install and checked the debugkit panel, all seems to be working ok but not yet working as I am getting permission issue. Any other suggestion.
# Nov 27th 2017, 12:57 saeideng primary key ...
# Nov 27th 2017, 12:56 saeideng I found
# Nov 27th 2017, 12:53 saeideng why?
# Nov 27th 2017, 12:53 saeideng ``` protected $_accessible = [ 'id' => true, ```
# Nov 27th 2017, 12:53 saeideng makes entity
# Nov 27th 2017, 12:52 saeideng bake model ...
# Nov 27th 2017, 12:36 neon1024 If it was part of MySQL schema, you’d have to read the value first, store it, then re-insert it with the update
# Nov 27th 2017, 12:36 neon1024 Say you were updating a users record in a shell, your Users table would have the behaviour attached, but in your shell you could unload it, update the record and it’d still have the correct timestamps
# Nov 27th 2017, 12:35 neon1024 You can unbind the behaviour for a certain save for example
# Nov 27th 2017, 12:35 obinoob neon1024: meaning?
# Nov 27th 2017, 12:34 obinoob neon1024: allows optionality by transaction"
# Nov 27th 2017, 12:27 neon1024 Because not everyone uses MySQL. Because it allows optionality by transaction. Because it’s brought over from Cake 2. To allow for application of timestamping only in certain models
# Nov 27th 2017, 12:26 obinoob neon1024: why is that extra layer of complexity if mysql can handle timestamp update etc? any guesses?
# Nov 27th 2017, 12:24 justcharlz @neon1024 don't have access to do shell script. It's on a shared server.
# Nov 27th 2017, 12:24 obinoob neon1024: existing ;)
# Nov 27th 2017, 12:24 neon1024 https://github.com/cakephp/cakephp/blob/f0e61d9b665249eef415e9749e8506e82e53fdc7/src/ORM/Behavior/TimestampBehavior.php#L32-L34
# Nov 27th 2017, 12:22 neon1024 Probably
# Nov 27th 2017, 12:22 obinoob neon1024: ok that part is pretty straight forward is there any other option besides 'always' ?
# Nov 27th 2017, 12:22 neon1024 I mean, hoping that you’re not using something archaic like FTP
# Nov 27th 2017, 12:22 neon1024 justcharlz, My guess would be that it’s a DebugKit panel perhaps. If not, then perhaps you’ve not done `composer install` on the server