[Jim Lacy]

So I just moved my site from development to production, and everything (I thought) was working great until I attempted to upload a new image for a directory entry.

I should note that I can upload images just fine via the media manager… no problems at all. It’s worth mentioning that the DocumentRoot folders in Apache on the two servers (dev and live) are slightly different.

Symptoms:

1. After I attempt the image upload, a folder with the slug name is sucessfully created on the file system, but Connections reports the image does not exist. See step1.png and step2.png… note odd path name with missing slashes.
2. If I manually copy the image to the appropriate folder (via the file system), Connections finds the image, generates the various resolutions, and the image is correctly displayed. See step3.png

So it doesn’t seem like a permissions problem, but something specific to the upload?

This clearly isn’t a bug or problem per se with Connections, but a push in the right direction would be appreciated! I’m running out of ideas.

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ Jim

What I can tell you is that the error is triggered right here:

https://github.com/Connections-Business-Directory/Connections/blob/8.4.4/includes/image/class.image.php#L1676

Since this seem to be a Windows server, I would expect the path to start with C://www.. Perhaps there is something misconfigured in the wp-config.php file???

Can you go to the Connections : Tools admin page and generate a temp secret remote viewing URL under the System tab and share that with me? Thanks!

[Jim Lacy]

This reply has been marked as private.

[Steven Zahm]

@ Jim

Hmmm… the paths are what I would expect, they do being with C:\www\geoalliance so something is stripping those two backslashes. To debug further, I’ll need a temp admin account and an FTP login (can be limited to the wp-content folder if you wish).

[Jim Lacy]

Let me do a little more digging before you take time out of your day. It’s clearly something goofed on our side. I think it can probably be traced to the fact than the development server had a slightly different path (c:\www\geoalliance_wp) compared to the live server. Stand by, I may very well take you up on your offer!

[Steven Zahm]

@ Jim

Alrighty, just let me know.

[Jim Lacy]

This reply has been marked as private.

[Steven Zahm]

@ Jim

Connections does use the rename() function, but only to move the images from the legacy folder to the current folder structure. Now, that said, core WordPress does use it too, in the wp_handle_upload() function which is what Connections uses process upload images… but the rename() would only be used in the wp_handle_upload() if the upload action var was changed from its default which is not the case so it do not think that rename() is being used at all in this case.

After looking at the other functions, I did not think any of those were being used and I verified by searching the code source. The only one I found is the exec() function in an unused email verification function so it does not apply.

So… I’m at a loss why any of those would cause the issue when disabled. Even still, why would any of those being disabled strip those two backslashes from the file path??? Very strange indeed.

[Jim Lacy]

For the benefit of anyone else reading this thread: the problem was traced to some PHP functions I have disabled on our server for security purposes. I made some changes, and all is well. Nothing at all “wrong” with Connections.

[Author]

Posts