Log message #3881598

# At Username Text
# May 27th 2016, 13:28 rossc Anyone migrated 1.3 -> 3.0
# May 27th 2016, 13:27 d0rxy the RequestHandler is correct in turning the responsetype into json, but then the AjaxView turns it into text/html and it has issues with rendering
# May 27th 2016, 13:26 d0rxy @markstory I think it might have to do with the AjaxView of DebugKit itself...
# May 27th 2016, 13:13 icyrizard Ah ok thanks for the info, I'll do that :)
# May 27th 2016, 13:08 d0rxy ah, ok I'll check out the request handler! :)
# May 27th 2016, 13:08 markstory which is more likely
# May 27th 2016, 13:08 markstory Or we were relying on the bug :slightly_smiling_face:
# May 27th 2016, 13:07 markstory d0rxy: sounds like it might be a regression. A small part of RequestHandler was changed in 3.2.10
# May 27th 2016, 13:06 markstory icyrizard: A pull request for the readme would be great
# May 27th 2016, 13:03 icyrizard The other is a 'missing database' issue, where you just need to switch to Sqlite in database.php
# May 27th 2016, 13:02 icyrizard First problem is the AutoLoad missing, which is fixed by running: composer global require "phpunit/phpunit=3.7.*" (or whatever version you need).
# May 27th 2016, 13:00 icyrizard Hi guys, I am adding tests for pull request #8844 and ran into some issues related to running the tests. There is really some information missing about on how to run them. Shall I create a pull request to update the readme?
# May 27th 2016, 12:35 d0rxy (if I update that other previously working instance to cakephp 3.2.10 it also fails)
# May 27th 2016, 12:33 d0rxy can anyone point me in the right direction where to debug? I also have an instance where it is working but I can not figure out where the difference lies
# May 27th 2016, 12:33 d0rxy it gives me this error message: https://gist.github.com/anonymous/38444c09069de57d2b06d471ab08d2e2
# May 27th 2016, 12:32 d0rxy Whenever I click a previous request in the history panel it gives an error500, as if it doesn't know it needs to produce json...
# May 27th 2016, 12:31 d0rxy I don't know if it's the upgrade to cakephp 3.2.10 I did today or something else I messed up in my code but it just occurred today
# May 27th 2016, 12:31 d0rxy hi all! I'm having an issue with debug kit... :(
# May 27th 2016, 12:18 bernat1 Which transaction isolation level does CakePHP uses or expects in the database? When using tables with multi-column primary keys it checks if it exists then inserts or updates. I guess this needs the serializable level to work.
# May 27th 2016, 12:12 johnW_ sry that was not for you... :(
# May 27th 2016, 12:03 mesterjagel http://book.cakephp.org/3.0/en/core-libraries/time.html#creating-time-instances
# May 27th 2016, 12:02 mesterjagel @johnW Iâ??m not sure there is a global function for that. You could make a component with a function that translates your DB timestamp into a localised one, and then include that component whenever you need to translate a timestamp:)
# May 27th 2016, 11:57 johnW_ and you call your function every time or it is somewhere "global"
# May 27th 2016, 11:56 mesterjagel I get a â??Nicelyâ?? formatted string rather than numbers, anyone know why?
# May 27th 2016, 11:56 mesterjagel $month = $query->func()->date_format([ 'created' => 'identifier', "'%Y:%M:%D'" => 'literal' ]);
# May 27th 2016, 11:56 mesterjagel Hi guys:) Iâ??m using the date_format function from the ORM to group some entries like this:
# May 27th 2016, 11:52 johnW_ now we are using something like this -> $user->created->nice('Europe/Paris')
# May 27th 2016, 11:51 johnW_ is there option in cakephp3 that I can always read data in UTC+2 time and when I write data or edit that is always in UTC-0 saved in DB? Not manual for each date/time... something global... thx
# May 27th 2016, 11:47 Neon1024x https://github.com/lorenzo/cakephp3-examples/blob/master/config/Schema/world.sql
# May 27th 2016, 11:47 sab-cakefest Thanks Neon1024!
# May 27th 2016, 11:45 Neon1024x sab-cakefest, Here is the link to the belongsToMany Through option, http://book.cakephp.org/3.0/en/orm/associations.html#using-the-through-option
# May 27th 2016, 11:44 elboletaire After what we've discussed, I'm not gonna use View Cells. As you previously said it's a good replacement for the old `requestAction` method, so... moving the logic to the tables should be my main priority now x__D
# May 27th 2016, 11:37 bernat1 Or do you want to write blocks in the view cell and read them in the main view? I think that would be awful to do with view cells.
# May 27th 2016, 11:35 bernat1 @elboletaire, do you really need to pass the main view? Can't you just pass the blocks? I think it would make sense passing just what the cell needs. You'd have a more reusable view cell.
# May 27th 2016, 11:32 unorthodox Gah, requestAction.
# May 27th 2016, 11:31 bernat1 @elboletaire, view cells is a new feature in 3.0, we have lived long without them and I don't use them. It can replace the old requestAction method that some people needed, not me. They help reuse controller actions from views.
# May 27th 2016, 11:30 elboletaire thanks @fquffio, it's a good example :slightly_smiling_face:
# May 27th 2016, 11:30 spriz I feel like Iâ??m missing something, I sure canâ??t be the first that wants to edit a bunch of objects at once? :P
# May 27th 2016, 11:29 spriz Am I doing something stupid when implementing a â??bulk editâ? Crud Action?
# May 27th 2016, 11:27 fquffio @elboletaire: for instance, I wanted to show the amount of tickets assigned to the logged user on every page. This required a small amount of logic to be executed, but that had nothing to do with the current controller/action, and especially I didn't want that logic to be executed if I wasn't rendering the view (APIs), so I used view cells. :)
# May 27th 2016, 11:21 elboletaire Then... what would be a good reason to use a view cell? Now I don't get how could I use them xD