Change Details

Hello! On some shared hostings **Pygments** can't be run because the shell execution was limited by "security" reasons and I can't enable it. However, I have built my own workaround which turns Pygments into CGI-BIN application I can run via HTTP. It's the patch to `SyntaxHighlight.php` which adds the flag `$wgPygmentsUseCgiProxy`. When you'll set it into `1`, the `wgPygmentizePath` will be interpreted as HTTP link and will be executed via cURL. {F27239660} It's the CGI script which will execute Pygments and will forward input data into it, and will return back the result: {F27239664}

Hello! On some shared hostings **Pygments** can't be run because the shell execution was limited by "security" reasons and I can't enable it. However, I have built my own workaround which turns Pygments into CGI-BIN application I can run via HTTP. It's the patch to `SyntaxHighlight.php` which adds the flag `$wgPygmentsUseCgiProxy`. When you'll set it into `1`, the `wgPygmentizePath` will be interpreted as HTTP link and will be executed via cURL. {F27239748} It's the CGI script which will execute Pygments and will forward input data into it, and will return back the result: {F27239664}

Hello! On some shared hostings **Pygments** can't be run because the shell execution was limited by "security" reasons and I can't enable it. However, I have built my own workaround which turns Pygments into CGI-BIN application I can run via HTTP. It's the patch to `SyntaxHighlight.php` which adds the flag `$wgPygmentsUseCgiProxy`. When you'll set it into `1`, the `wgPygmentizePath` will be interpreted as HTTP link and will be executed via cURL. {F27239660}748} It's the CGI script which will execute Pygments and will forward input data into it, and will return back the result: {F27239664}