Log message #4116850

# At Username Text
# Feb 13th, 15:02 saeideng that run before queries
# Feb 13th, 15:02 saeideng neon1024 yes you can add your query into `'init'`
# Feb 13th, 14:51 loginews thanks neon
# Feb 13th, 14:51 loginews ok. I may have switched to another layout in that particular ctp file's main controller. Will check.
# Feb 13th, 14:50 hmic it works the same in all files - you will see on the link neon1024 provided...
# Feb 13th, 14:50 loginews well, I didn't know because in the first files I put it, it worked.... I will read your link.
# Feb 13th, 14:50 neon1024 Here, https://github.com/cakephp/app/blob/master/src/Template/Layout/default.ctp#L24
# Feb 13th, 14:49 loginews it's the tab name at the top of the browser.
# Feb 13th, 14:49 neon1024 That’s the default string appending in the layout
# Feb 13th, 14:49 loginews I have used $this->assign('title','mytitle') near the top of several ctp files. It works. But in one index.ctp file, mytitle is appended to Cakephp: the rapid development framework... What could have gone wrong ?
# Feb 13th, 14:45 neon1024 Feels more like a sidestep than a fix
# Feb 13th, 14:45 neon1024 So far I’ve just updated my init `'init' => ['SET GLOBAL sql_mode=(SELECT REPLACE(@@sql_mode,"ONLY_FULL_GROUP_BY",""))'],`
# Feb 13th, 14:44 neon1024 Just not sure if I should disable the mode, or really try and fix my query
# Feb 13th, 14:44 neon1024 The one I remember was like this, https://github.com/cakephp/app/blob/master/config/app.default.php#L258
# Feb 13th, 14:44 neon1024 I’d read that issue, but didn’t see a solution
# Feb 13th, 14:44 neon1024 Oh, thanks @saeideng
# Feb 13th, 14:43 neon1024 Found it, https://stackoverflow.com/a/36033983/234451
# Feb 13th, 14:40 saeideng https://github.com/cakephp/cakephp/issues/10723
# Feb 13th, 14:40 saeideng neon1024
# Feb 13th, 14:39 loginews I have used $this->assign('title','mytitle') near the top of several ctp files. It works. But in one index.ctp file, mytitle is appended to Cakephp: the rapid development framework... What could have gone wrong ?
# Feb 13th, 14:27 rmilldes No worries.. This is truly a test user table that I created by hand in MySQL, baked it and now am stepping through adding authentication.
# Feb 13th, 14:24 neon1024 Apologies for being lazy, but can someone remind me the database config for disabling the correct group by? `sql_mode=only_full_group_by`
# Feb 13th, 14:23 admad rmilldes: "When I edit an existing user with a plaintext password" why is existing password in plain text in the first place? :slightly_smiling_face: I presume you are upgrading an old system. Such a problem would not occur when password is already properly hashed. In your case forcing password field to be dirty is the easiest option
# Feb 13th, 14:17 dereuromark using the same value for hashed and nonhashed is a code smell IMO. too many things that then can go wrong.
# Feb 13th, 14:17 dereuromark super old example, the id shouldnt be in there anymore, 2.x relict
# Feb 13th, 14:17 rmilldes In this specific case, it was because they were previously plaintext and the intent was to hash them but I can see the point in not querying if not dirty but it is always nice to know how things work behind the scenes. dereuromark: Thanks, I will check that out.
# Feb 13th, 14:15 dereuromark rmilldes: so many struggle with it always, but its actually rather easy if you e.g. use https://github.com/dereuromark/cakephp-sandbox/blob/3.0/src/Controller/AccountController.php#L237-L242 3 lines of code, nothing in entity or model. but find your own approach that works for you.
# Feb 13th, 14:15 admad *but why
# Feb 13th, 14:15 admad but bother if nothing has changed?
# Feb 13th, 14:14 neon1024 Or you could manually set the fields as dirty if you wanted to
# Feb 13th, 14:14 rmilldes How/where would I do so? I'm just getting my feet wet in Cake.
# Feb 13th, 14:09 dereuromark rmilldes: I recommend using aliases here for the fields, to avoid this.
# Feb 13th, 14:09 admad np
# Feb 13th, 14:09 rmilldes Thanks!
# Feb 13th, 14:08 rmilldes Ahh, OK... It was driving me crazy for a good while
# Feb 13th, 14:08 admad yes the ORM won't make any DB query if none of the entity fields are dirty.
# Feb 13th, 14:07 rmilldes The reason I ask is that in an app similar to the tutorials, when I add a user, the password hashes. When I edit an existing user with a plaintext password, it will not hash via edit unless I change it to something else first. If I submit or re-enter the existing plaintext password, _setPassword() is never called. If I alter it, _setPassword is called from the edit page.
# Feb 13th, 14:05 rmilldes Hello all... I have a general question regarding the edit functionality generated by bake in v. 3.5. Is it normal behavior to not process the submit from the edit form if none of the fields have been altered?
# Feb 13th, 13:59 hmic :P
# Feb 13th, 13:51 jameg83 I’ll follow this step and report back. I’m away from my machine atm,
# Feb 13th, 13:49 hmic what happens?