Warning: file_exists() [function.file-exists]: open_basedir restriction in effect.

Permalink
I get this error on newest C5 installation at the regular registration page.

Warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(C:\Inetpub\vhosts\*************\c5/js//*************/c5/index.php/tools/required/attribute_type_actions?atID=9&akID=46&action=load_provinces_js) is not within the allowed path(s): (C:/Inetpub/vhosts/*************\;C:\Windows\Temp\) in C:\Inetpub\vhosts\*************\c5\concrete\helpers\html.php on line 109

I'm not sure what is happening.

Deladroid
 
lawsonium replied on at Permalink Reply
I am getting a similar problem since I centralized the core. I posted here: (http://www.concrete5.org/community/forums/customizing_c5/after-centralizing-core-getthemedirectory-path-errors-in-html.ph/)

Any information greatly received.

Matt.
Deladroid replied on at Permalink Reply
Deladroid
Interesting. This is a bit of an issue for me since the biggest selling point for using C5 for my client's website redesign was that there was a Paid Membership add-on that integrates with the current registration system. Not good.

I think further, it's related to sym linking on windows 2008 servers.
Deladroid replied on at Permalink Reply
Deladroid
BTT (<-- Sorry, I don't like to "bump", but I'm on a time constraint :/)
lawsonium replied on at Permalink Reply
Hi there,
Not getting much interest in this issue are we :-(

I have done some digging around and I think I know what the issue is I don't have a very good or easily maintainable fix, just some hacks, one of which I strongly suggest shouldn't be used.
See my second post here: (http://www.concrete5.org/community/forums/customizing_c5/after-centralizing-core-getthemedirectory-path-errors-in-html.ph/)

This bug report is describing the same issue: (http://www.concrete5.org/developers/bugs/5405/file_exists-not-good-with-relative-paths-and-php-5-1-6/) but nothing posted yet about it being fixed across the concrete5 code base.

I am not sure what to do now, I can't go changing loads of code here, there and everywhere, it'll be a nightmare when it comes time to upgrade. Also, you just don't know where it will crop up until you start seeing errors...
We need a proper fix, either to PHP itself or concrete5 core.

Anyone out there from Concrete5 development team have any thoughts?

Matt.
lawsonium replied on at Permalink Reply
I have raised a fresh bug if you'd like to tick it up:
http://www.concrete5.org/developers/bugs/5-5-2-1/file_exists-open_b...

Matt.