Thread

Ok, I have searched and read about every last post on these forums one can find that have anything to do with a masked cp, https and path errors… so here goes.

We have masked access to our CP as recommended.

If we log-in to the site via https… everything works fine except when we go to upload an image with the publish form.

We get the error…

“The path specified in your image upload preferences is not correct”

However, no error occurs when logged in and uploading via normal http.

Without a doubt, our paths are correct.

On the server, all https and http reside in the same directory, same files.

In the path file we have the optional variable set…

$cp_url = 'https://www.ourdomain.com/admin.php';

We are currently running build 20090915 with MSM. (Why? Everytime I upgrade… another release comes the next day.)

Any ideas or suggestions on how to correct this issue?

Todd,

CP Home ›  Admin ›  Weblog Administration ›  File Upload Preferences ›  Edit File Upload Preferences

Just to confirm that this is where your upload paths reside

On the server, all https and http reside in the same directory, same files.

Just to confirm this as all I have ever worked with has been the https folder living alongside the http folder on a web server. Then I usually create a symlink to the any image directory in the https folder

What happens if you login and try it using this as opposed to the masked URL

https://www.ourdomain.com/system/index.php

What happens if you login and try it using this as opposed to the masked URL

https://www.ourdomain.com/system/index.php

When logged in without the masked access I get an error as soon as I go to the publish form.

“Could not create /var/www/vhosts/ourdomain.com/httpdocs/uploads/articles_media/ : edit upload preferences”

This errors appears on the publish form immediately… no submission required.

Do you have PHP safe mode on? Are there any open_base_dir restrictions in place?

Safe mode is off for that domain. No openbase dir restrictions.

It seems there is an issue with forcing https. I came across a relevant post.

Does this help? Does this get rid of the error?

I tried implementing the changes recommended there from Greg which you highlighted Adam… and no, they didn’t have any effect on the results.

Upon further testing though… I did learn something that might reveal a possible bug in EE.

I have been testing on one of our weblogs that use the normal file field that comes with EE. Essentially a text field where you upload the file first before submitting anything else with the weblog. It is during this process that the upload fails… prior to submitting the rest of the entry.

However, if I use a weblog that uses nGen file field for the image… the submission, which is processed at the time everything else is being processed, works fine. The image is uploaded without issue.

The above results occur with or without the fix suggested by Greg.

Hi Todd-
I was able to replicate a similar behavior. Can you report this to the Bug Tracker, linking to this thread? Thanks!

Done

Thanks, Todd. Closing this thread, let’s focus on the tracker. Please don’t hesitate to post again as needed.