Problem/Motivation
file_unmanaged_move() logs an error if file copy failed. When doing so it sends wrong arguments to LoggerInterface::error().
Proposed resolution
Remove unneeded argument.
Remaining tasks
- prepare patch
- review patch
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 2393455-wrong-argument-sent-to-logger.patch | 795 bytes | RavindraSingh |
| #1 | 2393455_1.patch | 790 bytes | slashrsm |
Comments
Comment #1
slashrsm commentedComment #4
primsi commentedLooks ok.
Comment #9
slashrsm commentedStill works. It seems test fail was just a temporary hick-up.
Comment #10
RavindraSingh commentedI think lets try to fix the testing fail also. Here I am uploading updated patch.
Comment #11
slashrsm commentedI don't see any changes compared to #1 (except wrong indentation). Can you explain?
Comment #12
RavindraSingh commentedIts almost same except $logger->error(t('The specified file %file could not be copied to %destination.'), array('%file' => $source, '%destination' => $destination));
I have used t() function.
Comment #15
dawehnerWrong intentation. Not: We also don't use t() for log messages, so just remove 'file' and be done with it :)
Comment #16
slashrsm commentedIt is exactly what #1 did, which was already RTBC.
Comment #17
dawehner@slashrsm
Sorry, I haven't seen that. +1 to your old path
Comment #18
slashrsm commentedNP :) Thank you.
Comment #19
catchCommitted/pushed #1 to 8.0.x, thanks!