Thread

Where did you get the error that you mentioned here? If it was while editing the file upload preferences and setting the server path to the upload directory, that error is likely caused by the open_basedir restriction. Also, if the new site you’re creating is copying over settings from a site with paths of your file upload preferences are currently set to ‘/’, that could be the cause of the errors you posted here. It could very well be the reason Media Temple keeps saying that your application is trying to access ‘/’.

What are the file upload paths that you have actually saved in the CP?

I get the “You do not have access to the directory specified for this field” error when creating a new entry/page on a new site. It shows up on every channel field of the File type, in every channel across the site. I didn’t get any errors from the file upload preferences.

My file upload paths are all set to /nfs/c09/h02/mnt/000000/domains/honduras.missionlazarus.org/html/images/uploads/site_short_name/folder/ with one exception, which is a folder I set up for downloads at /nfs/c09/h02/mnt/000000/domains/honduras.missionlazarus.org/html/downloads/

I’ve looked everywhere that I can think of and can’t find any path set to ‘/’.

Hmm. I want to get a closer look at this if you don’t mind. Be on the lookout for an email from me!

My client forwarded your email to me, and I submitted the login request on his behalf. If possible, it would be best for you to contact me directly at studio[at]brookecondolora[dot]com, as he doesn’t always have internet access to forward me the emails quickly. Thanks!

Just discovered another problem, though I’m not sure if it’s related. I’m getting exactly the problem referenced in this thread:

http://ellislab.com/forums/viewthread/192754/P0/

The error is related to an issue that was fixed in the latest release of ExpressionEngine, so let’s do this: upgrade your system to the latest version and check to see if the issues with creating a new site in MSM still persist. If so, we’ll go from there. But the latest version of EE includes a considerable about of work on the MSM expansion itself.

I’ll keep my eye on this and wait to hear back after your upgrade!

Thanks, Kevin!

I’ve upgraded to the latest release, and the Member Group errors are gone. However, I’m still getting the open_basedir errors when I try to create a new site, unless I have open_basedir turned off.

Also, I came across what looks like a bug in the latest version. On a new channel, when I set the preference “Automatically turn URLs and email addresses into links?” to No, it still outputs my URL entry formatted as a link.

Should I report this as a bug?

And now the Upload File button in the File Manager is no longer working (bug: https://support.ellislab.com/bugs/detail/16322/).

I like ExpressionEngine, but this has been such a headache.

Thanks, Kevin!

I’ve upgraded to the latest release, and the Member Group errors are gone. However, I’m still getting the open_basedir errors when I try to create a new site, unless I have open_basedir turned off.

At this point, it’s an issue that you’ll need to work with Media Temple to solve. They have a very unique way of setting their servers up in general, and the open_basedir restriction specifically is one that we can help you work around only on a very basic level. If all your paths are set correctly, then there’s nothing in the core of EE that needs to access ‘/’. You may need to just disable open_basedir on your account completely. If the only thing you’re running on this server is this MSM install, there’s not a real reason to sandbox anyway.

Also, I came across what looks like a bug in the latest version. On a new channel, when I set the preference “Automatically turn URLs and email addresses into links?” to No, it still outputs my URL entry formatted as a link.

Should I report this as a bug?

Could you give me some more information about this? Are you just posting a URL into a channel field and that URL is automatically converted on the front end?

And now the Upload File button in the File Manager is no longer working (bug: https://support.ellislab.com/bugs/detail/16322/).

I like ExpressionEngine, but this has been such a headache.

I completely understand. This must be terribly frustrating. We’re working hard to try to get you back up to speed, I assure you.

At this point, it’s an issue that you’ll need to work with Media Temple to solve.

Media Temple has looked into it and has no idea why it would be trying to access ‘/’. I’ll just go ahead and disable open_basedir to avoid the issue.

But I still have the “You do not have access to the directory specified for this field” error on new sites, which needs to be resolved asap. This happens even when open_basedir is disabled. It doesn’t happen on the original site.

Are you just posting a URL into a channel field and that URL is automatically converted on the front end?

Yes, it’s a channel field I created to hold a URL that would be dynamically added to a link in the navigation. Instead of just the URL, the output is formatted like this:

<a href="http://URL">URL</a>

What I need to do is add it to my code like this:

<a href="http://URL" title="title">Title</a>

I expected it to be fixed when I set “Automatically turn URLs and email addresses into links?” to No, but it wasn’t. The option is still set to No, but the output is the same.

Thanks for your help!

But I still have the “You do not have access to the directory specified for this field” error on new sites, which needs to be resolved asap. This happens even when open_basedir is disabled. It doesn’t happen on the original site.

Looks like those channel fields just needed to be saved again in order to work properly. I went back through all the channel fields with the file fieldtype in the About channel field group and saved them all without changing anything. Back in working order!

Yes, it’s a channel field I created to hold a URL that would be dynamically added to a link in the navigation. Instead of just the URL, the output is formatted like this:

<a href="http://URL">URL</a>

What I need to do is add it to my code like this:

<a href="http://URL" title="title">Title</a>

I expected it to be fixed when I set “Automatically turn URLs and email addresses into links?” to No, but it wasn’t. The option is still set to No, but the output is the same.

Thanks for your help!

Which field in which channel is causing you this trouble? I want to look in the same place you’re looking.

Looks like those channel fields just needed to be saved again in order to work properly.

Yes, I mentioned previously that this was the only way to take the error away, but there are two problems with that method: 1) I had specified directories for each of those fields, and they’re all reset when you go to edit them, and 2) my client needs to be able to create new sites without having to go back through every single file channel field, reselect the correct directory, and save. This will keep happening with every site they create, and it’s not acceptable as is.

Which field in which channel is causing you this trouble?

Channel: Site Info
Field: Blog URL

The Blog URL field is only on the Honduras site at this point.

It looks like the preference “Automatically turn URLs and email addresses into links?” was actually set to Yes for your Site Info channel. I changed that preference and it’s working as you’d expect now. You can see it in the test template EL_test I created in the main template group.

With regards to the issue with creating new MSM sites and seeing the file fieldtype break, I’m brought a dev into the loop on this one, and we’re going to investigate a little further here to see what the expected behavior should be. I’ll update this thread when I have some more info there.

That’s so strange, because I tried it over and over, and I even created a new channel and field to see if that one would work, with no luck. I’m certain it was set to No. But I’m very glad it works now, for whatever reason.

I’ll keep an eye on the thread. Thanks!

*EDIT* I just figured out what the URL problem was: my own mistake. I didn’t notice I was only setting it to No under the Comment Posting section. Sorry!

If I could make a suggestion, I would love to have that set to No by default in the future! I’ve never had a need for it to output links for me.