Steven Zahm@ Enrique
Seems there is a bug in WordPress…
This is going to be a bit technical, bear with me.
WordPress allows custom error handlers to be used there and there are multiple ways to define the callback function for a custom error handler. One is a string and another an array. Connections defines the custom error handler using an array. There are a couple ways to run a custom error handler callback, but only one is compatible with arrays.
All other instances in the WordPress upload function call the custom error handler callback using the way that is compatible with an array… except for one. Unfortunately this is the error you are experiencing and it is triggering the fatal PHP error. I’ll report the bug to the WordPress devs.
The exact error you are experiencing, as reported by WordPress is:
“The uploaded file could not be moved to %s.”
The %s would be the path.
When Connections uploads an image the path would be this:
../wp-content/uploads/connections-images/{entry-slug}/
The {entry-slug} is created from the entry name.
You said, “if we add a new entry with an image, the entry in the “uploads/connections-images” is created OK as expected”
Can you clarify this statement?
When you say it is created OK? Do you mean the {entry-slug} folder? Or do you mean that the folder is created and the image is in it?
I would expect based on the error WordPress is reporting, the folder is created, but that the image is not in it because WordPress can not verify that the file was moved correctly.
I’ve glanced over your other support topics posted in the past and it seems server permissions has been an issue. Unfortunately I am not certain what the solution would be for this, you’ll need to contact your web host to see what they suggest. Writing to the WordPress uploads folder should be non-issue and it is for nearly all web hosts so there has to be a server setting they can change for you.
This might help your host, the PHP function failing is either move_uploaded_file() or rename(). These functions generally only fail when the folder that object is being move into does not have the write permissions for the user/group (server user/group, not WordPress user) moving the file.
My guess is that when WordPress creates the {entry-slug} folder it is not able to set correct write permissions for the server user/group. It should inherit the parent’s folder (/connections-images/) permissions and for some reason it is not.
Hope that helps!