Last modified: 2010-05-15 15:56:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T8298, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 6298 - Use exec() function when shell_exec() function is disabled
Use exec() function when shell_exec() function is disabled
Status: RESOLVED DUPLICATE of bug 5405
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
PC Windows XP
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-06-13 17:50 UTC by Ben
Modified: 2010-05-15 15:56 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Ben 2006-06-13 17:50:21 UTC
While uploading images I was getting the error "shell_exec() has been disabled for 
security reasons".  To fix this problem I have made the following core code changes to 
the "wfShellExec()" function in the includes/Globalfunctions.php file.  I am receiving 
this error because my ISP has disabled the shell_exec php function but this problem can 
also be reproduced if the server is in safe mode.

I would like to know if this basic functionality can be added to the core code.  Error 
code would be needed to be added to check if shell_exec() is disabled on the server or 
not, it should then use the exec() function instead of shell_exec().

What are your thoughts?  Can this be added?

"changes made to -- Globalfunctions.php --
1616	#return shell_exec( $cmd );
1617	 return exec( $cmd );"

You can view [
60m_receive_this_warning_during_installing_Wiki_.26_then_Thumb.60s_don.27t_created] as a 
Comment 1 Brion Vibber 2006-06-13 18:52:16 UTC

*** This bug has been marked as a duplicate of 5405 ***

Note You need to log in before you can comment on or make changes to this bug.