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
Installer check for Curl HTTP Loopback support #3062
Comments
I second that. My hosting did not really understand the issue when I tried to explain and wanted to start poking around in the software. So there definitely needs to be an official page to explain the issue that people can direct their hosting to. |
I posted a comment at #3062. Don't know if this makes sense, but would it not be better if supporting curl http loopback was not a "requirement"? My server supports loopback, but when trying to use CDN service like Cloud Flare I got the same error because of the way they handle DNS routing. |
The design really isn't bad, it's just unfortunate that servers are not willing to enable it. |
can changing the URL to localhost or 127.0.0.1? |
Ok i have a solution. Need to set a config value so a sub domain can be used. Maybe api.yourstore.com |
that did not work either. looks like i'm rewriting the order editor system |
Hi! I have the same bug!! any news on this? Thank you very much for contributions. |
How is this closed? Daniel have you approved this? So many changes here, far more than just curl issue fix. |
Daniel has rewritten it to use another method in the next version. Meanwhile I have a work around here: http://forum.opencart.com/viewtopic.php?f=34&t=146714#p567180 |
i closed the issue because some d*** head is trying to market their project via github. |
I do a lot of upgrades to 2.x and I think about 35% of people's servers DO NOT support curl http loopback which means the API calls throw an ajax error and people cannot do any of the API calls like edit orders or update order history. This is a pretty major showstopper and I think a check should be done during install to see that curl loopback is enabled.
The easiest way would be to simply attempt a curl call to the main install index and either check the response isn't empty, or use curl_getinfo() to check the http_code. This returns "0" on sites that do not have loopback enabled.
It should also be documented somewhere explaining the issue. Backupbuddy for Wordpress has some info for their own system here: http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#HTTP_Loopback_Connections_Disabled
The text was updated successfully, but these errors were encountered: