exec() function cant be enabled. What do i do now?
|
paxter
Joined: 2007-04-02
Posts: 1 |
Posted: Mon, 2007-04-09 06:13
|
|
Hey i need someones help. I tried installing gallery(1) and this pop up during the settings page. Now i contacted the web company and their reply is as below. According to them the PHP exec() function is not allowed on shared hosting. So does this mean i cant use gallery at all? is there a way or another gallery type program that does not execute external scripts to work? "PHPs exec() function enabled - The exec() function is what Gallery uses to launch programs such as NetPBM, ImageMagick, and jhead. If exec() is disabled on your server then Gallery will not be able operate. Serious warning, no go ! Dear Customer, Please be informed that PHP exec() function is not allowed on shared hosting environment as it allows external script to be executed, this could invite security hazzard as well. Therefor this function is disabled. Best Regards, |
|
| Login or register to post comments |
Posts: 6
While it is true that without exec() you won't be able to use those toolkits, most webhosts usually configure PHP with GD which will work fine. Create a simple php script with just "phpinfo();" in it, execute it and see if your host has enabled GD with the "--with-gd" option for you. If so, configure Gallery to use that toolkit.
Without exec(), a lot of other cool tools will be unavailable as well, and that's a shame for most of us shared hosters.
Regards
Posts: 32246
The above warning is from Gallery 1. Gallery 2 works without PHP's exec() function, you'll just lose some features.
--------------
Documentation: Support / Troubleshooting | Installation, Upgrade, Configuration and Usage
Posts: 18
In some cases you can override the general settings:
1)Drop the attached php.txt into your gallery directory.
2)Rename it into php.ini
This will override the server settings and allow you to use exec()
It may also create a security hole... maybe. Or so your web host thinks.
It may not help - a paranoid sysadmin can disable this "local override" feature.
Hmm... this probably belongs in an FAQ somewhere...
A>