You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Question] adding admin user relies on exec, shell_exec #1461
The bin/console bolt:add-user --admin command line relies on exec and shell_exec. My guess is a lot of (shared) hosting providers have these options disabled by default.
I don't know much about PHP settings and server security , so I do not know if it is save to enable these commands but does this mean that some (a lot?) of users can't use Bolt4?
I recently updated to PHP 7.3 on my server. I think both exec and shell_exec are disabled by default, so I changed this in the php.ini after I ran into this error.
When I tried adding a new admin user, by the time a password is being generated, the following error appears in an endless loop: [ERROR] Warning: exec() has been disabled for security reasons
It's not a problem for me personally but I think it's a good idea that this is mentioned in a "system requirements" paragraph in the docs. I know you are still working on the docs btw. ;)
Activity
bobdenotter commentedon Jun 10, 2020
What error are you getting exactly, if it's not there?
I'm not sure we can make that optional, as both Composer and Symfony itself rely on it as well.
peterboorsma commentedon Jun 10, 2020
I recently updated to PHP 7.3 on my server. I think both exec and shell_exec are disabled by default, so I changed this in the php.ini after I ran into this error.
When I tried adding a new admin user, by the time a password is being generated, the following error appears in an endless loop:
[ERROR] Warning: exec() has been disabled for security reasonsIt's not a problem for me personally but I think it's a good idea that this is mentioned in a "system requirements" paragraph in the docs. I know you are still working on the docs btw. ;)
bobdenotter commentedon Jun 10, 2020
As in: After you were getting that error, you enabled it, and then it was smooth sailing? :-)
peterboorsma commentedon Jun 10, 2020
Yes. Enabled them, restarted PHP. Problem solved.
bobdenotter commentedon Jun 11, 2020
Ok, will add to docs!
I-Valchev commentedon Sep 1, 2020
Let's bump this to 4.1 for now