-
Notifications
You must be signed in to change notification settings - Fork 12
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
2.1.12 Breaking Changes : TypeError: file.getFileEncodeBase64String is not a function #29
Comments
Should be fixed in 2.1.13 |
still getting this error. |
@rikschennink Also getting this error:
|
Update: downgrade to 2.1.10 did indeed fix the issue |
In 2.1.13?
…On 12 Dec 2023 at 16:14 -0400, vaclavgreif ***@***.***>, wrote:
Update: downgrade to 2.1.10 did indeed fix the issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Did you also get this error in 2.1.13
(Sorry for previous message, replied to wrong one)
…On 12 Dec 2023 at 16:12 -0400, vaclavgreif ***@***.***>, wrote:
@rikschennink Also getting this error:
<FilePond
allowFileEncode={true}
instantUpload={false}
files={files}
onupdatefiles={files => {
setFiles(files);
}}
allowMultiple={true}
name="file"
onaddfile={(err, item) => {
console.log(item.getFileEncodeBase64String());
}}
labelIdle='Drag & Drop your files or <span class="filepond--label-action">Browse</span>'
onprocessfiles={(response) => {
}}
/>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@rikschennink Yes, I did get the error in 2.1.13 |
Thanks for confirming, I’ll run some additional tests.
…On 12 Dec 2023 at 16:43 -0400, vaclavgreif ***@***.***>, wrote:
@rikschennink Yes, I did get the error in 2.1.13
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Looks like 2.1.13 contained the erroneous 2.1.12 files 🫠 Just pushed 2.1.14 which contains the actual fixes for 2.1.13 |
Awesome, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
file.getFileEncodeBase64String() is not available in 2.1.12
From what I understand the function has been deleted because it should never have been there in the first place. The problem is that we use it.
More context : #3 (comment)
I think version 2.1.12 should therefore be a major release, as it introduces a breaking changes.
Solution : downgrade to 2.1.10
The text was updated successfully, but these errors were encountered: