FTP PHP Warnings (Low priority)
-
Alright, you’re probably going to say to check credentials, but don’t worry, I have.
I get these warnings in Apache log at the end of an image upload :
[Wed Jun 15 18:07:37.819540 2016] [:error] [pid 29670] [client 192.168.1.68:44806] PHP Warning: ftp_chmod(): SITE CHMOD command failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 31 [Wed Jun 15 18:07:37.818956 2016] [:error] [pid 29670] [client 192.168.1.68:44806] PHP Warning: ftp_delete(): Delete operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 58 [Wed Jun 15 18:07:37.752180 2016] [:error] [pid 29670] [client 192.168.1.68:44806] PHP Warning: ftp_rmdir(): Remove directory operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 172 [Wed Jun 15 18:07:37.752129 2016] [:error] [pid 29670] [client 192.168.1.68:44806] PHP Warning: ftp_delete(): Delete operation failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 58
However, images upload fine, everything wroks as expected, etc, so it doesn’t seem like it should throw these warnings.
So obviously it’s not really a big concern, I’m mostly just confused about why these warnings show up.
-
I don’t consider any of these things bugs. I stopped having it (ftp) hide errors as to do is is pretty bad from a performance perspective and it may help in tracking issues.
-
Moved to General and marked as solved.
I’m not going to “hide” this errors as I stated earlier. One, using the @ method to hide/block errors is really really slow (albeit slow is relative here).
Also, hiding errors makes it way too difficult to track an issue. We are using hiding in a few area’s, but only on min/max functions as them throwing an error is not really important as all they typically throw for is the item is not an array or no value was returned in which case our internals already know what to do.