Log message #4218718

# At Username Text
# Dec 13th 2019, 18:44 daniel.upshaw And ```$paginatorHelper = new PaginatorHelper($this);```
# Dec 13th 2019, 18:44 daniel.upshaw Like hacking it into the View ```$paginator = new Paginator; $paginator->setConfig([ 'limit' => 10, ]);```
# Dec 13th 2019, 18:43 daniel.upshaw Trying a few different ways that aren't super clean just yet
# Dec 13th 2019, 18:43 daniel.upshaw Seems like there must be a way to use Pagination from a View Cell
# Dec 13th 2019, 18:06 damiano yes
# Dec 13th 2019, 17:57 admad an easier way would be to use db based based sessions. That would allow you to check if session already existing for user of particular id
# Dec 13th 2019, 17:56 damiano i think this solution should be good but...boring for customer that everytime need to check their email to login
# Dec 13th 2019, 17:50 damiano is that right?
# Dec 13th 2019, 17:50 damiano @challgren ok so i should create a system that generate a new token everytime, but i missed one thing...banks for example, send the code via SMS, so should i generate a new token and send it via email to allow that user...only
# Dec 13th 2019, 17:45 challgren @damiano https://en.wikipedia.org/wiki/One-time_password
# Dec 13th 2019, 17:45 challgren Yeah I saw that
# Dec 13th 2019, 17:44 admad @challgren laravel has started using semver with laravel 6. But they will do new major every 6 months
# Dec 13th 2019, 17:44 challgren the code changes every 30 seconds
# Dec 13th 2019, 17:44 challgren No the user setups an app that generates a code and then when they login it asks for that code
# Dec 13th 2019, 17:43 damiano yes, you are right hmm... so basically i can activate an auth code and put it in a cookie to only enable that device
# Dec 13th 2019, 17:42 challgren since carriers route through multiple DCs
# Dec 13th 2019, 17:42 challgren ip based is bad for mobile devices
# Dec 13th 2019, 17:42 challgren OTP
# Dec 13th 2019, 17:42 damiano i can block multi logins for sure, no problem about that..but i wonder if there is a clever solution ..maybe ip based
# Dec 13th 2019, 17:41 damiano guys do you know a good system to prevent user sharing their login credentials?
# Dec 13th 2019, 17:40 storkovo “we have good devs andand we are using cake” = one can jump right into coding, in almost no time
# Dec 13th 2019, 17:39 challgren Well laravel and not using semver is a big one
# Dec 13th 2019, 17:39 damiano :)
# Dec 13th 2019, 17:38 storkovo it is mostly lack of conventions what bothers me in another swamps ;)
# Dec 13th 2019, 17:37 challgren I love cake and other frameworks just suck IMHO
# Dec 13th 2019, 17:37 challgren Sadly Im going to be taking over a laravel project and Im not looking forward to it
# Dec 13th 2019, 17:33 damiano cakephp is a wonderful framework, i like it very much...i have used laravel too but, cake..is...cake
# Dec 13th 2019, 17:30 challgren I do still have one 2.9 app running but if it aint broke dont touch it!
# Dec 13th 2019, 17:30 damiano ok
# Dec 13th 2019, 17:29 challgren Not a member of cakephp at all
# Dec 13th 2019, 17:29 challgren But Im just a guy that likes to help out
# Dec 13th 2019, 17:29 damiano ah ok!
# Dec 13th 2019, 17:29 challgren Too much 3.x and 4.x code in my head now
# Dec 13th 2019, 17:29 challgren Me? Nope. I even stopped 2.10 support a few months ago
# Dec 13th 2019, 17:28 damiano are you still giving support for cake 1.x ?!!?
# Dec 13th 2019, 17:25 damiano :)
# Dec 13th 2019, 17:18 slackebot Action: challgren hides in corner with all the 1.x talk
# Dec 13th 2019, 17:18 storkovo @admad I can imagine thing like that popping out during 1.x-3.x transition - there was some renaming stuff between 1.2->1.3, and 2.0 had deprecated things from 1.x, plus I am not sure when App::build() was added for paths (it also affected a lot of non-conventional things)
# Dec 13th 2019, 17:11 admad > Support for finding classes in .php files that didn't match their declared names got dropped in that release. Why would one not have their class names match file names?
# Dec 13th 2019, 17:07 slackebot but instead was simply a `model->find` method with `recursive=2` no longer returning the expected results. Imagine finding that particular needle in a much larger haystack of many, many other changes.
# Dec 13th 2019, 17:07 sean.kelly The other reason (for anyone who cares) is that some of the changes between even minor release numbers are subtle but have vast effects. For example, 2.0 to 2.1 claims to be "API compatible" but that should come with an asterisk. Support for finding classes in `.php` files that didn't match their declared names got dropped in that release. The behavior in the application, though, wasn't a warning or a stack trace or any useful diagnostic,