dug
04-23-2010, 04:39 PM
Not sure what's gone on here...
I have an image upload script on one of my sites that's been in production and stable for 4 years. Yesterday I got this:
Warning: copy() [function.copy]: The first argument to copy() function cannot be a directory in ....
I haven't done any work on this site in months, and I use this feature EVERY day ( it just works... always has ). I initially wondered if there'd been some major incremental PHP upgrade on the Bluehost Box my sites are on, and I was using the copy() function in a way that had become deprecated. In which case of course, it's my job to rewrite my code and fix it.
I was a short way into investigating this when I though I'd try again... and the problem *magically* seemed to fix itself. I did some more tests and from that point on was unable to get the bug to repeat - everything seemed back to normal.
This morning though, the problem returned.... but only in Firefox. I repeated the process in IE and it worked perfectly. THEN when I shut down FF and restarted it, AND repeated, it suddenly started working again. As this is a PHP error, I can't see how it could be client-related - I reckon changing browsers was a phurphy.
Anyone else noticed anything like this? If so I'll lodge a ticket... but I'm just trying to rule out some other problem of my own doing that has suddenly chosen to unearth itself.
I have an image upload script on one of my sites that's been in production and stable for 4 years. Yesterday I got this:
Warning: copy() [function.copy]: The first argument to copy() function cannot be a directory in ....
I haven't done any work on this site in months, and I use this feature EVERY day ( it just works... always has ). I initially wondered if there'd been some major incremental PHP upgrade on the Bluehost Box my sites are on, and I was using the copy() function in a way that had become deprecated. In which case of course, it's my job to rewrite my code and fix it.
I was a short way into investigating this when I though I'd try again... and the problem *magically* seemed to fix itself. I did some more tests and from that point on was unable to get the bug to repeat - everything seemed back to normal.
This morning though, the problem returned.... but only in Firefox. I repeated the process in IE and it worked perfectly. THEN when I shut down FF and restarted it, AND repeated, it suddenly started working again. As this is a PHP error, I can't see how it could be client-related - I reckon changing browsers was a phurphy.
Anyone else noticed anything like this? If so I'll lodge a ticket... but I'm just trying to rule out some other problem of my own doing that has suddenly chosen to unearth itself.