Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for cURL or allow_url_fopen? #93

Open
bcorke opened this issue Aug 1, 2023 · 1 comment
Open

Support for cURL or allow_url_fopen? #93

bcorke opened this issue Aug 1, 2023 · 1 comment
Labels

Comments

@bcorke
Copy link

bcorke commented Aug 1, 2023

Is there support for cURL & allow_url_fopen? (VS Code extension on Windows in wp-content mode.)

Steps to reproduce

  • Ensured php.ini in ~\.wp-now\php-exe\ has allow_url_fopen = On and extension=curl is uncommented (couldn't locate any other php.ini files)

Guzzle
$ composer require guzzlehttp/guzzle

GuzzleHttp requires cURL, the allow_url_fopen ini setting, or a custom HTTP handler.

Curl
<?php $ch = curl_init(); ?>

Call to undefined function curl_init()

ini_get
<?php if ( ! ini_get('allow_url_fopen') ) { ini_set('allow_url_fopen', true); } var_dump( ini_get('allow_url_fopen') ); ?>

false

<?php var_dump( ini_get('disable_functions') ); ?>

proc_open,popen,curl_exec,curl_multi_exec

Cheers
Ben

@danielbachhuber
Copy link
Member

I don't recall all of the specifics but here are some relevant issues:

I don't think node has the networking limitation, so it might just be that var_dump( ini_get('disable_functions') ); represents the web limitations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants