PHP warnings are displayed when use of copy() is allowed and the resource file doesn't exist. However the php error message is more useful than the warning generated by the FeedsParser. It reports "Cannot write content to XY", but in this particular case the copy failed because the resource can't be read. So the message text is bit misleading and without the PHP error message I will assume that the Processor can't write to the tmp directory.

warning: copy(http://localhost/work/ban2-001/www/sites/default/files/testimage_0.png) [function.copy]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in feeds\plugins\FeedsParser.inc on line 275.

Cannot write content to /tmp/testimage_0.png

Comments

Branndon’s picture

Branndon commented

Saw this same issue, found this while looking for a solution.

My error was slightly different tough:

copy(http://www.website.com/sites/website.com/files/long%image%name.jpg) [function.copy]: failed to open stream: Connection timed out in /website.com/sites/all/modules/feeds/plugins/FeedsParser.inc on line 275.

(edit a tiny bit, but you get the idea)

Yours wasn't a connection timed out though, so maybe I can fix mine easily.

Branndon’s picture

Branndon commented

My problem was something related to reverse DNS on my server. The IP address it was sending out was the same as it was getting back, and the server didn't route it to the correct internal IP address.

I agree though, the error given of not being able to write to the /tmp directory was way off from the average users perspective.

twistor’s picture

twistor commented
Issue summary: View changes
Status: Active » Closed (outdated)