X3Photo Gallery Forums

margouillat wrote:How do I set the path for open_basedir in php.ini with X3

open_basedir = /

; open_basedir = /

fsfs wrote:Hmm I get that question too from my host company.

your host wrote:open_basedir specifies which directories PHP can write to.
Reply with complete path and code used so we can examine what you are trying to do.

The reason I know the above statement is not entirely accurate, is because X3 has already created files- and folders inside the app/_cache/ folder on your server, as you can witness yourself by navigating into /app/_cache/ by FTP. The problem is that for some reason, as diagnosed from the error, your open_basedir restriction is preventing X3 from deleting (with unlink) PHP files that itself has created earlier!

So basically you can reply to them the above, as I can't really make it any clearer: X3 needs to create cache files, and it does so inside /app/_cache/, and even with open_basedir this works fine. However, your open_basedir restriction is preventing X3 from deleting the same files that it has created itself.

Hello,

Yes, if you have permission to create the file, you also have permission to delete
file would both fall under the "write access". A simple script to test this
could look like this:

Code Select all

<? php
header ('Content-Type: text / plain \ r \ n ");
$ Droot = $ _SERVER ['DOCUMENT_ROOT'];

// List files into directory
print_r (scandir ($ Droot));

// Create a new file and directory listings
file_put_contents ("$ Droot / testfile", "Hello");
print_r (scandir ($ Droot));

// Delete the file and directory listings
unlink ("$ Droot / testfile");
print_r (scandir ($ Droot));

The above are test driven on an ordinary web hosting account with us
and work well, even together with open_basedir. However, we have unfortunately
no ability to troubleshoot and fix the customer's own code or code
that someone else wrote for our customers.

You server has open_basedir restriction enabled. This seems to be harmless, although it may prevent X3 from removing unused PHP template files within the app/_cache folder.

open_basedir issue Warning: unlink() [function.unlink]: open_basedir restriction in effect. File() is not within the allowed path(s):

fsfs wrote:The website works, I can add/remove pictures. But on /check I get the orange mark on open_basedir: You server has open_basedir restriction enabled. This seems to be harmless, although it may prevent X3 from removing unused PHP template files within the app/_cache folder.

fsfs wrote:What should I do to see if i'm affected by this open_basedir?

fsfs wrote:EDIT: I see that app/_cache is increasing size, few kbs when I delete/create a folder/pictures. The folder should be empty?

mjau-mjau wrote:Are you actually seeing the "Warning: unlink()" error in your website sometimes? Likely you are affected, but as mentioned above, there is no reason to believe it has any negative impact on your website.