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
Provisioning API broken on PHP 5.4 #18428
Comments
Maybe this re-merge? |
@oparoz I tried some GET methods of the OCS API and they worked :( |
@Xenopathic @PVince81 |
Ah right. I tried with 5.6 ...sorry |
Argh, not the router thing again? |
@oparoz can you bisect this? THX |
This is highly likely to be that php://input bug... |
Sorry guys, #18691 didn't fix it.
Test is available here: |
@oparoz Ah, good thing you have more comprehensive tests. Thanks for sending me the link, I'll try and fix it |
Cool :) Try to reverse 127b6e2 and see how it goes. |
Hmm, that test works just fine on PHP 5.5.9 (Ubuntu 14.04 Docker). That was with current master. |
Travis Ubuntu 12.4 - PHP 5.4 One thing I've noticed is that once the test passes, after you've commented out the changes per example, it will pass again, after you re-implement them. Might be a cookie thing. I haven't looked at why yet. I was just surprised it did. |
@oparoz I'm unable to reproduce the error on Ubuntu 12.04 running PHP 5.4.44... even without the Request patch. Everything just works. |
I'm going to create a branch of Gallery with just that test. That way, if it still fails, you'll be able to tell Travis what to do in case you want to debug it on there. |
Here you go: Fails on master with any version of PHP, but still works on 8.1 |
A recent change seems to have broken the provisioning API and it doesn't behave properly any more on PHP 5.4 and 5.5 (probably old) on Travis when trying to create a user and verify its creation.
It works fine on PHP 5.6.
I don't have more details at this point, except that everything was fine last night.
This is what happens when I try to create a user
Checking for the presence of a user still works.
Could someone please confirm that behaviour.
The text was updated successfully, but these errors were encountered: