Log message #4179587

# At Username Text
# Mar 13th 2019, 15:01 ricksaccous but i'm never sure what's the best way
# Mar 13th 2019, 15:01 ricksaccous i've done this different ways
# Mar 13th 2019, 15:00 ricksaccous 'login_lockdown <' => todays date in cakephp3 terms
# Mar 13th 2019, 15:00 ricksaccous let's say i'm querying
# Mar 13th 2019, 15:00 neon1024 `$datetime->isToday()`
# Mar 13th 2019, 15:00 ricksaccous datetime i should say
# Mar 13th 2019, 15:00 ricksaccous in cake 3 what's the best way to compare a field to today's date
# Mar 13th 2019, 15:00 neon1024 It just feels very counterintuitive to my brain
# Mar 13th 2019, 14:58 dereuromark but nowadays you need to always enable listeners on app side for everything. no more good old "just lock to file x"
# Mar 13th 2019, 14:58 dereuromark I had similar feelings once upgrading stuff from 2.x :slightly_smiling_face: https://sandbox.dereuromark.de/pages/best-practices#logging still is useful as default for all apps.
# Mar 13th 2019, 14:57 neon1024 Not without writing it to a variety of handlers
# Mar 13th 2019, 14:57 neon1024 I just want to log a message to a text file and it feels like the Log class can’t do this
# Mar 13th 2019, 14:57 dereuromark known issue from back in 3.0, yeah. scopes need to default to false as per new app templates
# Mar 13th 2019, 14:57 Martin` hmm never used scopes for debug
# Mar 13th 2019, 14:56 Martin` now it works?
# Mar 13th 2019, 14:51 neon1024 How do I make this exclusive to just exitlinks.log? Can I use this form of logging or do I need to use a different implementation
# Mar 13th 2019, 14:51 neon1024 However, when I log using `Log::debug('Example', ['scope' => ['exitlinks']])`, it is logged to both my debug.log and exitlinks.log
# Mar 13th 2019, 14:50 slackebot <neon1024>
# Mar 13th 2019, 14:50 neon1024 I have configured my logging like this
# Mar 13th 2019, 14:12 neon1024 :face_palm: I had the loads inside the cli check. Why do I only notice these things once I’ve asked the question!
# Mar 13th 2019, 14:11 neon1024 I’ve looked at a few other plugins and they don’t implement any methods in Plugin.php, so I’m a little confused as to what I’ve missed
# Mar 13th 2019, 14:10 neon1024 I changed my plugin to use the new plugin loading, with Plugin.php, but now my routes are missing
# Mar 13th 2019, 12:58 admad @neon1024 you can hold off updating notEmpty() methods, new methods are coming in 3.8 :slightly_smiling_face: https://github.com/cakephp/cakephp/pull/12990
# Mar 13th 2019, 12:19 challgren TY, Ok I’ll have to investigate it and try it out. The use case for the Password Rehash I’m just implementing the plugin so now maybe the best time to migrate
# Mar 13th 2019, 12:19 steinkel ^ 8.4.0 released btw
# Mar 13th 2019, 12:19 steinkel @challgren yes, we are migrating internal projects to test it now
# Mar 13th 2019, 12:17 neon1024 Answers on a postcard ;)
# Mar 13th 2019, 12:17 neon1024 Actually looking at it, that could be improved to be more robust!
# Mar 13th 2019, 12:17 neon1024 replace with `->allowEmptyString($1, $2)$3`
# Mar 13th 2019, 12:17 neon1024 Maybe helpful to others :slightly_smiling_face:
# Mar 13th 2019, 12:17 neon1024 If you’re using search and replace `->allowEmpty\(([\w']+),\s([\w']+)\);`
# Mar 13th 2019, 12:11 neon1024 Updating deprecated `notEmpty` and `allowEmpty` is a real time sync pita
# Mar 13th 2019, 12:07 challgren Is it beta quality?
# Mar 13th 2019, 12:04 steinkel you could prefer migrating first to the new version and adding features there instead...
# Mar 13th 2019, 12:04 steinkel take a look at develop branch
# Mar 13th 2019, 12:02 challgren I saw #761 but there’s no tests and it kind of breaks bc
# Mar 13th 2019, 12:01 challgren I was going to tackle the allow superusers to change any password #408
# Mar 13th 2019, 11:59 steinkel yep
# Mar 13th 2019, 11:59 challgren Ok cool I’m using the 8.3.x and want to make sure it makes it way into the 8.3 branch at least
# Mar 13th 2019, 11:58 steinkel and BC vs master
# Mar 13th 2019, 11:58 steinkel we have develop branch with the new auth plugins