-
Notifications
You must be signed in to change notification settings - Fork 59
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
Use HTTP POST vars rather than body to avoid PHP 5.6 warning #48
Comments
This kills asset admin for me. |
Are we actually using RAW_POST_DATA? |
I can't find it anywhere, but it only seems to happen on the graphql endpoints (for me anyway) |
@robbieaverill Can you please dig into this a bit? |
The SilverStripe GraphQL module uses |
I suspect that it's some weird PHP config, either on Robbie's dev environment, or on the production environment he's deploying to. |
At its core, this is a very bad deprecation process in PHP which will hit anybody using POST body: https://www.bram.us/2014/10/26/php-5-6-automatically-populating-http_raw_post_data-is-deprecated-and-will-be-removed-in-a-future-version/. To make matters worse, the generated warning is misleading: It also applies for using Background:
Recommendation:
|
Also created a ticket for adding a warning to the installer: silverstripe/silverstripe-installer#147 |
Heh, I should’ve probably left my ticket open #38 🙃. Recommendation looks good 👍 |
Pull request created silverstripe/silverstripe-framework#6500 |
Merged Chris' PR, and split out the GraphiQL one to a new issue on the separate repo: silverstripe/silverstripe-graphql-devtools#1 |
…se-me-baby Expose as vendor module
…18n-jsfiles FIX i18n js localisations
http://php.net/manual/en/reserved.variables.httprawpostdata.php
The text was updated successfully, but these errors were encountered: