We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here what I get with the current v3.0 RC2
curl -s -F "token=token_XXXXX" -F "upload=@FILE.jpg" https://xxx.xxx/xback/upload
"message":"OK.","version":"3.0.RC2","url":"\/xback\/929c5\/PikIfIPI07.jpg"}
As you see the url is trucated and no longer provides the full url
Also the new script does not use the full url for curl, hre is the portion from the generated script
RESPONSE="$(curl -s -F "token=XXXXX" -F "upload=@${1}" /xback/upload)";
The text was updated successfully, but these errors were encountered:
It's a known issue, there is still some problems with url generation due to upgrade to slim 4 (which the docs are pretty bad or not updated).
Sorry, something went wrong.
Sure but does that mean that it will be broken as is or a fix on the way given that you closed the bug?
Fixed in RC3.
I see thank you. I will test it
No branches or pull requests
Here what I get with the current v3.0 RC2
curl -s -F "token=token_XXXXX" -F "upload=@FILE.jpg" https://xxx.xxx/xback/upload
"message":"OK.","version":"3.0.RC2","url":"\/xback\/929c5\/PikIfIPI07.jpg"}
As you see the url is trucated and no longer provides the full url
Also the new script does not use the full url for curl, hre is the portion from the generated script
RESPONSE="$(curl -s -F "token=XXXXX" -F "upload=@${1}" /xback/upload)";
The text was updated successfully, but these errors were encountered: